What is CVE-2026-46318?

CVE-2026-46318 is a Medium severity Linux kernel vulnerability with a CVSS score of 5.5 out of 10, affecting Linux kernel versions from 6.19 onward and patched in 7.0.12 and 7.1. CVE-2026-46318 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.

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

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

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

Yes, CVE-2026-46318 has been patched. Fixed versions include 7.0.12 and 7.1. If you are running Linux kernel 6.19 or later up to the fix versions, apply the relevant patch for your kernel branch.

Is CVE-2026-46318 actively exploited?

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

CVE-2026-46318

Medium

In the Linux kernel, the following vulnerability has been resolved: Revert "mm/hugetlbfs: update hugetlbfs to use mmap_prepare" This reverts commit ea52cb24cd3f ("mm/hugetlbfs: update hugetlbfs to use mmap_prepare") with conflict resolution to account for changes in commit ea52cb24cd3f ("mm/hugetlbfs: update hugetlbfs to use mmap_prepare"). The patch incorrectly handled hugetlb VMA lock allocation at the mmap_prepare stage, where a failed allocation occurring after mmap_prepare is called might result in the lock leaking. There is no risk of a merge causing a similar issues, as VMA_DONTEXPAND_BIT is set for hugetlb mappings. As a first step in addressing this issue, simply revert the change so we can rework how we do this having corrected the underlying issues. We maintain the VMA flags changes as best we can, accounting for the fact that we were working with a VMA descriptor previously and propagating like-for-like changes for this. Note that we invoke vma_set_flags() and do not call vma_start_write() as vm_flags_set() does. This is OK as it's being done in an .mmap hook where the VMA is not yet linked into the tree so nobody else can be accessing it.

Package Linux Kernel

Published 2026-06-09

Last modified 2026-07-23

CVSS version 3.1

Patch available

Yes

CVSS 3.1 score

5.5

out of 10

Medium

Attack Vector

Local

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

Low

Integrity

None

Availability

High

Vector string

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

Affected versions

Linux kernel versions 6.19 and later are affected. Fixed in 7.0.12, 7.1 and their respective stable series.

Affected from

≥ 6.19

Fixed in

✓ 7.0.12 7.0.x ✓ 7.1

References

2 total

Kernel Git
https://git.kernel.org/stable/c/3af5fc3f0ac98c624c109c8c0796fa46e814344c

Patch
Kernel Git
https://git.kernel.org/stable/c/83f9efcce93f8574be2279090ee2aec58b86cda7

Patch

Details

CVE ID CVE-2026-46318

Severity Medium

CVSS score 5.5 / 10

CVSS version 3.1

Published 2026-06-09

Modified 2026-07-23

KEV No

Patch

Yes

Package linux

Frequently asked questions

What is CVE-2026-46318?

CVE-2026-46318 is a Medium severity Linux kernel vulnerability with a CVSS score of 5.5 out of 10 . It affects Linux kernel versions from 6.19 onward and has been patched in 7.0.12 and 7.1. CVE-2026-46318 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.
What is the CVSS score for CVE-2026-46318?

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

Yes. CVE-2026-46318 has been patched. Fixed versions include 7.0.12 and 7.1. If you are running Linux kernel 6.19 or later up to the fix versions, apply the relevant patch for your kernel branch.
Is CVE-2026-46318 actively exploited?

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