CVE-2024-46772: drm/amd/display: Check denominator crb_pipes before used
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.23% (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 04805efe8623f8721f3c01182ea73d68e88c62d8, b9264aa24f628eba5779d1c916441e0cedde9b3d, ea79068d4073bf303f8203f2625af7d9185a1bc6.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 04805efe8623f8721f3c01182ea73d68e88c62d8, b9264aa24f628eba5779d1c916441e0cedde9b3d, ea79068d4073bf303f8203f2625af7d9185a1bc6 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/amd/display: Check denominator crb_pipes before used [WHAT & HOW] A denominator cannot be 0, and is checked before used. This fixes 2 DIVIDE_BY_ZERO issues reported by Coverity.
- Published
- Sep 18, 2024
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 14th percentile
- CWE
- CWE-369
Report tools
Action score
22
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.
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 |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernelbefore 6.10.10
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.15affected
- 4562236b3bc0a28aeb6ee93b2d8a849a4c4e1c7c and later · before 04805efe8623f8721f3c01182ea73d68e88c62d8affected · git
- 4562236b3bc0a28aeb6ee93b2d8a849a4c4e1c7c and later · before b9264aa24f628eba5779d1c916441e0cedde9b3daffected · git
- 4562236b3bc0a28aeb6ee93b2d8a849a4c4e1c7c and later · before ede06d23392529b039cf7ac11b5875b047900f1caffected · git
- 4562236b3bc0a28aeb6ee93b2d8a849a4c4e1c7c and later · before ea79068d4073bf303f8203f2625af7d9185a1bc6affected · git
- before 4.15not affected · semver
- 6.1.133 and later · up to and including 6.1.*not affected · semver
- 6.6.86 and later · up to and including 6.6.*not affected · semver
- 6.10.10 and later · up to and including 6.10.*not affected · semver
- 6.11 and laternot affected · original_commit_for_fix
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.137-1~deb11u1 | 6.1.137-1~deb11u1 |
| Debian:12 | linux | before 6.1.133-1 | 6.1.133-1 |
| Debian:13 | linux | before 6.10.11-1 | 6.10.11-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-2024-46770Sep 18, 2024 · ice: Add netif_device_attach/detach into PF reset flow22Monitor
- ← EarlierCVE-2024-46771Sep 18, 2024 · can: bcm: Remove proc entry when dev is unregistered.22Monitor
- Later →CVE-2024-46773Sep 18, 2024 · drm/amd/display: Check denominator pbn_div before used22Monitor
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 | 04805efe8623f8721f3c01182ea73d68e88c62d8 | Vendor (CNA) |
| Linux Linux | b9264aa24f628eba5779d1c916441e0cedde9b3d | Vendor (CNA) |
| Linux Linux | ea79068d4073bf303f8203f2625af7d9185a1bc6 | Vendor (CNA) |
| Linux Linux | ede06d23392529b039cf7ac11b5875b047900f1c | Vendor (CNA) |
| debian:linux | 6.1.133-1 · Debian:12 | Package registry (OSV) |
| debian:linux-6.1 | 6.1.137-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 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.
- CVE-2024-26945140 days apartcrypto: iaa - Fix nr_cpus < nr_iaa case33Monitor
- CVE-2024-467320 days apartdrm/amd/display: Assign linear_pitch_alignment even for VM22Monitor
- CVE-2024-467730 days apartdrm/amd/display: Check denominator pbn_div before used22Monitor
- CVE-2024-466765 days apartnfc: pn533: Add poll mod list filling check22Monitor
- CVE-2024-468069 days apartdrm/amdgpu: Fix the warning division or modulo by zero22Monitor
- CVE-2024-4766421 days apartspi: hisi-kunpeng: Add verification for the max_frequency provided by the firmware22Monitor
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-1498 · Sep 19, 2024(Linux Kernel Güvenlik Bildirimi)
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-369 · Divide By ZeroCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
nvd-primary
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 (4 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.