CVE-2022-49450
published 2025-02-26CVE-2022-49450: In the Linux kernel, the following vulnerability has been resolved: rxrpc: Fix listen() setting the bar too high for the prealloc rings AF_RXRPC's listen()…
PriorityP419medium5.5CVSS 3.1
AVLACLPRLUINSUCNINAH
EPSS
0.29%
21.3th percentile
In the Linux kernel, the following vulnerability has been resolved:
rxrpc: Fix listen() setting the bar too high for the prealloc rings
AF_RXRPC's listen() handler lets you set the backlog up to 32 (if you bump
up the sysctl), but whilst the preallocation circular buffers have 32 slots
in them, one of them has to be a dead slot because we're using CIRC_CNT().
This means that listen(rxrpc_sock, 32) will cause an oops when the socket
is closed because rxrpc_service_prealloc_one() allocated one too many calls
and rxrpc_discard_prealloc() won't then be able to get rid of them because
it'll think the ring is empty. rxrpc_release_calls_on_socket() then tries
to abort them, but oopses because call->peer isn't yet set.
Fix this by setting the maximum backlog to RXRPC_BACKLOG_MAX - 1 to match
the ring capacity.
BUG: kernel NULL pointer dereference, address: 0000000000000086
...
RIP: 0010:rxrpc_send_abort_packet+0x73/0x240 [rxrpc]
Call Trace:
? __wake_up_common_lock+0x7a/0x90
? rxrpc_notify_socket+0x8e/0x140 [rxrpc]
? rxrpc_abort_call+0x4c/0x60 [rxrpc]
rxrpc_release_calls_on_socket+0x107/0x1a0 [rxrpc]
rxrpc_release+0xc9/0x1c0 [rxrpc]
__sock_release+0x37/0xa0
sock_close+0x11/0x20
__fput+0x89/0x240
task_work_run+0x59/0x90
do_exit+0x319/0xaa0
Affected
23 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | linux | < linux 5.18.5-1 (bookworm) | linux 5.18.5-1 (bookworm) |
| linux | linux | — | — |
| linux | linux | >= 00e907127e6f86d0f9b122d9b4347a8aa09a8b61 < 61fb38cfbb1d54d3dafd0c25752f684b3cd00b32 | 61fb38cfbb1d54d3dafd0c25752f684b3cd00b32 |
| linux | linux | >= 00e907127e6f86d0f9b122d9b4347a8aa09a8b61 < 616f76498d5ddf26b997caf64a95cda3c8a55533 | 616f76498d5ddf26b997caf64a95cda3c8a55533 |
| linux | linux | >= 00e907127e6f86d0f9b122d9b4347a8aa09a8b61 < 4a3a78b7918bdd723d8c7c9786522ca969bffcc4 | 4a3a78b7918bdd723d8c7c9786522ca969bffcc4 |
| linux | linux | >= 00e907127e6f86d0f9b122d9b4347a8aa09a8b61 < 91b34bf0409f43bb60453bab23c5beadd726d022 | 91b34bf0409f43bb60453bab23c5beadd726d022 |
| linux | linux | >= 00e907127e6f86d0f9b122d9b4347a8aa09a8b61 < 5b4826657d36c218e9f08e8d3223b0edce3de88f | 5b4826657d36c218e9f08e8d3223b0edce3de88f |
| linux | linux | >= 00e907127e6f86d0f9b122d9b4347a8aa09a8b61 < b3a9b227d5e7467b8518160ff034ea22bb9de573 | b3a9b227d5e7467b8518160ff034ea22bb9de573 |
| linux | linux | >= 00e907127e6f86d0f9b122d9b4347a8aa09a8b61 < 369de57492c4f1a42563c5a3bd365822ca3bfc79 | 369de57492c4f1a42563c5a3bd365822ca3bfc79 |
| linux | linux | >= 00e907127e6f86d0f9b122d9b4347a8aa09a8b61 < e198f1930050e3115c80b67d9249f80f98a27c67 | e198f1930050e3115c80b67d9249f80f98a27c67 |
| linux | linux | >= 00e907127e6f86d0f9b122d9b4347a8aa09a8b61 < 88e22159750b0d55793302eeed8ee603f5c1a95c | 88e22159750b0d55793302eeed8ee603f5c1a95c |
| linux | linux_kernel | >= 0 < 5.10.127-1 | 5.10.127-1 |
| linux | linux_kernel | >= 0 < 5.18.5-1 | 5.18.5-1 |
| linux | linux_kernel | >= 0 < 5.18.5-1 | 5.18.5-1 |
| linux | linux_kernel | >= 0 < 5.18.5-1 | 5.18.5-1 |
| linux | linux_kernel | >= 4.10 < 4.14.283 | 4.14.283 |
| linux | linux_kernel | >= 4.15 < 4.19.247 | 4.19.247 |
| linux | linux_kernel | >= 4.20 < 5.4.198 | 5.4.198 |
| linux | linux_kernel | >= 4.9 < 4.9.318 | 4.9.318 |
| linux | linux_kernel | >= 5.11 < 5.15.46 | 5.15.46 |
| linux | linux_kernel | >= 5.16 < 5.17.14 | 5.17.14 |
| linux | linux_kernel | >= 5.18 < 5.18.3 | 5.18.3 |
| linux | linux_kernel | >= 5.5 < 5.10.121 | 5.10.121 |
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.
GHSA
GHSA-fcw8-q8jr-pq38: In the Linux kernel, the following vulnerability has been resolved:
rxrpc: Fix listen() setting the bar too high for the prealloc rings
AF_RXRPC's l
ghsa_unreviewed·2025-03-17
CVE-2022-49450 [MEDIUM] CWE-476 GHSA-fcw8-q8jr-pq38: In the Linux kernel, the following vulnerability has been resolved:
rxrpc: Fix listen() setting the bar too high for the prealloc rings
AF_RXRPC's l
In the Linux kernel, the following vulnerability has been resolved:
rxrpc: Fix listen() setting the bar too high for the prealloc rings
AF_RXRPC's listen() handler lets you set the backlog up to 32 (if you bump
up the sysctl), but whilst the preallocation circular buffers have 32 slots
in them, one of them has to be a dead slot because we're using CIRC_CNT().
This means that listen(rxrpc_sock, 32) will cause an oops when the socket
is closed because rxrpc_service_prealloc_one() allocated one too many calls
and rxrpc_discard_prealloc() won't then be able to get rid of them because
it'll think the ring is empty. rxrpc_release_calls_on_socket() then tries
to abort them, but oopses because call->peer isn't yet set.
Fix this by setting the maximum backlog to RXRPC_BACKLOG_MAX - 1 to match
t
OSV
CVE-2022-49450: In the Linux kernel, the following vulnerability has been resolved: rxrpc: Fix listen() setting the bar too high for the prealloc rings AF_RXRPC's lis
osv·2025-02-26·CVSS 5.5
CVE-2022-49450 [MEDIUM] CVE-2022-49450: In the Linux kernel, the following vulnerability has been resolved: rxrpc: Fix listen() setting the bar too high for the prealloc rings AF_RXRPC's lis
In the Linux kernel, the following vulnerability has been resolved: rxrpc: Fix listen() setting the bar too high for the prealloc rings AF_RXRPC's listen() handler lets you set the backlog up to 32 (if you bump up the sysctl), but whilst the preallocation circular buffers have 32 slots in them, one of them has to be a dead slot because we're using CIRC_CNT(). This means that listen(rxrpc_sock, 32) will cause an oops when the socket is closed because rxrpc_service_prealloc_one() allocated one too many calls and rxrpc_discard_prealloc() won't then be able to get rid of them because it'll think the ring is empty. rxrpc_release_calls_on_socket() then tries to abort them, but oopses because call->peer isn't yet set. Fix this by setting the maximum backlog to RXRPC_BACKLOG_MAX - 1 to match the r
Red Hat
kernel: rxrpc: Fix listen() setting the bar too high for the prealloc rings
vendor_redhat·2025-02-26·CVSS 5.5
CVE-2022-49450 [MEDIUM] CWE-476 kernel: rxrpc: Fix listen() setting the bar too high for the prealloc rings
kernel: rxrpc: Fix listen() setting the bar too high for the prealloc rings
In the Linux kernel, the following vulnerability has been resolved:
rxrpc: Fix listen() setting the bar too high for the prealloc rings
AF_RXRPC's listen() handler lets you set the backlog up to 32 (if you bump
up the sysctl), but whilst the preallocation circular buffers have 32 slots
in them, one of them has to be a dead slot because we're using CIRC_CNT().
This means that listen(rxrpc_sock, 32) will cause an oops when the socket
is closed because rxrpc_service_prealloc_one() allocated one too many calls
and rxrpc_discard_prealloc() won't then be able to get rid of them because
it'll think the ring is empty. rxrpc_release_calls_on_socket() then tries
to abort them, but oopses because call->peer isn't yet set.
Fi
Debian
CVE-2022-49450: linux - In the Linux kernel, the following vulnerability has been resolved: rxrpc: Fix ...
vendor_debian·2022·CVSS 5.5
CVE-2022-49450 [MEDIUM] CVE-2022-49450: linux - In the Linux kernel, the following vulnerability has been resolved: rxrpc: Fix ...
In the Linux kernel, the following vulnerability has been resolved: rxrpc: Fix listen() setting the bar too high for the prealloc rings AF_RXRPC's listen() handler lets you set the backlog up to 32 (if you bump up the sysctl), but whilst the preallocation circular buffers have 32 slots in them, one of them has to be a dead slot because we're using CIRC_CNT(). This means that listen(rxrpc_sock, 32) will cause an oops when the socket is closed because rxrpc_service_prealloc_one() allocated one too many calls and rxrpc_discard_prealloc() won't then be able to get rid of them because it'll think the ring is empty. rxrpc_release_calls_on_socket() then tries to abort them, but oopses because call->peer isn't yet set. Fix this by setting the maximum backlog to RXRPC_BACKLOG_MAX - 1 to match the r
No detection rules found.
No public exploits indexed.
https://git.kernel.org/stable/c/369de57492c4f1a42563c5a3bd365822ca3bfc79https://git.kernel.org/stable/c/4a3a78b7918bdd723d8c7c9786522ca969bffcc4https://git.kernel.org/stable/c/5b4826657d36c218e9f08e8d3223b0edce3de88fhttps://git.kernel.org/stable/c/616f76498d5ddf26b997caf64a95cda3c8a55533https://git.kernel.org/stable/c/61fb38cfbb1d54d3dafd0c25752f684b3cd00b32https://git.kernel.org/stable/c/88e22159750b0d55793302eeed8ee603f5c1a95chttps://git.kernel.org/stable/c/91b34bf0409f43bb60453bab23c5beadd726d022https://git.kernel.org/stable/c/b3a9b227d5e7467b8518160ff034ea22bb9de573https://git.kernel.org/stable/c/e198f1930050e3115c80b67d9249f80f98a27c67
2025-02-26
Published