Linux kernel vulnerability affecting the SMB client can impact many distributions and devices; potential kernel memory corruption/RCE is widely disruptive and newsworthy.
CVE-2026-98171
Linux kernel SMB client use-after-free/bounds bug allows kernel memory corruption.
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.
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.
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.
Immediate action required
- affected>= b24df3e30cbf48255db866720fb71f14bf9d2f39 and < 72eaef1f37a3b6bec11c342736834dc3707be3e4
- affected>= b24df3e30cbf48255db866720fb71f14bf9d2f39 and < 491e33144dee872cffda207f6fcb09260728f803
- affected>= b24df3e30cbf48255db866720fb71f14bf9d2f39 and < 8749946579708ea0d339034bb7f423a67dbe89cf
- affected>= b24df3e30cbf48255db866720fb71f14bf9d2f39 and < 96c436e4b010711452b2872558938f4ef276492a
- affected>= b24df3e30cbf48255db866720fb71f14bf9d2f39 and < 858d5ac22cb889266993e7670f9f0c4f4aeedd78
- affected>= b24df3e30cbf48255db866720fb71f14bf9d2f39 and < 05762c5bc1cfdcac36747994fde2c04387a457f1
- affected4.19
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.