CVE-2023-53708: ACPI: x86: s2idle: Catch multiple ACPI_TYPE_PACKAGE objects
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 1ea7e47807279369c82718efd2677ea25c6579e3, 7b7964cd9db30bc84808a40d13a0633b4313f149, 883cf0d4cf288313b71146ddebdf5d647b76c78b.
Low priority for now. Upgrade to Linux Linux 1ea7e47807279369c82718efd2677ea25c6579e3, 7b7964cd9db30bc84808a40d13a0633b4313f149, 883cf0d4cf288313b71146ddebdf5d647b76c78b 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: ACPI: x86: s2idle: Catch multiple ACPI_TYPE_PACKAGE objects If a badly constructed firmware includes multiple `ACPI_TYPE_PACKAGE` objects while evaluating the AMD LPS0 _DSM, there will be a memory leak. Explicitly guard against this.
- Published
- Oct 22, 2025
- Updated
- Oct 28, 2026
- EPSS
- 0.2% · 11th percentile
- CWE
- —
Report tools
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.
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.
—
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.11affected
- 146f1ed852a87b802ed6e71c31e189c64871383c and later · before 7b7964cd9db30bc84808a40d13a0633b4313f149affected · git
- 146f1ed852a87b802ed6e71c31e189c64871383c and later · before 1ea7e47807279369c82718efd2677ea25c6579e3affected · git
- 146f1ed852a87b802ed6e71c31e189c64871383c and later · before 9e8bbde9293151430884aed882a88eaa22298f72affected · git
- 146f1ed852a87b802ed6e71c31e189c64871383c and later · before 883cf0d4cf288313b71146ddebdf5d647b76c78baffected · git
- before 5.11not affected · semver
- 5.15.133 and later · up to and including 5.15.*not affected · semver
- 6.1.55 and later · up to and including 6.1.*not affected · semver
- 6.5.5 and later · up to and including 6.5.*not affected · semver
- 6.6 and laternot affected · original_commit_for_fix
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.55-1 | 6.1.55-1 |
| Debian:13 | linux | before 6.5.6-1 | 6.5.6-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2023-53706Oct 22, 2025 · mm/vmemmap/devdax: fix kernel crash when probing devdax devices0Monitor
- ← EarlierCVE-2023-53707Oct 22, 2025 · drm/amdgpu: Fix integer overflow in amdgpu_cs_pass131Monitor
- Later →CVE-2023-53709Oct 22, 2025 · ring-buffer: Handle race between rb_move_tail and rb_check_pages0Monitor
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 | 1ea7e47807279369c82718efd2677ea25c6579e3 | Vendor (CNA) |
| Linux Linux | 7b7964cd9db30bc84808a40d13a0633b4313f149 | Vendor (CNA) |
| Linux Linux | 883cf0d4cf288313b71146ddebdf5d647b76c78b | Vendor (CNA) |
| Linux Linux | 9e8bbde9293151430884aed882a88eaa22298f72 | Vendor (CNA) |
| debian:linux | 6.1.55-1 · Debian:12 | Package 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.
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
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
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (3 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.