Skip to main content
Mallory
HighVulnerability

CVE-2025-40082: Out-of-bounds Read in Linux Kernel HFS+ hfsplus_uni2asc()

Published Oct 28, 2025 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS7.1High · v3.1
EPSS0.20%9th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Linux
IdentifiersCVE-2025-40082CWE-125 · Out-of-bounds Read

CVE-2025-40082 is an out-of-bounds read vulnerability in the Linux kernel HFS+ filesystem implementation. The hfsplus_uni2asc() function can be called by hfsplus_listxattr() with an hfsplus_attr_unistr structure rather than an hfsplus_unistr structure. Because the structures have different sizes, prior bounds handling did not prevent the Unicode-buffer pointer from exceeding the allocated object when the supplied ustrlen exceeds the available buffer size. The flaw is reachable during extended-attribute enumeration on an HFS+ filesystem.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation causes an out-of-bounds read in kernel context. Depending on kernel configuration and adjacent memory layout, this may disclose kernel memory or cause a kernel crash and denial of service.

Mitigation

If you can’t patch tonight, do this now.

Until a fixed kernel is deployed, avoid mounting or processing untrusted HFS+ filesystems, particularly removable media. Restrict untrusted users' ability to enumerate extended attributes on HFS+ mounts. Where operationally feasible, disable or do not load HFS+ filesystem support to make the vulnerable code path unreachable.

Remediation

Patch, then assume compromise.

Apply a Linux kernel update containing the upstream correction. The fix separates handling of hfsplus_attr_unistr and hfsplus_unistr buffers through dedicated wrapper functions and clamps ustrlen to a safe limit based on the allocated buffer size. Distribution-provided kernel security updates that incorporate this fix should be installed, followed by a reboot into the updated kernel where required.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
LinuxLinux Kerneloperating_system
FAQ

Frequently asked questions

Is CVE-2025-40082 exploited in the wild?
As of Oct 16, 2026, Mallory has no reports of CVE-2025-40082 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2025-40082?
As of Oct 16, 2026, Mallory has found no public exploit for CVE-2025-40082.
Is there a patch for CVE-2025-40082?
Apply a Linux kernel update containing the upstream correction. The fix separates handling of hfsplus_attr_unistr and hfsplus_unistr buffers through dedicated wrapper functions and clamps ustrlen to a safe limit based on the allocated buffer size.
What products are affected by CVE-2025-40082?
Linux Kernel.
How severe is CVE-2025-40082?
CVE-2025-40082 has a CVSS v3.1 score of 7.1 (High) and an EPSS score of 0.20% (9th percentile) as of Oct 16, 2026.
Activity feed

Recent activity

14 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.

View more in app →

No news coverage yet. Advisories and community discussion only.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity3Community discussion across Reddit, Mastodon, and other social sources.