CVE-2022-49958: net/sched: fix netdevice reference leaks in attach_default_qdiscs()
In the Linux kernel, the following vulnerability has been resolved:
net/sched: fix netdevice reference leaks in attach_default_qdiscs()
In attach_default_qdiscs(), if a dev has multiple queues and queue 0 fails
to attach qdisc because there is no memory in attach_one_default_qdisc().
Then dev->qdisc will be noop_qdisc by default. But the other queues may be
able to successfully attach to default qdisc.
In this case, the fallback to noqueue process will be triggered. If the
original attached qdisc is not released and a new one is directly
attached, this will cause netdevice reference leaks.
The following is the bug log:
veth0: default qdisc (fq_codel) fail, fallback to noqueue
unregister_netdevice: waiting for veth0 to become free. Usage count = 32
leaked reference.
qdisc_alloc+0x12e/0x210
qdisc_create_dflt+0x62/0x140
attach_one_default_qdisc.constprop.41+0x44/0x70
dev_activate+0x128/0x290
__dev_open+0x12a/0x190
__dev_change_flags+0x1a2/0x1f0
dev_change_flags+0x23/0x60
do_setlink+0x332/0x1150
__rtnl_newlink+0x52f/0x8e0
rtnl_newlink+0x43/0x70
rtnetlink_rcv_msg+0x140/0x3b0
netlink_rcv_skb+0x50/0x100
netlink_unicast+0x1bb/0x290
netlink_sendmsg+0x37c/0x4e0
sock_sendmsg+0x5f/0x70
____sys_sendmsg+0x208/0x280
Fix this bug by clearing any non-noop qdiscs that may have been assigned
before trying to re-attach.
Security readout for executives and security teams
Plain-English summary
This Linux kernel issue can leak network device references when default queue disciplines fail during setup and the fallback path replaces them. The visible impact is operational: network devices may not be freed cleanly, shown by unregister_netdevice waiting on leaked references. Public sources do not provide CVSS, exploitation evidence, or a named attacker path.
Executive priority
Handle through normal kernel maintenance unless logs show network device cleanup failures or affected hosts are critical. There is no source-backed evidence of active exploitation or remote compromise, but unresolved kernel resource leaks can create reliability risk in high-churn networking environments.
Technical view
The bug is in net/sched attach_default_qdiscs(). If queue 0 fails qdisc attachment under memory pressure while other queues succeed, fallback to noqueue can attach over existing non-noop qdiscs without releasing them, leaking netdevice references. The upstream fix clears non-noop qdiscs before reattaching.
Likely exposure
Exposure is limited to Linux kernels matching the affected versions or vulnerable commits identified by CVE sources. The scenario involves multiqueue network devices, default qdisc attachment, and allocation failure. Distribution kernels may differ because of backports, so version checks alone are not enough.
Exploitation context
The source bundle does not show active exploitation, public exploit code, or KEV listing. The described trigger requires a qdisc attachment failure, apparently due to lack of memory, followed by fallback handling. Treat this as an availability and resource-leak concern unless vendor guidance says otherwise.
Researcher notes
Focus analysis on attach_default_qdiscs(), attach_one_default_qdisc(), fallback to noqueue, and reference lifecycle around non-noop qdiscs. The available evidence supports a reference leak fix, not a broader exploit primitive. CVSS, CWE, and precise distro impact are not provided in the bundle.
Mitigation direction
Update to a Linux kernel containing one of the referenced stable fixes.
Check distribution vendor advisories for backported fixes before relying on upstream version numbers.
Prioritize hosts with heavy virtual networking, containers, or frequent interface creation.
Monitor for unregister_netdevice waits or netdevice reference leak messages.
If patch status is unclear, request vendor confirmation for CVE-2022-49958.
Validation and detection
Inventory Linux kernel versions and vendor build identifiers across affected fleets.
Compare installed kernels with distribution advisories and referenced upstream stable commits.
Review kernel logs for qdisc fallback and leaked reference messages.
Identify systems using multiqueue virtual or physical network devices.
Confirm patched systems no longer report netdevice unregister waits.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2022-49958 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
0CVSS vectors
3Timeline events
0ADP providers
5Source links
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
CVE publishedCVE Program
The CVE record was published.
Jun 18, 2025, 11:00 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.