CVE-2023-52767
published 2024-05-21CVE-2023-52767: In the Linux kernel, the following vulnerability has been resolved: tls: fix NULL deref on tls_sw_splice_eof() with empty record syzkaller discovered that if…
PriorityP420medium5.5CVSS 3.1
AVLACLPRLUINSUCNINAH
EPSS
0.17%
6.8th percentile
In the Linux kernel, the following vulnerability has been resolved:
tls: fix NULL deref on tls_sw_splice_eof() with empty record
syzkaller discovered that if tls_sw_splice_eof() is executed as part of
sendfile() when the plaintext/ciphertext sk_msg are empty, the send path
gets confused because the empty ciphertext buffer does not have enough
space for the encryption overhead. This causes tls_push_record() to go on
the `split = true` path (which is only supposed to be used when interacting
with an attached BPF program), and then get further confused and hit the
tls_merge_open_record() path, which then assumes that there must be at
least one populated buffer element, leading to a NULL deref.
It is possible to have empty plaintext/ciphertext buffers if we previously
bailed from tls_sw_sendmsg_locked() via the tls_trim_both_msgs() path.
tls_sw_push_pending_record() already handles this case correctly; let's do
the same check in tls_sw_splice_eof().
Affected
10 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | linux | < linux 6.1.82-1 (bookworm) | linux 6.1.82-1 (bookworm) |
| linux | linux | — | — |
| linux | linux | >= 5ad627faed136089e27bcd15e0c33760e575c8c3 < 944900fe2736c07288efe2d9394db4d3ca23f2c9 | 944900fe2736c07288efe2d9394db4d3ca23f2c9 |
| linux | linux | >= df720d288dbb1793e82b6ccbfc670ec871e9def4 < 2214e2bb5489145aba944874d0ee1652a0a63dc8 | 2214e2bb5489145aba944874d0ee1652a0a63dc8 |
| linux | linux | >= df720d288dbb1793e82b6ccbfc670ec871e9def4 < 53f2cb491b500897a619ff6abd72f565933760f0 | 53f2cb491b500897a619ff6abd72f565933760f0 |
| linux | linux_kernel | — | — |
| linux | linux_kernel | >= 0 < 6.1.82-1 | 6.1.82-1 |
| linux | linux_kernel | >= 0 < 6.6.8-1 | 6.6.8-1 |
| linux | linux_kernel | >= 0 < 6.6.8-1 | 6.6.8-1 |
| linux | linux_kernel | >= 6.5 < 6.6.4 | 6.6.4 |
CVSS provenance
nvdv3.15.5MEDIUMCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
osv5.5MEDIUM
vendor_debian5.5MEDIUM
vendor_redhat5.5MEDIUM
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
Red Hat
kernel: tls: fix NULL deref on tls_sw_splice_eof() with empty record
vendor_redhat·2024-05-21·CVSS 5.5
CVE-2023-52767 [MEDIUM] CWE-476 kernel: tls: fix NULL deref on tls_sw_splice_eof() with empty record
kernel: tls: fix NULL deref on tls_sw_splice_eof() with empty record
In the Linux kernel, the following vulnerability has been resolved:
tls: fix NULL deref on tls_sw_splice_eof() with empty record
syzkaller discovered that if tls_sw_splice_eof() is executed as part of
sendfile() when the plaintext/ciphertext sk_msg are empty, the send path
gets confused because the empty ciphertext buffer does not have enough
space for the encryption overhead. This causes tls_push_record() to go on
the `split = true` path (which is only supposed to be used when interacting
with an attached BPF program), and then get further confused and hit the
tls_merge_open_record() path, which then assumes that there must be at
least one populated buffer element, leading to a NULL deref.
It is possible to have empty p
Debian
CVE-2023-52767: linux - In the Linux kernel, the following vulnerability has been resolved: tls: fix NU...
vendor_debian·2023·CVSS 5.5
CVE-2023-52767 [MEDIUM] CVE-2023-52767: linux - In the Linux kernel, the following vulnerability has been resolved: tls: fix NU...
In the Linux kernel, the following vulnerability has been resolved: tls: fix NULL deref on tls_sw_splice_eof() with empty record syzkaller discovered that if tls_sw_splice_eof() is executed as part of sendfile() when the plaintext/ciphertext sk_msg are empty, the send path gets confused because the empty ciphertext buffer does not have enough space for the encryption overhead. This causes tls_push_record() to go on the `split = true` path (which is only supposed to be used when interacting with an attached BPF program), and then get further confused and hit the tls_merge_open_record() path, which then assumes that there must be at least one populated buffer element, leading to a NULL deref. It is possible to have empty plaintext/ciphertext buffers if we previously bailed from tls_sw_sendms
GHSA
GHSA-vr35-f6m3-rh89: In the Linux kernel, the following vulnerability has been resolved:
tls: fix NULL deref on tls_sw_splice_eof() with empty record
syzkaller discovere
ghsa_unreviewed·2024-05-21
CVE-2023-52767 [MEDIUM] CWE-476 GHSA-vr35-f6m3-rh89: In the Linux kernel, the following vulnerability has been resolved:
tls: fix NULL deref on tls_sw_splice_eof() with empty record
syzkaller discovere
In the Linux kernel, the following vulnerability has been resolved:
tls: fix NULL deref on tls_sw_splice_eof() with empty record
syzkaller discovered that if tls_sw_splice_eof() is executed as part of
sendfile() when the plaintext/ciphertext sk_msg are empty, the send path
gets confused because the empty ciphertext buffer does not have enough
space for the encryption overhead. This causes tls_push_record() to go on
the `split = true` path (which is only supposed to be used when interacting
with an attached BPF program), and then get further confused and hit the
tls_merge_open_record() path, which then assumes that there must be at
least one populated buffer element, leading to a NULL deref.
It is possible to have empty plaintext/ciphertext buffers if we previously
bailed from tls_sw_sen
OSV
CVE-2023-52767: In the Linux kernel, the following vulnerability has been resolved: tls: fix NULL deref on tls_sw_splice_eof() with empty record syzkaller discovered
osv·2024-05-21·CVSS 5.5
CVE-2023-52767 [MEDIUM] CVE-2023-52767: In the Linux kernel, the following vulnerability has been resolved: tls: fix NULL deref on tls_sw_splice_eof() with empty record syzkaller discovered
In the Linux kernel, the following vulnerability has been resolved: tls: fix NULL deref on tls_sw_splice_eof() with empty record syzkaller discovered that if tls_sw_splice_eof() is executed as part of sendfile() when the plaintext/ciphertext sk_msg are empty, the send path gets confused because the empty ciphertext buffer does not have enough space for the encryption overhead. This causes tls_push_record() to go on the `split = true` path (which is only supposed to be used when interacting with an attached BPF program), and then get further confused and hit the tls_merge_open_record() path, which then assumes that there must be at least one populated buffer element, leading to a NULL deref. It is possible to have empty plaintext/ciphertext buffers if we previously bailed from tls_sw_sendms
No detection rules found.
No public exploits indexed.
https://git.kernel.org/stable/c/2214e2bb5489145aba944874d0ee1652a0a63dc8https://git.kernel.org/stable/c/53f2cb491b500897a619ff6abd72f565933760f0https://git.kernel.org/stable/c/944900fe2736c07288efe2d9394db4d3ca23f2c9https://git.kernel.org/stable/c/2214e2bb5489145aba944874d0ee1652a0a63dc8https://git.kernel.org/stable/c/53f2cb491b500897a619ff6abd72f565933760f0https://git.kernel.org/stable/c/944900fe2736c07288efe2d9394db4d3ca23f2c9
2024-05-21
Published