CVE-2026-80704

System crash via premature display logger access

Published Aug 28, 2026 · Updated Aug 28, 2026

NULL pointer dereference in Linux kernel 4.17 and affected Git revisions allows attackers to crash systems via unspecified vectors. AMD display clock-source construction calls get_ss_info_from_atombios before initializing calc_pll_cs->ctx, so logging dereferences its null logger pointer. Reachability requires an affected AMD display path to produce log output during clock-source setup; the bounded consequence is a kernel oops or system crash.

CVSS severityUnavailable
Unscored
EPSS probability0.16%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

NULL pointer dereference in Linux kernel 4.17 and affected Git revisions allows attackers to crash systems via unspecified vectors. AMD display clock-source construction calls get_ss_info_from_atombios before initializing calc_pll_cs->ctx, so logging dereferences its null logger pointer. Reachability requires an affected AMD display path to produce log output during clock-source setup; the bounded consequence is a kernel oops or system crash.

The record

CVE
CVE-2026-80704
Published
Aug 28, 2026
Updated
Aug 28, 2026
Vendor
The Linux Kernel Organization
Product
Linux
Classifications
T1499
Attack vector
Unavailable
Privileges
Unavailable

Timeline

How it unfolded

  1. Aug 28, 2026CVE publishedPublication date reported by the CVE source.
  2. Aug 28, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=1296423bf23c7a58133970e223b1f47ec6570308 <02647d98340738f918690ed227fdcf154db1b84a
  2. Affected versionversion=1296423bf23c7a58133970e223b1f47ec6570308 <114b42507b6a23d9d24e24e4ef165233332c64d4
  3. Affected versionversion=1296423bf23c7a58133970e223b1f47ec6570308 <a94e62b7c7018fcfe0251e53fa96af30f12d923a
  4. Affected versionversion=1296423bf23c7a58133970e223b1f47ec6570308 <f556bc844cc4423e5ad41ae41a4c24f1cf75b978
  5. Affected versionversion=4.17

What conditions does exploitation require?

Attack vectorUnavailable in this record.
Required privilegesUnavailable in this record.

What is affected?

The Linux Kernel Organization · Linuxversion=1296423bf23c7a58133970e223b1f47ec6570308 <02647d98340738f918690ed227fdcf154db1b84a; version=1296423bf23c7a58133970e223b1f47ec6570308 <114b42507b6a23d9d24e24e4ef165233332c64d4; version=1296423bf23c7a58133970e223b1f47ec6570308 <a94e62b7c7018fcfe0251e53fa96af30f12d923a; version=1296423bf23c7a58133970e223b1f47ec6570308 <f556bc844cc4423e5ad41ae41a4c24f1cf75b978; version=4.17

Published CVSS scores

No CVSS assessment is available in this record.

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
VectorUnavailable
PrivilegesUnavailable
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

T1499Endpoint Denial of Service

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo