Skip to main content
Mallory
UnratedVulnerability

CVE-2026-101316: FreeBSD inotify Watch Descriptor Wraparound Use-After-Free

Updated 3 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days3 mentions · peak 2 in a dayToday
CVSS-Not scored
EPSS-30-day exploit probability
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
IdentifiersCVE-2026-101316CWE-416

CVE-2026-101316 is a kernel use-after-free vulnerability in FreeBSD 15.1 and 14.5 inotify watch handling. During automatic watch removal, inotify_log_one() checks whether a watch descriptor remains registered without verifying that it identifies the same watch. Watch descriptors are allocated from a 32-bit counter. Forcing that counter to wrap allows a newly created watch to reuse the descriptor of a watch being removed concurrently, potentially causing the kernel to free a watch that is still in use. An unprivileged local user may exploit this condition to escalate privileges.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation may allow an unprivileged local user to gain elevated privileges and potentially full control of the affected system, compromising system confidentiality, integrity, and availability.

Mitigation

If you can’t patch tonight, do this now.

No workaround is available. Install the corrected kernel and reboot.

Remediation

Patch, then assume compromise.

Upgrade FreeBSD 15.1 to 15.1-RELEASE-p7 or later, or FreeBSD 14.5 to 14.5-RELEASE-p4 or later, and reboot. Corresponding fixed FreeBSD-kernel package versions are 15.1_7 and 14.5_4. Alternatively, upgrade to a supported stable or release/security branch containing the correction. Eligible base-package installations can use 'pkg upgrade -r FreeBSD-base'; eligible binary distribution installations can run 'freebsd-update fetch' followed by 'freebsd-update install'. For source-based installations, obtain and verify the signed security patch, apply it, rebuild the kernel, and reboot.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
FAQ

Frequently asked questions

Is CVE-2026-101316 exploited in the wild?
As of Nov 19, 2026, Mallory has no reports of CVE-2026-101316 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-101316?
As of Nov 19, 2026, Mallory has found no public exploit for CVE-2026-101316.
Is there a patch for CVE-2026-101316?
Upgrade FreeBSD 15.1 to 15.1-RELEASE-p7 or later, or FreeBSD 14.5 to 14.5-RELEASE-p4 or later, and reboot. Corresponding fixed FreeBSD-kernel package versions are 15.1_7 and 14.5_4.
Activity feed

Recent activity

3 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.