What is CVE-2026-68145?

CVE-2026-68145 is a High severity Linux kernel vulnerability with a CVSS score of 7.8 out of 10, affecting Linux kernel versions from 6.6 onward and patched in 6.6.153, 6.12.101, 6.18.42 and others. CVE-2026-68145 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.

What is the CVSS score for CVE-2026-68145?

CVE-2026-68145 has a CVSS score of 7.8 out of 10, rated High severity. The vector string is CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H.

Is there a patch available for CVE-2026-68145?

Yes, CVE-2026-68145 has been patched. Fixed versions include 6.6.153, 6.12.101, 6.18.42 and others. If you are running Linux kernel 6.6 or later up to the fix versions, apply the relevant patch for your kernel branch.

Is CVE-2026-68145 actively exploited?

CVE-2026-68145 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.

CVE-2026-68145

High

In the Linux kernel, the following vulnerability has been resolved: iomap: fix out-of-bounds bitmap_set() with zero-length range ifs_set_range_dirty() and ifs_set_range_uptodate() compute last_blk as (off + len - 1) >> i_blkbits. When off is 0 and len is 0, the unsigned subtraction underflows to SIZE_MAX, producing a huge last_blk and nr_blks value that causes bitmap_set() to write far beyond the ifs->state allocation. Regarding ifs_set_range_uptodate(), it is temporarily safe because len cannot be passed in as 0. However, for ifs_set_range_dirty() this is reachable from __iomap_write_end(): when copy_folio_from_iter_atomic() returns 0 (e.g. user buffer fault) and the folio is already uptodate, the guard at the top of __iomap_write_end() does not trigger because !folio_test_uptodate() is false, and iomap_set_range_dirty() is called with copied == 0. Add a !len guard to both functions before the computation, so that a zero-length range is a no-op.

Package Linux Kernel

Published 2026-08-10

Last modified 2026-08-23

CVSS version 3.1

Patch available

Yes

CVSS 3.1 score

7.8

out of 10

High

Attack Vector

Local

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Vector string

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

Affected versions

Linux kernel versions 6.6 and later are affected. Fixed in 6.6.153, 6.12.101, 6.18.42, 7.1.6, 7.2 and their respective stable series.

Affected from

≥ 6.6

Fixed in

✓ 6.6.153 6.6.x ✓ 6.12.101 6.12.x ✓ 6.18.42 6.18.x ✓ 7.1.6 7.1.x ✓ 7.2

References

5 total

Details

CVE ID CVE-2026-68145

Severity High

CVSS score 7.8 / 10

CVSS version 3.1

Published 2026-08-10

Modified 2026-08-23

KEV No

Patch

Yes

Package linux

Frequently asked questions

What is CVE-2026-68145?

CVE-2026-68145 is a High severity Linux kernel vulnerability with a CVSS score of 7.8 out of 10 . It affects Linux kernel versions from 6.6 onward and has been patched in 6.6.153, 6.12.101, 6.18.42 and others. CVE-2026-68145 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.
What is the CVSS score for CVE-2026-68145?

CVE-2026-68145 has a CVSS score of 7.8 out of 10, rated High severity (CVSS 3.1). The vector string is CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H.
Is there a patch available for CVE-2026-68145?

Yes. CVE-2026-68145 has been patched. Fixed versions include 6.6.153, 6.12.101, 6.18.42 and others. If you are running Linux kernel 6.6 or later up to the fix versions, apply the relevant patch for your kernel branch.
Is CVE-2026-68145 actively exploited?

No. CVE-2026-68145 has not been confirmed as actively exploited. It is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog.