Answer in brief
CVE-2024-35951 records a High severity (CVSS 7.8) vulnerability in drm/panfrost: Fix the error path in panfrost_mmu_map_fault_addr(). The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:6.9:rc1:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:6.9:rc2:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:6.9:rc3:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=187d2929206e6b098312c174ea873e4cedf5420d <31806711e8a4b75e09b1c43652f2a6420e6e1002 || >=187d2929206e6b098312c174ea873e4cedf5420d <e18070c622c63f0cab170348e320454728c277aa || >=187d2929206e6b098312c174ea873e4cedf5420d <1fc9af813b25e146d3607669247d0f970f5a87c3 | 31806711e8a4b75e09b1c43652f2a6420e6e1002, e18070c622c63f0cab170348e320454728c277aa, 1fc9af813b25e146d3607669247d0f970f5a87c3 |
| Linux/Linuxgeneric | 5.4 | Not reported |
| Linux/Linuxgeneric | >=187d2929206e6b098312c174ea873e4cedf5420d <f959d043b745b352c7d1c9b832a57ffcf05bc935 || >=187d2929206e6b098312c174ea873e4cedf5420d <31806711e8a4b75e09b1c43652f2a6420e6e1002 || >=187d2929206e6b098312c174ea873e4cedf5420d <e18070c622c63f0cab170348e320454728c277aa || >=187d2929206e6b098312c174ea873e4cedf5420d <1fc9af813b25e146d3607669247d0f970f5a87c3 | f959d043b745b352c7d1c9b832a57ffcf05bc935, 31806711e8a4b75e09b1c43652f2a6420e6e1002, e18070c622c63f0cab170348e320454728c277aa, 1fc9af813b25e146d3607669247d0f970f5a87c3 |
Published upstream
May 20, 2024
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 30, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
In the Linux kernel, the following vulnerability has been resolved: drm/panfrost: Fix the error path in panfrost_mmu_map_fault_addr() Subject: [PATCH] drm/panfrost: Fix the error path in panfrost_mmu_map_fault_addr() If some the pages or sgt allocation failed, we shouldn't release the pages ref we got earlier, otherwise we will end up with unbalanced get/put_pages() calls. We should instead leave everything in place and let the BO release function deal with extra cleanup when the object is destroyed, or let the fault handler try again next time it's called.
Quoted source text, attributed separately from HOL analysis.