Skip to main content

CVE-2026-99514Linux vulnerability

Low priorityNot scoredEPSS not scored yet

CVE-2026-99514 is a vulnerability in Linux, not yet scored.

Why this priority: Not scored yet, and no exploitation signal.

Published · Updated · NVD status: Received

What it is

The record does not classify the weakness yet; the description below says what the reporter found.

How it is reached

The record does not say yet how the flaw is reached; the description below is the best guide until it is scored.

What an attacker gains

Its impact has not been scored yet.

Is it being exploited?

There is no public report of exploitation yet.

What to do

  1. Upgrade Linux to a fixed version for your release line (6.12.117, 6.18.61, 7.3.2).

Description from NVD

In the Linux kernel, the following vulnerability has been resolved:

landlock: Fix superblock use-after-free in release_inode()

Without this fix, release_inode() (task 1) can race with a umount operation in hook_sb_delete() (task 2). The order of operations in which the race occurs is:

* task 2: hook_sb_delete() arrives at the end of the function, waiting for landlock_superblock(sb)->inode_refs to become zero. * task 1: release_inode(): does atomic_long_dec_and_test(), decrementing inode_refs to zero. * task 2: gets woken up through some other means, sees that inode_refs is zero and returns. The caller is the unmount operation and proceeds to release the superblock. * task 1: Runs wake_up_var(&landlock_superblock(sb)->inode_refs), *dereferencing the sb_security on the freed-up superblock*.

Notably, wake_up_var() does not dereference the pointer passed to it, and only uses it to determine an overapproximated set of tasks to wake up. So while it's potentially possible for an attacker to provide a different value for that pointer, this only results in the wrong set of tasks getting woken up, and in this scenario, no further tasks are actually waiting.

Nevertheless, KASAN detects it as a slab-use-after-free read on sb->s_security:

BUG: KASAN: slab-use-after-free in release_inode+0x196/0x290 Read of size 8 at addr ffff888103b6c0a8 by task repro/217 release_inode+0x196/0x290 landlock_put_object+0x71/0x90 landlock_free_rules+0x38/0xc0 landlock_put_ruleset+0x47/0x130 fop_ruleset_release+0x33/0x40 __fput+0x305/0x780 Freed by task 54: kfree+0x11c/0x390 process_scheduled_works+0x766/0xe50 worker_thread+0x7bc/0xb20

The fix is to determine &landlock_superblock(inode->i_sb)->inode_refs only once earlier in release_inode(), and later use that precalculated address for the wake_up_var() call, without having to dereference through the superblock.

What this means for your architecture.

A CVE names a product. Whether it matters depends on where that product sits in your systems: what reaches it, which trust boundary it guards and what it can reach once compromised. Veriom maps your components, their relationships and your trust boundaries from your code, cloud and delivery evidence, so you can see where a component like this sits. The radar itself does not look at your systems.

Components it touches

  • Linux. Start from where it runs and what it is connected to.

Trust boundaries in play

    Questions to answer about your own systems

    • Where does Linux run in your systems, and at which version?
    • Which of those instances are reachable by people you do not trust?
    • What can it reach once compromised: which data stores, secrets and services?

    14-day free trial

    Understand how your systems connect.

    See your services, dependencies and trust boundaries in one place, with evidence from your connected environment.

    Sources

    • CVE records and CVSS scores from the NVD CVE API. This product uses the NVD API but is not endorsed or certified by the NVD.
    • Exploitation status from CISA’s Known Exploited Vulnerabilities catalog.
    • Exploit likelihood from FIRST’s Exploit Prediction Scoring System (EPSS), refreshed daily.
    • Explanations are written by Veriom from fixed templates over each record’s data, not by a person reviewing each CVE. Descriptions are quoted from the records as published.