CVE-2021-47131
Last modified
CVE-2021-47131 is a high-severity vulnerability rated 7.8/10 on the CVSS scale. In the Linux kernel, the following vulnerability has been resolved: net/tls: Fix use-after-free after the TLS device goes down and up When a netdev with active TLS offload goes down, tls_device_down is called to stop the offload and tear down the TLS context. However, the socket stays alive, and it still points to the TLS context, which is now deallocated. EPSS estimates a 0.26% chance of exploitation in the next 30 days.
Description
In the Linux kernel, the following vulnerability has been resolved: net/tls: Fix use-after-free after the TLS device goes down and up When a netdev with active TLS offload goes down, tls_device_down is called to stop the offload and tear down the TLS context. However, the socket stays alive, and it still points to the TLS context, which is now deallocated. If a netdev goes up, while the connection is still active, and the data flow resumes after a number of TCP retransmissions, it will lead to a use-after-free of the TLS context. This commit addresses this bug by keeping the context alive until its normal destruction, and implements the necessary fallbacks, so that the connection can resume in software (non-offloaded) kTLS mode. On the TX side tls_sw_fallback is used to encrypt all packets. The RX side already has all the necessary fallbacks, because receiving non-decrypted packets is supported. The thing needed on the RX side is to block resync requests, which are normally produced after receiving non-decrypted packets. The necessary synchronization is implemented for a graceful teardown: first the fallbacks are deployed, then the driver resources are released (it used to be possible to have a tls_dev_resync after tls_dev_del). A new flag called TLS_RX_DEV_DEGRADED is added to indicate the fallback mode. It's used to skip the RX resync logic completely, as it becomes useless, and some objects may be released (for example, resync_async, which is allocated and freed by the driver).
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Linux | Linux Kernel | >= 4.18, < 5.10.43 | — |
| Linux | Linux Kernel | >= 5.11, < 5.12.10 | — |
| Linux | Linux Kernel | 5.13 | Rc1 |
References
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2021-47131?
How severe is CVE-2021-47131?
How do I fix CVE-2021-47131?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2021
- CVE-2021-47125In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2021-47126In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2021-47127In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2021-47128In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2021-47129In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2021-47130In the Linux kernel, the following vulnerability has been re…7.5
- CVE-2021-47132In the Linux kernel, the following vulnerability has been re…7.1
- CVE-2021-47133In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2021-47134In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2021-47135In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2021-47136In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2021-47137In the Linux kernel, the following vulnerability has been re…9.8
Are you affected by CVE-2021-47131?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
