Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2024-26800: tls: fix use-after-free on failed backlog decryption

HighCVSS 7.8 · v3.1—No exploit Fix available

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.74% (FIRST EPSS); higher than 55.2% of all records.
  • 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 13114dc5543069f7b97991e3b79937b6da05f5b0, 1ac9fb84bc7ecd4bc6428118301d9d864d2a58d1, 5.16; cbl2 kernel 5.15.202.1-1 on CBL-Mariner 2.0 Release Notes.
  • Severity is disputed: the assigning authority (CNA) scores it 9.8, NVD 7.8.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 13114dc5543069f7b97991e3b79937b6da05f5b0, 1ac9fb84bc7ecd4bc6428118301d9d864d2a58d1, 5.16; 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: tls: fix use-after-free on failed backlog decryption When the decrypt request goes to the backlog and crypto_aead_decrypt returns -EBUSY, tls_do_decryption will wait until all async decryptions have completed. If one of them fails, tls_do_decryption will return -EBADMSG and tls_decrypt_sg jumps to the error path, releasing all the pages. But the pages have been passed to the async callback, and have already been released by tls_decrypt_done. The only true async case is when crypto_aead_decrypt returns -EINPROGRESS. With -EBUSY, we already waited so we can tell tls_sw_recvmsg that the data is available for immediate copy, but we need to notify tls_decrypt_sg (via the new ->async_done flag) that the memory has already been released.

Published
Apr 4, 2024
Updated
Aug 5, 2026
EPSS
0.7% · 55th percentile

Report tools

JSON

Action score

31

Monitor

Low priority for now.

CVSS
31 / 40 · 7.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.7%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
7.8
CNA · Linux
9.8
2.0 point gap

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

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-2024-26800

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 every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • 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, at most 30 a day (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.

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.

VendorProduct
linuxlinux 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.16
  • linux linux kernel6.6.18 and later · before 6.6.21
  • linux linux kernel6.7.6 and later · before 6.7.9
  • linux linux kernel6.8

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

    • 3ade391adc584f17b5570fd205de3ad029090368affected
    • cd1bbca03f3c1d845ce274c0d0a66de8e5929f72 and later · before f2b85a4cc763841843de693bbd7308fe9a2c4c89affected · git
    • 13eca403876bbea3716e82cdfe6f1e6febb38754 and later · before 81be85353b0f5a7b660635634b655329b429eefeaffected · git
    • ab6397f072e5097f267abf5cb08a8004e6b17694 and later · before 1ac9fb84bc7ecd4bc6428118301d9d864d2a58d1affected · git
    • 8590541473188741055d27b955db0777569438e3 and later · before 13114dc5543069f7b97991e3b79937b6da05f5b0affected · git
    • 5.15.160 and later · before 5.16affected · semver
    • 6.6.18 and later · before 6.6.21affected · semver
    • 6.7.6 and later · before 6.7.9affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.85-16.1.85-1
Debian:13linuxbefore 6.7.9-16.7.9-1
SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSSkernel-64kbbefore 5.3.18-150300.59.170.15.3.18-150300.59.170.1
SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSSkernel-default-basebefore 5.3.18-150300.59.170.1.150300.18.100.15.3.18-150300.59.170.1.150300.18.100.1
SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSSkernel-docsbefore 5.3.18-150300.59.170.25.3.18-150300.59.170.2
SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSSkernel-obs-buildbefore 5.3.18-150300.59.170.15.3.18-150300.59.170.1
SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSSkernel-preemptbefore 5.3.18-150300.59.170.15.3.18-150300.59.170.1
SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSSkernel-sourcebefore 5.3.18-150300.59.170.15.3.18-150300.59.170.1
SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSSkernel-symsbefore 5.3.18-150300.59.170.15.3.18-150300.59.170.1
SUSE:Linux Enterprise Live Patching 15 SP3kernel-defaultbefore 5.3.18-150300.59.170.15.3.18-150300.59.170.1
SUSE:Linux Enterprise Live Patching 15 SP3kernel-livepatch-SLE15-SP3_Update_47before 1-150300.7.3.11-150300.7.3.1
SUSE:Linux Enterprise Micro 5.1kernel-rtbefore 5.3.18-150300.178.15.3.18-150300.178.1
SUSE:Linux Enterprise Micro 5.1kernel-source-rtbefore 5.3.18-150300.178.15.3.18-150300.178.1
SUSE:Linux Enterprise Server 15 SP3-LTSSkernel-zfcpdumpbefore 5.3.18-150300.59.170.15.3.18-150300.59.170.1

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • 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…KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2024-26797Apr 4, 2024 · drm/amd/display: Prevent potential buffer overflow in map_hw_resources
    31Monitor
  • ← EarlierCVE-2024-26798Apr 4, 2024 · fbcon: always restore the old font data in fbcon_do_set_font()
    22Monitor
  • Later →CVE-2024-26801Apr 4, 2024 · Bluetooth: Avoid potential use-after-free in hci_error_reset
    22Monitor

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 Linux13114dc5543069f7b97991e3b79937b6da05f5b0Vendor (CNA)
Linux Linux1ac9fb84bc7ecd4bc6428118301d9d864d2a58d1Vendor (CNA)
Linux Linux5.16Vendor (CNA)
Linux Linux6.6.21Vendor (CNA)
Linux Linux6.7.9Vendor (CNA)
Linux Linux81be85353b0f5a7b660635634b655329b429eefeVendor (CNA)
Linux Linuxf2b85a4cc763841843de693bbd7308fe9a2c4c89Vendor (CNA)
cbl2 kernel 5.15.202.1-1 on CBL-Mariner 2.0Release NotesMicrosoft (MSRC)
debian:linux6.1.85-1 · Debian:12Package registry (OSV)
suse:kernel-64kb5.3.18-150300.59.170.1 · SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSSPackage registry (OSV)
suse:kernel-default5.3.18-150300.59.170.1 · SUSE:Linux Enterprise Live Patching 15 SP3Package registry (OSV)
suse:kernel-default-base5.3.18-150300.59.170.1.150300.18.100.1 · SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSSPackage registry (OSV)
suse:kernel-docs5.3.18-150300.59.170.2 · SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSSPackage registry (OSV)
suse:kernel-livepatch-SLE15-SP3_Update_471-150300.7.3.1 · SUSE:Linux Enterprise Live Patching 15 SP3Package registry (OSV)
suse:kernel-obs-build5.3.18-150300.59.170.1 · SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSSPackage registry (OSV)
suse:kernel-preempt5.3.18-150300.59.170.1 · SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSSPackage registry (OSV)
suse:kernel-rt5.3.18-150300.178.1 · SUSE:Linux Enterprise Micro 5.1Package registry (OSV)
suse:kernel-source5.3.18-150300.59.170.1 · SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSSPackage registry (OSV)
suse:kernel-source-rt5.3.18-150300.178.1 · SUSE:Linux Enterprise Micro 5.1Package registry (OSV)
suse:kernel-syms5.3.18-150300.59.170.1 · SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSSPackage registry (OSV)
suse:kernel-zfcpdump5.3.18-150300.59.170.1 · SUSE:Linux Enterprise Server 15 SP3-LTSSPackage 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.

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

CVSS vector

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

nvd-primary

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.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

c
free(dev->buf);/* ... another thread is still running ... */process(dev->buf);

Fixed

c
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

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records