Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2026-98074: bonding: do not clear curr_active_slave prematurely when releasing all slaves

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.17% (FIRST EPSS).
  • Fixed version: Linux Linux 19ba7ecfade159b3702c78a360fd7d971e2b7109, 384739c631aa6749356ba062d6b7c9a484a733f6, 6d0ee411d5437f3d126ea6979acb83a8da29dc81; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 6.6.158.1-1.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 19ba7ecfade159b3702c78a360fd7d971e2b7109, 384739c631aa6749356ba062d6b7c9a484a733f6, 6d0ee411d5437f3d126ea6979acb83a8da29dc81; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 6.6.158.1-1 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: bonding: do not clear curr_active_slave prematurely when releasing all slaves When releasing all slaves during bond destruction (all == true), __bond_release_one() unconditionally clears bond->curr_active_slave to NULL in every iteration. If a backup slave is released before the active slave, bond_alb_deinit_slave() triggers rlb_teach_disabled_mac_on_primary(), which increments the active slave dev promiscuity counter and sets bond_info->primary_is_promisc = 1. Because bond->curr_active_slave was prematurely cleared to NULL when releasing the backup slave, the subsequent iteration releasing the active slave evaluates oldcurrent as NULL, so bond_change_active_slave(bond, NULL) is skipped. Consequently, bond_alb_handle_active_change() is never called to decrement the promiscuity counter, permanently leaking promiscuous mode on the physical device after bond teardown. When oldcurrent == slave, bond_change_active_slave(bond, NULL) already sets bond->curr_active_slave to NULL. We only need to avoid selecting a new active slave when all == true. Replace the if (all) branch with if (!all && oldcurrent == slave).

—No exploit Fix available
Published
Sep 25, 2026
Updated
Oct 19, 2026
EPSS
0.1% · 7th percentile
CWE
—

Report tools

JSON

Action score

0

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.

Follow CVE-2026-98074

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

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

    • 3.9affected
    • 0896341a44bf04bf6149d9307fe4686006f3eee1 and later · before b1ded242135071769902778dbab081e3fc09730faffected · git
    • 0896341a44bf04bf6149d9307fe4686006f3eee1 and later · before e39b203ec9e73852098d41b26386172d51babeb9affected · git
    • 0896341a44bf04bf6149d9307fe4686006f3eee1 and later · before 384739c631aa6749356ba062d6b7c9a484a733f6affected · git
    • 0896341a44bf04bf6149d9307fe4686006f3eee1 and later · before 7b435c69a30b40efc642de98b9bfa95fcf2ad4f0affected · git
    • 0896341a44bf04bf6149d9307fe4686006f3eee1 and later · before d6ef22e79c2be3612868daede0e9a84f05439d9eaffected · git
    • 0896341a44bf04bf6149d9307fe4686006f3eee1 and later · before 19ba7ecfade159b3702c78a360fd7d971e2b7109affected · git
    • 0896341a44bf04bf6149d9307fe4686006f3eee1 and later · before 6d0ee411d5437f3d126ea6979acb83a8da29dc81affected · git
    • 0896341a44bf04bf6149d9307fe4686006f3eee1 and later · before af602c7aa5fedc9be3043244017aef4f26c96b70affected · git
    • before 3.9not affected · semver

Package-level exposure

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

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.190-16.1.190-1
Debian:12linux-6.12before 6.12.111-1~deb12u16.12.111-1~deb12u1
Debian:13linuxbefore 6.12.111-16.12.111-1
Debian:14linuxbefore 7.2.7-17.2.7-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-98072Sep 25, 2026 · net/rds: use wq_has_sleeper() in release_in_xmit()
    0Monitor
  • ← EarlierCVE-2026-98073Sep 25, 2026 · net: Remove conflicting altnames for dying netns in __dev_change_net_namespace().
    31Monitor
  • Later →CVE-2026-98075Sep 25, 2026 · bpf: reject BPF_PSEUDO_FUNC reference to the main program
    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 / packageFixed versionSource
Linux Linux19ba7ecfade159b3702c78a360fd7d971e2b7109Vendor (CNA)
Linux Linux384739c631aa6749356ba062d6b7c9a484a733f6Vendor (CNA)
Linux Linux6d0ee411d5437f3d126ea6979acb83a8da29dc81Vendor (CNA)
Linux Linux7b435c69a30b40efc642de98b9bfa95fcf2ad4f0Vendor (CNA)
Linux Linuxaf602c7aa5fedc9be3043244017aef4f26c96b70Vendor (CNA)
Linux Linuxb1ded242135071769902778dbab081e3fc09730fVendor (CNA)
Linux Linuxd6ef22e79c2be3612868daede0e9a84f05439d9eVendor (CNA)
Linux Linuxe39b203ec9e73852098d41b26386172d51babeb9Vendor (CNA)
azl3 kernel 6.6.157.1-1 on Azure Linux 3.06.6.158.1-1 · Release NotesMicrosoft (MSRC)
debian:linux6.1.190-1 · Debian:12Package registry (OSV)
debian:linux6.12.111-1 · Debian:13Package registry (OSV)
debian:linux-6.126.12.111-1~deb12u1 · Debian:12Package 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).

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

Technical details

No CVSS vector for this record, so attack conditions can't be derived.

Weakness class (CWE)

—

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (7 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records