CVE-2025-22047

Security-control bypass via promoted failure return

Published Apr 16, 2025 · Updated Aug 5, 2026

Improper return-value handling in affected Linux kernel releases allows local users to retain exposure to AMD CPU errata. In __apply_microcode_amd(), a failed SHA-256 verification returns -1 from a Boolean function, promoting the failure to true instead of rejecting the patch. On AMD x86 systems, boot, CPU hotplug, resume, or a privileged reload can create the state; local code can then exploit unmitigated errata to read cross-process or cross-VM data, corrupt kernel security state, or interrupt service.

CVSS severity7.8
High
EPSS probability0.21%
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

Improper return-value handling in affected Linux kernel releases allows local users to retain exposure to AMD CPU errata. In __apply_microcode_amd(), a failed SHA-256 verification returns -1 from a Boolean function, promoting the failure to true instead of rejecting the patch. On AMD x86 systems, boot, CPU hotplug, resume, or a privileged reload can create the state; local code can then exploit unmitigated errata to read cross-process or cross-VM data, corrupt kernel security state, or interrupt service.

The record

CVE
CVE-2025-22047
Published
Apr 16, 2025
Updated
Aug 5, 2026
Vendor
The Linux Kernel Organization
Product
Linux
Classifications
Unavailable
Attack vector
local
Privileges
authenticated

Timeline

How it unfolded

  1. Apr 16, 2025CVE publishedPublication date reported by the CVE source.
  2. Aug 5, 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=3e8653e399e7111a3e87d534ff4533b250ae574f <ada88219d5315fc13f2910fe278c7112d8d68889
  2. Affected versionversion=50cef76d5cb0e199cda19f026842560f6eedc4f7 <31ab12df723543047c3fc19cb8f8c4498ec6267f
  3. Affected versionversion=50cef76d5cb0e199cda19f026842560f6eedc4f7 <7f705a45f130a85fbf31c2abdc999c65644c8307
  4. Affected versionversion=6.12.18 <6.12.23
  5. Affected versionversion=6.13.6 <6.13.11
  6. Affected versionversion=6.14
  7. Affected versionversion=6.6.81 <6.6.87
  8. Affected versionversion=bef830144febedb7de86863ae99d8f53bed76e95 <763f4d638f71cb45235395790a46e9f9e84227fd
  9. Affected versionversion=c162ba4f45ab6ef3b7114af6fb419f1833f050c0 <d295c58fad1d5ab987a81f139dd21498732c4f13

What conditions does exploitation require?

Attack vectorlocal
Required privilegesauthenticated

What is affected?

The Linux Kernel Organization · Linuxversion=3e8653e399e7111a3e87d534ff4533b250ae574f <ada88219d5315fc13f2910fe278c7112d8d68889; version=50cef76d5cb0e199cda19f026842560f6eedc4f7 <31ab12df723543047c3fc19cb8f8c4498ec6267f; version=50cef76d5cb0e199cda19f026842560f6eedc4f7 <7f705a45f130a85fbf31c2abdc999c65644c8307; version=6.12.18 <6.12.23; version=6.13.6 <6.13.11; version=6.14; version=6.6.81 <6.6.87; version=bef830144febedb7de86863ae99d8f53bed76e95 <763f4d638f71cb45235395790a46e9f9e84227fd; version=c162ba4f45ab6ef3b7114af6fb419f1833f050c0 <d295c58fad1d5ab987a81f139dd21498732c4f13

Published CVSS scores

5.5UbuntuCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
5.5Oracle LinuxCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
7.8Linux kernel CVE teamCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
5.5SUSECVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
6.8SUSECVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

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)
Vectorlocal
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

No sourced classifications are available.

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