CVE-2026-43056: Linux kernel · net: mana: fix use-after-free in add_adev() error path
Affects Linux kernelSource CVE Database V5
Not known to be exploited · CVSS 7.8 High · fixed in e5a75bf026c686b91a7dc6f9c5caf5016745d1fe : patch Linux kernel soon.
Data as of 26 Oct 2026, 14:18 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 1% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- CISA SSVC
- Exploitation
- No evidence of active exploitation and no public proof of concept
- Automatable
- Attackers cannot reliably automate steps 1–4 of the kill chain
- Technical impact
- Total control over the software or total information disclosure
CISA SSVC assessment, 2026-10-16.
- Patch
- Available – fixed in e5a75bf026c686b91a7dc6f9c5caf5016745d1fe, d88541ffd56d62a61e77209080001eddd4d69815, c4ea7d8907cf72b259bf70bd8c2e791e1c4ff70f +2
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 1 May 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
Description
In the Linux kernel, the following vulnerability has been resolved: net: mana: fix use-after-free in add_adev() error path If auxiliary_device_add() fails, add_adev() jumps to add_fail and calls auxiliary_device_uninit(adev). The auxiliary device has its release callback set to adev_release(), which frees the containing struct mana_adev. Since adev is embedded in struct mana_adev, the subsequent fall-through to init_fail and access to adev->id may result in a use-after-free. Fix this by saving the allocated auxiliary device id in a local variable before calling auxiliary_device_add(), and use that saved id in the cleanup path after auxiliary_device_uninit().
References
- git.kernel.org/stable/c/d88541ffd56d62a61e77209080001eddd4d69815 (opens in a new tab)
- git.kernel.org/stable/c/43f5b19fd190fea20d052bc84741b28031d5baa9 (opens in a new tab)
- git.kernel.org/stable/c/5f4061f8225d18695e5afe9bbf1cb7bd673d7872 (opens in a new tab)
- git.kernel.org/stable/c/e5a75bf026c686b91a7dc6f9c5caf5016745d1fe (opens in a new tab)
- git.kernel.org/stable/c/c4ea7d8907cf72b259bf70bd8c2e791e1c4ff70f (opens in a new tab)