Skip to main content
← Vulnerabilities

ksmbd: drain session procfs readers before dropping table references

Exploited
No known exploitation
Fix
Fixed in 7.3
Who is exposed
Not reported

Do first: Upgrade to a fixed version: 7.3.

Published
Last modified
20/100 · provisional
None on Exploit-DB, Metasploit or GitHub

Summary

The Linux kernel's ksmbd SMB server has a flaw in session cleanup, where a procfs reader can access a session's file table during or after its destruction. The fix changes the order of teardown so readers finish before references are dropped.

Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.

Read the original description

In the Linux kernel, the following vulnerability has been resolved:

ksmbd: drain session procfs readers before dropping table references

Session registration failure and connection cleanup can drop the table reference while the per-session procfs entry is still accessible. If a reader holds the last remaining reference, its final put calls proc_remove() from its own callback and waits for that callback to finish.

Remove the procfs entry before dropping the table reference in the registration failure path. Queue sessions removed during connection cleanup and drain their procfs readers after releasing both session locks, then return their table references. Keep the global hash node unhashed while a session is queued so a concurrent unregister cannot drop the reference again.

Previous-session replacement also destroys the file table before the session is finally freed. Detach the idr under the lock used by procfs file counters, and report zero files after it has been detached. This prevents a reader from accessing the idr during or after its destruction.

cve.now Index

20Pcve.now Index 20 of 100 · methodology v3 · provisional
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure?/25Unknown. No advisory context yet
  • Reach20/20Affects Linux kernel (software on nearly every server, desktop or phone)
  • Severity?/10Unknown. No CVSS score or vendor rating
  • No patch0/5No signal

What would change the score

  • Would score about 75 if added to CISA KEV
  • Would score about 70 if CISA's SSVC rates exploitation active
  • Would score about 42 if advisories confirm default setups are exposed

What to do

  • Upgrade to a fixed version: 7.3.

Timeline

  1. CVE published
  2. First seen by cve.now

Affected versions

  • Linux Linux

    From 7.2.8 · fixed in 7.3

  • Linux Linux

    7.3

Evidence 2

  1. Link
  2. Link

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-99280

Is CVE-2026-99280 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

Which versions are affected by CVE-2026-99280?

Linux: from 7.2.8 before 7.3. Linux: version 7.3.Source: cve.now feed data

How do I fix CVE-2026-99280?

Upgrade to a fixed version: 7.3.Source: cve.now feed data