CVE-2023-53830: platform/x86: think-lmi: Fix memory leak when showing current settings
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.23% (FIRST EPSS).
- Fixed version: Linux Linux 5f99014c19fa50a5719c0bb78143282632675893, 9071525bfcb1f5674117dbed3eca0cd7b122813b, a3c4c053014585dcf20f4df954791b74d8a8afcd.
Low priority for now. Upgrade to Linux Linux 5f99014c19fa50a5719c0bb78143282632675893, 9071525bfcb1f5674117dbed3eca0cd7b122813b, a3c4c053014585dcf20f4df954791b74d8a8afcd 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: platform/x86: think-lmi: Fix memory leak when showing current settings When retriving a item string with tlmi_setting(), the result has to be freed using kfree(). In current_value_show() however, malformed item strings are not freed, causing a memory leak. Fix this by eliminating the early return responsible for this.
- Published
- Dec 9, 2025
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 14th 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.14affected
- 0fdf10e5fc964c315cf131a2eaab9cc531a9f40f and later · before b9396d991abe8d1ac31a043274ab20b49f92c2e6affected · git
- 0fdf10e5fc964c315cf131a2eaab9cc531a9f40f and later · before 9071525bfcb1f5674117dbed3eca0cd7b122813baffected · git
- 0fdf10e5fc964c315cf131a2eaab9cc531a9f40f and later · before 5f99014c19fa50a5719c0bb78143282632675893affected · git
- 0fdf10e5fc964c315cf131a2eaab9cc531a9f40f and later · before a3c4c053014585dcf20f4df954791b74d8a8afcdaffected · git
- before 5.14not affected · semver
- 5.15.107 and later · up to and including 5.15.*not affected · semver
- 6.1.24 and later · up to and including 6.1.*not affected · semver
- 6.2.11 and later · up to and including 6.2.*not affected · semver
- 6.3 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.25-1 | 6.1.25-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-53826Dec 9, 2025 · ubi: Fix UAF wear-leveling entry in eraseblk_count_seq_show()0Monitor
- ← EarlierCVE-2023-53829Dec 9, 2025 · f2fs: flush inode if atomic file is aborted31Monitor
- Later →CVE-2023-53831Dec 9, 2025 · net: read sk->sk_family once in sk_mc_loop()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 / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 5f99014c19fa50a5719c0bb78143282632675893 | Vendor (CNA) |
| Linux Linux | 9071525bfcb1f5674117dbed3eca0cd7b122813b | Vendor (CNA) |
| Linux Linux | a3c4c053014585dcf20f4df954791b74d8a8afcd | Vendor (CNA) |
| Linux Linux | b9396d991abe8d1ac31a043274ab20b49f92c2e6 | Vendor (CNA) |
| debian:linux | 6.1.25-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.