Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2026-53325: agp/amd64: Fix broken error propagation in agp_amd64_probe()

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.13% (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 0aa9b27c454c53074cde592eaceb442d30341585, 1d7d45050e14083c1de1460c93f4063c1f0bca7b, 3e844a63668d1c3d10a9d347d7ebf161b2f91c84; azl3 kernel 6.6.143.1-1 on Azure Linux 3.0 6.6.144.1-1.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 0aa9b27c454c53074cde592eaceb442d30341585, 1d7d45050e14083c1de1460c93f4063c1f0bca7b, 3e844a63668d1c3d10a9d347d7ebf161b2f91c84; azl3 kernel 6.6.143.1-1 on Azure Linux 3.0 6.6.144.1-1 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: agp/amd64: Fix broken error propagation in agp_amd64_probe() A NULL pointer dereference was observed in the AMD64 AGP driver when running in a virtualized environment (e.g. qemu/kvm) without a physical AMD northbridge. The crash occurs in amd64_fetch_size() when attempting to dereference the pointer returned by node_to_amd_nb(0). The root cause of this crash is broken error propagation in agp_amd64_probe(): When no AMD northbridges are found, cache_nbs() correctly returns -ENODEV. However, the probe function erroneously checks the return value against exactly -1, rather than < 0. As a result, the hardware absence error is masked, allowing the driver to improperly proceed with initialization. It eventually calls agp_add_bridge(), which invokes amd64_fetch_size(). Since the hardware does not exist, node_to_amd_nb(0) returns NULL, leading to a General Protection Fault (GPF) when accessing its ->misc member. Fix the issue by correcting the error check in agp_amd64_probe() to abort properly when cache_nbs() returns any negative error code. This prevents the driver from erroneously proceeding without hardware, thereby avoiding the subsequent NULL pointer dereference at its source.

MediumCVSS 5.5 · v3.1—No exploit Fix available
Published
Jun 29, 2026
Updated
Oct 15, 2026
EPSS
0.1% · 2th percentile

Report tools

JSON

Action score

22

Monitor

Low priority for now.

CVSS
22 / 40 · 5.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

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.

Follow CVE-2026-53325

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

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.

VendorProduct
linuxlinux kernel

Affected versions

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

  • linux linux kernel2.6.18 and later · before 5.10.260
  • linux linux kernel5.11 and later · before 5.15.211
  • linux linux kernel5.16 and later · before 6.1.177
  • linux linux kernel6.2 and later · before 6.6.144
  • linux linux kernel6.7 and later · before 6.12.95
  • linux linux kernel6.13 and later · before 6.18.37
  • linux linux kernel6.19 and later · before 7.0.14
  • linux linux kernel7.1 and later · before 7.1.2

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

    • 2.6.18affected
    • a32073bffc656ca4bde6002b6cf7c1a8e0e22712 and later · before ce800993af477fc24187349c6a20d3073140b759affected · git
    • a32073bffc656ca4bde6002b6cf7c1a8e0e22712 and later · before 1d7d45050e14083c1de1460c93f4063c1f0bca7baffected · git
    • a32073bffc656ca4bde6002b6cf7c1a8e0e22712 and later · before 3e844a63668d1c3d10a9d347d7ebf161b2f91c84affected · git
    • a32073bffc656ca4bde6002b6cf7c1a8e0e22712 and later · before eb045714bc6a2bbb0befb7a31b996a196e188869affected · git
    • a32073bffc656ca4bde6002b6cf7c1a8e0e22712 and later · before 564b3b3f6565313eb6fa5355ffd037d6fb27897faffected · git
    • a32073bffc656ca4bde6002b6cf7c1a8e0e22712 and later · before 53483a9f4ee9eeb18aa866ec16cce79e136987e1affected · git
    • a32073bffc656ca4bde6002b6cf7c1a8e0e22712 and later · before 0aa9b27c454c53074cde592eaceb442d30341585affected · git
    • a32073bffc656ca4bde6002b6cf7c1a8e0e22712 and later · before cefe535a60a2e00e09f4b2689b0c8ffc6912459aaffected · git
    • a32073bffc656ca4bde6002b6cf7c1a8e0e22712 and later · before b08472db93b1ccff84a7adec5779d47f0e9d3a30affected · git

Package-level exposure

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

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.177-16.1.177-1
Debian:13linuxbefore 6.12.95-16.12.95-1
Debian:14linuxbefore 7.0.14-17.0.14-1
openSUSE:Tumbleweedkernel-sourcebefore 7.1.2-1.17.1.2-1.1

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-2026-53317Jun 26, 2026 · wifi: mt76: mt7921: Place upper limit on station AID
    22Monitor
  • ← EarlierCVE-2026-53321Jun 26, 2026 · io_uring/napi: cap busy_poll_to 10 msec
    22Monitor
  • Later →CVE-2026-53326Jul 1, 2026 · debugobjects: Don't call fill_pool() in early boot hardirq context
    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 / packageFixed versionSource
Linux Linux0aa9b27c454c53074cde592eaceb442d30341585Vendor (CNA)
Linux Linux1d7d45050e14083c1de1460c93f4063c1f0bca7bVendor (CNA)
Linux Linux3e844a63668d1c3d10a9d347d7ebf161b2f91c84Vendor (CNA)
Linux Linux53483a9f4ee9eeb18aa866ec16cce79e136987e1Vendor (CNA)
Linux Linux564b3b3f6565313eb6fa5355ffd037d6fb27897fVendor (CNA)
Linux Linuxb08472db93b1ccff84a7adec5779d47f0e9d3a30Vendor (CNA)
Linux Linuxce800993af477fc24187349c6a20d3073140b759Vendor (CNA)
Linux Linuxcefe535a60a2e00e09f4b2689b0c8ffc6912459aVendor (CNA)
Linux Linuxeb045714bc6a2bbb0befb7a31b996a196e188869Vendor (CNA)
azl3 kernel 6.6.143.1-1 on Azure Linux 3.06.6.144.1-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
debian:linux6.1.177-1 · Debian:12Package registry (OSV)
opensuse:kernel-source7.1.2-1.1 · openSUSE:TumbleweedPackage 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.

Finders, 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.

No nightly-computed relations.

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.

All national notices →

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

CVSS 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

  1. Fix✗ → ✓

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

References

All records