CVE-2022-49667: net: bonding: fix use-after-free after 802.3ad slave unbind
Noroxi assessment
Priority: Monitor (action score 31/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.28% (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 050133e1aa2cb49bb17be847d48a4431598ef562, 2765749def4765c5052a4c66445cf4c96fcccdbc, 63b2fe509f69b90168a75e04e14573dccf7984e6.
Low priority for now. Upgrade to Linux Linux 050133e1aa2cb49bb17be847d48a4431598ef562, 2765749def4765c5052a4c66445cf4c96fcccdbc, 63b2fe509f69b90168a75e04e14573dccf7984e6 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: net: bonding: fix use-after-free after 802.3ad slave unbind commit 0622cab0341c ("bonding: fix 802.3ad aggregator reselection"), resolve case, when there is several aggregation groups in the same bond. bond_3ad_unbind_slave will invalidate (clear) aggregator when __agg_active_ports return zero. So, ad_clear_agg can be executed even, when num_of_ports!=0. Than bond_3ad_unbind_slave can be executed again for, previously cleared aggregator. NOTE: at this time bond_3ad_unbind_slave will not update slave ports list, because lag_ports==NULL. So, here we got slave ports, pointing to freed aggregator memory. Fix with checking actual number of ports in group (as was before commit 0622cab0341c ("bonding: fix 802.3ad aggregator reselection") ), before ad_clear_agg(). The KASAN logs are as follows: [ 767.617392] ================================================================== [ 767.630776] BUG: KASAN: use-after-free in bond_3ad_state_machine_handler+0x13dc/0x1470 [ 767.638764] Read of size 2 at addr ffff00011ba9d430 by task kworker/u8:7/767 [ 767.647361] CPU: 3 PID: 767 Comm: kworker/u8:7 Tainted: G O 5.15.11 #15 [ 767.655329] Hardware name: DNI AmazonGo1 A7040 board (DT) [ 767.660760] Workqueue: lacp_1 bond_3ad_state_machine_handler [ 767.666468] Call trace: [ 767.668930] dump_backtrace+0x0/0x2d0 [ 767.672625] show_stack+0x24/0x30 [ 767.675965] dump_stack_lvl+0x68/0x84 [ 767.679659] print_address_description.constprop.0+0x74/0x2b8 [ 767.685451] kasan_report+0x1f0/0x260 [ 767.689148] __asan_load2+0x94/0xd0 [ 767.692667] bond_3ad_state_machine_handler+0x13dc/0x1470
- Published
- Feb 26, 2025
- Updated
- Aug 5, 2026
- EPSS
- 0.2% · 21th percentile
- CWE
- CWE-416
Report tools
Action score
31
Monitor
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 7.8
- 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.
Running WordPress? Scan your site free with WP Lens
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 helpAffected 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.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel4.7 and later · before 4.9.322
- linux linux kernel4.10 and later · before 4.14.287
- linux linux kernel4.15 and later · before 4.19.251
- linux linux kernel4.20 and later · before 5.4.204
- linux linux kernel5.5 and later · before 5.10.129
- linux linux kernel5.11 and later · before 5.15.53
- linux linux kernel5.16 and later · before 5.18.10
- linux linux kernel5.19
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
- 4.7affected
- 0622cab0341cac6b30da177b0faa39fae0680e71 and later · before a853b7a3a9fd1d74a4ccdd9cd73512b7dace2f1eaffected · git
- 0622cab0341cac6b30da177b0faa39fae0680e71 and later · before b90ac60303063a43e17dd4aec159067599d255e6affected · git
- 0622cab0341cac6b30da177b0faa39fae0680e71 and later · before f162f7c348fa2a5555bafdb5cc890b89b221e69caffected · git
- 0622cab0341cac6b30da177b0faa39fae0680e71 and later · before 893825289ba840afd86bfffcb6f7f363c73efff8affected · git
- 0622cab0341cac6b30da177b0faa39fae0680e71 and later · before 63b2fe509f69b90168a75e04e14573dccf7984e6affected · git
- 0622cab0341cac6b30da177b0faa39fae0680e71 and later · before ef0af7d08d26c5333ff4944a559279464edf6f15affected · git
- 0622cab0341cac6b30da177b0faa39fae0680e71 and later · before 2765749def4765c5052a4c66445cf4c96fcccdbcaffected · git
- 0622cab0341cac6b30da177b0faa39fae0680e71 and later · before 050133e1aa2cb49bb17be847d48a4431598ef562affected · git
- before 4.7not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 5.18.14-1 | 5.18.14-1 |
| Red Hat:rhel_e4s:9.0::appstream | bpftool-debuginfo | before 0:5.14.0-70.163.1.el9_0 | 0:5.14.0-70.163.1.el9_0 |
| Red Hat:rhel_e4s:9.0::appstream | kernel-debug-debuginfo | before 0:5.14.0-70.163.1.el9_0 | 0:5.14.0-70.163.1.el9_0 |
| Red Hat:rhel_e4s:9.0::appstream | kernel-debug-devel | before 0:5.14.0-70.163.1.el9_0 | 0:5.14.0-70.163.1.el9_0 |
| Red Hat:rhel_e4s:9.0::appstream | kernel-debug-devel-matched | before 0:5.14.0-70.163.1.el9_0 | 0:5.14.0-70.163.1.el9_0 |
| Red Hat:rhel_e4s:9.0::appstream | kernel-debuginfo | before 0:5.14.0-70.163.1.el9_0 | 0:5.14.0-70.163.1.el9_0 |
| Red Hat:rhel_e4s:9.0::appstream | kernel-debuginfo-common-aarch64 | before 0:5.14.0-70.163.1.el9_0 | 0:5.14.0-70.163.1.el9_0 |
| Red Hat:rhel_e4s:9.0::appstream | kernel-debuginfo-common-ppc64le | before 0:5.14.0-70.163.1.el9_0 | 0:5.14.0-70.163.1.el9_0 |
| Red Hat:rhel_e4s:9.0::appstream | kernel-debuginfo-common-s390x | before 0:5.14.0-70.163.1.el9_0 | 0:5.14.0-70.163.1.el9_0 |
| Red Hat:rhel_e4s:9.0::appstream | kernel-debuginfo-common-x86_64 | before 0:5.14.0-70.163.1.el9_0 | 0:5.14.0-70.163.1.el9_0 |
| Red Hat:rhel_e4s:9.0::appstream | kernel-devel | before 0:5.14.0-70.163.1.el9_0 | 0:5.14.0-70.163.1.el9_0 |
| Red Hat:rhel_e4s:9.0::appstream | kernel-devel-matched | before 0:5.14.0-70.163.1.el9_0 | 0:5.14.0-70.163.1.el9_0 |
| Red Hat:rhel_e4s:9.0::appstream | kernel-doc | before 0:5.14.0-70.163.1.el9_0 | 0:5.14.0-70.163.1.el9_0 |
| Red Hat:rhel_e4s:9.0::appstream | kernel-tools-debuginfo | before 0:5.14.0-70.163.1.el9_0 | 0:5.14.0-70.163.1.el9_0 |
| Red Hat:rhel_e4s:9.0::appstream | kernel-zfcpdump-debuginfo | before 0:5.14.0-70.163.1.el9_0 | 0:5.14.0-70.163.1.el9_0 |
| Red Hat:rhel_e4s:9.0::appstream | kernel-zfcpdump-devel | before 0:5.14.0-70.163.1.el9_0 | 0:5.14.0-70.163.1.el9_0 |
| Red Hat:rhel_e4s:9.0::appstream | kernel-zfcpdump-devel-matched | before 0:5.14.0-70.163.1.el9_0 | 0:5.14.0-70.163.1.el9_0 |
| Red Hat:rhel_e4s:9.0::appstream | perf | before 0:5.14.0-70.163.1.el9_0 | 0:5.14.0-70.163.1.el9_0 |
| Red Hat:rhel_e4s:9.0::appstream | perf-debuginfo | before 0:5.14.0-70.163.1.el9_0 | 0:5.14.0-70.163.1.el9_0 |
| Red Hat:rhel_e4s:9.0::appstream | python3-perf-debuginfo | before 0:5.14.0-70.163.1.el9_0 | 0:5.14.0-70.163.1.el9_0 |
| Red Hat:rhel_e4s:9.0::baseos | bpftool | before 0:5.14.0-70.163.1.el9_0 | 0:5.14.0-70.163.1.el9_0 |
| Red Hat:rhel_e4s:9.0::baseos | kernel | before 0:5.14.0-70.163.1.el9_0 | 0:5.14.0-70.163.1.el9_0 |
| Red Hat:rhel_e4s:9.0::baseos | kernel-abi-stablelists | before 0:5.14.0-70.163.1.el9_0 | 0:5.14.0-70.163.1.el9_0 |
| Red Hat:rhel_e4s:9.0::baseos | kernel-core | before 0:5.14.0-70.163.1.el9_0 | 0:5.14.0-70.163.1.el9_0 |
+28
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2022-49665Feb 26, 2025 · platform/x86: thinkpad_acpi: Fix a memory leak of EFCH MMIO resource22Monitor
- ← EarlierCVE-2022-49666Feb 26, 2025 · powerpc/memhotplug: Add add_pages override for PPC22Monitor
- Later →CVE-2022-49668Feb 26, 2025 · PM / devfreq: exynos-ppmu: Fix refcount leak in of_get_devfreq_events22Monitor
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 | 050133e1aa2cb49bb17be847d48a4431598ef562 | Vendor (CNA) |
| Linux Linux | 2765749def4765c5052a4c66445cf4c96fcccdbc | Vendor (CNA) |
| Linux Linux | 63b2fe509f69b90168a75e04e14573dccf7984e6 | Vendor (CNA) |
| Linux Linux | 893825289ba840afd86bfffcb6f7f363c73efff8 | Vendor (CNA) |
| Linux Linux | a853b7a3a9fd1d74a4ccdd9cd73512b7dace2f1e | Vendor (CNA) |
| Linux Linux | b90ac60303063a43e17dd4aec159067599d255e6 | Vendor (CNA) |
| Linux Linux | ef0af7d08d26c5333ff4944a559279464edf6f15 | Vendor (CNA) |
| Linux Linux | f162f7c348fa2a5555bafdb5cc890b89b221e69c | Vendor (CNA) |
| debian:linux | 5.18.14-1 · Debian:12 | Package registry (OSV) |
| red hat:bpftool-debuginfo | 0:5.14.0-70.163.1.el9_0 · Red Hat:rhel_e4s:9.0::appstream | Package registry (OSV) |
| red hat:kernel-debug-debuginfo | 0:5.14.0-70.163.1.el9_0 · Red Hat:rhel_e4s:9.0::appstream | Package registry (OSV) |
| red hat:kernel-debug-devel | 0:5.14.0-70.163.1.el9_0 · Red Hat:rhel_e4s:9.0::appstream | Package registry (OSV) |
| red hat:kernel-debug-devel-matched | 0:5.14.0-70.163.1.el9_0 · Red Hat:rhel_e4s:9.0::appstream | Package registry (OSV) |
| red hat:kernel-debuginfo | 0:5.14.0-70.163.1.el9_0 · Red Hat:rhel_e4s:9.0::appstream | Package registry (OSV) |
| red hat:kernel-debuginfo-common-aarch64 | 0:5.14.0-70.163.1.el9_0 · Red Hat:rhel_e4s:9.0::appstream | Package registry (OSV) |
| red hat:kernel-debuginfo-common-ppc64le | 0:5.14.0-70.163.1.el9_0 · Red Hat:rhel_e4s:9.0::appstream | Package registry (OSV) |
| red hat:kernel-debuginfo-common-s390x | 0:5.14.0-70.163.1.el9_0 · Red Hat:rhel_e4s:9.0::appstream | Package registry (OSV) |
| red hat:kernel-debuginfo-common-x86_64 | 0:5.14.0-70.163.1.el9_0 · Red Hat:rhel_e4s:9.0::appstream | Package registry (OSV) |
| red hat:kernel-devel | 0:5.14.0-70.163.1.el9_0 · Red Hat:rhel_e4s:9.0::appstream | Package registry (OSV) |
| red hat:kernel-devel-matched | 0:5.14.0-70.163.1.el9_0 · Red Hat:rhel_e4s:9.0::appstream | Package registry (OSV) |
| red hat:kernel-doc | 0:5.14.0-70.163.1.el9_0 · Red Hat:rhel_e4s:9.0::appstream | 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.
No history yet (it accumulates with the daily EPSS job).
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 researchersFinders, 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).
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
- high · 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
- High
- Availability impact
- High
Weakness class (CWE)
CWE-416 · Use After FreeCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-secondary
Root cause
After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.
The bug in code
The whole CWE-416 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
free(dev->buf);
/* ... another thread is still running ... */
process(dev->buf);Fixed
lock(&dev->lock);
free(dev->buf);
dev->buf = NULL;
unlock(&dev->lock);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
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/2765749def4765c5052a4c66445cf4c96fcccdbc
- git.kernel.org/stable/c/63b2fe509f69b90168a75e04e14573dccf7984e6
- git.kernel.org/stable/c/893825289ba840afd86bfffcb6f7f363c73efff8
- git.kernel.org/stable/c/a853b7a3a9fd1d74a4ccdd9cd73512b7dace2f1e
- git.kernel.org/stable/c/b90ac60303063a43e17dd4aec159067599d255e6
- git.kernel.org/stable/c/ef0af7d08d26c5333ff4944a559279464edf6f15
- git.kernel.org/stable/c/f162f7c348fa2a5555bafdb5cc890b89b221e69c
Vendor advisories and official records. Exploit/PoC links are deliberately left out.