NVD / CVE Program· CNA Linux

CVE-2024-26915: drm/amdgpu: Reset IH OVERFLOW_CLEAR bit

MediumCVSS 5.5 · v3.1—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 22/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.24% (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 2827633c9dab6304ec4cdbf369363219832e605d, 7330256268664ea0a7dd5b07a3fed363093477dd, 8983397951b4b0bd51bb4b4ba9749424e1ccbb70.

Low priority for now. Upgrade to Linux Linux 2827633c9dab6304ec4cdbf369363219832e605d, 7330256268664ea0a7dd5b07a3fed363093477dd, 8983397951b4b0bd51bb4b4ba9749424e1ccbb70 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: drm/amdgpu: Reset IH OVERFLOW_CLEAR bit Allows us to detect subsequent IH ring buffer overflows as well.

BDU:2025-02910

Published: Apr 17, 2024
Updated: Jun 17, 2026
EPSS: 0.2% · 16th percentile
CWE: CWE-120

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 22 / 40 · 5.5 / 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.

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

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.2affected
- d38ceaf99ed015f2a0b9af3499791bd3a3daae21 and later · before 9a9d00c23d170d4ef5a1b28e6b69f5c85dd12bc1affected · git
- d38ceaf99ed015f2a0b9af3499791bd3a3daae21 and later · before a28f4d1e0bed85943d309ac243fd1c200f8af9a2affected · git
- d38ceaf99ed015f2a0b9af3499791bd3a3daae21 and later · before 8983397951b4b0bd51bb4b4ba9749424e1ccbb70affected · git
- d38ceaf99ed015f2a0b9af3499791bd3a3daae21 and later · before 2827633c9dab6304ec4cdbf369363219832e605daffected · git
- d38ceaf99ed015f2a0b9af3499791bd3a3daae21 and later · before 7330256268664ea0a7dd5b07a3fed363093477ddaffected · git
- before 4.2not affected · semver
- 5.15.152 and later · up to and including 5.15.*not affected · semver
- 6.1.82 and later · up to and including 6.1.*not affected · semver
- 6.6.18 and later · up to and including 6.6.*not affected · semver

Affected versions · NVD (5)

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

linux linux kernelbefore 5.15.152
linux linux kernel5.16 and later · before 6.1.82
linux linux kernel6.2 and later · before 6.6.18
linux linux kernel6.7 and later · before 6.7.6
linux linux kernel6.8

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

Ecosystem	Package	Affected range	Fix
Debian:12	linux	before 6.1.82-1	6.1.82-1
Debian:13	linux	before 6.7.7-1	6.7.7-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-26913Apr 17, 2024 · drm/amd/display: Fix dcn35 8k30 Underflow/Corruption Issue
31Monitor
← EarlierCVE-2024-26914Apr 17, 2024 · drm/amd/display: fix incorrect mpc_combine array size
31Monitor
Later →CVE-2024-26916Apr 17, 2024 · Revert "drm/amd: flush any delayed gfxoff on suspend entry"
22Monitor

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	2827633c9dab6304ec4cdbf369363219832e605d	Vendor (CNA)
Linux Linux	7330256268664ea0a7dd5b07a3fed363093477dd	Vendor (CNA)
Linux Linux	8983397951b4b0bd51bb4b4ba9749424e1ccbb70	Vendor (CNA)
Linux Linux	9a9d00c23d170d4ef5a1b28e6b69f5c85dd12bc1	Vendor (CNA)
Linux Linux	a28f4d1e0bed85943d309ac243fd1c200f8af9a2	Vendor (CNA)
debian:linux	6.1.82-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.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

CVE-2023-44466201 days apartAn issue was discovered in net/ceph/messenger_v2.c in the Linux kernel before 6.4.5.
48Plan
CVE-2023-5273534 days apartbpf, sockmap: Don't let sock_map_{close,destroy,unhash} call itself
36Monitor
CVE-2024-2692711 days apartASoC: SOF: Add some bounds checking to firmware data
33Monitor
CVE-2022-4865711 days apartarm64: topology: fix possible overflow in amu_fie_setup()
31Monitor
CVE-2024-2679713 days apartdrm/amd/display: Prevent potential buffer overflow in map_hw_resources
31Monitor
CVE-2024-2704514 days apartdrm/amd/display: Fix a potential buffer overflow in 'dp_dsc_clock_en_read()'
31Monitor

Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · public bounty program.

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: none
Integrity: none
Availability: high · the service can be disrupted

Attack vector: Local
Attack complexity: Low
Privileges required: Low
User interaction: None
Scope: Unchanged
Confidentiality impact: None
Integrity impact: None
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:N/I:N/A:H

nvd-secondary

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 (1)

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

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

References

git.kernel.org/stable/c/2827633c9dab6304ec4cdbf369363219832e605d

Show all references (4 more)

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

All records