NVD / CVE Program· CNA Linux

CVE-2024-26952: ksmbd: fix potencial out-of-bounds when buffer offset is invalid

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.72% (FIRST EPSS); higher than 54.3% of all records.
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 0c5541b4c980626fa3cab16ba1a451757778bbb5, 2dcda336b6e80b72d58d30d40f2fad9724e5fe63, 39bdc4197acf2ed13269167ccf093ee28cfa2a4e; azl3 kernel 6.6.35.1-4 on Azure Linux 3.0 6.6.35.1-4; azl3 kernel 6.6.85.1-4 on Azure Linux 3.0 6.6.35.1-4.

Low priority for now. Upgrade to Linux Linux 0c5541b4c980626fa3cab16ba1a451757778bbb5, 2dcda336b6e80b72d58d30d40f2fad9724e5fe63, 39bdc4197acf2ed13269167ccf093ee28cfa2a4e; azl3 kernel 6.6.35.1-4 on Azure Linux 3.0 6.6.35.1-4; azl3 kernel 6.6.85.1-4 on Azure Linux 3.0 6.6.35.1-4 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: ksmbd: fix potencial out-of-bounds when buffer offset is invalid I found potencial out-of-bounds when buffer offset fields of a few requests is invalid. This patch set the minimum value of buffer offset field to ->Buffer offset to validate buffer length.

HighCVSS 7.8 · v3.1—No exploit Fix available

Memory safety

Published: May 1, 2024
Updated: Aug 5, 2026
EPSS: 0.7% · 54th percentile
CWE: CWE-120

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 31 / 40 · 7.8 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.7%

CISA SSVC decision

Exploitation: none
Automatable: no
Technical impact: total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD: 7.8
CNA · Linux: 8.3; 0.5 point gap

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:H

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

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

Is your version affected? Check it

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 help

Affected 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

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

linux linux kernel5.15 and later · before 5.15.181
linux linux kernel5.16 and later · before 6.1.119
linux linux kernel6.2 and later · before 6.6.32
linux linux kernel6.7 and later · before 6.7.12
linux linux kernel6.8 and later · before 6.8.3

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
- 5.15affected
- 0626e6641f6b467447c81dd7678a69c66f7746cf and later · before 480469f145e5abf83361e608734e421b7d99693daffected · git
- 0626e6641f6b467447c81dd7678a69c66f7746cf and later · before ad6480c9a5d884e2704adc51d69895d93339176caffected · git
- 0626e6641f6b467447c81dd7678a69c66f7746cf and later · before 39bdc4197acf2ed13269167ccf093ee28cfa2a4eaffected · git
- 0626e6641f6b467447c81dd7678a69c66f7746cf and later · before 2dcda336b6e80b72d58d30d40f2fad9724e5fe63affected · git
- 0626e6641f6b467447c81dd7678a69c66f7746cf and later · before 0c5541b4c980626fa3cab16ba1a451757778bbb5affected · git
- 0626e6641f6b467447c81dd7678a69c66f7746cf and later · before c6cd2e8d2d9aa7ee35b1fa6a668e32a22a9753daaffected · git
- before 5.15not affected · semver
- 5.15.181 and later · up to and including 5.15.*not affected · semver
- 6.1.119 and later · up to and including 6.1.*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-6.1	before 6.1.119-1~deb11u1	6.1.119-1~deb11u1
Debian:12	linux	before 6.1.119-1	6.1.119-1
Debian:13	linux	before 6.7.12-1	6.7.12-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
90Now
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 KEV
89Now
CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
85Now

Published before and after this one in the same product

← EarlierCVE-2024-26946May 1, 2024 · kprobes/x86: Use copy_from_kernel_nofault() to read from unsafe address
22Monitor
← EarlierCVE-2024-26949May 1, 2024 · drm/amdgpu/pm: Fix NULL pointer dereference when get power limit
22Monitor
Later →CVE-2024-26954May 1, 2024 · ksmbd: fix slab-out-of-bounds in smb_strndup_from_utf16()
28Monitor

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	0c5541b4c980626fa3cab16ba1a451757778bbb5	Vendor (CNA)
Linux Linux	2dcda336b6e80b72d58d30d40f2fad9724e5fe63	Vendor (CNA)
Linux Linux	39bdc4197acf2ed13269167ccf093ee28cfa2a4e	Vendor (CNA)
Linux Linux	480469f145e5abf83361e608734e421b7d99693d	Vendor (CNA)
Linux Linux	ad6480c9a5d884e2704adc51d69895d93339176c	Vendor (CNA)
Linux Linux	c6cd2e8d2d9aa7ee35b1fa6a668e32a22a9753da	Vendor (CNA)
azl3 kernel 6.6.35.1-4 on Azure Linux 3.0	6.6.35.1-4 · CBL-Mariner Releases	Microsoft (MSRC)
azl3 kernel 6.6.85.1-4 on Azure Linux 3.0	6.6.35.1-4 · CBL-Mariner Releases	Microsoft (MSRC)
cbl2 kernel 5.15.158.2-1 on CBL Mariner 2.0	5.15.158.2-1 · CBL-Mariner Releases	Microsoft (MSRC)
cbl2 kernel 5.15.180.1-1 on CBL Mariner 2.0	5.15.158.2-1 · CBL-Mariner Releases	Microsoft (MSRC)
debian:linux	6.1.119-1 · Debian:12	Package registry (OSV)
debian:linux-6.1	6.1.119-1~deb11u1 · Debian:11	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 researchers

Finders, 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.

CVE-2023-44466215 days apartAn issue was discovered in net/ceph/messenger_v2.c in the Linux kernel before 6.4.5.
48Plan
CVE-2023-5273520 days apartbpf, sockmap: Don't let sock_map_{close,destroy,unhash} call itself
36Monitor
CVE-2024-269273 days apartASoC: SOF: Add some bounds checking to firmware data
33Monitor
CVE-2024-269360 days apartksmbd: validate request buffer size in smb2_allocate_rsp_buf()
31Monitor
CVE-2024-270450 days apartdrm/amd/display: Fix a potential buffer overflow in 'dp_dsc_clock_en_read()'
31Monitor
CVE-2022-486573 days apartarm64: topology: fix possible overflow in amu_fie_setup()
31Monitor

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).

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-120 · Buffer Copy without Checking Size of Input ('Classic Buffer Overflow')

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

nvd-primary

Root cause

When data is copied, the source length is not compared with the size of the destination buffer. Excess data overwrites adjacent memory.

The bug in code

The whole CWE-120 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1char buf[256];
2memcpy(buf, pkt->data, pkt->len);

Fixed

1char buf[256];
2if (pkt->len > sizeof(buf)) {
3  return -EINVAL;
4}
5memcpy(buf, pkt->data, pkt->len);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Attack patterns (CAPEC)

ATT&CK techniques

—

Change log

Fix✗ → ✓Sep 28, 2026, 10:11 PM UTC

For records you follow, these changes also arrive as notifications. →

References

git.kernel.org/stable/c/0c5541b4c980626fa3cab16ba1a451757778bbb5

Show all references (6 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records