Skip to content
Systems

CVE-2026-80752

8.4
High
EPSS 0.18%Patch availableSep 4, 2026

Linux kernel psxpad-spi NULL dereference can crash kernel (DoS).

common questions

Is CVE-2026-80752 being exploited?

Not confirmed. CVE-2026-80752 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.18% probability of exploitation in the next 30 days.

How severe is CVE-2026-80752?

CVE-2026-80752 is rated High with a CVSS score of 8.4. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-80752?

Yes. A fix has been recorded for CVE-2026-80752. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-80752 affect?

CVE-2026-80752 affects Linux kernel (psxpad-spi driver), Linux distributions with affected kernel versions. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-80752?

Update Linux kernel to the stable fixed commit or apply vendor patch immediately.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Linux kernel (psxpad-spi driver)Linux distributions with affected kernel versions
impact

NULL pointer deref in psxpad_spi_suspend can trigger kernel panic/reboot, enabling local or device-triggered denial-of-service.

action required

Patch when possible

affected versions
Linux Linux
  • affected>= 8be193c7b1f44d3f4dcb27107df0831709c2deb1 and < e980066e434a9c74ff1665ed9140427e95b0ee7c
  • affected>= 8be193c7b1f44d3f4dcb27107df0831709c2deb1 and < 1bba6bd6861b1e0c8ecf20cd1892f0d3877c02a2
  • affected>= 8be193c7b1f44d3f4dcb27107df0831709c2deb1 and < 86531cdfb3a03213e2569deed5195412a4e3f7ee
  • affected>= 8be193c7b1f44d3f4dcb27107df0831709c2deb1 and < da6b8b05db0cf43e0cc198431fa8ee9739b3b817
  • affected>= 8be193c7b1f44d3f4dcb27107df0831709c2deb1 and < 1edcb7ffee7ac4dc35cbe5bbd0e27bac3614ebe4
  • affected>= 8be193c7b1f44d3f4dcb27107df0831709c2deb1 and < 8d622c58205adbc8af19864e277386528b671345
  • affected>= 8be193c7b1f44d3f4dcb27107df0831709c2deb1 and < 62e25677d1440085381b047ec4984be9b6793759
  • affected>= 8be193c7b1f44d3f4dcb27107df0831709c2deb1 and < 732f38c36059e68ba3b4b89c56911d777fd3185c
  • affected4.12
vendor says fixed in< 4.12, >= 5.10.266 and <= 5.10.*, >= 5.15.217 and <= 5.15.*, >= 6.1.184 and <= 6.1.*, >= 6.6.153 and <= 6.6.*, >= 6.12.105 and <= 6.12.*, >= 6.18.46 and <= 6.18.*, >= 7.1.10 and <= 7.1.*, >= 7.2 and <= *

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free