Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2025-68266: bfs: Reconstruct file type 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.21% (FIRST EPSS).
  • Fixed version: Linux Linux 34ab4c75588c07cca12884f2bf6b0347c7a13872, 77899444d46162aeb65f229590c26ba266864223, 8f73336b75bd3457b6f9410f2a0601a238f32238.

Low priority for now. Upgrade to Linux Linux 34ab4c75588c07cca12884f2bf6b0347c7a13872, 77899444d46162aeb65f229590c26ba266864223, 8f73336b75bd3457b6f9410f2a0601a238f32238 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: bfs: Reconstruct file type when loading from disk syzbot is reporting that S_IFMT bits of inode->i_mode can become bogus when the S_IFMT bits of the 32bits "mode" field loaded from disk are corrupted or when the 32bits "attributes" field loaded from disk are corrupted. A documentation says that BFS uses only lower 9 bits of the "mode" field. But I can't find an explicit explanation that the unused upper 23 bits (especially, the S_IFMT bits) are initialized with 0. Therefore, ignore the S_IFMT bits of the "mode" field loaded from disk. Also, verify that the value of the "attributes" field loaded from disk is either BFS_VREG or BFS_VDIR (because BFS supports only regular files and the root directory).

—No exploit Fix available
Published
Dec 16, 2025
Updated
Oct 15, 2026
EPSS
0.2% · 12th 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.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.

Follow CVE-2025-68266

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.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

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 d0c5ec1f57d8fbb953f166a27d9d32473dc8f3e4affected · git
    • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before aeccd6743ee4fdd1ab8cfcbb5b9a20b613418f6daffected · git
    • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 8f73336b75bd3457b6f9410f2a0601a238f32238affected · git
    • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before a9f626396bfe66f49b743601e862767928237cc0affected · git
    • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 77899444d46162aeb65f229590c26ba266864223affected · git
    • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before a8cb796e7e2cb7971311ba236922f5e7e1be77e6affected · git
    • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 34ab4c75588c07cca12884f2bf6b0347c7a13872affected · git
    • before 2.6.12not affected · semver
    • 5.10.248 and later · up to and including 5.10.*not 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.162-16.1.162-1
Debian:13linuxbefore 6.12.63-16.12.63-1
Debian:14linuxbefore 6.17.12-16.17.12-1

Same product

linux: all records

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-68264Dec 16, 2025 · ext4: refresh inline data size before write operations
    0Monitor
  • ← EarlierCVE-2025-68265Dec 16, 2025 · nvme: fix admin request_queue lifetime
    31Monitor
  • Later →CVE-2025-68281Dec 16, 2025 · ASoC: SDCA: bug fix while parsing mipi-sdca-control-cn-list
    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 Linux34ab4c75588c07cca12884f2bf6b0347c7a13872Vendor (CNA)
Linux Linux77899444d46162aeb65f229590c26ba266864223Vendor (CNA)
Linux Linux8f73336b75bd3457b6f9410f2a0601a238f32238Vendor (CNA)
Linux Linuxa8cb796e7e2cb7971311ba236922f5e7e1be77e6Vendor (CNA)
Linux Linuxa9f626396bfe66f49b743601e862767928237cc0Vendor (CNA)
Linux Linuxaeccd6743ee4fdd1ab8cfcbb5b9a20b613418f6dVendor (CNA)
Linux Linuxd0c5ec1f57d8fbb953f166a27d9d32473dc8f3e4Vendor (CNA)
debian:linux6.1.162-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.

Credits

All researchers

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

Show all references (8 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records