Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2025-40312: jfs: Verify inode mode when loading from disk

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.19% (FIRST EPSS).
  • Fixed version: Linux Linux 1795277a4e98d82e6451544d43695540cee042ea, 19cce65709a8a2966203653028d9004e28e85bd5, 2870a7dec49ccdc3f6ae35da8f5d6737f21133a8.

Low priority for now. Upgrade to Linux Linux 1795277a4e98d82e6451544d43695540cee042ea, 19cce65709a8a2966203653028d9004e28e85bd5, 2870a7dec49ccdc3f6ae35da8f5d6737f21133a8 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: jfs: Verify inode mode when loading from disk The inode mode loaded from corrupted disk can be invalid. Do like what commit 0a9e74051313 ("isofs: Verify inode mode when loading from disk") does.

—No exploit Fix available
Published
Dec 8, 2025
Updated
Oct 14, 2026
EPSS
0.1% · 9th percentile
CWE
—

Report tools

JSON

Action score

0

Monitor

Low priority for now.

CVSS
0 / 40 · —
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

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.

Follow CVE-2025-40312

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

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 help

Affected 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

    • 2.6.12affected
    • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 19cce65709a8a2966203653028d9004e28e85bd5affected · git
    • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before fabc1348bb8fe6bc80850014ee94bd89945f7f4daffected · git
    • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 46c76cfa17d1828c1a889cb54cb11d5ef3dfbc0faffected · git
    • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 2870a7dec49ccdc3f6ae35da8f5d6737f21133a8affected · git
    • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before ce054a366c54992185c9514e489a14f145b10c29affected · git
    • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 1795277a4e98d82e6451544d43695540cee042eaaffected · git
    • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 8d6a9cbd276b3b85da0e7e98208f89416fed9265affected · git
    • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 7a5aa54fba2bd591b22b9b624e6baa9037276986affected · git
    • before 2.6.12not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.159-16.1.159-1
Debian:13linuxbefore 6.12.63-16.12.63-1
Debian:14linuxbefore 6.17.8-16.17.8-1

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2025-40310Dec 8, 2025 · amd/amdkfd: resolve a race in amdgpu_amdkfd_device_fini_sw
    0Monitor
  • ← EarlierCVE-2025-40311Dec 8, 2025 · accel/habanalabs: support mapping cb with vmalloc-backed coherent memory
    0Monitor
  • Later →CVE-2025-40313Dec 8, 2025 · ntfs3: pretend $Extend records as regular files
    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 / packageFixed versionSource
Linux Linux1795277a4e98d82e6451544d43695540cee042eaVendor (CNA)
Linux Linux19cce65709a8a2966203653028d9004e28e85bd5Vendor (CNA)
Linux Linux2870a7dec49ccdc3f6ae35da8f5d6737f21133a8Vendor (CNA)
Linux Linux46c76cfa17d1828c1a889cb54cb11d5ef3dfbc0fVendor (CNA)
Linux Linux7a5aa54fba2bd591b22b9b624e6baa9037276986Vendor (CNA)
Linux Linux8d6a9cbd276b3b85da0e7e98208f89416fed9265Vendor (CNA)
Linux Linuxce054a366c54992185c9514e489a14f145b10c29Vendor (CNA)
Linux Linuxfabc1348bb8fe6bc80850014ee94bd89945f7f4dVendor (CNA)
debian:linux6.1.159-1 · Debian:12Package 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.

Finders, 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

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records