CVE-2024-26928: smb: client: fix potential UAF in cifs_debug_files_proc_show()
Noroxi assessment
Priority: Monitor (action score 31/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.27% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 229042314602db62559ecacba127067c22ee7b88, 3402faf78b2516b0af1259baff50cc8453ef0bd1, 8f8718afd446cd4ea3b62bacc3eec09f8aae85ee.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 229042314602db62559ecacba127067c22ee7b88, 3402faf78b2516b0af1259baff50cc8453ef0bd1, 8f8718afd446cd4ea3b62bacc3eec09f8aae85ee or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
In the Linux kernel, the following vulnerability has been resolved: smb: client: fix potential UAF in cifs_debug_files_proc_show() Skip sessions that are being teared down (status == SES_EXITING) to avoid UAF.
- Published
- Apr 28, 2024
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 20th percentile
- CWE
- CWE-416
Report tools
Action score
31
Monitor
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
| debian | debian linux | cpe:2.3:o:debian:debian_linux |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- debian debian linux11.0
- linux linux kernel4.20 and later · before 5.10.237
- linux linux kernel5.11 and later · before 5.15.180
- linux linux kernel5.16 and later · before 6.1.85
- linux linux kernel6.2 and later · before 6.6.26
- linux linux kernel6.7 and later · before 6.8.5
- linux linux kernel6.9
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 4.20affected
- dfe33f9abc08997e56f9bdf14fe9ac7ac0e14075 and later · before 8f8718afd446cd4ea3b62bacc3eec09f8aae85eeaffected · git
- dfe33f9abc08997e56f9bdf14fe9ac7ac0e14075 and later · before a140224bcf87eb98a87b67ff4c6826c57e47b704affected · git
- dfe33f9abc08997e56f9bdf14fe9ac7ac0e14075 and later · before 229042314602db62559ecacba127067c22ee7b88affected · git
- dfe33f9abc08997e56f9bdf14fe9ac7ac0e14075 and later · before a65f2b56334ba4dc30bd5ee9ce5b2691b973344daffected · git
- dfe33f9abc08997e56f9bdf14fe9ac7ac0e14075 and later · before 3402faf78b2516b0af1259baff50cc8453ef0bd1affected · git
- dfe33f9abc08997e56f9bdf14fe9ac7ac0e14075 and later · before ca545b7f0823f19db0f1148d59bc5e1a56634502affected · git
- before 4.20not affected · semver
- 5.10.237 and later · up to and including 5.10.*not affected · semver
- 5.15.180 and later · up to and including 5.15.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:11 | linux | before 5.10.237-1 | 5.10.237-1 |
| Debian:12 | linux | before 6.1.85-1 | 6.1.85-1 |
| Debian:13 | linux | before 6.8.9-1 | 6.8.9-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2023-52646Apr 26, 2024 · aio: fix mremap after fork null-deref22Monitor
- ← EarlierCVE-2024-26927Apr 28, 2024 · ASoC: SOF: Add some bounds checking to firmware data33Monitor
- Later →CVE-2022-48631Apr 28, 2024 · ext4: fix bug in extents parsing when eh_entries == 0 and eh_depth > 022Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 229042314602db62559ecacba127067c22ee7b88 | Vendor (CNA) |
| Linux Linux | 3402faf78b2516b0af1259baff50cc8453ef0bd1 | Vendor (CNA) |
| Linux Linux | 8f8718afd446cd4ea3b62bacc3eec09f8aae85ee | Vendor (CNA) |
| Linux Linux | a140224bcf87eb98a87b67ff4c6826c57e47b704 | Vendor (CNA) |
| Linux Linux | a65f2b56334ba4dc30bd5ee9ce5b2691b973344d | Vendor (CNA) |
| Linux Linux | ca545b7f0823f19db0f1148d59bc5e1a56634502 | Vendor (CNA) |
| debian:linux | 6.1.85-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-24-0360 · Apr 29, 2024(Linux Kernel Güncellemesi)
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-416 · Use After FreeCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Root cause
After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.
The bug in code
The whole CWE-416 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
free(dev->buf);
/* ... another thread is still running ... */
process(dev->buf);Fixed
lock(&dev->lock);
free(dev->buf);
dev->buf = NULL;
unlock(&dev->lock);Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (6 more)Show less
- git.kernel.org/stable/c/3402faf78b2516b0af1259baff50cc8453ef0bd1
- git.kernel.org/stable/c/8f8718afd446cd4ea3b62bacc3eec09f8aae85ee
- git.kernel.org/stable/c/a140224bcf87eb98a87b67ff4c6826c57e47b704
- git.kernel.org/stable/c/a65f2b56334ba4dc30bd5ee9ce5b2691b973344d
- git.kernel.org/stable/c/ca545b7f0823f19db0f1148d59bc5e1a56634502
- lists.debian.org/debian-lts-announce/2025/05/msg00030.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.