CVE-2026-31533: net/tls: fix use-after-free in -EBUSY error path of tls_do_encryption
Noroxi assessment
Priority: Monitor (action score 39/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.39% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- According to CISA the attack is automatable: targets can be found by mass scanning.
- Fixed version: Linux Linux 02f3ecadb23558bbe068e6504118f1b712d4ece0, 0e43e0a3c94044acc74b8e0927c27972eb5a59e8, 2694d408b0e595024e0fc1d64ff9db0358580f74; azl3 kernel 6.6.134.1-2 on Azure Linux 3.0 6.6.137.1-1; cbl2 kernel 5.15.202.1-1 on CBL-Mariner 2.0 Release Notes.
Low priority for now. Upgrade to Linux Linux 02f3ecadb23558bbe068e6504118f1b712d4ece0, 0e43e0a3c94044acc74b8e0927c27972eb5a59e8, 2694d408b0e595024e0fc1d64ff9db0358580f74; azl3 kernel 6.6.134.1-2 on Azure Linux 3.0 6.6.137.1-1; cbl2 kernel 5.15.202.1-1 on CBL-Mariner 2.0 Release Notes 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/tls: fix use-after-free in -EBUSY error path of tls_do_encryption The -EBUSY handling in tls_do_encryption(), introduced by commit 859054147318 ("net: tls: handle backlogging of crypto requests"), has a use-after-free due to double cleanup of encrypt_pending and the scatterlist entry. When crypto_aead_encrypt() returns -EBUSY, the request is enqueued to the cryptd backlog and the async callback tls_encrypt_done() will be invoked upon completion. That callback unconditionally restores the scatterlist entry (sge->offset, sge->length) and decrements ctx->encrypt_pending. However, if tls_encrypt_async_wait() returns an error, the synchronous error path in tls_do_encryption() performs the same cleanup again, double-decrementing encrypt_pending and double-restoring the scatterlist. The double-decrement corrupts the encrypt_pending sentinel (initialized to 1), making tls_encrypt_async_wait() permanently skip the wait for pending async callbacks. A subsequent sendmsg can then free the tls_rec via bpf_exec_tx_verdict() while a cryptd callback is still pending, resulting in a use-after-free when the callback fires on the freed record. Fix this by skipping the synchronous cleanup when the -EBUSY async wait returns an error, since the callback has already handled encrypt_pending and sge restoration.
- BDU:2026-09717
- SUSE-SU-2026:22598-1
- SUSE-SU-2026:22673-1
- SUSE-SU-2026:22674-1
- SUSE-SU-2026:22675-1
- SUSE-SU-2026:22676-1
- SUSE-SU-2026:22677-1
- SUSE-SU-2026:22678-1
- SUSE-SU-2026:22680-1
- SUSE-SU-2026:22681-1
- SUSE-SU-2026:22682-1
- SUSE-SU-2026:22683-1
- SUSE-SU-2026:22684-1
- SUSE-SU-2026:22685-1
- SUSE-SU-2026:22686-1
- SUSE-SU-2026:22687-1
- SUSE-SU-2026:22689-1
- SUSE-SU-2026:22690-1
- SUSE-SU-2026:22691-1
- SUSE-SU-2026:22692-1
- Published
- Apr 23, 2026
- Updated
- Nov 10, 2026
- EPSS
- 0.3% · 34th percentile
- CWE
- CWE-416
Report tools
Action score
39
Monitor
Low priority for now.
- CVSS
- 39 / 40 · 9.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.3%
CISA SSVC decision
- Exploitation
- none
- Automatable
- yes
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 9.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.
Is your version affected? Check itNoroxi 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 kernel5.15.160 and later · before 5.15.203
- linux linux kernel6.1.84 and later · before 6.1.169
- linux linux kernel6.6.18 and later · before 6.6.135
- linux linux kernel6.7.6 and later · before 6.8
- linux linux kernel6.8.1 and later · before 6.12.82
- linux linux kernel6.13 and later · before 6.18.23
- linux linux kernel6.19 and later · before 6.19.13
- linux linux kernel7.0
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
- ab6397f072e5097f267abf5cb08a8004e6b17694, 6.8affected
- 3ade391adc584f17b5570fd205de3ad029090368 and later · before 414fc5e5a5aff776c150f1b86770e0a25a35df3aaffected · git
- cd1bbca03f3c1d845ce274c0d0a66de8e5929f72 and later · before 02f3ecadb23558bbe068e6504118f1b712d4ece0affected · git
- 13eca403876bbea3716e82cdfe6f1e6febb38754 and later · before 0e43e0a3c94044acc74b8e0927c27972eb5a59e8affected · git
- 8590541473188741055d27b955db0777569438e3 and later · before aa9facde6c5005205874c37db3fd25799d741bafaffected · git
- 8590541473188741055d27b955db0777569438e3 and later · before 5d70eb25b41e9b010828cd12818b06a0c3b04412affected · git
- 8590541473188741055d27b955db0777569438e3 and later · before 2694d408b0e595024e0fc1d64ff9db0358580f74affected · git
- 8590541473188741055d27b955db0777569438e3 and later · before a9b8b18364fffce4c451e6f6fd218fa4ab646705affected · git
- 5.15.160 and later · before 5.15.203affected · semver
- 6.1.84 and later · before 6.1.169affected · 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 6.1.170-1 | 6.1.170-1 |
| Debian:13 | linux | before 6.12.85-1 | 6.12.85-1 |
| Debian:14 | linux | before 6.19.13-1 | 6.19.13-1 |
| SUSE:Linux Enterprise Live Patching 15 SP4 | kernel-livepatch-SLE15-SP4_Update_41 | before 21-150400.2.1 | 21-150400.2.1 |
| SUSE:Linux Enterprise Live Patching 15 SP4 | kernel-livepatch-SLE15-SP4_Update_43 | before 17-150400.2.1 | 17-150400.2.1 |
| SUSE:Linux Enterprise Live Patching 15 SP4 | kernel-livepatch-SLE15-SP4_Update_44 | before 16-150400.2.1 | 16-150400.2.1 |
| SUSE:Linux Enterprise Live Patching 15 SP4 | kernel-livepatch-SLE15-SP4_Update_45 | before 14-150400.2.1 | 14-150400.2.1 |
| SUSE:Linux Enterprise Live Patching 15 SP4 | kernel-livepatch-SLE15-SP4_Update_46 | before 10-150400.2.1 | 10-150400.2.1 |
| SUSE:Linux Enterprise Live Patching 15 SP4 | kernel-livepatch-SLE15-SP4_Update_49 | before 6-150400.2.1 | 6-150400.2.1 |
| SUSE:Linux Enterprise Live Patching 15 SP4 | kernel-livepatch-SLE15-SP4_Update_51 | before 5-150400.2.1 | 5-150400.2.1 |
| SUSE:Linux Enterprise Live Patching 15 SP4 | kernel-livepatch-SLE15-SP4_Update_52 | before 4-150400.2.1 | 4-150400.2.1 |
| SUSE:Linux Enterprise Live Patching 15 SP5 | kernel-livepatch-SLE15-SP5_Update_27 | before 21-150500.2.2 | 21-150500.2.2 |
| SUSE:Linux Enterprise Live Patching 15 SP5 | kernel-livepatch-SLE15-SP5_Update_28 | before 20-150500.2.2 | 20-150500.2.2 |
| SUSE:Linux Enterprise Live Patching 15 SP5 | kernel-livepatch-SLE15-SP5_Update_30 | before 15-150500.2.2 | 15-150500.2.2 |
| SUSE:Linux Enterprise Live Patching 15 SP5 | kernel-livepatch-SLE15-SP5_Update_31 | before 13-150500.2.2 | 13-150500.2.2 |
| SUSE:Linux Enterprise Live Patching 15 SP5 | kernel-livepatch-SLE15-SP5_Update_37 | before 6-150500.2.2 | 6-150500.2.2 |
| SUSE:Linux Enterprise Live Patching 15 SP5 | kernel-livepatch-SLE15-SP5_Update_39 | before 4-150500.2.2 | 4-150500.2.2 |
| SUSE:Linux Enterprise Live Patching 15 SP6 | kernel-livepatch-SLE15-SP6_Update_12 | before 20-150600.2.2 | 20-150600.2.2 |
| SUSE:Linux Enterprise Live Patching 15 SP6 | kernel-livepatch-SLE15-SP6_Update_13 | before 18-150600.2.2 | 18-150600.2.2 |
| SUSE:Linux Enterprise Live Patching 15 SP6 | kernel-livepatch-SLE15-SP6_Update_22 | before 6-150600.2.2 | 6-150600.2.2 |
| SUSE:Linux Enterprise Live Patching 15 SP6 | kernel-livepatch-SLE15-SP6_Update_23 | before 5-150600.2.2 | 5-150600.2.2 |
| SUSE:Linux Enterprise Live Patching 15 SP6 | kernel-livepatch-SLE15-SP6_Update_25 | before 3-150600.2.2 | 3-150600.2.2 |
| SUSE:Linux Enterprise Live Patching 15 SP7 | kernel-livepatch-SLE15-SP7_Update_1 | before 19-150700.2.2 | 19-150700.2.2 |
| SUSE:Linux Enterprise Live Patching 15 SP7 | kernel-livepatch-SLE15-SP7_Update_10 | before 6-150700.2.2 | 6-150700.2.2 |
+59
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-2026-31531Apr 23, 2026 · ipv4: nexthop: allocate skb dynamically in rtm_get_nexthop()22Monitor
- ← EarlierCVE-2026-31532Apr 23, 2026 · can: raw: fix ro->uniq use-after-free in raw_rcv()31Monitor
- Later →CVE-2026-31536Apr 24, 2026 · smb: server: let send_done handle a completion without IB_SEND_SIGNALED39Monitor
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 | 02f3ecadb23558bbe068e6504118f1b712d4ece0 | Vendor (CNA) |
| Linux Linux | 0e43e0a3c94044acc74b8e0927c27972eb5a59e8 | Vendor (CNA) |
| Linux Linux | 2694d408b0e595024e0fc1d64ff9db0358580f74 | Vendor (CNA) |
| Linux Linux | 414fc5e5a5aff776c150f1b86770e0a25a35df3a | Vendor (CNA) |
| Linux Linux | 5.15.203 | Vendor (CNA) |
| Linux Linux | 5d70eb25b41e9b010828cd12818b06a0c3b04412 | Vendor (CNA) |
| Linux Linux | 6.1.169 | Vendor (CNA) |
| Linux Linux | 6.6.135 | Vendor (CNA) |
| Linux Linux | 6.8 | Vendor (CNA) |
| Linux Linux | a9b8b18364fffce4c451e6f6fd218fa4ab646705 | Vendor (CNA) |
| Linux Linux | aa9facde6c5005205874c37db3fd25799d741baf | Vendor (CNA) |
| azl3 kernel 6.6.134.1-2 on Azure Linux 3.0 | 6.6.137.1-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| cbl2 kernel 5.15.202.1-1 on CBL-Mariner 2.0 | Release Notes | Microsoft (MSRC) |
| debian:linux | 6.1.170-1 · Debian:12 | Package registry (OSV) |
| suse:kernel-livepatch-MICRO-6-0_Update_10 | 14-1.1 · SUSE:Linux Micro 6.1 | Package registry (OSV) |
| suse:kernel-livepatch-MICRO-6-0_Update_11 | 13-1.1 · SUSE:Linux Micro 6.1 | Package registry (OSV) |
| suse:kernel-livepatch-MICRO-6-0_Update_12 | 13-1.1 · SUSE:Linux Micro 6.1 | Package registry (OSV) |
| suse:kernel-livepatch-MICRO-6-0_Update_13 | 11-1.1 · SUSE:Linux Micro 6.1 | Package registry (OSV) |
| suse:kernel-livepatch-MICRO-6-0_Update_14 | 9-1.2 · SUSE:Linux Micro 6.1 | Package registry (OSV) |
| suse:kernel-livepatch-MICRO-6-0_Update_16 | 8-1.1 · SUSE:Linux Micro 6.1 | Package registry (OSV) |
| suse:kernel-livepatch-MICRO-6-0_Update_17 | 7-1.1 · SUSE:Linux Micro 6.1 | Package registry (OSV) |
| suse:kernel-livepatch-MICRO-6-0_Update_18 | 6-1.1 · SUSE:Linux Micro 6.1 | Package registry (OSV) |
| suse:kernel-livepatch-MICRO-6-0_Update_21 | 3-1.1 · SUSE:Linux Micro 6.1 | Package registry (OSV) |
| suse:kernel-livepatch-MICRO-6-0_Update_8 | 20-1.2 · SUSE:Linux Micro 6.1 | Package registry (OSV) |
| suse:kernel-livepatch-MICRO-6-0_Update_9 | 20-1.2 · SUSE:Linux Micro 6.1 | Package registry (OSV) |
| suse:kernel-livepatch-SLE16-RT_Update_9 | 4-160000.1.1 · SUSE:Linux Micro 6.2 | 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
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- 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
- Network
- Attack complexity
- Low
- Privileges required
- None
- 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:N/AC:L/PR:N/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
- SSVC exploitation— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (9 more)Show less
- git.kernel.org/stable/c/0e43e0a3c94044acc74b8e0927c27972eb5a59e8
- git.kernel.org/stable/c/2694d408b0e595024e0fc1d64ff9db0358580f74
- git.kernel.org/stable/c/414fc5e5a5aff776c150f1b86770e0a25a35df3a
- git.kernel.org/stable/c/5d70eb25b41e9b010828cd12818b06a0c3b04412
- git.kernel.org/stable/c/a9b8b18364fffce4c451e6f6fd218fa4ab646705
- git.kernel.org/stable/c/aa9facde6c5005205874c37db3fd25799d741baf
- cert-portal.siemens.com/productcert/html/ssa-019113.html
- cert-portal.siemens.com/productcert/html/ssa-082556.html
- cert-portal.siemens.com/productcert/html/ssa-457936.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.