Skip to content
Noroxi
CVE-2025-68337· NVD / CVE Program· CNA Linux

jbd2: avoid bug_on in jbd2_journal_get_create_access() when file system corrupted

Noroxi assessment

Priority: Monitor (action score 30/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.55% (FIRST EPSS).
  • Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 3faac6531d4818cd6be45e5bbf32937bbbc795c0, 71bbe06c40fc59b5b15661eca8ff307f4176d7f9, 986835bf4d11032bba4ab8414d18fce038c61bb4.

Low priority for now. Upgrade to Linux Linux 3faac6531d4818cd6be45e5bbf32937bbbc795c0, 71bbe06c40fc59b5b15661eca8ff307f4176d7f9, 986835bf4d11032bba4ab8414d18fce038c61bb4 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: jbd2: avoid bug_on in jbd2_journal_get_create_access() when file system corrupted There's issue when file system corrupted: ------------[ cut here ]------------ kernel BUG at fs/jbd2/transaction.c:1289! Oops: invalid opcode: 0000 [#1] SMP KASAN PTI CPU: 5 UID: 0 PID: 2031 Comm: mkdir Not tainted 6.18.0-rc1-next RIP: 0010:jbd2_journal_get_create_access+0x3b6/0x4d0 RSP: 0018:ffff888117aafa30 EFLAGS: 00010202 RAX: 0000000000000000 RBX: ffff88811a86b000 RCX: ffffffff89a63534 RDX: 1ffff110200ec602 RSI: 0000000000000004 RDI: ffff888100763010 RBP: ffff888100763000 R08: 0000000000000001 R09: ffff888100763028 R10: 0000000000000003 R11: 0000000000000000 R12: 0000000000000000 R13: ffff88812c432000 R14: ffff88812c608000 R15: ffff888120bfc000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007f91d6970c99 CR3: 00000001159c4000 CR4: 00000000000006f0 Call Trace: <TASK> __ext4_journal_get_create_access+0x42/0x170 ext4_getblk+0x319/0x6f0 ext4_bread+0x11/0x100 ext4_append+0x1e6/0x4a0 ext4_init_new_dir+0x145/0x1d0 ext4_mkdir+0x326/0x920 vfs_mkdir+0x45c/0x740 do_mkdirat+0x234/0x2f0 __x64_sys_mkdir+0xd6/0x120 do_syscall_64+0x5f/0xfa0 entry_SYSCALL_64_after_hwframe+0x76/0x7e The above issue occurs with us in errors=continue mode when accompanied by storage failures. There have been many inconsistencies in the file system data. In the case of file system data inconsistency, for example, if the block bitmap of a referenced block is not set, it can lead to the situation where a block being committed is allocated and used again. As a result, the following condition will not be satisfied then trigger BUG_ON. Of course, it is entirely possible to construct a problematic image that can trigger this BUG_ON through specific operations. In fact, I have constructed such an image and easily reproduced this issue. Therefore, J_ASSERT() holds true only under ideal conditions, but it may not necessarily be satisfied in exceptional scenarios. Using J_ASSERT() directly in abnormal situations would cause the system to crash, which is clearly not what we want. So here we directly trigger a JBD abort instead of immediately invoking BUG_ON.

HighCVSS 7.5 · v3.1—No exploit Fix available
Published
Dec 22, 2025
Updated
Oct 15, 2026
EPSS
0.5% · 45th percentile
CWE
—

Report tools

JSON

Action score

30

Monitor

Low priority for now.

CVSS
30 / 40 · 7.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.5%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · Linux
7.5
NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

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-68337

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.19affected
    • 470decc613ab2048b619a01028072d932d9086ee and later · before 71bbe06c40fc59b5b15661eca8ff307f4176d7f9affected · git
    • 470decc613ab2048b619a01028072d932d9086ee and later · before ed62fd8c15d41c4127ad16b8219b63124f5962bcaffected · git
    • 470decc613ab2048b619a01028072d932d9086ee and later · before 3faac6531d4818cd6be45e5bbf32937bbbc795c0affected · git
    • 470decc613ab2048b619a01028072d932d9086ee and later · before b4f8eabf6d991bd41fabcdf9302c4b3eab590cf4affected · git
    • 470decc613ab2048b619a01028072d932d9086ee and later · before a2a7f854d154a3e9232fec80782dad951655f52faffected · git
    • 470decc613ab2048b619a01028072d932d9086ee and later · before bf34c72337e40c4670cceeb79b353356933a254baffected · git
    • 470decc613ab2048b619a01028072d932d9086ee and later · before aa1703f3f706ea0867fb1991dcac709c9ec94cfbaffected · git
    • 470decc613ab2048b619a01028072d932d9086ee and later · before 986835bf4d11032bba4ab8414d18fce038c61bb4affected · git
    • before 2.6.19not 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
openSUSE:Tumbleweedkernel-sourcebefore 6.18.5-1.16.18.5-1.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-68335Dec 22, 2025 · comedi: pcl818: fix null-ptr-deref in pcl818_ai_cancel()
    0Monitor
  • ← EarlierCVE-2025-68336Dec 22, 2025 · locking/spinlock/debug: Fix data-race in do_raw_write_lock
    30Monitor
  • Later →CVE-2025-68338Dec 23, 2025 · net: dsa: microchip: Don't free uninitialized ksz_irq
    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 Linux3faac6531d4818cd6be45e5bbf32937bbbc795c0Vendor (CNA)
Linux Linux71bbe06c40fc59b5b15661eca8ff307f4176d7f9Vendor (CNA)
Linux Linux986835bf4d11032bba4ab8414d18fce038c61bb4Vendor (CNA)
Linux Linuxa2a7f854d154a3e9232fec80782dad951655f52fVendor (CNA)
Linux Linuxaa1703f3f706ea0867fb1991dcac709c9ec94cfbVendor (CNA)
Linux Linuxb4f8eabf6d991bd41fabcdf9302c4b3eab590cf4Vendor (CNA)
Linux Linuxbf34c72337e40c4670cceeb79b353356933a254bVendor (CNA)
Linux Linuxed62fd8c15d41c4127ad16b8219b63124f5962bcVendor (CNA)
debian:linux6.1.162-1 · Debian:12Package registry (OSV)
opensuse:kernel-source6.18.5-1.1 · openSUSE:TumbleweedPackage 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.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

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

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
High

Weakness class (CWE)

—

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

nvd-secondary

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 (9 more)

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

All records