Skip to content

SystemsHigh 8.8Patch available

CVE-2026-98171

Linux kernel SMB client use-after-free/bounds bug allows kernel memory corruption.

How scary is it?

updated 30 Oct 2026
  • Yes

    Works without logging in1

    No account needed, but a person has to act, such as opening a link or a file (CVSS PR:N, UI:R).

  • Yes

    Reachable over the network1

    Can be attacked remotely (CVSS AV:N).

  • None known

    Public exploit code is out

    None on record in Exploit-DB, Metasploit, Nuclei templates or PoC-in-GitHub.

  • None known

    Attacks seen in the wild

    None reported that we know of.

  • No

    On CISA's exploited list2

    Not in the catalog as of our last sync.

Scare-o-meter

Routine patch

Serious on paper, with no sign of attacks that we know of. Patch in your normal cycle.

  1. Low signal
  2. Routine patch
  3. Act this week
  4. Drop everything

Why: our alert rule found no exploitation evidence and no easy remote attack path in the data we hold. Read from the same rule that decides our alert emails.

Are you affected? only if all are true

  1. You run Linux in an affected version>= b24df3e30cbf48255db866720fb71f14bf9d2f39 and < 72eaef1f37a3b6bec11c342736834dc3707be3e4 / >= b24df3e30cbf48255db866720fb71f14bf9d2f39 and < 491e33144dee872cffda207f6fcb09260728f803 / >= b24df3e30cbf48255db866720fb71f14bf9d2f39 and < 8749946579708ea0d339034bb7f423a67dbe89cf (+4 more)

    >= b24df3e30cbf48255db866720fb71f14bf9d2f39 and < 72eaef1f37a3b6bec11c342736834dc3707be3e4 >= b24df3e30cbf48255db866720fb71f14bf9d2f39 and < 491e33144dee872cffda207f6fcb09260728f803 >= b24df3e30cbf48255db866720fb71f14bf9d2f39 and < 8749946579708ea0d339034bb7f423a67dbe89cf >= b24df3e30cbf48255db866720fb71f14bf9d2f39 and < 96c436e4b010711452b2872558938f4ef276492a >= b24df3e30cbf48255db866720fb71f14bf9d2f39 and < 858d5ac22cb889266993e7670f9f0c4f4aeedd78 >= b24df3e30cbf48255db866720fb71f14bf9d2f39 and < 05762c5bc1cfdcac36747994fde2c04387a457f1 4.19

    Vendor says fixed in: < 4.19, >= 6.1.189 and <= 6.1.*, >= 6.6.158 and <= 6.6.*, >= 6.12.112 and <= 6.12.*, >= 6.18.54 and <= 6.18.*, >= 7.2.8 and <= 7.2.*, >= 7.3-rc4 and <= *.

    As published in the CVE record. A version outside these ranges is not a statement that it is unaffected: vendors sometimes understate a range, and distribution builds with backported fixes keep the upstream number.

    See the affected products table · Source 1

  2. An attacker can reach it over the network

    CVSS attack vector: Network (AV:N). Reachable over the internet or any routable network.

    Source 1

  3. A person takes an action, such as opening a link or a file

    CVSS user interaction: required (UI:R). A victim must click, open or otherwise cooperate.

    Source 1

Read from the CVE record: affected versions and the CVSS vector. It narrows things down. It does not prove you are safe.

What to do

  1. Per the vendorUpgrade to a fixed release< 4.19 / >= 6.1.189 and <= 6.1.* / >= 6.6.158 and <= 6.6.* / >= 6.12.112 and <= 6.12.* (+3 more)

    Linux: < 4.19, >= 6.1.189 and <= 6.1.*, >= 6.6.158 and <= 6.6.*, >= 6.12.112 and <= 6.12.*, >= 6.18.54 and <= 6.18.*, >= 7.2.8 and <= 7.2.*, >= 7.3-rc4 and <= *

    Fixed releases as stated by the vendor in the CVE record.

    See the affected products table · Source 1

  2. Recommendation, AI-writtenUpdate to the patched kernel from your vendor or apply upstream fixes immediately.

    Written by a language model from the CVE record. It is not the vendor's wording: check it against the sources.

Steps marked AI were written by a language model, from the CVE record or from the linked news pages. They are not the vendor's wording: check them against the sources.

Major vulnerability. Linux kernel vulnerability affecting the SMB client can impact many distributions and devices; potential kernel memory corruption/RCE is widely disruptive and newsworthy.

CVSS
8.8Highscored by the publisher (CNA)
Exploited in the wild
Not knownnot in CISA KEV as of our last sync
EPSS
0.54%chance of exploitation in the next 30 daystop 54% of scored CVEsFIRST score of 21 Nov 2026
Fix
Fixed in < 4.19, >= 6.1.189 and <= 6.1.*, >= 6.6.158 and <= 6.6.*per the vendor; 4 more listed below
Published
6 Oct 2026analysed here 7 Oct 2026

Do first. Upgrade to a fixed release: < 4.19, >= 6.1.189 and <= 6.1.*, >= 6.6.158 and <= 6.6.*, >= 6.12.112 and <= 6.12.* (and 3 more below).

Summary

Impact

A malicious SMB server can cause use-after-free and bounds overflow in the kernel SMB client, enabling crashes or potential remote code execution in kernel context.

Triage

Exploitable
At runtime
Attack vector
network
Can a WAF block it?
No. See why

The summary, impact and action text on this page are written by our AI analysis pipeline, or taken from the NVD description when a CVE was imported from NVD. They are not the vendor's wording: check them against the sources. A longer AI executive summary and technical analysis are generated for signed-in accounts on the Max plan.

Affected products

ProductAffected versions
Linux>= b24df3e30cbf48255db866720fb71f14bf9d2f39 and < 72eaef1f37a3b6bec11c342736834dc3707be3e4>= b24df3e30cbf48255db866720fb71f14bf9d2f39 and < 491e33144dee872cffda207f6fcb09260728f803>= b24df3e30cbf48255db866720fb71f14bf9d2f39 and < 8749946579708ea0d339034bb7f423a67dbe89cf>= b24df3e30cbf48255db866720fb71f14bf9d2f39 and < 96c436e4b010711452b2872558938f4ef276492a>= b24df3e30cbf48255db866720fb71f14bf9d2f39 and < 858d5ac22cb889266993e7670f9f0c4f4aeedd78>= b24df3e30cbf48255db866720fb71f14bf9d2f39 and < 05762c5bc1cfdcac36747994fde2c04387a457f14.19Vendor says fixed in: < 4.19, >= 6.1.189 and <= 6.1.*, >= 6.6.158 and <= 6.6.*, >= 6.12.112 and <= 6.12.*, >= 6.18.54 and <= 6.18.*, >= 7.2.8 and <= 7.2.*, >= 7.3-rc4 and <= *

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

Products named in our analysis

  • Linux kernel (smb client / CIFS/SMB subsystem)
  • Enterprise Linux distributions (RHEL, Ubuntu, SUSE, Debian)
  • Embedded devices using affected kernels

Fix and mitigation

Action required

Immediate action required

WAF and other mitigations

Can a WAF block it? No. The vulnerability is in the Linux kernel SMB client, which uses the SMB protocol, not HTTP. Therefore, a web application firewall cannot filter or block the malicious SMB network traffic.

Also consider: patch

Based on an AI reading of the CVE description, and no vendor rule found yet. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.

Remediation steps (AI-written)

Step-by-step remediation is generated for accounts on the Max plan, for CVEs that match a technology in their stack. Add this technology to your stack to see the fix checklist.

Exploitation evidence

CISA KEV catalog
Not listed as of our last sync.
Public exploit code
None on record in Exploit-DB, Metasploit, Nuclei templates or PoC-in-GitHub.

Timeline

  1. 6 Oct 2026Published
  2. 7 Oct 2026Analysed by vulneraibility.com1 day later
  3. 30 Oct 2026CVE record last updated23 days later

Common questions

Is CVE-2026-98171 being exploited?

Not confirmed. CVE-2026-98171 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.54% probability of exploitation in the next 30 days.

How severe is CVE-2026-98171?

CVE-2026-98171 is rated High with a CVSS score of 8.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-98171?

Yes. A fix has been recorded for CVE-2026-98171. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-98171 affect?

CVE-2026-98171 affects Linux kernel (smb client / CIFS/SMB subsystem), Enterprise Linux distributions (RHEL, Ubuntu, SUSE, Debian), Embedded devices using affected kernels. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-98171?

Update to the patched kernel from your vendor or apply upstream fixes immediately.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

References

NVDCVE.orgCVE DetailsSource

8 references in the CVE record, grouped by the tags the record gives them.

Other links (8)

Show 2 more

Where the data on this page comes from

Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.

Similar CVEs

Get CVEs like this by email. Join the free digest: the CVEs we flag as major, all CVSS 8.0 or higher, in up to three emails a day (sent at 05:00, 11:00 and 15:00 UTC). Matching alerts to the products you run needs an account, and accounts are invite-only during the beta.