NVD / CVE Program· CNA Linux

CVE-2026-80642: liveupdate: Reference count incoming FLB data

Noroxi assessment

Priority: Monitor (action score 0/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.19% (FIRST EPSS).
Fixed version: Linux Linux 725ada0273a0f48a67fd59cc518d7f8055fe3d5c, d8e47bd066d7e626f9f45d416182d585b7e18b9b.
Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 725ada0273a0f48a67fd59cc518d7f8055fe3d5c, d8e47bd066d7e626f9f45d416182d585b7e18b9b 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: liveupdate: Reference count incoming FLB data Increment the incoming FLB refcount in liveupdate_flb_get_incoming() so that the FLB structure cannot be freed while the caller is actively using it. Add an additional liveupdate_flb_put_incoming() function so the caller can explicitly indicate when it is done using the FLB data. During a Live Update, a subsystem might need to hold onto the incoming File-Lifecycle-Bound (FLB) data for an extended period, such as during device enumeration. Incrementing the reference count guarantees that the data remains valid and accessible until the subsystem releases it, preventing future use-after-free bugs.

—No exploit Fix available

EUVD-2026-67518

Published: Aug 28, 2026
Updated: Aug 28, 2026
EPSS: 0.1% · 9th percentile
CWE: —

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 0 / 40 · —
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.1%

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.

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
- 7.0affected
- cab056f2aae7250af50e503b81a80dfc567a1acd and later · before 725ada0273a0f48a67fd59cc518d7f8055fe3d5caffected · git
- cab056f2aae7250af50e503b81a80dfc567a1acd and later · before d8e47bd066d7e626f9f45d416182d585b7e18b9baffected · git
- before 7.0not affected · semver
- 7.1.5 and later · up to and including 7.1.*not affected · semver
- 7.2 and laternot affected · original_commit_for_fix

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

Ecosystem	Package	Affected range	Fix
Debian:14	linux	before 7.1.5-1	7.1.5-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-2026-80640Aug 28, 2026 · cxl/fwctl: Fix __fortify_panic
0Monitor
← EarlierCVE-2026-80641Aug 28, 2026 · wifi: wlcore: enable the right set of ciphers
0Monitor
Later →CVE-2026-80644Aug 28, 2026 · ocfs2: don't BUG_ON an invalid journal dinode
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 / package	Fixed version	Source
Linux Linux	725ada0273a0f48a67fd59cc518d7f8055fe3d5c	Vendor (CNA)
Linux Linux	d8e47bd066d7e626f9f45d416182d585b7e18b9b	Vendor (CNA)
debian:linux	7.1.5-1 · Debian:14	Package 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).