CVE-2025-38345: ACPICA: fix acpi operand cache leak in dswstate.c
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.20% (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 156fd20a41e776bbf334bd5e45c4f78dfc90ce1c, 1c0d9115a001979cb446ba5e8331dd1d29a10bbf, 4fa430a8bca708c7776f6b9d001257f48b19a5b7; azl3 kernel 6.6.92.2-2 on Azure Linux 3.0 6.6.96.1-1.
Low priority for now. Upgrade to Linux Linux 156fd20a41e776bbf334bd5e45c4f78dfc90ce1c, 1c0d9115a001979cb446ba5e8331dd1d29a10bbf, 4fa430a8bca708c7776f6b9d001257f48b19a5b7; azl3 kernel 6.6.92.2-2 on Azure Linux 3.0 6.6.96.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: ACPICA: fix acpi operand cache leak in dswstate.c ACPICA commit 987a3b5cf7175916e2a4b6ea5b8e70f830dfe732 I found an ACPI cache leak in ACPI early termination and boot continuing case. When early termination occurs due to malicious ACPI table, Linux kernel terminates ACPI function and continues to boot process. While kernel terminates ACPI function, kmem_cache_destroy() reports Acpi-Operand cache leak. Boot log of ACPI operand cache leak is as follows: >[ 0.585957] ACPI: Added _OSI(Module Device) >[ 0.587218] ACPI: Added _OSI(Processor Device) >[ 0.588530] ACPI: Added _OSI(3.0 _SCP Extensions) >[ 0.589790] ACPI: Added _OSI(Processor Aggregator Device) >[ 0.591534] ACPI Error: Illegal I/O port address/length above 64K: C806E00000004002/0x2 (20170303/hwvalid-155) >[ 0.594351] ACPI Exception: AE_LIMIT, Unable to initialize fixed events (20170303/evevent-88) >[ 0.597858] ACPI: Unable to start the ACPI Interpreter >[ 0.599162] ACPI Error: Could not remove SCI handler (20170303/evmisc-281) >[ 0.601836] kmem_cache_destroy Acpi-Operand: Slab cache still has objects >[ 0.603556] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.12.0-rc5 #26 >[ 0.605159] Hardware name: innotek gmb_h virtual_box/virtual_box, BIOS virtual_box 12/01/2006 >[ 0.609177] Call Trace: >[ 0.610063] ? dump_stack+0x5c/0x81 >[ 0.611118] ? kmem_cache_destroy+0x1aa/0x1c0 >[ 0.612632] ? acpi_sleep_proc_init+0x27/0x27 >[ 0.613906] ? acpi_os_delete_cache+0xa/0x10 >[ 0.617986] ? acpi_ut_delete_caches+0x3f/0x7b >[ 0.619293] ? acpi_terminate+0xa/0x14 >[ 0.620394] ? acpi_init+0x2af/0x34f >[ 0.621616] ? __class_create+0x4c/0x80 >[ 0.623412] ? video_setup+0x7f/0x7f >[ 0.624585] ? acpi_sleep_proc_init+0x27/0x27 >[ 0.625861] ? do_one_initcall+0x4e/0x1a0 >[ 0.627513] ? kernel_init_freeable+0x19e/0x21f >[ 0.628972] ? rest_init+0x80/0x80 >[ 0.630043] ? kernel_init+0xa/0x100 >[ 0.631084] ? ret_from_fork+0x25/0x30 >[ 0.633343] vgaarb: loaded >[ 0.635036] EDAC MC: Ver: 3.0.0 >[ 0.638601] PCI: Probing PCI hardware >[ 0.639833] PCI host bridge to bus 0000:00 >[ 0.641031] pci_bus 0000:00: root bus resource [io 0x0000-0xffff] > ... Continue to boot and log is omitted ... I analyzed this memory leak in detail and found acpi_ds_obj_stack_pop_and_ delete() function miscalculated the top of the stack. acpi_ds_obj_stack_push() function uses walk_state->operand_index for start position of the top, but acpi_ds_obj_stack_pop_and_delete() function considers index 0 for it. Therefore, this causes acpi operand memory leak. This cache leak causes a security threat because an old kernel (<= 4.9) shows memory locations of kernel functions in stack dump. Some malicious users could use this information to neutralize kernel ASLR. I made a patch to fix ACPI operand cache leak.
- Published
- Jul 10, 2025
- Updated
- Nov 5, 2026
- EPSS
- 0.2% · 9th percentile
- CWE
- CWE-401
Report tools
Action score
22
Monitor
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
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.
Running WordPress? Scan your site free with WP Lens
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 helpAffected 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.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
| debian | debian linux | cpe:2.3:o:debian:debian_linux |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- debian debian linux11.0
- linux linux kernel5.5 and later · before 5.10.239
- linux linux kernel5.11 and later · before 5.15.186
- linux linux kernel5.16 and later · before 6.1.142
- linux linux kernelbefore 5.4.295
- linux linux kernel6.7 and later · before 6.12.35
- linux linux kernel6.13 and later · before 6.15.4
- linux linux kernel6.2 and later · before 6.6.95
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.26affected
- 773069d48030e670cf2032a13ddf16a2e0034df3 and later · before 4fa430a8bca708c7776f6b9d001257f48b19a5b7affected · git
- 773069d48030e670cf2032a13ddf16a2e0034df3 and later · before 1c0d9115a001979cb446ba5e8331dd1d29a10bbfaffected · git
- 773069d48030e670cf2032a13ddf16a2e0034df3 and later · before 5a68893b594ee6ce0efce5f74c07e64e9dd0c2c4affected · git
- 773069d48030e670cf2032a13ddf16a2e0034df3 and later · before 64c4bcf0308dd1d752ef31d560040b8725e29984affected · git
- 773069d48030e670cf2032a13ddf16a2e0034df3 and later · before 755a8006b76792922ff7b1c9674d8897a476b5d7affected · git
- 773069d48030e670cf2032a13ddf16a2e0034df3 and later · before 76d37168155880f2b04a0aad92ceb0f9d799950eaffected · git
- 773069d48030e670cf2032a13ddf16a2e0034df3 and later · before e0783910ca4368b01466bc8dcdcc13c3e0b7db53affected · git
- 773069d48030e670cf2032a13ddf16a2e0034df3 and later · before 156fd20a41e776bbf334bd5e45c4f78dfc90ce1caffected · git
- before 2.6.26not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:10 | kernel | before 6.12.0-211.7.1.el10_2 | 6.12.0-211.7.1.el10_2 |
| AlmaLinux:10 | kernel-64k | before 6.12.0-211.7.1.el10_2 | 6.12.0-211.7.1.el10_2 |
| AlmaLinux:10 | kernel-64k-core | before 6.12.0-211.7.1.el10_2 | 6.12.0-211.7.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug | before 6.12.0-211.7.1.el10_2 | 6.12.0-211.7.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-core | before 6.12.0-211.7.1.el10_2 | 6.12.0-211.7.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-devel | before 6.12.0-211.7.1.el10_2 | 6.12.0-211.7.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-devel-matched | before 6.12.0-211.7.1.el10_2 | 6.12.0-211.7.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-modules | before 6.12.0-211.7.1.el10_2 | 6.12.0-211.7.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-modules-core | before 6.12.0-211.7.1.el10_2 | 6.12.0-211.7.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-modules-extra | before 6.12.0-211.7.1.el10_2 | 6.12.0-211.7.1.el10_2 |
| AlmaLinux:10 | kernel-64k-devel | before 6.12.0-211.7.1.el10_2 | 6.12.0-211.7.1.el10_2 |
| AlmaLinux:10 | kernel-64k-devel-matched | before 6.12.0-211.7.1.el10_2 | 6.12.0-211.7.1.el10_2 |
| AlmaLinux:10 | kernel-64k-modules | before 6.12.0-211.7.1.el10_2 | 6.12.0-211.7.1.el10_2 |
| AlmaLinux:10 | kernel-64k-modules-core | before 6.12.0-211.7.1.el10_2 | 6.12.0-211.7.1.el10_2 |
| AlmaLinux:10 | kernel-64k-modules-extra | before 6.12.0-211.7.1.el10_2 | 6.12.0-211.7.1.el10_2 |
| AlmaLinux:10 | kernel-abi-stablelists | before 6.12.0-211.7.1.el10_2 | 6.12.0-211.7.1.el10_2 |
| AlmaLinux:10 | kernel-core | before 6.12.0-211.7.1.el10_2 | 6.12.0-211.7.1.el10_2 |
| AlmaLinux:10 | kernel-cross-headers | before 6.12.0-211.7.1.el10_2 | 6.12.0-211.7.1.el10_2 |
| AlmaLinux:10 | kernel-debug | before 6.12.0-211.7.1.el10_2 | 6.12.0-211.7.1.el10_2 |
| AlmaLinux:10 | kernel-debug-core | before 6.12.0-211.7.1.el10_2 | 6.12.0-211.7.1.el10_2 |
| AlmaLinux:10 | kernel-debug-devel | before 6.12.0-211.7.1.el10_2 | 6.12.0-211.7.1.el10_2 |
| AlmaLinux:10 | kernel-debug-devel-matched | before 6.12.0-211.7.1.el10_2 | 6.12.0-211.7.1.el10_2 |
| AlmaLinux:10 | kernel-debug-modules | before 6.12.0-211.7.1.el10_2 | 6.12.0-211.7.1.el10_2 |
| AlmaLinux:10 | kernel-debug-modules-core | before 6.12.0-211.7.1.el10_2 | 6.12.0-211.7.1.el10_2 |
+96
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- 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 KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2025-38342Jul 10, 2025 · software node: Correct a OOB check in software_node_get_reference_args()28Monitor
- ← EarlierCVE-2025-38344Jul 10, 2025 · ACPICA: fix acpi parse and parseext cache leaks22Monitor
- Later →CVE-2025-38346Jul 10, 2025 · ftrace: Fix UAF when lookup kallsym after ftrace disabled31Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 156fd20a41e776bbf334bd5e45c4f78dfc90ce1c | Vendor (CNA) |
| Linux Linux | 1c0d9115a001979cb446ba5e8331dd1d29a10bbf | Vendor (CNA) |
| Linux Linux | 4fa430a8bca708c7776f6b9d001257f48b19a5b7 | Vendor (CNA) |
| Linux Linux | 5a68893b594ee6ce0efce5f74c07e64e9dd0c2c4 | Vendor (CNA) |
| Linux Linux | 64c4bcf0308dd1d752ef31d560040b8725e29984 | Vendor (CNA) |
| Linux Linux | 755a8006b76792922ff7b1c9674d8897a476b5d7 | Vendor (CNA) |
| Linux Linux | 76d37168155880f2b04a0aad92ceb0f9d799950e | Vendor (CNA) |
| Linux Linux | e0783910ca4368b01466bc8dcdcc13c3e0b7db53 | Vendor (CNA) |
| azl3 kernel 6.6.92.2-2 on Azure Linux 3.0 | 6.6.96.1-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| almalinux:kernel | 6.12.0-211.7.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k | 6.12.0-211.7.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-core | 6.12.0-211.7.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug | 6.12.0-211.7.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug-core | 6.12.0-211.7.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug-devel | 6.12.0-211.7.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug-devel-matched | 6.12.0-211.7.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules | 6.12.0-211.7.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules-core | 6.12.0-211.7.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules-extra | 6.12.0-211.7.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-devel | 6.12.0-211.7.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-devel-matched | 6.12.0-211.7.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| debian:linux | 6.1.147-1 · Debian:12 | Package registry (OSV) |
| red hat:kernel-64k-debug-debuginfo | 0:6.12.0-211.7.1.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:kernel-64k-debug-devel | 0:6.12.0-211.7.1.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:kernel-64k-debug-devel-matched | 0:6.12.0-211.7.1.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:kernel-64k-debuginfo | 0:6.12.0-211.7.1.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:kernel-64k-devel | 0:6.12.0-211.7.1.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:kernel-64k-devel-matched | 0:6.12.0-211.7.1.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:kernel-debug-debuginfo | 0:6.12.0-211.7.1.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:kernel-debug-devel | 0:6.12.0-211.7.1.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
+4
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.
Credits
All researchersFinders, 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
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-401 · Missing Release of Memory after Effective LifetimeCVSS 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
- SSVC exploitation— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (9 more)Show less
- git.kernel.org/stable/c/1c0d9115a001979cb446ba5e8331dd1d29a10bbf
- git.kernel.org/stable/c/4fa430a8bca708c7776f6b9d001257f48b19a5b7
- git.kernel.org/stable/c/5a68893b594ee6ce0efce5f74c07e64e9dd0c2c4
- git.kernel.org/stable/c/64c4bcf0308dd1d752ef31d560040b8725e29984
- git.kernel.org/stable/c/755a8006b76792922ff7b1c9674d8897a476b5d7
- git.kernel.org/stable/c/76d37168155880f2b04a0aad92ceb0f9d799950e
- git.kernel.org/stable/c/e0783910ca4368b01466bc8dcdcc13c3e0b7db53
- lists.debian.org/debian-lts-announce/2025/10/msg00007.html
- lists.debian.org/debian-lts-announce/2025/10/msg00008.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.