Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2025-37886: pds_core: make wait_context part of q_info

MediumCVSS 5.5 · v3.1—No exploit Fix available

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.30% (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 1d7c4b2b0bbfb09b55b2dc0e2355d7936bf89381, 3f77c3dfffc7063428b100c4945ca2a7a8680380, 520f012fe75fb8efc9f16a57ef929a7a2115d892; azl3 kernel 6.6.85.1-4 on Azure Linux 3.0 6.6.92.2-1; azl3 kernel 6.6.92.2-1 on Azure Linux 3.0 6.6.92.2-1.
  • Severity is disputed: the assigning authority (CNA) scores it 7.8, NVD 5.5.

Low priority for now. Upgrade to Linux Linux 1d7c4b2b0bbfb09b55b2dc0e2355d7936bf89381, 3f77c3dfffc7063428b100c4945ca2a7a8680380, 520f012fe75fb8efc9f16a57ef929a7a2115d892; azl3 kernel 6.6.85.1-4 on Azure Linux 3.0 6.6.92.2-1; azl3 kernel 6.6.92.2-1 on Azure Linux 3.0 6.6.92.2-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: pds_core: make wait_context part of q_info Make the wait_context a full part of the q_info struct rather than a stack variable that goes away after pdsc_adminq_post() is done so that the context is still available after the wait loop has given up. There was a case where a slow development firmware caused the adminq request to time out, but then later the FW finally finished the request and sent the interrupt. The handler tried to complete_all() the completion context that had been created on the stack in pdsc_adminq_post() but no longer existed. This caused bad pointer usage, kernel crashes, and much wailing and gnashing of teeth.

Published
May 9, 2025
Updated
Aug 5, 2026
EPSS
0.3% · 23th 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.3%

CNA vs NVD score

NVD
5.5
CNA · Linux
7.8
2.3 point gap

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

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

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-2025-37886

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

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records
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

    • 6.4affected
    • 01ba61b55b2041a39c54aefb3153c770dd59a0ef and later · before 1d7c4b2b0bbfb09b55b2dc0e2355d7936bf89381affected · git
    • 01ba61b55b2041a39c54aefb3153c770dd59a0ef and later · before 66d7702b42ffdf0dce4808626088268a4e905ca6affected · git
    • 01ba61b55b2041a39c54aefb3153c770dd59a0ef and later · before 520f012fe75fb8efc9f16a57ef929a7a2115d892affected · git
    • 01ba61b55b2041a39c54aefb3153c770dd59a0ef and later · before 3f77c3dfffc7063428b100c4945ca2a7a8680380affected · git
    • before 6.4not affected · semver
    • 6.6.89 and later · up to and including 6.6.*not affected · semver
    • 6.12.26 and later · up to and including 6.12.*not affected · semver
    • 6.14.5 and later · up to and including 6.14.*not affected · semver
    • 6.15 and laternot affected · original_commit_for_fix
Affected versions · NVD (4)

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

  • linux linux kernel6.4 and later · before 6.6.89
  • linux linux kernel6.7 and later · before 6.12.26
  • linux linux kernel6.13 and later · before 6.14.5
  • linux linux kernel6.15

Package-level exposure

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

EcosystemPackageAffected rangeFix
Debian:13linuxbefore 6.12.27-16.12.27-1

Same product

linux: all records

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-2025-37880May 9, 2025 · um: work around sched_yield not yielding in time-travel mode
    22Monitor
  • ← EarlierCVE-2025-37881May 9, 2025 · usb: gadget: aspeed: Add NULL pointer check in ast_vhub_init_dev()
    22Monitor
  • Later →CVE-2025-37887May 9, 2025 · pds_core: handle unsupported PDS_CORE_CMD_FW_CONTROL result
    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 Linux1d7c4b2b0bbfb09b55b2dc0e2355d7936bf89381Vendor (CNA)
Linux Linux3f77c3dfffc7063428b100c4945ca2a7a8680380Vendor (CNA)
Linux Linux520f012fe75fb8efc9f16a57ef929a7a2115d892Vendor (CNA)
Linux Linux66d7702b42ffdf0dce4808626088268a4e905ca6Vendor (CNA)
azl3 kernel 6.6.85.1-4 on Azure Linux 3.06.6.92.2-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
azl3 kernel 6.6.92.2-1 on Azure Linux 3.06.6.92.2-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
debian:linux6.12.27-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
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

Weakness class (CWE)

CWE-476 · NULL Pointer Dereference

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.

References

Show all references (3 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records