Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2025-40194: cpufreq: intel_pstate: Fix object lifecycle issue in update_qos_request()

Noroxi assessment

Priority: Monitor (action score 0/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.21% (FIRST EPSS).
  • Fixed version: Linux Linux 0a58d3e77b22b087a57831c87cafd360e144a5bd, 15ac9579ebdaf22a37d7f60b3a8efc1029732ef9, 57e4a6aadf12578b96a038373cffd54b3a58b092; azl3 kernel 6.6.112.1-2 on Azure Linux 3.0 6.6.117.1-1.

Low priority for now. Upgrade to Linux Linux 0a58d3e77b22b087a57831c87cafd360e144a5bd, 15ac9579ebdaf22a37d7f60b3a8efc1029732ef9, 57e4a6aadf12578b96a038373cffd54b3a58b092; azl3 kernel 6.6.112.1-2 on Azure Linux 3.0 6.6.117.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: cpufreq: intel_pstate: Fix object lifecycle issue in update_qos_request() The cpufreq_cpu_put() call in update_qos_request() takes place too early because the latter subsequently calls freq_qos_update_request() that indirectly accesses the policy object in question through the QoS request object passed to it. Fortunately, update_qos_request() is called under intel_pstate_driver_lock, so this issue does not matter for changing the intel_pstate operation mode, but it theoretically can cause a crash to occur on CPU device hot removal (which currently can only happen in virt, but it is formally supported nevertheless). Address this issue by modifying update_qos_request() to drop the reference to the policy later.

—No exploit Fix available
Published
Nov 12, 2025
Updated
Oct 19, 2026
EPSS
0.2% · 11th percentile
CWE
—

Report tools

JSON

Action score

0

Monitor

Low priority for now.

CVSS
0 / 40 · —
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

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-40194

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.

—

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

    • 5.4affected
    • da5c504c7aae96db68c4b38e2564a88e91842d89 and later · before 15ac9579ebdaf22a37d7f60b3a8efc1029732ef9affected · git
    • da5c504c7aae96db68c4b38e2564a88e91842d89 and later · before bc26564bcc659beb6d977cd6eb394041ec2f2851affected · git
    • da5c504c7aae96db68c4b38e2564a88e91842d89 and later · before ad4e8f9bdbef11a19b7cb93e7f313bf59bdcc3b4affected · git
    • da5c504c7aae96db68c4b38e2564a88e91842d89 and later · before 0a58d3e77b22b087a57831c87cafd360e144a5bdaffected · git
    • da5c504c7aae96db68c4b38e2564a88e91842d89 and later · before 69a18ff6c60e8e113420f15355fad862cb45d38eaffected · git
    • da5c504c7aae96db68c4b38e2564a88e91842d89 and later · before ba63d4e9857a72a89e71a4eff9f2cc8c283e94c3affected · git
    • da5c504c7aae96db68c4b38e2564a88e91842d89 and later · before 57e4a6aadf12578b96a038373cffd54b3a58b092affected · git
    • da5c504c7aae96db68c4b38e2564a88e91842d89 and later · before 69e5d50fcf4093fb3f9f41c4f931f12c2ca8c467affected · git
    • before 5.4not affected · semver

Package-level exposure

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

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.158-16.1.158-1
Debian:13linuxbefore 6.12.57-16.12.57-1
Debian:14linuxbefore 6.17.6-16.17.6-1

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2025-40192Nov 12, 2025 · Revert "ipmi: fix msg stack when IPMI is disconnected"
    0Monitor
  • ← EarlierCVE-2025-40193Nov 12, 2025 · xtensa: simdisk: add input size check in proc_write_simdisk
    0Monitor
  • Later →CVE-2025-40195Nov 12, 2025 · mount: handle NULL values in mnt_ns_release()
    0Monitor

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 Linux0a58d3e77b22b087a57831c87cafd360e144a5bdVendor (CNA)
Linux Linux15ac9579ebdaf22a37d7f60b3a8efc1029732ef9Vendor (CNA)
Linux Linux57e4a6aadf12578b96a038373cffd54b3a58b092Vendor (CNA)
Linux Linux69a18ff6c60e8e113420f15355fad862cb45d38eVendor (CNA)
Linux Linux69e5d50fcf4093fb3f9f41c4f931f12c2ca8c467Vendor (CNA)
Linux Linuxad4e8f9bdbef11a19b7cb93e7f313bf59bdcc3b4Vendor (CNA)
Linux Linuxba63d4e9857a72a89e71a4eff9f2cc8c283e94c3Vendor (CNA)
Linux Linuxbc26564bcc659beb6d977cd6eb394041ec2f2851Vendor (CNA)
azl3 kernel 6.6.112.1-2 on Azure Linux 3.06.6.117.1-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
debian:linux6.1.158-1 · Debian:12Package 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).

Technical details

No CVSS vector for this record, so attack conditions can't be derived.

Weakness class (CWE)

—

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