Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2026-74726: bonding: alb: re-check primary_is_promisc under RTNL in bond_alb_monitor

Noroxi assessment

Priority: Monitor (action score 29/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.12% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 09add8d5cfa9c46828f51eaad162c36e86366b71, 257c4a3a34d8f51efb00f35375a0c6ce3c8f6ce2, 2faf75a8a06504071b4c0aea7e45a9cc49a4e187; azl3 kernel 6.6.150.1-1 on Azure Linux 3.0 6.6.152.1-1.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 09add8d5cfa9c46828f51eaad162c36e86366b71, 257c4a3a34d8f51efb00f35375a0c6ce3c8f6ce2, 2faf75a8a06504071b4c0aea7e45a9cc49a4e187; azl3 kernel 6.6.150.1-1 on Azure Linux 3.0 6.6.152.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: alb: re-check primary_is_promisc under RTNL in bond_alb_monitor bond_alb_monitor() reads primary_is_promisc under RCU, then drops RCU and takes RTNL via rtnl_trylock() before undoing the promiscuity it set on the active slave. In that window the active slave can change under RTNL (RTM_DELLINK -> __bond_release_one() -> bond_alb_handle_active_change()), which already drops the promiscuity and clears primary_is_promisc. The monitor still acts on the stale decision: if the slave was removed with no failover, curr_active_slave is now NULL and the deref faults; if it failed over, the stale dev_set_promiscuity(-1) underflows the new slave's promiscuity counter and pins it in IFF_PROMISC. Oops: general protection fault, probably for non-canonical address ... KASAN: null-ptr-deref in range [0x0000000000000000-0x0000000000000007] Workqueue: b42 bond_alb_monitor RIP: 0010:bond_alb_monitor (drivers/net/bonding/bond_alb.c:1600) process_one_work (kernel/workqueue.c:3322) worker_thread (kernel/workqueue.c:3486) kthread (kernel/kthread.c:436) ret_from_fork (arch/x86/kernel/process.c:158) Kernel panic - not syncing: Fatal exception Re-check primary_is_promisc (and curr_active_slave) after taking RTNL so the monitor only undoes an increment it still owns. The other bonding monitors already re-read state under RTNL in their commit phase (bond_miimon_commit/bond_ab_arp_commit); bond_alb_monitor() was the only one acting on the pre-trylock decision.

HighCVSS 7.3 · v3.1—No exploit Fix available
Published
Aug 22, 2026
Updated
Oct 16, 2026
EPSS
0.1% · 2th percentile
CWE
—

Report tools

JSON

Action score

29

Monitor

Low priority for now.

CVSS
29 / 40 · 7.3 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · Linux
7.3
NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

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-74726

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

    • 2.6.24affected
    • d0e81b7e2246a41d068ecaf15aac9de570816d63 and later · before f7668762bf5fd6db9397de5c0514407489d9d815affected · git
    • d0e81b7e2246a41d068ecaf15aac9de570816d63 and later · before 09add8d5cfa9c46828f51eaad162c36e86366b71affected · git
    • d0e81b7e2246a41d068ecaf15aac9de570816d63 and later · before b82f51681a7a88c7d3c865e817a3340d42b5fa2aaffected · git
    • d0e81b7e2246a41d068ecaf15aac9de570816d63 and later · before dd148539fb4741d01c06b7d2c8bd84b01920756caffected · git
    • d0e81b7e2246a41d068ecaf15aac9de570816d63 and later · before dccec0227ed8d9e36936d66e256b957dc2858468affected · git
    • d0e81b7e2246a41d068ecaf15aac9de570816d63 and later · before 2faf75a8a06504071b4c0aea7e45a9cc49a4e187affected · git
    • d0e81b7e2246a41d068ecaf15aac9de570816d63 and later · before 257c4a3a34d8f51efb00f35375a0c6ce3c8f6ce2affected · git
    • d0e81b7e2246a41d068ecaf15aac9de570816d63 and later · before 683c6ba6e58e6ed1037831ea97dd58d9c0e76b8daffected · git
    • before 2.6.24not 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.187-16.1.187-1
Debian:12linux-6.12before 6.12.107-1~deb12u16.12.107-1~deb12u1
Debian:13linuxbefore 6.12.105-16.12.105-1
Debian:14linuxbefore 7.1.9-17.1.9-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-74724Aug 22, 2026 · ipvs: avoid out-of-bounds write in ip_vs_nat_icmp
    31Monitor
  • ← EarlierCVE-2026-74725Aug 22, 2026 · enic: fix tx_hang_reset use-after-free on device removal
    31Monitor
  • Later →CVE-2026-74727Aug 22, 2026 · ovpn: skip rehash for peers already removed from by_id
    39Monitor

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 Linux09add8d5cfa9c46828f51eaad162c36e86366b71Vendor (CNA)
Linux Linux257c4a3a34d8f51efb00f35375a0c6ce3c8f6ce2Vendor (CNA)
Linux Linux2faf75a8a06504071b4c0aea7e45a9cc49a4e187Vendor (CNA)
Linux Linux683c6ba6e58e6ed1037831ea97dd58d9c0e76b8dVendor (CNA)
Linux Linuxb82f51681a7a88c7d3c865e817a3340d42b5fa2aVendor (CNA)
Linux Linuxdccec0227ed8d9e36936d66e256b957dc2858468Vendor (CNA)
Linux Linuxdd148539fb4741d01c06b7d2c8bd84b01920756cVendor (CNA)
Linux Linuxf7668762bf5fd6db9397de5c0514407489d9d815Vendor (CNA)
azl3 kernel 6.6.150.1-1 on Azure Linux 3.06.6.152.1-1 · Release NotesMicrosoft (MSRC)
debian:linux6.1.187-1 · Debian:12Package registry (OSV)
debian:linux-6.126.12.107-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

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
low · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
Low
Availability impact
High

Weakness class (CWE)

—

CVSS vector

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

nvd-secondary

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. SSVC exploitation— → none
  2. 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