Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2026-31527: driver core: platform: use generic driver_override infrastructure

HighCVSS 7.8 · v3.1—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 31/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.12% (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 2b38efc05bf7a8568ec74bfffea0f5cfa62bc01d, 492349e5e4a369a8b62781100a3ade470bf1ce6b, 7c02a9bd7d14a89065fcf672b86d8e1d1a41d3b1.

Low priority for now. Upgrade to Linux Linux 2b38efc05bf7a8568ec74bfffea0f5cfa62bc01d, 492349e5e4a369a8b62781100a3ade470bf1ce6b, 7c02a9bd7d14a89065fcf672b86d8e1d1a41d3b1 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: driver core: platform: use generic driver_override infrastructure When a driver is probed through __driver_attach(), the bus' match() callback is called without the device lock held, thus accessing the driver_override field without a lock, which can cause a UAF. Fix this by using the driver-core driver_override infrastructure taking care of proper locking internally. Note that calling match() from __driver_attach() without the device lock held is intentional. [1]

Published
Apr 22, 2026
Updated
Nov 11, 2026
EPSS
0.1% · 2th percentile

Report tools

JSON

Action score

31

Monitor

Low priority for now.

CVSS
31 / 40 · 7.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

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.

Follow CVE-2026-31527

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 every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE 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, at most 30 a day (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
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

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

    • 3.17affected
    • 3d713e0e382e6fcfb4bba1501645b66c129ad60b and later · before 492349e5e4a369a8b62781100a3ade470bf1ce6baffected · git
    • 3d713e0e382e6fcfb4bba1501645b66c129ad60b and later · before 9a6086d2a828dd2ff74cf9abcae456670febd71faffected · git
    • 3d713e0e382e6fcfb4bba1501645b66c129ad60b and later · before 7c02a9bd7d14a89065fcf672b86d8e1d1a41d3b1affected · git
    • 3d713e0e382e6fcfb4bba1501645b66c129ad60b and later · before edee7ee5a14c3b33f6d54641f5af5c5e9180992daffected · git
    • 3d713e0e382e6fcfb4bba1501645b66c129ad60b and later · before 2b38efc05bf7a8568ec74bfffea0f5cfa62bc01daffected · git
    • before 3.17not affected · semver
    • 6.6.142 and later · up to and including 6.6.*not affected · semver
    • 6.12.80 and later · up to and including 6.12.*not affected · semver
    • 6.18.21 and later · up to and including 6.18.*not affected · semver

Package-level exposure

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

EcosystemPackageAffected rangeFix
Debian:12linuxfrom 0—
Debian:13linuxbefore 6.12.85-16.12.85-1
Debian:14linuxbefore 6.19.11-16.19.11-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-31525Apr 22, 2026 · bpf: Fix undefined behavior in interpreter sdiv/smod for INT_MIN
    31Monitor
  • ← EarlierCVE-2026-31526Apr 22, 2026 · bpf: Fix exception exit lock checking for subprogs
    22Monitor
  • Later →CVE-2026-31528Apr 22, 2026 · perf: Make sure to use pmu_ctx->pmu for groups
    31Monitor

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 Linux2b38efc05bf7a8568ec74bfffea0f5cfa62bc01dVendor (CNA)
Linux Linux492349e5e4a369a8b62781100a3ade470bf1ce6bVendor (CNA)
Linux Linux7c02a9bd7d14a89065fcf672b86d8e1d1a41d3b1Vendor (CNA)
Linux Linux9a6086d2a828dd2ff74cf9abcae456670febd71fVendor (CNA)
Linux Linuxedee7ee5a14c3b33f6d54641f5af5c5e9180992dVendor (CNA)
debian:linux6.12.85-1 · Debian:13Package 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.

Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.

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
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

CWE-416 · Use After Free

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

nvd-primary

Root cause

After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

c
free(dev->buf);/* ... another thread is still running ... */process(dev->buf);

Fixed

c
lock(&dev->lock);free(dev->buf);dev->buf = NULL;unlock(&dev->lock);

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.

References

All records