CVE-2025-21693
mm: zswap: properly synchronize freeing resources during CPU hotunplug
In the Linux kernel, the following vulnerability has been resolved:
mm: zswap: properly synchronize freeing resources during CPU hotunplug
In zswap_compress() and zswap_decompress(), the per-CPU acomp_ctx of the current CPU at the beginning of the operation is retrieved and used throughout. However, since neither preemption nor migration are disabled, it is possible that the operation continues on a different CPU.
If the original CPU is hotunplugged while the acomp_ctx is still in use, we run into a UAF bug as some of the resources attached to the acomp_ctx are freed during hotunplug in zswap_cpu_comp_dead() (i.e. acomp_ctx.buffer, acomp_ctx.req, or acomp_ctx.acomp).
The problem was introduced in commit 1ec3b5fe6eec ("mm/zswap: move to use crypto_acomp API for hardware acceleration") when the switch to the crypto_acomp API was made. Prior to that, the per-CPU crypto_comp was retrieved using get_cpu_ptr() which disables preemption and makes sure the CPU cannot go away from under us. Preemption cannot be disabled with the crypto_acomp API as a sleepable context is needed.
Use the acomp_ctx.mutex to synchronize CPU hotplug callbacks allocating and freeing resources with compression/decompression paths. Make sure that acomp_ctx.req is NULL when the resources are freed. In the compression/decompression paths, check if acomp_ctx.req is NULL after acquiring the mutex (meaning the CPU was offlined) and retry on the new CPU.
The initialization of acomp_ctx.mutex is moved from the CPU hotplug callback to the pool initialization where it belongs (where the mutex is allocated). In addition to adding clarity, this makes sure that CPU hotplug cannot reinitialize a mutex that is already locked by compression/decompression.
Previously a fix was attempted by holding cpus_read_lock() [1]. This would have caused a potential deadlock as it is possible for code already holding the lock to fall into reclaim and enter zswap (causing a deadlock). A fix was also attempted using SRCU for synchronization, but Johannes pointed out that synchronize_srcu() cannot be used in CPU hotplug notifiers [2].
Alternative fixes that were considered/attempted and could have worked:
- Refcounting the per-CPU acomp_ctx. This involves complexity in handling the race between the refcount dropping to zero in zswap_[de]compress() and the refcount being re-initialized when the CPU is onlined.
- Disabling migration before getting the per-CPU acomp_ctx [3], but that's discouraged and is a much bigger hammer than needed, and could result in subtle performance issues.
[1]https://lkml.kernel.org/[email protected]/ [2]https://lkml.kernel.org/[email protected]/ [3]https://lkml.kernel.org/[email protected]/
[[email protected]: remove comment]
Attack profile
How easy it is to exploit
- Attack vector
- Local
- Complexity
- Low
- Privileges needed
- Low
- User interaction
- None
What an attacker can affect
- Confidentiality
- High
- Integrity
- High
- Availability
- High
Exploit likelihood
What each source reports
CVE List Score used
7.8
mm: zswap: properly synchronize freeing resources during CPU hotunplug
In the Linux kernel, the following vulnerability has been resolved:
mm: zswap: properly synchronize freeing resources during CPU hotunplug
In zswap_compress() and zswap_decompress(), the per-CPU acomp_ctx of the current CPU at the beginning of the operation is retrieved and used throughout. However, since neither preemption nor migration are disabled, it is possible that the operation continues on a different CPU.
If the original CPU is hotunplugged while the acomp_ctx is still in use, we run into a UAF bug as some of the resources attached to the acomp_ctx are freed during hotunplug in zswap_cpu_comp_dead() (i.e. acomp_ctx.buffer, acomp_ctx.req, or acomp_ctx.acomp).
The problem was introduced in commit 1ec3b5fe6eec ("mm/zswap: move to use crypto_acomp API for hardware acceleration") when the switch to the crypto_acomp API was made. Prior to that, the per-CPU crypto_comp was retrieved using get_cpu_ptr() which disables preemption and makes sure the CPU cannot go away from under us. Preemption cannot be disabled with the crypto_acomp API as a sleepable context is needed.
Use the acomp_ctx.mutex to synchronize CPU hotplug callbacks allocating and freeing resources with compression/decompression paths. Make sure that acomp_ctx.req is NULL when the resources are freed. In the compression/decompression paths, check if acomp_ctx.req is NULL after acquiring the mutex (meaning the CPU was offlined) and retry on the new CPU.
The initialization of acomp_ctx.mutex is moved from the CPU hotplug callback to the pool initialization where it belongs (where the mutex is allocated). In addition to adding clarity, this makes sure that CPU hotplug cannot reinitialize a mutex that is already locked by compression/decompression.
Previously a fix was attempted by holding cpus_read_lock() [1]. This would have caused a potential deadlock as it is possible for code already holding the lock to fall into reclaim and enter zswap (causing a deadlock). A fix was also attempted using SRCU for synchronization, but Johannes pointed out that synchronize_srcu() cannot be used in CPU hotplug notifiers [2].
Alternative fixes that were considered/attempted and could have worked:
- Refcounting the per-CPU acomp_ctx. This involves complexity in handling the race between the refcount dropping to zero in zswap_[de]compress() and the refcount being re-initialized when the CPU is onlined.
- Disabling migration before getting the per-CPU acomp_ctx [3], but that's discouraged and is a much bigger hammer than needed, and could result in subtle performance issues.
[1]https://lkml.kernel.org/[email protected]/ [2]https://lkml.kernel.org/[email protected]/ [3]https://lkml.kernel.org/[email protected]/
[[email protected]: remove comment]
- Record
CVE-2025-21693- CVSS 3.1
- 7.8 High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H - Weakness
- CWE-416
- Updated
- 2026-11-02
EUVDEUVD-2025-2642
7.8
In the Linux kernel, the following vulnerability has been resolved:
mm: zswap: properly synchronize freeing resources during CPU hotunplug
In zswap_compress() and zswap_decompress(), the per-CPU acomp_ctx of the current CPU at the beginning of the operation is retrieved and used throughout. However, since neither preemption nor migration are disabled, it is possible that the operation continues on a different CPU.
If the original CPU is hotunplugged while the acomp_ctx is still in use, we run into a UAF bug as some of the resources attached to the acomp_ctx are freed during hotunplug in zswap_cpu_comp_dead() (i.e. acomp_ctx.buffer, acomp_ctx.req, or acomp_ctx.acomp).
The problem was introduced in commit 1ec3b5fe6eec ("mm/zswap: move to use crypto_acomp API for hardware acceleration") when the switch to the crypto_acomp API was made. Prior to that, the per-CPU crypto_comp was retrieved using get_cpu_ptr() which disables preemption and makes sure the CPU cannot go away from under us. Preemption cannot be disabled with the crypto_acomp API as a sleepable context is needed.
Use the acomp_ctx.mutex to synchronize CPU hotplug callbacks allocating and freeing resources with compression/decompression paths. Make sure that acomp_ctx.req is NULL when the resources are freed. In the compression/decompression paths, check if acomp_ctx.req is NULL after acquiring the mutex (meaning the CPU was offlined) and retry on the new CPU.
The initialization of acomp_ctx.mutex is moved from the CPU hotplug callback to the pool initialization where it belongs (where the mutex is allocated). In addition to adding clarity, this makes sure that CPU hotplug cannot reinitialize a mutex that is already locked by compression/decompression.
Previously a fix was attempted by holding cpus_read_lock() [1]. This would have caused a potential deadlock as it is possible for code already holding the lock to fall into reclaim and enter zswap (causing a deadlock). A fix was also attempted using SRCU for synchronization, but Johannes pointed out that synchronize_srcu() cannot be used in CPU hotplug notifiers [2].
Alternative fixes that were considered/attempted and could have worked:
- Refcounting the per-CPU acomp_ctx. This involves complexity in handling the race between the refcount dropping to zero in zswap_[de]compress() and the refcount being re-initialized when the CPU is onlined.
- Disabling migration before getting the per-CPU acomp_ctx [3], but that's discouraged and is a much bigger hammer than needed, and could result in subtle performance issues.
[1]https://lkml.kernel.org/[email protected]/ [2]https://lkml.kernel.org/[email protected]/ [3]https://lkml.kernel.org/[email protected]/
[[email protected]: remove comment]
- Record
EUVD-2025-2642- CVSS 3.1
- 7.8 High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H - Updated
- 2026-11-02
GitHub AdvisoriesGHSA-jqr2-rwpf-xrf3
7.8
In the Linux kernel, the following vulnerability has been resolved: mm: zswap: properly...
In the Linux kernel, the following vulnerability has been resolved:
mm: zswap: properly synchronize freeing resources during CPU hotunplug
In zswap_compress() and zswap_decompress(), the per-CPU acomp_ctx of the current CPU at the beginning of the operation is retrieved and used throughout. However, since neither preemption nor migration are disabled, it is possible that the operation continues on a different CPU.
If the original CPU is hotunplugged while the acomp_ctx is still in use, we run into a UAF bug as some of the resources attached to the acomp_ctx are freed during hotunplug in zswap_cpu_comp_dead() (i.e. acomp_ctx.buffer, acomp_ctx.req, or acomp_ctx.acomp).
The problem was introduced in commit 1ec3b5fe6eec ("mm/zswap: move to use crypto_acomp API for hardware acceleration") when the switch to the crypto_acomp API was made. Prior to that, the per-CPU crypto_comp was retrieved using get_cpu_ptr() which disables preemption and makes sure the CPU cannot go away from under us. Preemption cannot be disabled with the crypto_acomp API as a sleepable context is needed.
Use the acomp_ctx.mutex to synchronize CPU hotplug callbacks allocating and freeing resources with compression/decompression paths. Make sure that acomp_ctx.req is NULL when the resources are freed. In the compression/decompression paths, check if acomp_ctx.req is NULL after acquiring the mutex (meaning the CPU was offlined) and retry on the new CPU.
The initialization of acomp_ctx.mutex is moved from the CPU hotplug callback to the pool initialization where it belongs (where the mutex is allocated). In addition to adding clarity, this makes sure that CPU hotplug cannot reinitialize a mutex that is already locked by compression/decompression.
Previously a fix was attempted by holding cpus_read_lock() [1]. This would have caused a potential deadlock as it is possible for code already holding the lock to fall into reclaim and enter zswap (causing a deadlock). A fix was also attempted using SRCU for synchronization, but Johannes pointed out that synchronize_srcu() cannot be used in CPU hotplug notifiers [2].
Alternative fixes that were considered/attempted and could have worked:
- Refcounting the per-CPU acomp_ctx. This involves complexity in handling the race between the refcount dropping to zero in zswap_[de]compress() and the refcount being re-initialized when the CPU is onlined.
- Disabling migration before getting the per-CPU acomp_ctx [3], but that's discouraged and is a much bigger hammer than needed, and could result in subtle performance issues.
[1]https://lkml.kernel.org/[email protected]/ [2]https://lkml.kernel.org/[email protected]/ [3]https://lkml.kernel.org/[email protected]/
[[email protected]: remove comment] Link: https://lkml.kernel.org/r/CAJD7tkaxS1wjn+swugt8QCvQ-rVF5RZnjxwPGX17k8x9zSManA@mail.gmail.com
- Record
GHSA-jqr2-rwpf-xrf3- CVSS 3.1
- 7.8 High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H - Weakness
- CWE-416
- Updated
- 2026-11-02
NVD
7.8
In the Linux kernel, the following vulnerability has been resolved:
mm: zswap: properly synchronize freeing resources during CPU hotunplug
In zswap_compress() and zswap_decompress(), the per-CPU acomp_ctx of the current CPU at the beginning of the operation is retrieved and used throughout. However, since neither preemption nor migration are disabled, it is possible that the operation continues on a different CPU.
If the original CPU is hotunplugged while the acomp_ctx is still in use, we run into a UAF bug as some of the resources attached to the acomp_ctx are freed during hotunplug in zswap_cpu_comp_dead() (i.e. acomp_ctx.buffer, acomp_ctx.req, or acomp_ctx.acomp).
The problem was introduced in commit 1ec3b5fe6eec ("mm/zswap: move to use crypto_acomp API for hardware acceleration") when the switch to the crypto_acomp API was made. Prior to that, the per-CPU crypto_comp was retrieved using get_cpu_ptr() which disables preemption and makes sure the CPU cannot go away from under us. Preemption cannot be disabled with the crypto_acomp API as a sleepable context is needed.
Use the acomp_ctx.mutex to synchronize CPU hotplug callbacks allocating and freeing resources with compression/decompression paths. Make sure that acomp_ctx.req is NULL when the resources are freed. In the compression/decompression paths, check if acomp_ctx.req is NULL after acquiring the mutex (meaning the CPU was offlined) and retry on the new CPU.
The initialization of acomp_ctx.mutex is moved from the CPU hotplug callback to the pool initialization where it belongs (where the mutex is allocated). In addition to adding clarity, this makes sure that CPU hotplug cannot reinitialize a mutex that is already locked by compression/decompression.
Previously a fix was attempted by holding cpus_read_lock() [1]. This would have caused a potential deadlock as it is possible for code already holding the lock to fall into reclaim and enter zswap (causing a deadlock). A fix was also attempted using SRCU for synchronization, but Johannes pointed out that synchronize_srcu() cannot be used in CPU hotplug notifiers [2].
Alternative fixes that were considered/attempted and could have worked:
- Refcounting the per-CPU acomp_ctx. This involves complexity in handling the race between the refcount dropping to zero in zswap_[de]compress() and the refcount being re-initialized when the CPU is onlined.
- Disabling migration before getting the per-CPU acomp_ctx [3], but that's discouraged and is a much bigger hammer than needed, and could result in subtle performance issues.
[1]https://lkml.kernel.org/[email protected]/ [2]https://lkml.kernel.org/[email protected]/ [3]https://lkml.kernel.org/[email protected]/
[[email protected]: remove comment]
- Record
CVE-2025-21693- CVSS 3.1
- 7.8 High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H - Weakness
- CWE-416
- Updated
- 2026-11-02
OSVBELL-CVE-2025-21693
7.8
- Record
BELL-CVE-2025-21693- CVSS 3.1
- 7.8 High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H - Updated
- 2026-11-02
OSV
7.8
mm: zswap: properly synchronize freeing resources during CPU hotunplug
In the Linux kernel, the following vulnerability has been resolved:
mm: zswap: properly synchronize freeing resources during CPU hotunplug
In zswap_compress() and zswap_decompress(), the per-CPU acomp_ctx of the current CPU at the beginning of the operation is retrieved and used throughout. However, since neither preemption nor migration are disabled, it is possible that the operation continues on a different CPU.
If the original CPU is hotunplugged while the acomp_ctx is still in use, we run into a UAF bug as some of the resources attached to the acomp_ctx are freed during hotunplug in zswap_cpu_comp_dead() (i.e. acomp_ctx.buffer, acomp_ctx.req, or acomp_ctx.acomp).
The problem was introduced in commit 1ec3b5fe6eec ("mm/zswap: move to use crypto_acomp API for hardware acceleration") when the switch to the crypto_acomp API was made. Prior to that, the per-CPU crypto_comp was retrieved using get_cpu_ptr() which disables preemption and makes sure the CPU cannot go away from under us. Preemption cannot be disabled with the crypto_acomp API as a sleepable context is needed.
Use the acomp_ctx.mutex to synchronize CPU hotplug callbacks allocating and freeing resources with compression/decompression paths. Make sure that acomp_ctx.req is NULL when the resources are freed. In the compression/decompression paths, check if acomp_ctx.req is NULL after acquiring the mutex (meaning the CPU was offlined) and retry on the new CPU.
The initialization of acomp_ctx.mutex is moved from the CPU hotplug callback to the pool initialization where it belongs (where the mutex is allocated). In addition to adding clarity, this makes sure that CPU hotplug cannot reinitialize a mutex that is already locked by compression/decompression.
Previously a fix was attempted by holding cpus_read_lock() [1]. This would have caused a potential deadlock as it is possible for code already holding the lock to fall into reclaim and enter zswap (causing a deadlock). A fix was also attempted using SRCU for synchronization, but Johannes pointed out that synchronize_srcu() cannot be used in CPU hotplug notifiers [2].
Alternative fixes that were considered/attempted and could have worked:
- Refcounting the per-CPU acomp_ctx. This involves complexity in handling the race between the refcount dropping to zero in zswap_[de]compress() and the refcount being re-initialized when the CPU is onlined.
- Disabling migration before getting the per-CPU acomp_ctx [3], but that's discouraged and is a much bigger hammer than needed, and could result in subtle performance issues.
[1]https://lkml.kernel.org/[email protected]/ [2]https://lkml.kernel.org/[email protected]/ [3]https://lkml.kernel.org/[email protected]/
[[email protected]: remove comment]
- Record
CVE-2025-21693- CVSS 3.1
- 7.8 High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H - Updated
- 2026-11-02
Show 35 moreShow less
OSVDEBIAN-CVE-2025-21693
7.8
In the Linux kernel, the following vulnerability has been resolved: mm: zswap: properly synchronize freeing resources during CPU hotunplug In zswap_compress() and zswap_decompress(), the per-CPU acomp_ctx of the current CPU at the beginning of the operation is retrieved and used throughout. However, since neither preemption nor migration are disabled, it is possible that the operation continues on a different CPU. If the original CPU is hotunplugged while the acomp_ctx is still in use, we run into a UAF bug as some of the resources attached to the acomp_ctx are freed during hotunplug in zswap_cpu_comp_dead() (i.e. acomp_ctx.buffer, acomp_ctx.req, or acomp_ctx.acomp). The problem was introduced in commit 1ec3b5fe6eec ("mm/zswap: move to use crypto_acomp API for hardware acceleration") when the switch to the crypto_acomp API was made. Prior to that, the per-CPU crypto_comp was retrieved using get_cpu_ptr() which disables preemption and makes sure the CPU cannot go away from under us. Preemption cannot be disabled with the crypto_acomp API as a sleepable context is needed. Use the acomp_ctx.mutex to synchronize CPU hotplug callbacks allocating and freeing resources with compression/decompression paths. Make sure that acomp_ctx.req is NULL when the resources are freed. In the compression/decompression paths, check if acomp_ctx.req is NULL after acquiring the mutex (meaning the CPU was offlined) and retry on the new CPU. The initialization of acomp_ctx.mutex is moved from the CPU hotplug callback to the pool initialization where it belongs (where the mutex is allocated). In addition to adding clarity, this makes sure that CPU hotplug cannot reinitialize a mutex that is already locked by compression/decompression. Previously a fix was attempted by holding cpus_read_lock() [1]. This would have caused a potential deadlock as it is possible for code already holding the lock to fall into reclaim and enter zswap (causing a deadlock). A fix was also attempted using SRCU for synchronization, but Johannes pointed out that synchronize_srcu() cannot be used in CPU hotplug notifiers [2]. Alternative fixes that were considered/attempted and could have worked: - Refcounting the per-CPU acomp_ctx. This involves complexity in handling the race between the refcount dropping to zero in zswap_[de]compress() and the refcount being re-initialized when the CPU is onlined. - Disabling migration before getting the per-CPU acomp_ctx [3], but that's discouraged and is a much bigger hammer than needed, and could result in subtle performance issues. [1]https://lkml.kernel.org/[email protected]/ [2]https://lkml.kernel.org/[email protected]/ [3]https://lkml.kernel.org/[email protected]/ [[email protected]: remove comment]
- Record
DEBIAN-CVE-2025-21693- CVSS 3.1
- 7.8 High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H - Updated
- 2026-11-02
OSVOESA-2025-2772
7.8
kernel security update
The Linux Kernel, the operating system core itself.
Security Fix(es):
In the Linux kernel, the following vulnerability has been resolved:
media: davinci: vpif: fix use-after-free on driver unbind
The driver allocates and registers two platform device structures during probe, but the devices were never deregistered on driver unbind.
This results in a use-after-free on driver unbind as the device structures were allocated using devres and would be freed by driver core when remove() returns.
Fix this by adding the missing deregistration calls to the remove() callback and failing probe on registration errors.
Note that the platform device structures must be freed using a proper release callback to avoid leaking associated resources like device names.(CVE-2021-47653)
In the Linux kernel, the following vulnerability has been resolved:
mmc: core: use sysfs_emit() instead of sprintf()
sprintf() (still used in the MMC core for the sysfs output) is vulnerable to the buffer overflow. Use the new-fangled sysfs_emit() instead.
Found by Linux Verification Center (linuxtesting.org) with the SVACE static analysis tool.(CVE-2022-49267)
In the Linux kernel, the following vulnerability has been resolved:
Bluetooth: btmtksdio: fix use-after-free at btmtksdio_recv_event
We should not access skb buffer data anymore after hci_recv_frame was called.
[ 39.634809] BUG: KASAN: use-after-free in btmtksdio_recv_event+0x1b0 [ 39.634855] Read of size 1 at addr ffffff80cf28a60d by task kworker [ 39.634962] Call trace: [ 39.634974] dump_backtrace+0x0/0x3b8 [ 39.634999] show_stack+0x20/0x2c [ 39.635016] dump_stack_lvl+0x60/0x78 [ 39.635040] print_address_description+0x70/0x2f0 [ 39.635062] kasan_report+0x154/0x194 [ 39.635079] __asan_report_load1_noabort+0x44/0x50 [ 39.635099] btmtksdio_recv_event+0x1b0/0x1c4 [ 39.635129] btmtksdio_txrx_work+0x6cc/0xac4 [ 39.635157] process_one_work+0x560/0xc5c [ 39.635177] worker_thread+0x7ec/0xcc0 [ 39.635195] kthread+0x2d0/0x3d0 [ 39.635215] ret_from_fork+0x10/0x20 [ 39.635247] Allocated by task 0: [ 39.635260] (stack is not available) [ 39.635281] Freed by task 2392: [ 39.635295] kasan_save_stack+0x38/0x68 [ 39.635319] kasan_set_track+0x28/0x3c [ 39.635338] kasan_set_free_info+0x28/0x4c [ 39.635357] ____kasan_slab_free+0x104/0x150 [ 39.635374] __kasan_slab_free+0x18/0x28 [ 39.635391] slab_free_freelist_hook+0x114/0x248 [ 39.635410] kfree+0xf8/0x2b4 [ 39.635427] skb_free_head+0x58/0x98 [ 39.635447] skb_release_data+0x2f4/0x410 [ 39.635464] skb_release_all+0x50/0x60 [ 39.635481] kfree_skb+0xc8/0x25c [ 39.635498] hci_event_packet+0x894/0xca4 [bluetooth] [ 39.635721] hci_rx_work+0x1c8/0x68c [bluetooth] [ 39.635925] process_one_work+0x560/0xc5c [ 39.635951] worker_thread+0x7ec/0xcc0 [ 39.635970] kthread+0x2d0/0x3d0 [ 39.635990] ret_from_fork+0x10/0x20 [ 39.636021] The buggy address belongs to the object at ffffff80cf28a600 which belongs to the cache kmalloc-512 of size 512 [ 39.636039] The buggy address is located 13 bytes inside of 512-byte region [ffffff80cf28a600, ffffff80cf28a800)(CVE-2022-49470)
In the Linux kernel, the following vulnerability has been resolved:
Bluetooth: L2CAP: Fix use-after-free
Fix potential use-after-free in l2cap_le_command_rej.(CVE-2023-53305)
In the Linux kernel, the following vulnerability has been resolved:
ip6mr: Fix skb_under_panic in ip6mr_cache_report()
skbuff: skb_under_panic: text:ffffffff88771f69 len:56 put:-4 head:ffff88805f86a800 data:ffff887f5f86a850 tail:0x88 end:0x2c0 dev:pim6reg ------------[ cut here ]------------ kernel BUG at net/core/skbuff.c:192! invalid opcode: 0000 [#1] PREEMPT SMP KASAN CPU: 2 PID: 22968 Comm: kworker/2:11 Not tainted 6.5.0-rc3-00044-g0a8db05b571a #236 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.15.0-1 04/01/2014 Workqueue: ipv6_addrconf addrconf_dad_work RIP:…
- Record
OESA-2025-2772- CVSS 3.1
- 7.8 High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H - Updated
- 2026-11-02
OSVOESA-2025-2773
7.8
kernel security update
The Linux Kernel, the operating system core itself.
Security Fix(es):
In the Linux kernel, the following vulnerability has been resolved:
media: davinci: vpif: fix use-after-free on driver unbind
The driver allocates and registers two platform device structures during probe, but the devices were never deregistered on driver unbind.
This results in a use-after-free on driver unbind as the device structures were allocated using devres and would be freed by driver core when remove() returns.
Fix this by adding the missing deregistration calls to the remove() callback and failing probe on registration errors.
Note that the platform device structures must be freed using a proper release callback to avoid leaking associated resources like device names.(CVE-2021-47653)
In the Linux kernel, the following vulnerability has been resolved:
mmc: core: use sysfs_emit() instead of sprintf()
sprintf() (still used in the MMC core for the sysfs output) is vulnerable to the buffer overflow. Use the new-fangled sysfs_emit() instead.
Found by Linux Verification Center (linuxtesting.org) with the SVACE static analysis tool.(CVE-2022-49267)
In the Linux kernel, the following vulnerability has been resolved:
Bluetooth: btmtksdio: fix use-after-free at btmtksdio_recv_event
We should not access skb buffer data anymore after hci_recv_frame was called.
[ 39.634809] BUG: KASAN: use-after-free in btmtksdio_recv_event+0x1b0 [ 39.634855] Read of size 1 at addr ffffff80cf28a60d by task kworker [ 39.634962] Call trace: [ 39.634974] dump_backtrace+0x0/0x3b8 [ 39.634999] show_stack+0x20/0x2c [ 39.635016] dump_stack_lvl+0x60/0x78 [ 39.635040] print_address_description+0x70/0x2f0 [ 39.635062] kasan_report+0x154/0x194 [ 39.635079] __asan_report_load1_noabort+0x44/0x50 [ 39.635099] btmtksdio_recv_event+0x1b0/0x1c4 [ 39.635129] btmtksdio_txrx_work+0x6cc/0xac4 [ 39.635157] process_one_work+0x560/0xc5c [ 39.635177] worker_thread+0x7ec/0xcc0 [ 39.635195] kthread+0x2d0/0x3d0 [ 39.635215] ret_from_fork+0x10/0x20 [ 39.635247] Allocated by task 0: [ 39.635260] (stack is not available) [ 39.635281] Freed by task 2392: [ 39.635295] kasan_save_stack+0x38/0x68 [ 39.635319] kasan_set_track+0x28/0x3c [ 39.635338] kasan_set_free_info+0x28/0x4c [ 39.635357] ____kasan_slab_free+0x104/0x150 [ 39.635374] __kasan_slab_free+0x18/0x28 [ 39.635391] slab_free_freelist_hook+0x114/0x248 [ 39.635410] kfree+0xf8/0x2b4 [ 39.635427] skb_free_head+0x58/0x98 [ 39.635447] skb_release_data+0x2f4/0x410 [ 39.635464] skb_release_all+0x50/0x60 [ 39.635481] kfree_skb+0xc8/0x25c [ 39.635498] hci_event_packet+0x894/0xca4 [bluetooth] [ 39.635721] hci_rx_work+0x1c8/0x68c [bluetooth] [ 39.635925] process_one_work+0x560/0xc5c [ 39.635951] worker_thread+0x7ec/0xcc0 [ 39.635970] kthread+0x2d0/0x3d0 [ 39.635990] ret_from_fork+0x10/0x20 [ 39.636021] The buggy address belongs to the object at ffffff80cf28a600 which belongs to the cache kmalloc-512 of size 512 [ 39.636039] The buggy address is located 13 bytes inside of 512-byte region [ffffff80cf28a600, ffffff80cf28a800)(CVE-2022-49470)
In the Linux kernel, the following vulnerability has been resolved:
scsi: ufs: core: Fix handling of lrbp->cmd
ufshcd_queuecommand() may be called two times in a row for a SCSI command before it is completed. Hence make the following changes:
-
In the functions that submit a command, do not check the old value of lrbp->cmd nor clear lrbp->cmd in error paths.
-
In ufshcd_release_scsi_cmd(), do not clear lrbp->cmd.
See also scsi_send_eh_cmnd().
This commit prevents that the following appears if a command times out:
WARNING: at drivers/ufs/core/ufshcd.c:2965 ufshcd_queuecommand+0x6f8/0x9a8 Call trace: ufshcd_queuecommand+0x6f8/0x9a8 scsi_send_eh_cmnd+0x2c0/0x960 scsi_eh_test_devices+0x100/0x314 scsi_eh_ready_devs+0xd90/0x114c …
- Record
OESA-2025-2773- CVSS 3.1
- 7.8 High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H - Updated
- 2026-11-02
OSVOESA-2025-2774
7.8
kernel security update
The Linux Kernel, the operating system core itself.
Security Fix(es):
In the Linux kernel, the following vulnerability has been resolved:
mm: zswap: properly synchronize freeing resources during CPU hotunplug
In zswap_compress() and zswap_decompress(), the per-CPU acomp_ctx of the current CPU at the beginning of the operation is retrieved and used throughout. However, since neither preemption nor migration are disabled, it is possible that the operation continues on a different CPU.
If the original CPU is hotunplugged while the acomp_ctx is still in use, we run into a UAF bug as some of the resources attached to the acomp_ctx are freed during hotunplug in zswap_cpu_comp_dead() (i.e. acomp_ctx.buffer, acomp_ctx.req, or acomp_ctx.acomp).
The problem was introduced in commit 1ec3b5fe6eec ("mm/zswap: move to use crypto_acomp API for hardware acceleration") when the switch to the crypto_acomp API was made. Prior to that, the per-CPU crypto_comp was retrieved using get_cpu_ptr() which disables preemption and makes sure the CPU cannot go away from under us. Preemption cannot be disabled with the crypto_acomp API as a sleepable context is needed.
Use the acomp_ctx.mutex to synchronize CPU hotplug callbacks allocating and freeing resources with compression/decompression paths. Make sure that acomp_ctx.req is NULL when the resources are freed. In the compression/decompression paths, check if acomp_ctx.req is NULL after acquiring the mutex (meaning the CPU was offlined) and retry on the new CPU.
The initialization of acomp_ctx.mutex is moved from the CPU hotplug callback to the pool initialization where it belongs (where the mutex is allocated). In addition to adding clarity, this makes sure that CPU hotplug cannot reinitialize a mutex that is already locked by compression/decompression.
Previously a fix was attempted by holding cpus_read_lock() [1]. This would have caused a potential deadlock as it is possible for code already holding the lock to fall into reclaim and enter zswap (causing a deadlock). A fix was also attempted using SRCU for synchronization, but Johannes pointed out that synchronize_srcu() cannot be used in CPU hotplug notifiers [2].
Alternative fixes that were considered/attempted and could have worked:
- Refcounting the per-CPU acomp_ctx. This involves complexity in handling the race between the refcount dropping to zero in zswap_[de]compress() and the refcount being re-initialized when the CPU is onlined.
- Disabling migration before getting the per-CPU acomp_ctx [3], but that's discouraged and is a much bigger hammer than needed, and could result in subtle performance issues.
[1]https://lkml.kernel.org/(CVE-2025-21693)
In the Linux kernel, the following vulnerability has been resolved:
cdx: Fix possible UAF error in driver_override_show()
Fixed a possible UAF problem in driver_override_show() in drivers/cdx/cdx.c
This function driver_override_show() is part of DEVICE_ATTR_RW, which includes both driver_override_show() and driver_override_store(). These functions can be executed concurrently in sysfs.
The driver_override_store() function uses driver_set_override() to update the driver_override value, and driver_set_override() internally locks the device (device_lock(dev)). If driver_override_show() reads cdx_dev->driver_override without locking, it could potentially access a freed pointer if driver_override_store() frees the string concurrently. This could lead to printing a kernel address, which is a security risk since DEVICE_ATTR can be read by all users.
Additionally, a similar pattern is used in drivers/amba/bus.c, as well as many other bus drivers, where device_lock() is taken in the show function, and it has been working without issues.
This potential bug was detected by our experimental static analysis tool, which analyzes locking APIs and paired functions to identify data races and atomicity violations.(CVE-2025-21915)
In the Linux kernel, the…
- Record
OESA-2025-2774- CVSS 3.1
- 7.8 High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H - Updated
- 2026-11-02
OSVOESA-2025-2775
7.8
kernel security update
The Linux Kernel, the operating system core itself.
Security Fix(es):
In the Linux kernel, the following vulnerability has been resolved:
mm: zswap: properly synchronize freeing resources during CPU hotunplug
In zswap_compress() and zswap_decompress(), the per-CPU acomp_ctx of the current CPU at the beginning of the operation is retrieved and used throughout. However, since neither preemption nor migration are disabled, it is possible that the operation continues on a different CPU.
If the original CPU is hotunplugged while the acomp_ctx is still in use, we run into a UAF bug as some of the resources attached to the acomp_ctx are freed during hotunplug in zswap_cpu_comp_dead() (i.e. acomp_ctx.buffer, acomp_ctx.req, or acomp_ctx.acomp).
The problem was introduced in commit 1ec3b5fe6eec ("mm/zswap: move to use crypto_acomp API for hardware acceleration") when the switch to the crypto_acomp API was made. Prior to that, the per-CPU crypto_comp was retrieved using get_cpu_ptr() which disables preemption and makes sure the CPU cannot go away from under us. Preemption cannot be disabled with the crypto_acomp API as a sleepable context is needed.
Use the acomp_ctx.mutex to synchronize CPU hotplug callbacks allocating and freeing resources with compression/decompression paths. Make sure that acomp_ctx.req is NULL when the resources are freed. In the compression/decompression paths, check if acomp_ctx.req is NULL after acquiring the mutex (meaning the CPU was offlined) and retry on the new CPU.
The initialization of acomp_ctx.mutex is moved from the CPU hotplug callback to the pool initialization where it belongs (where the mutex is allocated). In addition to adding clarity, this makes sure that CPU hotplug cannot reinitialize a mutex that is already locked by compression/decompression.
Previously a fix was attempted by holding cpus_read_lock() [1]. This would have caused a potential deadlock as it is possible for code already holding the lock to fall into reclaim and enter zswap (causing a deadlock). A fix was also attempted using SRCU for synchronization, but Johannes pointed out that synchronize_srcu() cannot be used in CPU hotplug notifiers [2].
Alternative fixes that were considered/attempted and could have worked:
- Refcounting the per-CPU acomp_ctx. This involves complexity in handling the race between the refcount dropping to zero in zswap_[de]compress() and the refcount being re-initialized when the CPU is onlined.
- Disabling migration before getting the per-CPU acomp_ctx [3], but that's discouraged and is a much bigger hammer than needed, and could result in subtle performance issues.
[1]https://lkml.kernel.org/(CVE-2025-21693)
In the Linux kernel, the following vulnerability has been resolved:
memstick: rtsx_usb_ms: Fix slab-use-after-free in rtsx_usb_ms_drv_remove
This fixes the following crash:
================================================================== BUG: KASAN: slab-use-after-free in rtsx_usb_ms_poll_card+0x159/0x200 [rtsx_usb_ms] Read of size 8 at addr ffff888136335380 by task kworker/6:0/140241
CPU: 6 UID: 0 PID: 140241 Comm: kworker/6:0 Kdump: loaded Tainted: G E 6.14.0-rc6+ #1 Tainted: [E]=UNSIGNED_MODULE Hardware name: LENOVO 30FNA1V7CW/1057, BIOS S0EKT54A 07/01/2024 Workqueue: events rtsx_usb_ms_poll_card [rtsx_usb_ms] Call Trace: <TASK> dump_stack_lvl+0x51/0x70 print_address_description.constprop.0+0x27/0x320 ? rtsx_usb_ms_poll_card+0x159/0x200 [rtsx_usb_ms] print_report+0x3e/0x70 kasan_report+0xab/0xe0 ? rtsx_usb_ms_poll_card+0x159/0x200 [rtsx_usb_ms] rtsx_usb_ms_poll_card+0x159/0x200 [rtsx_usb_ms] ? __pfx_rtsx_usb_ms_poll_card+0x10/0x10 [rtsx_usb_ms] ? __pfx___schedule+0x10/0x10 ? kick_pool+0x3b/0x270 process_one_work+0x357/0x660 worker_thread+0x390/0x4c0 ? __pfx_worker_thread+0x10/0x10 kthread+0x190/0x1d0 ? __pfx_kthread+0x10/0x10 ret_from_fork+0x2d/0x50 ? __pfx_kthread+0x10/0x10 ret_from_fork_asm+0x1a/0x30 …
- Record
OESA-2025-2775- CVSS 3.1
- 7.8 High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H - Updated
- 2026-11-02
OSVOESA-2025-2776
7.8
kernel security update
The Linux Kernel, the operating system core itself.
Security Fix(es):
In the Linux kernel, the following vulnerability has been resolved:
jfs: add check read-only before txBeginAnon() call
Added a read-only check before calling txBeginAnon in extAlloc
and extRecord. This prevents modification attempts on a read-only
mounted filesystem, avoiding potential errors or crashes.
Call trace: txBeginAnon+0xac/0x154 extAlloc+0xe8/0xdec fs/jfs/jfs_extent.c:78 jfs_get_block+0x340/0xb98 fs/jfs/inode.c:248 __block_write_begin_int+0x580/0x166c fs/buffer.c:2128 __block_write_begin fs/buffer.c:2177 [inline] block_write_begin+0x98/0x11c fs/buffer.c:2236 jfs_write_begin+0x44/0x88 fs/jfs/inode.c:299(CVE-2024-58095)
In the Linux kernel, the following vulnerability has been resolved:
mm: zswap: properly synchronize freeing resources during CPU hotunplug
In zswap_compress() and zswap_decompress(), the per-CPU acomp_ctx of the current CPU at the beginning of the operation is retrieved and used throughout. However, since neither preemption nor migration are disabled, it is possible that the operation continues on a different CPU.
If the original CPU is hotunplugged while the acomp_ctx is still in use, we run into a UAF bug as some of the resources attached to the acomp_ctx are freed during hotunplug in zswap_cpu_comp_dead() (i.e. acomp_ctx.buffer, acomp_ctx.req, or acomp_ctx.acomp).
The problem was introduced in commit 1ec3b5fe6eec ("mm/zswap: move to use crypto_acomp API for hardware acceleration") when the switch to the crypto_acomp API was made. Prior to that, the per-CPU crypto_comp was retrieved using get_cpu_ptr() which disables preemption and makes sure the CPU cannot go away from under us. Preemption cannot be disabled with the crypto_acomp API as a sleepable context is needed.
Use the acomp_ctx.mutex to synchronize CPU hotplug callbacks allocating and freeing resources with compression/decompression paths. Make sure that acomp_ctx.req is NULL when the resources are freed. In the compression/decompression paths, check if acomp_ctx.req is NULL after acquiring the mutex (meaning the CPU was offlined) and retry on the new CPU.
The initialization of acomp_ctx.mutex is moved from the CPU hotplug callback to the pool initialization where it belongs (where the mutex is allocated). In addition to adding clarity, this makes sure that CPU hotplug cannot reinitialize a mutex that is already locked by compression/decompression.
Previously a fix was attempted by holding cpus_read_lock() [1]. This would have caused a potential deadlock as it is possible for code already holding the lock to fall into reclaim and enter zswap (causing a deadlock). A fix was also attempted using SRCU for synchronization, but Johannes pointed out that synchronize_srcu() cannot be used in CPU hotplug notifiers [2].
Alternative fixes that were considered/attempted and could have worked:
- Refcounting the per-CPU acomp_ctx. This involves complexity in handling the race between the refcount dropping to zero in zswap_[de]compress() and the refcount being re-initialized when the CPU is onlined.
- Disabling migration before getting the per-CPU acomp_ctx [3], but that's discouraged and is a much bigger hammer than needed, and could result in subtle performance issues.
[1]https://lkml.kernel.org/(CVE-2025-21693)
In the Linux kernel, the following vulnerability has been resolved:
memstick: rtsx_usb_ms: Fix slab-use-after-free in rtsx_usb_ms_drv_remove
This fixes the following crash:
================================================================== BUG: KASAN: slab-use-after-free in rtsx_usb_ms_poll_card+0x159/0x200 [rtsx_usb_ms] Read of size 8 at addr ffff888136335380 by task kworker/6:0/140241
CPU: 6 UID: 0 PID: 140241 Comm: kworker/6:0 Kdump: loaded Tainted: G E 6.14.0-rc6+ #1 Tainted: [E]=UNSIGNED_MODULE Hardware name: LENOVO 30FNA1V7CW/1057, BIOS S0EKT54A 07/01/2024 Workqueue: events…
- Record
OESA-2025-2776- CVSS 3.1
- 7.8 High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H - Updated
- 2026-11-02
OSVRHSA-2025:20095
7.8
Red Hat Security Advisory: kernel security update
- Record
RHSA-2025:20095- CVSS 3.1
- 7.8 High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H - Updated
- 2026-11-02
OSVRHSA-2025:20518
7.8
Red Hat Security Advisory: kernel security update
- Record
RHSA-2025:20518- CVSS 3.1
- 7.8 High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H - Updated
- 2026-11-02
OSVRLSA-2025:20095
7.8
Moderate: kernel security update
The kernel packages contain the Linux kernel, the core of any Linux operating system.
Security Fix(es):
-
kernel: xen: Xen hypercall page unsafe against speculative attacks (Xen Security Advisory 466) (CVE-2024-53241)
-
kernel: exfat: fix out-of-bounds access of directory entries (CVE-2024-53147)
-
kernel: zram: fix NULL pointer in comp_algorithm_show() (CVE-2024-53222)
-
kernel: nfsd: release svc_expkey/svc_export with rcu_work (CVE-2024-53216)
-
kernel: acpi: nfit: vmalloc-out-of-bounds Read in acpi_nfit_ctl (CVE-2024-56662)
-
kernel: bpf: Fix UAF via mismatching bpf_prog/attachment RCU flavors (CVE-2024-56675)
-
kernel: crypto: pcrypt - Call crypto layer directly when padata_do_parallel() return -EBUSY (CVE-2024-56690)
-
kernel: igb: Fix potential invalid memory access in igb_init_module() (CVE-2024-52332)
-
kernel: af_packet: fix vlan_get_protocol_dgram() vs MSG_PEEK (CVE-2024-57901)
-
kernel: af_packet: fix vlan_get_tci() vs MSG_PEEK (CVE-2024-57902)
-
kernel: io_uring/sqpoll: zero sqd->thread on tctx errors (CVE-2025-21633)
-
kernel: ipvlan: Fix use-after-free in ipvlan_get_iflink(). (CVE-2025-21652)
-
kernel: sched: sch_cake: add bounds checks to host bulk flow fairness counts (CVE-2025-21647)
-
kernel: io_uring/eventfd: ensure io_eventfd_signal() defers another RCU period (CVE-2025-21655)
-
kernel: netfs: Fix the (non-)cancellation of copy when cache is temporarily disabled (CVE-2024-57941)
-
kernel: netfs: Fix ceph copy to cache on write-begin (CVE-2024-57942)
-
kernel: zram: fix potential UAF of zram table (CVE-2025-21671)
-
kernel: pktgen: Avoid out-of-bounds access in get_imix_entries (CVE-2025-21680)
-
kernel: mm: zswap: properly synchronize freeing resources during CPU hotunplug (CVE-2025-21693)
-
kernel: cachestat: fix page cache statistics permission checking (CVE-2025-21691)
-
kernel: mm: clear uffd-wp PTE/PMD state on mremap() (CVE-2025-21696)
-
kernel: pfifo_tail_enqueue: Drop new packet when sch->limit == 0 (CVE-2025-21702)
-
kernel: RDMA/mlx5: Fix a race for an ODP MR which leads to CQE with error (CVE-2025-21732)
-
kernel: NFSD: fix hang in nfsd4_shutdown_callback (CVE-2025-21795)
-
kernel: NFS: Fix potential buffer overflowin nfs_sysfs_link_rpc_client() (CVE-2024-54456)
-
kernel: Bluetooth: btrtl: check for NULL in btrtl_setup_realtek() (CVE-2024-57987)
-
kernel: wifi: brcmsmac: add gain range check to wlc_phy_iqcal_gainparams_nphy() (CVE-2024-58014)
-
kernel: Bluetooth: btbcm: Fix NULL deref in btbcm_get_board_name() (CVE-2024-57988)
-
kernel: drm/xe/tracing: Fix a potential TP_printk UAF (CVE-2024-49570)
-
kernel: media: intel/ipu6: remove cpu latency qos request on error (CVE-2024-58004)
-
kernel: usbnet: ipheth: use static NDP16 location in URB (CVE-2025-21742)
-
kernel: usbnet: ipheth: fix possible overflow in DPE length check (CVE-2025-21743)
-
kernel: wifi: mt76: mt7925: fix NULL deref check in mt7925_change_vif_links (CVE-2024-57989)
-
kernel: wifi: ath12k: Fix for out-of bound access error (CVE-2024-58015)
-
kernel: wifi: ath12k: fix read pointer after free in ath12k_mac_assign_vif_to_vdev() (CVE-2024-57995)
-
kernel: nfsd: clear acl_access/acl_default after releasing them (CVE-2025-21796)
-
kernel: workqueue: Put the pwq after detaching the rescuer from the pool (CVE-2025-21786)
-
kernel: tpm: Change to kvalloc() in eventlog/acpi.c (CVE-2024-58005)
-
kernel: Bluetooth: MGMT: Fix slab-use-after-free Read in mgmt_remove_adv_monitor_sync (CVE-2024-58013)
-
kernel: ring-buffer: Validate the persistent meta data subbuf array (CVE-2025-21777)
-
kernel: ata: libata-sff: Ensure that we cannot write outside the allocated buffer (CVE-2025-21738)
-
kernel: HID: core: Fix assumption that Resolution Multipliers must be in Logical Collections (CVE-2024-57986)
-
kernel: padata: avoid UAF for reorder_work (CVE-2025-21726)
-
kernel: vrf: use RCU protection in l3mdev_l3_out() (CVE-2025-21791)
-
kernel: HID: multitouch: Add NULL check in mt_input_configured…
- Record
RLSA-2025:20095- CVSS 3.1
- 7.8 High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H - Updated
- 2026-11-02
OSVRLSA-2025:20518
7.8
Moderate: kernel security update
The kernel packages contain the Linux kernel, the core of any Linux operating system.
Security Fix(es):
-
kernel: can: isotp: fix potential CAN frame reception race in isotp_rcv() (CVE-2022-48830)
-
kernel: soc: qcom: cmd-db: Map shared memory as WC, not WB (CVE-2024-46689)
-
kernel: Squashfs: sanity check symbolic link size (CVE-2024-46744)
-
kernel: vfs: fix race between evice_inodes() and find_inode()&iput() (CVE-2024-47679)
-
kernel: x86/tdx: Fix "in-kernel MMIO" check (CVE-2024-47727)
-
kernel: rxrpc: Fix a race between socket set up and I/O thread creation (CVE-2024-49864)
-
kernel: io_uring: check if we need to reschedule during overflow flush (CVE-2024-50060)
-
kernel: can: m_can: pci: add missing m_can_class_free_dev() in probe/remove methods (CVE-2022-49024)
-
kernel: posix-clock: Fix missing timespec64 check in pc_clock_settime() (CVE-2024-50195)
-
kernel: rxrpc: Fix missing locking causing hanging calls (CVE-2024-50294)
-
kernel: io_uring/rw: fix missing NOWAIT check for O_DIRECT start write (CVE-2024-53052)
-
kernel: afs: Fix lock recursion (CVE-2024-53090)
-
kernel: virtio/vsock: Fix accept_queue memory leak (CVE-2024-53119)
-
kernel: KVM: VMX: Bury Intel PT virtualization (guest/host mode) behind CONFIG_BROKEN (CVE-2024-53135)
-
kernel: xen: Xen hypercall page unsafe against speculative attacks (Xen Security Advisory 466) (CVE-2024-53241)
-
kernel: RDMA/rxe: Fix the qp flush warnings in req (CVE-2024-53229)
-
kernel: block: fix uaf for flush rq while iterating tags (CVE-2024-53170)
-
kernel: nfsd: release svc_expkey/svc_export with rcu_work (CVE-2024-53216)
-
kernel: net: af_can: do not leave a dangling sk pointer in can_create() (CVE-2024-56603)
-
kernel: blk-cgroup: Fix UAF in blkcg_unpin_online() (CVE-2024-56672)
-
kernel: acpi: nfit: vmalloc-out-of-bounds Read in acpi_nfit_ctl (CVE-2024-56662)
-
kernel: bpf: Fix UAF via mismatching bpf_prog/attachment RCU flavors (CVE-2024-56675)
-
kernel: can: j1939: j1939_session_new(): fix skb reference counting (CVE-2024-56645)
-
kernel: crypto: pcrypt - Call crypto layer directly when padata_do_parallel() return -EBUSY (CVE-2024-56690)
-
kernel: io_uring: check if iowq is killed before queuing (CVE-2024-56709)
-
kernel: rtc: check if __rtc_read_time was successful in rtc_timer_do_work() (CVE-2024-56739)
-
kernel: bpf: put bpf_link's program when link is safe to be deallocated (CVE-2024-56786)
-
kernel: igb: Fix potential invalid memory access in igb_init_module() (CVE-2024-52332)
-
kernel: ipvs: fix UB due to uninitialized stack access in ip_vs_protocol_init() (CVE-2024-53680)
-
kernel: netfilter: conntrack: clamp maximum hashtable size to INT_MAX (CVE-2025-21648)
-
kernel: sched: sch_cake: add bounds checks to host bulk flow fairness counts (CVE-2025-21647)
-
kernel: block, bfq: fix waker_bfqq UAF after bfq_split_bfqq() (CVE-2025-21631)
-
kernel: zram: fix potential UAF of zram table (CVE-2025-21671)
-
kernel: afs: Fix merge preference rule failure condition (CVE-2025-21672)
-
kernel: mm: zswap: properly synchronize freeing resources during CPU hotunplug (CVE-2025-21693)
-
kernel: cachestat: fix page cache statistics permission checking (CVE-2025-21691)
-
kernel: mm: clear uffd-wp PTE/PMD state on mremap() (CVE-2025-21696)
-
kernel: pfifo_tail_enqueue: Drop new packet when sch->limit == 0 (CVE-2025-21702)
-
kernel: usbnet: fix memory leak in error case (CVE-2022-49657)
-
kernel: powerpc/xics: fix refcount leak in icp_opal_init() (CVE-2022-49432)
-
kernel: net: tun: unlink NAPI from device on destruction (CVE-2022-49672)
-
kernel: powerpc/papr_scm: don't requests stats with '0' sized stats buffer (CVE-2022-49353)
-
kernel: powerpc/xive: Fix refcount leak in xive_spapr_init (CVE-2022-49437)
-
kernel: ima: Fix potential memory leak in ima_init_crypto() (CVE-2022-49627)
-
kernel: linux/dim: Fix divide by 0 in RDMA DIM (CVE-2022-49670)
-
kernel: can: isotp: sanitize CAN ID checks in isotp_bind() (CVE-2022-49269)
-
kernel:…
- Record
RLSA-2025:20518- CVSS 3.1
- 7.8 High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H - Updated
- 2026-11-02
OSVUBUNTU-CVE-2025-21693
7.8
In the Linux kernel, the following vulnerability has been resolved: mm: zswap: properly synchronize freeing resources during CPU hotunplug In zswap_compress() and zswap_decompress(), the per-CPU acomp_ctx of the current CPU at the beginning of the operation is retrieved and used throughout. However, since neither preemption nor migration are disabled, it is possible that the operation continues on a different CPU. If the original CPU is hotunplugged while the acomp_ctx is still in use, we run into a UAF bug as some of the resources attached to the acomp_ctx are freed during hotunplug in zswap_cpu_comp_dead() (i.e. acomp_ctx.buffer, acomp_ctx.req, or acomp_ctx.acomp). The problem was introduced in commit 1ec3b5fe6eec ("mm/zswap: move to use crypto_acomp API for hardware acceleration") when the switch to the crypto_acomp API was made. Prior to that, the per-CPU crypto_comp was retrieved using get_cpu_ptr() which disables preemption and makes sure the CPU cannot go away from under us. Preemption cannot be disabled with the crypto_acomp API as a sleepable context is needed. Use the acomp_ctx.mutex to synchronize CPU hotplug callbacks allocating and freeing resources with compression/decompression paths. Make sure that acomp_ctx.req is NULL when the resources are freed. In the compression/decompression paths, check if acomp_ctx.req is NULL after acquiring the mutex (meaning the CPU was offlined) and retry on the new CPU. The initialization of acomp_ctx.mutex is moved from the CPU hotplug callback to the pool initialization where it belongs (where the mutex is allocated). In addition to adding clarity, this makes sure that CPU hotplug cannot reinitialize a mutex that is already locked by compression/decompression. Previously a fix was attempted by holding cpus_read_lock() [1]. This would have caused a potential deadlock as it is possible for code already holding the lock to fall into reclaim and enter zswap (causing a deadlock). A fix was also attempted using SRCU for synchronization, but Johannes pointed out that synchronize_srcu() cannot be used in CPU hotplug notifiers [2]. Alternative fixes that were considered/attempted and could have worked: - Refcounting the per-CPU acomp_ctx. This involves complexity in handling the race between the refcount dropping to zero in zswap_[de]compress() and the refcount being re-initialized when the CPU is onlined. - Disabling migration before getting the per-CPU acomp_ctx [3], but that's discouraged and is a much bigger hammer than needed, and could result in subtle performance issues. [1]https://lkml.kernel.org/[email protected]/ [2]https://lkml.kernel.org/[email protected]/ [3]https://lkml.kernel.org/[email protected]/ [[email protected]: remove comment]
- Record
UBUNTU-CVE-2025-21693- CVSS 3.1
- 7.8 High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H - Updated
- 2026-11-06
OSVALSA-2025:20095 No score
Moderate: kernel security update
The kernel packages contain the Linux kernel, the core of any Linux operating system.
Security Fix(es):
- kernel: xen: Xen hypercall page unsafe against speculative attacks (Xen Security Advisory 466) (CVE-2024-53241)
- kernel: exfat: fix out-of-bounds access of directory entries (CVE-2024-53147)
- kernel: zram: fix NULL pointer in comp_algorithm_show() (CVE-2024-53222)
- kernel: nfsd: release svc_expkey/svc_export with rcu_work (CVE-2024-53216)
- kernel: acpi: nfit: vmalloc-out-of-bounds Read in acpi_nfit_ctl (CVE-2024-56662)
- kernel: bpf: Fix UAF via mismatching bpf_prog/attachment RCU flavors (CVE-2024-56675)
- kernel: crypto: pcrypt - Call crypto layer directly when padata_do_parallel() return -EBUSY (CVE-2024-56690)
- kernel: igb: Fix potential invalid memory access in igb_init_module() (CVE-2024-52332)
- kernel: af_packet: fix vlan_get_protocol_dgram() vs MSG_PEEK (CVE-2024-57901)
- kernel: af_packet: fix vlan_get_tci() vs MSG_PEEK (CVE-2024-57902)
- kernel: io_uring/sqpoll: zero sqd->thread on tctx errors (CVE-2025-21633)
- kernel: ipvlan: Fix use-after-free in ipvlan_get_iflink(). (CVE-2025-21652)
- kernel: sched: sch_cake: add bounds checks to host bulk flow fairness counts (CVE-2025-21647)
- kernel: io_uring/eventfd: ensure io_eventfd_signal() defers another RCU period (CVE-2025-21655)
- kernel: netfs: Fix the (non-)cancellation of copy when cache is temporarily disabled (CVE-2024-57941)
- kernel: netfs: Fix ceph copy to cache on write-begin (CVE-2024-57942)
- kernel: zram: fix potential UAF of zram table (CVE-2025-21671)
- kernel: pktgen: Avoid out-of-bounds access in get_imix_entries (CVE-2025-21680)
- kernel: mm: zswap: properly synchronize freeing resources during CPU hotunplug (CVE-2025-21693)
- kernel: cachestat: fix page cache statistics permission checking (CVE-2025-21691)
- kernel: mm: clear uffd-wp PTE/PMD state on mremap() (CVE-2025-21696)
- kernel: pfifo_tail_enqueue: Drop new packet when sch->limit == 0 (CVE-2025-21702)
- kernel: RDMA/mlx5: Fix a race for an ODP MR which leads to CQE with error (CVE-2025-21732)
- kernel: NFSD: fix hang in nfsd4_shutdown_callback (CVE-2025-21795)
- kernel: NFS: Fix potential buffer overflowin nfs_sysfs_link_rpc_client() (CVE-2024-54456)
- kernel: Bluetooth: btrtl: check for NULL in btrtl_setup_realtek() (CVE-2024-57987)
- kernel: wifi: brcmsmac: add gain range check to wlc_phy_iqcal_gainparams_nphy() (CVE-2024-58014)
- kernel: Bluetooth: btbcm: Fix NULL deref in btbcm_get_board_name() (CVE-2024-57988)
- kernel: drm/xe/tracing: Fix a potential TP_printk UAF (CVE-2024-49570)
- kernel: media: intel/ipu6: remove cpu latency qos request on error (CVE-2024-58004)
- kernel: usbnet: ipheth: use static NDP16 location in URB (CVE-2025-21742)
- kernel: usbnet: ipheth: fix possible overflow in DPE length check (CVE-2025-21743)
- kernel: wifi: mt76: mt7925: fix NULL deref check in mt7925_change_vif_links (CVE-2024-57989)
- kernel: wifi: ath12k: Fix for out-of bound access error (CVE-2024-58015)
- kernel: wifi: ath12k: fix read pointer after free in ath12k_mac_assign_vif_to_vdev() (CVE-2024-57995)
- kernel: nfsd: clear acl_access/acl_default after releasing them (CVE-2025-21796)
- kernel: workqueue: Put the pwq after detaching the rescuer from the pool (CVE-2025-21786)
- kernel: tpm: Change to kvalloc() in eventlog/acpi.c (CVE-2024-58005)
- kernel: Bluetooth: MGMT: Fix slab-use-after-free Read in mgmt_remove_adv_monitor_sync (CVE-2024-58013)
- kernel: ring-buffer: Validate the persistent meta data subbuf array (CVE-2025-21777)
- kernel: ata: libata-sff: Ensure that we cannot write outside the allocated buffer (CVE-2025-21738)
- kernel: HID: core: Fix assumption that Resolution Multipliers must be in Logical Collections (CVE-2024-57986)
- kernel: padata: avoid UAF for reorder_work (CVE-2025-21726)
- kernel: vrf: use RCU protection in l3mdev_l3_out() (CVE-2025-21791)
- kernel: HID:…
- Record
ALSA-2025:20095- Updated
- 2026-11-02
OSVALSA-2025:20518 No score
Moderate: kernel security update
The kernel packages contain the Linux kernel, the core of any Linux operating system.
Security Fix(es):
- kernel: can: isotp: fix potential CAN frame reception race in isotp_rcv() (CVE-2022-48830)
- kernel: soc: qcom: cmd-db: Map shared memory as WC, not WB (CVE-2024-46689)
- kernel: Squashfs: sanity check symbolic link size (CVE-2024-46744)
- kernel: vfs: fix race between evice_inodes() and find_inode()&iput() (CVE-2024-47679)
- kernel: x86/tdx: Fix "in-kernel MMIO" check (CVE-2024-47727)
- kernel: rxrpc: Fix a race between socket set up and I/O thread creation (CVE-2024-49864)
- kernel: io_uring: check if we need to reschedule during overflow flush (CVE-2024-50060)
- kernel: can: m_can: pci: add missing m_can_class_free_dev() in probe/remove methods (CVE-2022-49024)
- kernel: posix-clock: Fix missing timespec64 check in pc_clock_settime() (CVE-2024-50195)
- kernel: rxrpc: Fix missing locking causing hanging calls (CVE-2024-50294)
- kernel: io_uring/rw: fix missing NOWAIT check for O_DIRECT start write (CVE-2024-53052)
- kernel: afs: Fix lock recursion (CVE-2024-53090)
- kernel: virtio/vsock: Fix accept_queue memory leak (CVE-2024-53119)
- kernel: KVM: VMX: Bury Intel PT virtualization (guest/host mode) behind CONFIG_BROKEN (CVE-2024-53135)
- kernel: xen: Xen hypercall page unsafe against speculative attacks (Xen Security Advisory 466) (CVE-2024-53241)
- kernel: RDMA/rxe: Fix the qp flush warnings in req (CVE-2024-53229)
- kernel: block: fix uaf for flush rq while iterating tags (CVE-2024-53170)
- kernel: nfsd: release svc_expkey/svc_export with rcu_work (CVE-2024-53216)
- kernel: net: af_can: do not leave a dangling sk pointer in can_create() (CVE-2024-56603)
- kernel: blk-cgroup: Fix UAF in blkcg_unpin_online() (CVE-2024-56672)
- kernel: acpi: nfit: vmalloc-out-of-bounds Read in acpi_nfit_ctl (CVE-2024-56662)
- kernel: bpf: Fix UAF via mismatching bpf_prog/attachment RCU flavors (CVE-2024-56675)
- kernel: can: j1939: j1939_session_new(): fix skb reference counting (CVE-2024-56645)
- kernel: crypto: pcrypt - Call crypto layer directly when padata_do_parallel() return -EBUSY (CVE-2024-56690)
- kernel: io_uring: check if iowq is killed before queuing (CVE-2024-56709)
- kernel: rtc: check if __rtc_read_time was successful in rtc_timer_do_work() (CVE-2024-56739)
- kernel: bpf: put bpf_link's program when link is safe to be deallocated (CVE-2024-56786)
- kernel: igb: Fix potential invalid memory access in igb_init_module() (CVE-2024-52332)
- kernel: ipvs: fix UB due to uninitialized stack access in ip_vs_protocol_init() (CVE-2024-53680)
- kernel: netfilter: conntrack: clamp maximum hashtable size to INT_MAX (CVE-2025-21648)
- kernel: sched: sch_cake: add bounds checks to host bulk flow fairness counts (CVE-2025-21647)
- kernel: block, bfq: fix waker_bfqq UAF after bfq_split_bfqq() (CVE-2025-21631)
- kernel: zram: fix potential UAF of zram table (CVE-2025-21671)
- kernel: afs: Fix merge preference rule failure condition (CVE-2025-21672)
- kernel: mm: zswap: properly synchronize freeing resources during CPU hotunplug (CVE-2025-21693)
- kernel: cachestat: fix page cache statistics permission checking (CVE-2025-21691)
- kernel: mm: clear uffd-wp PTE/PMD state on mremap() (CVE-2025-21696)
- kernel: pfifo_tail_enqueue: Drop new packet when sch->limit == 0 (CVE-2025-21702)
- kernel: usbnet: fix memory leak in error case (CVE-2022-49657)
- kernel: powerpc/xics: fix refcount leak in icp_opal_init() (CVE-2022-49432)
- kernel: net: tun: unlink NAPI from device on destruction (CVE-2022-49672)
- kernel: powerpc/papr_scm: don't requests stats with '0' sized stats buffer (CVE-2022-49353)
- kernel: powerpc/xive: Fix refcount leak in xive_spapr_init (CVE-2022-49437)
- kernel: ima: Fix potential memory leak in ima_init_crypto() (CVE-2022-49627)
- kernel: linux/dim: Fix divide by 0 in RDMA DIM (CVE-2022-49670)
- kernel: can: isotp: sanitize CAN ID…
- Record
ALSA-2025:20518- Updated
- 2026-11-02
OSVAZL-58989 No score
CVE-2025-21693 affecting package kernel 5.15.200.1-1
In the Linux kernel, the following vulnerability has been resolved:
mm: zswap: properly synchronize freeing resources during CPU hotunplug
In zswap_compress() and zswap_decompress(), the per-CPU acomp_ctx of the current CPU at the beginning of the operation is retrieved and used throughout. However, since neither preemption nor migration are disabled, it is possible that the operation continues on a different CPU.
If the original CPU is hotunplugged while the acomp_ctx is still in use, we run into a UAF bug as some of the resources attached to the acomp_ctx are freed during hotunplug in zswap_cpu_comp_dead() (i.e. acomp_ctx.buffer, acomp_ctx.req, or acomp_ctx.acomp).
The problem was introduced in commit 1ec3b5fe6eec ("mm/zswap: move to use crypto_acomp API for hardware acceleration") when the switch to the crypto_acomp API was made. Prior to that, the per-CPU crypto_comp was retrieved using get_cpu_ptr() which disables preemption and makes sure the CPU cannot go away from under us. Preemption cannot be disabled with the crypto_acomp API as a sleepable context is needed.
Use the acomp_ctx.mutex to synchronize CPU hotplug callbacks allocating and freeing resources with compression/decompression paths. Make sure that acomp_ctx.req is NULL when the resources are freed. In the compression/decompression paths, check if acomp_ctx.req is NULL after acquiring the mutex (meaning the CPU was offlined) and retry on the new CPU.
The initialization of acomp_ctx.mutex is moved from the CPU hotplug callback to the pool initialization where it belongs (where the mutex is allocated). In addition to adding clarity, this makes sure that CPU hotplug cannot reinitialize a mutex that is already locked by compression/decompression.
Previously a fix was attempted by holding cpus_read_lock() [1]. This would have caused a potential deadlock as it is possible for code already holding the lock to fall into reclaim and enter zswap (causing a deadlock). A fix was also attempted using SRCU for synchronization, but Johannes pointed out that synchronize_srcu() cannot be used in CPU hotplug notifiers [2].
Alternative fixes that were considered/attempted and could have worked:
- Refcounting the per-CPU acomp_ctx. This involves complexity in handling the race between the refcount dropping to zero in zswap_[de]compress() and the refcount being re-initialized when the CPU is onlined.
- Disabling migration before getting the per-CPU acomp_ctx [3], but that's discouraged and is a much bigger hammer than needed, and could result in subtle performance issues.
[1]https://lkml.kernel.org/[email protected]/ [2]https://lkml.kernel.org/[email protected]/ [3]https://lkml.kernel.org/[email protected]/
[[email protected]: remove comment]
- Record
AZL-58989- Updated
- 2026-11-02
OSVAZL-59094 No score
CVE-2025-21693 affecting package kernel 6.6.161.1-1
In the Linux kernel, the following vulnerability has been resolved:
mm: zswap: properly synchronize freeing resources during CPU hotunplug
In zswap_compress() and zswap_decompress(), the per-CPU acomp_ctx of the current CPU at the beginning of the operation is retrieved and used throughout. However, since neither preemption nor migration are disabled, it is possible that the operation continues on a different CPU.
If the original CPU is hotunplugged while the acomp_ctx is still in use, we run into a UAF bug as some of the resources attached to the acomp_ctx are freed during hotunplug in zswap_cpu_comp_dead() (i.e. acomp_ctx.buffer, acomp_ctx.req, or acomp_ctx.acomp).
The problem was introduced in commit 1ec3b5fe6eec ("mm/zswap: move to use crypto_acomp API for hardware acceleration") when the switch to the crypto_acomp API was made. Prior to that, the per-CPU crypto_comp was retrieved using get_cpu_ptr() which disables preemption and makes sure the CPU cannot go away from under us. Preemption cannot be disabled with the crypto_acomp API as a sleepable context is needed.
Use the acomp_ctx.mutex to synchronize CPU hotplug callbacks allocating and freeing resources with compression/decompression paths. Make sure that acomp_ctx.req is NULL when the resources are freed. In the compression/decompression paths, check if acomp_ctx.req is NULL after acquiring the mutex (meaning the CPU was offlined) and retry on the new CPU.
The initialization of acomp_ctx.mutex is moved from the CPU hotplug callback to the pool initialization where it belongs (where the mutex is allocated). In addition to adding clarity, this makes sure that CPU hotplug cannot reinitialize a mutex that is already locked by compression/decompression.
Previously a fix was attempted by holding cpus_read_lock() [1]. This would have caused a potential deadlock as it is possible for code already holding the lock to fall into reclaim and enter zswap (causing a deadlock). A fix was also attempted using SRCU for synchronization, but Johannes pointed out that synchronize_srcu() cannot be used in CPU hotplug notifiers [2].
Alternative fixes that were considered/attempted and could have worked:
- Refcounting the per-CPU acomp_ctx. This involves complexity in handling the race between the refcount dropping to zero in zswap_[de]compress() and the refcount being re-initialized when the CPU is onlined.
- Disabling migration before getting the per-CPU acomp_ctx [3], but that's discouraged and is a much bigger hammer than needed, and could result in subtle performance issues.
[1]https://lkml.kernel.org/[email protected]/ [2]https://lkml.kernel.org/[email protected]/ [3]https://lkml.kernel.org/[email protected]/
[[email protected]: remove comment]
- Record
AZL-59094- Updated
- 2026-11-05
OSVCLSA-2026-1779434490 No score
kernel: Fix of 100 CVEs
- tracing: Verify event formats that have "%*p.." {CVE-2025-37938}
- HID: pidff: Fix null pointer dereference in pidff_find_fields {CVE-2025-37862}
- scsi: st: Fix array overflow in st_setup() {CVE-2025-37857}
- drm/amdkfd: debugfs hang_hws skip GPU with MES {CVE-2025-37853}
- mm/vmscan: don't try to reclaim hwpoison folio {CVE-2025-37834}
- cpufreq: scmi: Fix null-ptr-deref in scmi_cpufreq_get_rate() {CVE-2025-37830}
- drm/amdgpu: handle amdgpu_cgs_create_device() errors in amd_powerplay_create() {CVE-2025-37852}
- cpufreq: scpi: Fix null-ptr-deref in scpi_cpufreq_get_rate() {CVE-2025-37829}
- sound/virtio: Fix cancel_sync warnings on uninitialized work_structs {CVE-2025-37805}
- net: tls: explicitly disallow disconnect {CVE-2025-37756}
- drm/amd/pm: Prevent division by zero {CVE-2025-37770}
- drm/amd/pm: Prevent division by zero {CVE-2025-37768}
- net: Remove RTNL dance for SIOCBRADDIF and SIOCBRDELIF. {CVE-2025-22111}
- wifi: ath11k: Clear affinity hint before calling ath11k_pcic_free_irq() in error path {CVE-2025-23129}
- x86/mm: Fix flush_tlb_range() when used for zapping normal PMDs {CVE-2025-22045}
- ftrace: Avoid potential division by zero in function_stat_show() {CVE-2025-21898}
- md/md-bitmap: Synchronize bitmap_get_stats() with bitmap lifetime {CVE-2025-21712}
- bpf: Fix softlockup in arena_map_free on 64k page kernel {CVE-2025-21851}
- RDMA/rxe: Fix the warning "__rxe_cleanup+0x12c/0x170 [rdma_rxe]" {CVE-2025-21829}
- mm: zswap: properly synchronize freeing resources during CPU hotunplug {CVE-2025-21693}
- drop_monitor: fix incorrect initialization order {CVE-2025-21862}
- ptp: Ensure info->enable callback is always set {CVE-2025-21814}
- efi: Don't map the entire mokvar table to determine its size {CVE-2025-21872}
- drm/amd/display: Assign normalized_pix_clk when color depth = 14 {CVE-2025-21956}
- net: usb: rtl8150: enable basic endpoint checking {CVE-2025-21708}
- nfp: bpf: Add check for nfp_app_ctrl_msg_alloc() {CVE-2025-21848}
- netfilter: nf_tables: reject mismatching sum of field_len with set key length {CVE-2025-21826}
- mm: clear uffd-wp PTE/PMD state on mremap() {CVE-2025-21696}
- wifi: cfg80211: regulatory: improve invalid hints checking {CVE-2025-21910}
- eth: bnxt: always recalculate features after XDP clearing, fix null-deref {CVE-2025-21682}
- vxlan: check vxlan_vnigroup_init() return value {CVE-2025-21790}
- ata: libata-sff: Ensure that we cannot write outside the allocated buffer {CVE-2025-21738}
- wifi: mac80211: don't flush non-uploaded STAs {CVE-2025-21828}
- team: better TEAM_OPTION_TYPE_STRING validation {CVE-2025-21787}
- ppp: Fix KMSAN uninit-value warning with bpf {CVE-2025-21922}
- scsi: storvsc: Ratelimit warning logs to prevent VM denial of service {CVE-2025-21690}
- sctp: sysctl: udp_port: avoid using current->nsproxy {CVE-2025-21637}
- cgroup/cpuset: remove kernfs active break {CVE-2025-21634}
- KVM: Explicitly verify target vCPU is online in kvm_get_vcpu() {CVE-2024-58083}
- idpf: convert workqueues to unbound {CVE-2024-58057}
- xfrm: state: fix out-of-bounds read during lookup {CVE-2024-57982}
- printk: Fix signed integer overflow when defining LOG_BUF_LEN_MAX {CVE-2024-58017}
- Bluetooth: btbcm: Fix NULL deref in btbcm_get_board_name() {CVE-2024-57988}
- HID: core: Fix assumption that Resolution Multipliers must be in Logical Collections {CVE-2024-57986}
- virtio-blk: don't keep queue frozen during system suspend {CVE-2024-57946}
- drm/amd/display: Initialize denominator defaults to 1 {CVE-2024-57950}
- fs: relax assertions on failure to encode file handles {CVE-2024-57924}
- drm/amd/display: Add check for granularity in dml ceil/floor helpers {CVE-2024-57922}
- scsi: qedf: Fix a possible memory leak in qedf_alloc_and_init_sb() {CVE-2024-56748}
- ACPI: x86: Add adev NULL check to acpi_quirk_skip_serdev_enumeration() {CVE-2024-56782}
- scsi: qedi: Fix a possible memory leak in qedi_alloc_and_init_sb() {CVE-2024-56747}
- netdevsim: prevent bad user input in…
- Record
CLSA-2026-1779434490- Updated
- 2026-11-02
OSVROOT-OS-DEBIAN-12-CVE-2025-21693 No score
CVE-2025-21693 in linux - Patched by Root
Root has patched CVE-2025-21693 in the linux package for Root:Debian:12. Multiple fixed versions available.
- Record
ROOT-OS-DEBIAN-12-CVE-2025-21693- Updated
- 2026-11-02
OSVROOT-OS-UBUNTU-2204-CVE-2025-21693 No score
CVE-2025-21693 in linux - Patched by Root
Root has patched CVE-2025-21693 in the linux package for Root:Ubuntu:22.04. Multiple fixed versions available.
- Record
ROOT-OS-UBUNTU-2204-CVE-2025-21693- Updated
- 2026-11-06
OSVROOT-OS-UBUNTU-2404-CVE-2025-21693 No score
CVE-2025-21693 in linux - Patched by Root
Root has patched CVE-2025-21693 in the linux package for Root:Ubuntu:24.04. Multiple fixed versions available.
- Record
ROOT-OS-UBUNTU-2404-CVE-2025-21693- Updated
- 2026-11-06
OSVSUSE-SU-2025:01919-1 No score
Security update for the Linux Kernel
The SUSE Linux Enterprise 15 SP6 Confidential Computing kernel was updated to receive various security bugfixes.
The following security bugs were fixed:
- CVE-2023-52927: netfilter: allow exp not to be removed in nf_ct_find_expectation (bsc#1239644).
- CVE-2024-28956: x86/ibt: Keep IBT disabled during alternative patching (bsc#1242006).
- CVE-2024-35840: mptcp: use OPTION_MPTCP_MPJ_SYNACK in subflow_finish_connect() (bsc#1224597).
- CVE-2024-35910: tcp: properly terminate timers for kernel sockets (bsc#1224489).
- CVE-2024-41005: netpoll: Fix race condition in netpoll_owner_active (bsc#1227858).
- CVE-2024-43869: perf: Fix hang while freeing sigtrap event (bsc#1229491).
- CVE-2024-46713: kabi fix for perf/aux: Fix AUX buffer serialization (bsc#1230581).
- CVE-2024-46782: ila: call nf_unregister_net_hooks() sooner (bsc#1230769).
- CVE-2024-47408: net/smc: check smcd_v2_ext_offset when receiving proposal msg (bsc#1235711).
- CVE-2024-47794: kABI: bpf: Prevent tailcall infinite loop caused by freplace kABI workaround (bsc#1235712).
- CVE-2024-49571: net/smc: check iparea_offset and ipv6_prefixes_cnt when receiving proposal msg (bsc#1235733).
- CVE-2024-49940: l2tp: prevent possible tunnel refcount underflow (bsc#1232812).
- CVE-2024-50029: Bluetooth: hci_conn: Fix UAF in hci_enhanced_setup_sync (bsc#1231949).
- CVE-2024-50036: net: do not delay dst_entries_add() in dst_release() (bsc#1231912).
- CVE-2024-50038: netfilter: xtables: fix typo causing some targets not to load on IPv6 (bsc#1231910).
- CVE-2024-50056: usb: gadget: uvc: Fix ERR_PTR dereference in uvc_v4l2.c (bsc#1232389).
- CVE-2024-50140: net: sched: use RCU read-side critical section in taprio_dump() (bsc#1233060).
- CVE-2024-50162: bpf: selftests: send packet to devmap redirect XDP (bsc#1233075).
- CVE-2024-50163: bpf: Make sure internal and UAPI bpf_redirect flags do not overlap (bsc#1233098).
- CVE-2024-50223: sched/numa: Fix the potential null pointer dereference in (bsc#1233192).
- CVE-2024-50294: rxrpc: Fix missing locking causing hanging calls (bsc#1233483).
- CVE-2024-53057: net/sched: stop qdisc_tree_reduce_backlog on TC_H_ROOT (bsc#1233551).
- CVE-2024-53124: net: fix data-races around sk->sk_forward_alloc (bsc#1234074).
- CVE-2024-53135: KVM: VMX: Bury Intel PT virtualization (guest/host mode) behind CONFIG_BROKEN (bsc#1234154).
- CVE-2024-53139: sctp: fix possible UAF in sctp_v6_available() (bsc#1234157).
- CVE-2024-53140: netlink: terminate outstanding dump on socket close (bsc#1234222).
- CVE-2024-53176: smb: During unmount, ensure all cached dir instances drop their dentry (bsc#1234894).
- CVE-2024-53177: smb: prevent use-after-free due to open_cached_dir error paths (bsc#1234896).
- CVE-2024-53178: smb: Do not leak cfid when reconnect races with open_cached_dir (bsc#1234895).
- CVE-2024-53680: ipvs: fix UB due to uninitialized stack access in ip_vs_protocol_init() (bsc#1235715).
- CVE-2024-54458: scsi: ufs: bsg: Set bsg_queue to NULL after removal (bsc#1238992).
- CVE-2024-54683: netfilter: IDLETIMER: Fix for possible ABBA deadlock (bsc#1235729).
- CVE-2024-56638: kABI fix for 'netfilter: nft_inner: incorrect percpu area handling under softirq' (bsc#1235524).
- CVE-2024-56640: net/smc: fix LGR and link use-after-free issue (bsc#1235436).
- CVE-2024-56703: ipv6: Fix soft lockups in fib6_select_path under high next hop churn (bsc#1235455).
- CVE-2024-56718: net/smc: protect link down work from execute after lgr freed (bsc#1235589).
- CVE-2024-56719: net: stmmac: fix TSO DMA API usage causing oops (bsc#1235591).
- CVE-2024-56751: ipv6: release nexthop on device removal (bsc#1234936).
- CVE-2024-56758: btrfs: check folio mapping after unlock in relocate_one_folio() (bsc#1235621).
- CVE-2024-56770: net/sched: netem: account for backlog updates from child qdisc (bsc#1235637).
- CVE-2024-57900: ila: serialize calls to nf_register_net_hooks() (bsc#1235973).
- CVE-2024-57924: fs: relax assertions on failure to encode file handles (bsc#1236086). -…
- Record
SUSE-SU-2025:01919-1- Updated
- 2026-11-02
OSVSUSE-SU-2025:01967-1 No score
Security update for the Linux Kernel
The SUSE Linux Enterprise 15 SP7 Azure kernel was updated to receive various security bugfixes.
The following security bugs were fixed:
- CVE-2023-52927: netfilter: allow exp not to be removed in nf_ct_find_expectation (bsc#1239644).
- CVE-2024-28956: x86/ibt: Keep IBT disabled during alternative patching (bsc#1242006).
- CVE-2024-35840: mptcp: use OPTION_MPTCP_MPJ_SYNACK in subflow_finish_connect() (bsc#1224597).
- CVE-2024-35910: tcp: properly terminate timers for kernel sockets (bsc#1224489).
- CVE-2024-41005: netpoll: Fix race condition in netpoll_owner_active (bsc#1227858).
- CVE-2024-46713: kabi fix for perf/aux: Fix AUX buffer serialization (bsc#1230581).
- CVE-2024-46782: ila: call nf_unregister_net_hooks() sooner (bsc#1230769).
- CVE-2024-47408: net/smc: check smcd_v2_ext_offset when receiving proposal msg (bsc#1235711).
- CVE-2024-47794: kABI: bpf: Prevent tailcall infinite loop caused by freplace kABI workaround (bsc#1235712).
- CVE-2024-49570: drm/xe/tracing: Fix a potential TP_printk UAF (bsc#1238782).
- CVE-2024-49571: net/smc: check iparea_offset and ipv6_prefixes_cnt when receiving proposal msg (bsc#1235733).
- CVE-2024-50038: netfilter: xtables: fix typo causing some targets not to load on IPv6 (bsc#1231910).
- CVE-2024-50056: usb: gadget: uvc: Fix ERR_PTR dereference in uvc_v4l2.c (bsc#1232389).
- CVE-2024-50140: net: sched: use RCU read-side critical section in taprio_dump() (bsc#1233060).
- CVE-2024-50223: sched/numa: Fix the potential null pointer dereference in (bsc#1233192).
- CVE-2024-53057: net/sched: stop qdisc_tree_reduce_backlog on TC_H_ROOT (bsc#1233551).
- CVE-2024-53124: net: fix data-races around sk->sk_forward_alloc (bsc#1234074).
- CVE-2024-53139: sctp: fix possible UAF in sctp_v6_available() (bsc#1234157).
- CVE-2024-53140: netlink: terminate outstanding dump on socket close (bsc#1234222).
- CVE-2024-53680: ipvs: fix UB due to uninitialized stack access in ip_vs_protocol_init() (bsc#1235715).
- CVE-2024-54458: scsi: ufs: bsg: Set bsg_queue to NULL after removal (bsc#1238992).
- CVE-2024-54683: netfilter: IDLETIMER: Fix for possible ABBA deadlock (bsc#1235729).
- CVE-2024-56638: kABI fix for 'netfilter: nft_inner: incorrect percpu area handling under softirq' (bsc#1235524).
- CVE-2024-56640: net/smc: fix LGR and link use-after-free issue (bsc#1235436).
- CVE-2024-56703: ipv6: Fix soft lockups in fib6_select_path under high next hop churn (bsc#1235455).
- CVE-2024-56718: net/smc: protect link down work from execute after lgr freed (bsc#1235589).
- CVE-2024-56719: net: stmmac: fix TSO DMA API usage causing oops (bsc#1235591).
- CVE-2024-56751: ipv6: release nexthop on device removal (bsc#1234936).
- CVE-2024-56758: btrfs: check folio mapping after unlock in relocate_one_folio() (bsc#1235621).
- CVE-2024-56770: net/sched: netem: account for backlog updates from child qdisc (bsc#1235637).
- CVE-2024-57900: ila: serialize calls to nf_register_net_hooks() (bsc#1235973).
- CVE-2024-57924: fs: relax assertions on failure to encode file handles (bsc#1236086).
- CVE-2024-57947: netfilter: nf_set_pipapo: fix initial map fill (bsc#1236333).
- CVE-2024-57974: udp: Deal with race between UDP socket address change and rehash (bsc#1238532).
- CVE-2024-58018: nvkm: correctly calculate the available space of the GSP cmdq buffer (bsc#1238990).
- CVE-2024-58019: nvkm/gsp: correctly advance the read pointer of GSP message queue (bsc#1238997).
- CVE-2024-58068: OPP: fix dev_pm_opp_find_bw_*() when bandwidth table not initialized (bsc#1238961).
- CVE-2024-58070: bpf: bpf_local_storage: Always use bpf_mem_alloc in PREEMPT_RT (bsc#1238983).
- CVE-2024-58071: team: prevent adding a device which is already a team device lower (bsc#1238970).
- CVE-2024-58074: drm/i915: Grab intel_display from the encoder to avoid potential (bsc#1238972).
- CVE-2024-58083: KVM: Explicitly verify target vCPU is online in kvm_get_vcpu() (bsc#1239036).
- CVE-2024-58088: bpf: Fix deadlock when freeing cgroup storage (bsc#1239510). -…
- Record
SUSE-SU-2025:01967-1- Updated
- 2026-11-02
OSVSUSE-SU-2025:1176-1 No score
Security update for the Linux Kernel
The SUSE Linux Enterprise 15 SP5 RT kernel was updated to receive various security bugfixes.
The following security bugs were fixed:
- CVE-2022-49053: scsi: target: tcmu: Fix possible page UAF (bsc#1237918).
- CVE-2022-49465: blk-throttle: Set BIO_THROTTLED when bio has been throttled (bsc#1238919).
- CVE-2022-49739: gfs2: Always check inode size of inline inodes (bsc#1240207).
- CVE-2023-52935: mm/khugepaged: fix ->anon_vma race (bsc#1240276).
- CVE-2024-53124: net: fix data-races around sk->sk_forward_alloc (bsc#1234074).
- CVE-2024-53176: smb: During unmount, ensure all cached dir instances drop their dentry (bsc#1234894).
- CVE-2024-53178: smb: Do not leak cfid when reconnect races with open_cached_dir (bsc#1234895).
- CVE-2024-56651: can: hi311x: hi3110_can_ist(): fix potential use-after-free (bsc#1235528).
- CVE-2024-57996: net_sched: sch_sfq: do not allow 1 packet limit (bsc#1239076).
- CVE-2024-58013: Bluetooth: MGMT: Fix slab-use-after-free Read in mgmt_remove_adv_monitor_sync (bsc#1239095).
- CVE-2024-58014: wifi: brcmsmac: add gain range check to wlc_phy_iqcal_gainparams_nphy() (bsc#1239109).
- CVE-2025-21693: mm: zswap: properly synchronize freeing resources during CPU hotunplug (bsc#1237029).
- CVE-2025-21718: net: rose: fix timer races against user threads (bsc#1239073).
- CVE-2025-21772: partitions: mac: fix handling of bogus partition table (bsc#1238911).
- CVE-2025-21780: drm/amdgpu: avoid buffer overflow attach in smu_sys_set_pp_table() (bsc#1239115).
The following non-security bugs were fixed:
- ACPI: processor: idle: Return an error if both P_LVL{2,3} idle states are invalid (bsc#1237530).
- RDMA/mana_ib: Prefer struct_size over open coded arithmetic (bsc#1239016).
- RDMA/mana_ib: Use v2 version of cfg_rx_steer_req to enable RX coalescing (bsc#1239016).
- Revert 'gfs2: Fix inode height consistency check (git-fixes).
- btrfs: defrag: do not use merged extent map for their generation check (bsc#1239968).
- btrfs: fix defrag not merging contiguous extents due to merged extent maps (bsc#1239968).
- btrfs: fix extent map merging not happening for adjacent extents (bsc#1239968).
- btrfs: send: allow cloning non-aligned extent if it ends at i_size (bsc#1239969).
- btrfs: send: fix invalid clone operation for file that got its size decreased (bsc#1239969).
- cifs: Add a laundromat thread for cached directories (git-fixes).
- cifs: fix potential null pointer use in destroy_workqueue in init_cifs error path (git-fixes).
- gfs2: Fix inode height consistency check (git-fixes).
- mm/mmu_notifier.c: fix race in mmu_interval_notifier_remove() (bsc#1239126).
- mm: zswap: move allocations during CPU init outside the lock (git-fixes).
- net: mana: Add flex array to struct mana_cfg_rx_steer_req_v2 (bsc#1239016).
- net: mana: Allow variable size indirection table (bsc#1239016).
- net: mana: Avoid open coded arithmetic (bsc#1239016).
- net: mana: Support holes in device list reply msg (bsc#1240133).
- sched/membarrier: Fix redundant load of membarrier_state (bsc#1232743).
- smb3: allow controlling length of time directory entries are cached with dir leases (git-fixes).
- smb3: do not start laundromat thread when dir leases disabled (git-fixes).
- smb3: retrying on failed server close (git-fixes).
- smb: client: destroy cfid_put_wq on module exit (git-fixes).
- smb: client: disable directory caching when dir_cache_timeout is zero (git-fixes).
- smb: client: do not start laundromat thread on nohandlecache (git-fixes).
- smb: client: make laundromat a delayed worker (git-fixes).
- smb: client: properly close cfids on umount (bsc#1231432, bsc#1232299, bsc#1235599, bsc#1234896).
- tpm: send_data: Wait longer for the TPM to become ready (bsc#1235870).
- Record
SUSE-SU-2025:1176-1- Updated
- 2026-11-02
OSVSUSE-SU-2025:1177-1 No score
Security update for the Linux Kernel
The SUSE Linux Enterprise 15 SP6 Azure kernel was updated to receive various security bugfixes.
The following security bugs were fixed:
- CVE-2023-52927: netfilter: allow exp not to be removed in nf_ct_find_expectation (bsc#1239644).
- CVE-2024-35910: tcp: properly terminate timers for kernel sockets (bsc#1224489).
- CVE-2024-41005: netpoll: Fix race condition in netpoll_owner_active (bsc#1227858).
- CVE-2024-46782: ila: call nf_unregister_net_hooks() sooner (bsc#1230769).
- CVE-2024-47408: net/smc: check smcd_v2_ext_offset when receiving proposal msg (bsc#1235711).
- CVE-2024-47794: kABI: bpf: Prevent tailcall infinite loop caused by freplace kABI workaround (bsc#1235712).
- CVE-2024-49571: net/smc: check iparea_offset and ipv6_prefixes_cnt when receiving proposal msg (bsc#1235733).
- CVE-2024-49940: kABI fix for l2tp: prevent possible tunnel refcount underflow (bsc#1232812).
- CVE-2024-50056: usb: gadget: uvc: Fix ERR_PTR dereference in uvc_v4l2.c (bsc#1232389).
- CVE-2024-50140: net: sched: use RCU read-side critical section in taprio_dump() (bsc#1233060).
- CVE-2024-53057: net/sched: stop qdisc_tree_reduce_backlog on TC_H_ROOT (bsc#1233551).
- CVE-2024-53140: netlink: terminate outstanding dump on socket close (bsc#1234222).
- CVE-2024-53680: ipvs: fix UB due to uninitialized stack access in ip_vs_protocol_init() (bsc#1235715).
- CVE-2024-54683: netfilter: IDLETIMER: Fix for possible ABBA deadlock (bsc#1235729).
- CVE-2024-56638: kABI fix for 'netfilter: nft_inner: incorrect percpu area handling under softirq' (bsc#1235524).
- CVE-2024-56640: net/smc: fix LGR and link use-after-free issue (bsc#1235436).
- CVE-2024-56702: bpf: Add tracepoints with null-able arguments (bsc#1235501).
- CVE-2024-56703: ipv6: Fix soft lockups in fib6_select_path under high next hop churn (bsc#1235455).
- CVE-2024-56718: net/smc: protect link down work from execute after lgr freed (bsc#1235589).
- CVE-2024-56719: net: stmmac: fix TSO DMA API usage causing oops (bsc#1235591).
- CVE-2024-56751: ipv6: release nexthop on device removal (bsc#1234936).
- CVE-2024-56758: btrfs: check folio mapping after unlock in relocate_one_folio() (bsc#1235621).
- CVE-2024-56770: net/sched: netem: account for backlog updates from child qdisc (bsc#1235637).
- CVE-2024-57900: ila: serialize calls to nf_register_net_hooks() (bsc#1235973).
- CVE-2024-57947: netfilter: nf_set_pipapo: fix initial map fill (bsc#1236333).
- CVE-2024-57974: udp: Deal with race between UDP socket address change and rehash (bsc#1238532).
- CVE-2024-57996: net_sched: sch_sfq: do not allow 1 packet limit (bsc#1239076).
- CVE-2024-58012: ASoC: SOF: Intel: hda-dai: Ensure DAI widget is valid during params (bsc#1239104).
- CVE-2024-58019: nvkm/gsp: correctly advance the read pointer of GSP message queue (bsc#1238997).
- CVE-2024-58083: KVM: Explicitly verify target vCPU is online in kvm_get_vcpu() (bsc#1239036).
- CVE-2025-21635: rds: sysctl: rds_tcp_{rcv,snd}buf: avoid using current->nsproxy (bsc#1236111).
- CVE-2025-21659: netdev: prevent accessing NAPI instances from another namespace (bsc#1236206).
- CVE-2025-21693: mm: zswap: properly synchronize freeing resources during CPU hotunplug (bsc#1237029).
- CVE-2025-21701: net: avoid race between device unregistration and ethnl ops (bsc#1237164).
- CVE-2025-21703: netem: Update sch->q.qlen before qdisc_tree_reduce_backlog() (bsc#1237313).
- CVE-2025-21706: mptcp: pm: only set fullmesh for subflow endp (bsc#1238528).
- CVE-2025-21739: kABI: ufshcd: add ufshcd_dealloc_host back (bsc#1238506).
- CVE-2025-21753: btrfs: fix use-after-free when attempting to join an aborted transaction (bsc#1237875).
- CVE-2025-21759: ipv6: mcast: extend RCU protection in igmp6_send() (bsc#1238738).
- CVE-2025-21760: ndisc: extend RCU protection in ndisc_send_skb() (bsc#1238763).
- CVE-2025-21761: openvswitch: use RCU protection in ovs_vport_cmd_fill_info() (bsc#1238775).
- CVE-2025-21762: arp: use RCU protection in arp_xmit() (bsc#1238780).
- CVE-2025-21763:…
- Record
SUSE-SU-2025:1177-1- Updated
- 2026-11-02
OSVSUSE-SU-2025:1178-1 No score
Security update for the Linux Kernel
The SUSE Linux Enterprise 15 SP6 RT kernel was updated to receive various security bugfixes.
The following security bugs were fixed:
- CVE-2023-52927: netfilter: allow exp not to be removed in nf_ct_find_expectation (bsc#1239644).
- CVE-2024-35910: tcp: properly terminate timers for kernel sockets (bsc#1224489).
- CVE-2024-41005: netpoll: Fix race condition in netpoll_owner_active (bsc#1227858).
- CVE-2024-46782: ila: call nf_unregister_net_hooks() sooner (bsc#1230769).
- CVE-2024-47408: net/smc: check smcd_v2_ext_offset when receiving proposal msg (bsc#1235711).
- CVE-2024-47794: kABI: bpf: Prevent tailcall infinite loop caused by freplace kABI workaround (bsc#1235712).
- CVE-2024-49571: net/smc: check iparea_offset and ipv6_prefixes_cnt when receiving proposal msg (bsc#1235733).
- CVE-2024-49940: kABI fix for l2tp: prevent possible tunnel refcount underflow (bsc#1232812).
- CVE-2024-50056: usb: gadget: uvc: Fix ERR_PTR dereference in uvc_v4l2.c (bsc#1232389).
- CVE-2024-50140: net: sched: use RCU read-side critical section in taprio_dump() (bsc#1233060).
- CVE-2024-53057: net/sched: stop qdisc_tree_reduce_backlog on TC_H_ROOT (bsc#1233551).
- CVE-2024-53140: netlink: terminate outstanding dump on socket close (bsc#1234222).
- CVE-2024-53680: ipvs: fix UB due to uninitialized stack access in ip_vs_protocol_init() (bsc#1235715).
- CVE-2024-54683: netfilter: IDLETIMER: Fix for possible ABBA deadlock (bsc#1235729).
- CVE-2024-56638: kABI fix for 'netfilter: nft_inner: incorrect percpu area handling under softirq' (bsc#1235524).
- CVE-2024-56640: net/smc: fix LGR and link use-after-free issue (bsc#1235436).
- CVE-2024-56702: bpf: Add tracepoints with null-able arguments (bsc#1235501).
- CVE-2024-56703: ipv6: Fix soft lockups in fib6_select_path under high next hop churn (bsc#1235455).
- CVE-2024-56718: net/smc: protect link down work from execute after lgr freed (bsc#1235589).
- CVE-2024-56719: net: stmmac: fix TSO DMA API usage causing oops (bsc#1235591).
- CVE-2024-56751: ipv6: release nexthop on device removal (bsc#1234936).
- CVE-2024-56758: btrfs: check folio mapping after unlock in relocate_one_folio() (bsc#1235621).
- CVE-2024-56770: net/sched: netem: account for backlog updates from child qdisc (bsc#1235637).
- CVE-2024-57900: ila: serialize calls to nf_register_net_hooks() (bsc#1235973).
- CVE-2024-57947: netfilter: nf_set_pipapo: fix initial map fill (bsc#1236333).
- CVE-2024-57974: udp: Deal with race between UDP socket address change and rehash (bsc#1238532).
- CVE-2024-57979: kABI workaround for pps changes (bsc#1238521).
- CVE-2024-57996: net_sched: sch_sfq: do not allow 1 packet limit (bsc#1239076).
- CVE-2024-58012: ASoC: SOF: Intel: hda-dai: Ensure DAI widget is valid during params (bsc#1239104).
- CVE-2024-58019: nvkm/gsp: correctly advance the read pointer of GSP message queue (bsc#1238997).
- CVE-2024-58083: KVM: Explicitly verify target vCPU is online in kvm_get_vcpu() (bsc#1239036).
- CVE-2025-21635: rds: sysctl: rds_tcp_{rcv,snd}buf: avoid using current->nsproxy (bsc#1236111).
- CVE-2025-21659: netdev: prevent accessing NAPI instances from another namespace (bsc#1236206).
- CVE-2025-21693: mm: zswap: properly synchronize freeing resources during CPU hotunplug (bsc#1237029).
- CVE-2025-21701: net: avoid race between device unregistration and ethnl ops (bsc#1237164).
- CVE-2025-21703: netem: Update sch->q.qlen before qdisc_tree_reduce_backlog() (bsc#1237313).
- CVE-2025-21706: mptcp: pm: only set fullmesh for subflow endp (bsc#1238528).
- CVE-2025-21733: tracing/osnoise: Fix resetting of tracepoints (bsc#1238494).
- CVE-2025-21739: kABI: ufshcd: add ufshcd_dealloc_host back (bsc#1238506).
- CVE-2025-21753: btrfs: fix use-after-free when attempting to join an aborted transaction (bsc#1237875).
- CVE-2025-21754: btrfs: fix assertion failure when splitting ordered extent after transaction abort (bsc#1238496).
- CVE-2025-21759: ipv6: mcast: extend RCU protection in igmp6_send() (bsc#1238738). -…
- Record
SUSE-SU-2025:1178-1- Updated
- 2026-11-02
OSVSUSE-SU-2025:1180-1 No score
Security update for the Linux Kernel
The SUSE Linux Enterprise 15 SP6 kernel was updated to receive various security bugfixes.
The following security bugs were fixed:
- CVE-2023-52927: netfilter: allow exp not to be removed in nf_ct_find_expectation (bsc#1239644).
- CVE-2024-35910: tcp: properly terminate timers for kernel sockets (bsc#1224489).
- CVE-2024-41005: netpoll: Fix race condition in netpoll_owner_active (bsc#1227858).
- CVE-2024-46782: ila: call nf_unregister_net_hooks() sooner (bsc#1230769).
- CVE-2024-47408: net/smc: check smcd_v2_ext_offset when receiving proposal msg (bsc#1235711).
- CVE-2024-47794: kABI: bpf: Prevent tailcall infinite loop caused by freplace kABI workaround (bsc#1235712).
- CVE-2024-49571: net/smc: check iparea_offset and ipv6_prefixes_cnt when receiving proposal msg (bsc#1235733).
- CVE-2024-49940: kABI fix for l2tp: prevent possible tunnel refcount underflow (bsc#1232812).
- CVE-2024-50056: usb: gadget: uvc: Fix ERR_PTR dereference in uvc_v4l2.c (bsc#1232389).
- CVE-2024-50140: net: sched: use RCU read-side critical section in taprio_dump() (bsc#1233060).
- CVE-2024-53057: net/sched: stop qdisc_tree_reduce_backlog on TC_H_ROOT (bsc#1233551).
- CVE-2024-53140: netlink: terminate outstanding dump on socket close (bsc#1234222).
- CVE-2024-53680: ipvs: fix UB due to uninitialized stack access in ip_vs_protocol_init() (bsc#1235715).
- CVE-2024-54683: netfilter: IDLETIMER: Fix for possible ABBA deadlock (bsc#1235729).
- CVE-2024-56638: kABI fix for 'netfilter: nft_inner: incorrect percpu area handling under softirq' (bsc#1235524).
- CVE-2024-56640: net/smc: fix LGR and link use-after-free issue (bsc#1235436).
- CVE-2024-56702: bpf: Add tracepoints with null-able arguments (bsc#1235501).
- CVE-2024-56703: ipv6: Fix soft lockups in fib6_select_path under high next hop churn (bsc#1235455).
- CVE-2024-56718: net/smc: protect link down work from execute after lgr freed (bsc#1235589).
- CVE-2024-56719: net: stmmac: fix TSO DMA API usage causing oops (bsc#1235591).
- CVE-2024-56751: ipv6: release nexthop on device removal (bsc#1234936).
- CVE-2024-56758: btrfs: check folio mapping after unlock in relocate_one_folio() (bsc#1235621).
- CVE-2024-56770: net/sched: netem: account for backlog updates from child qdisc (bsc#1235637).
- CVE-2024-57900: ila: serialize calls to nf_register_net_hooks() (bsc#1235973).
- CVE-2024-57947: netfilter: nf_set_pipapo: fix initial map fill (bsc#1236333).
- CVE-2024-57974: udp: Deal with race between UDP socket address change and rehash (bsc#1238532).
- CVE-2024-57979: kABI workaround for pps changes (bsc#1238521).
- CVE-2024-57996: net_sched: sch_sfq: do not allow 1 packet limit (bsc#1239076).
- CVE-2024-58012: ASoC: SOF: Intel: hda-dai: Ensure DAI widget is valid during params (bsc#1239104).
- CVE-2024-58019: nvkm/gsp: correctly advance the read pointer of GSP message queue (bsc#1238997).
- CVE-2024-58083: KVM: Explicitly verify target vCPU is online in kvm_get_vcpu() (bsc#1239036).
- CVE-2025-21635: rds: sysctl: rds_tcp_{rcv,snd}buf: avoid using current->nsproxy (bsc#1236111).
- CVE-2025-21659: netdev: prevent accessing NAPI instances from another namespace (bsc#1236206).
- CVE-2025-21693: mm: zswap: properly synchronize freeing resources during CPU hotunplug (bsc#1237029).
- CVE-2025-21701: net: avoid race between device unregistration and ethnl ops (bsc#1237164).
- CVE-2025-21703: netem: Update sch->q.qlen before qdisc_tree_reduce_backlog() (bsc#1237313).
- CVE-2025-21706: mptcp: pm: only set fullmesh for subflow endp (bsc#1238528).
- CVE-2025-21733: tracing/osnoise: Fix resetting of tracepoints (bsc#1238494).
- CVE-2025-21739: kABI: ufshcd: add ufshcd_dealloc_host back (bsc#1238506).
- CVE-2025-21753: btrfs: fix use-after-free when attempting to join an aborted transaction (bsc#1237875).
- CVE-2025-21754: btrfs: fix assertion failure when splitting ordered extent after transaction abort (bsc#1238496).
- CVE-2025-21759: ipv6: mcast: extend RCU protection in igmp6_send() (bsc#1238738). -…
- Record
SUSE-SU-2025:1180-1- Updated
- 2026-11-02
OSVSUSE-SU-2025:1183-1 No score
Security update for the Linux Kernel
The SUSE Linux Enterprise 15 SP4 RT kernel was updated to receive various security bugfixes.
The following security bugs were fixed:
- CVE-2022-49053: scsi: target: tcmu: Fix possible page UAF (bsc#1237918).
- CVE-2022-49465: blk-throttle: Set BIO_THROTTLED when bio has been throttled (bsc#1238919).
- CVE-2022-49739: gfs2: Always check inode size of inline inodes (bsc#1240207).
- CVE-2023-52935: mm/khugepaged: fix ->anon_vma race (bsc#1240276).
- CVE-2024-2201: Fixed information leak in x86/BHI (bsc#1217339).
- CVE-2024-41092: drm/i915/gt: Fix potential UAF by revoke of fence registers (bsc#1228483).
- CVE-2024-42098: crypto: ecdh - explicitly zeroize private_key (bsc#1228779).
- CVE-2024-42229: crypto: aead,cipher - zeroize key buffer after use (bsc#1228708).
- CVE-2024-53064: idpf: fix idpf_vc_core_init error path (bsc#1233558 bsc#1234464).
- CVE-2024-56651: can: hi311x: hi3110_can_ist(): fix potential use-after-free (bsc#1235528).
- CVE-2024-57996: net_sched: sch_sfq: do not allow 1 packet limit (bsc#1239076).
- CVE-2024-58014: wifi: brcmsmac: add gain range check to wlc_phy_iqcal_gainparams_nphy() (bsc#1239109).
- CVE-2024-58083: KVM: Explicitly verify target vCPU is online in kvm_get_vcpu() (bsc#1239036).
- CVE-2025-21693: mm: zswap: properly synchronize freeing resources during CPU hotunplug (bsc#1237029).
- CVE-2025-21714: RDMA/mlx5: Fix implicit ODP use after free (bsc#1237890).
- CVE-2025-21718: net: rose: fix timer races against user threads (bsc#1239073).
- CVE-2025-21732: RDMA/mlx5: Fix a race for an ODP MR which leads to CQE with error (bsc#1237877).
- CVE-2025-21753: btrfs: fix use-after-free when attempting to join an aborted transaction (bsc#1237875).
- CVE-2025-21772: partitions: mac: fix handling of bogus partition table (bsc#1238911).
- CVE-2025-21780: drm/amdgpu: avoid buffer overflow attach in smu_sys_set_pp_table() (bsc#1239115).
- CVE-2025-21839: kABI: Fix kABI after backport od CVE-2025-21839 (bsc#1239061).
The following non-security bugs were fixed:
- ACPI: processor: idle: Return an error if both P_LVL{2,3} idle states are invalid (bsc#1237530).
- RDMA/mana_ib: Prefer struct_size over open coded arithmetic (bsc#1239016).
- RDMA/mana_ib: Use v2 version of cfg_rx_steer_req to enable RX coalescing (bsc#1239016).
- RDMA/mlx5: Fix implicit ODP hang on parent deregistration (git-fixes)
- btrfs: defrag: do not use merged extent map for their generation check (bsc#1239968).
- btrfs: fix defrag not merging contiguous extents due to merged extent maps (bsc#1239968).
- btrfs: fix extent map merging not happening for adjacent extents (bsc#1239968).
- btrfs: send: allow cloning non-aligned extent if it ends at i_size (bsc#1239969).
- btrfs: send: fix invalid clone operation for file that got its size decreased (bsc#1239969).
- gfs2: Fix inode height consistency check (git-fixes).
- mm/mmu_notifier.c: fix race in mmu_interval_notifier_remove() (bsc#1239126).
- mm: zswap: move allocations during CPU init outside the lock (git-fixes).
- net: mana: Add flex array to struct mana_cfg_rx_steer_req_v2 (bsc#1239016).
- net: mana: Allow variable size indirection table (bsc#1239016).
- net: mana: Avoid open coded arithmetic (bsc#1239016).
- net: mana: Fix error handling in mana_create_txq/rxq's NAPI cleanup (bsc#1240195).
- net: mana: Support holes in device list reply msg (bsc#1240133).
- x86/bhi: Avoid warning in #DB handler due to BHI mitigation (git-fixes).
- x86/bugs: Cache the value of MSR_IA32_ARCH_CAPABILITIES (git-fixes).
- x86/bugs: Fix BHI documentation (git-fixes).
- x86/bugs: Fix BHI handling of RRSBA (git-fixes).
- x86/bugs: Fix BHI retpoline check (git-fixes).
- x86/bugs: Fix return type of spectre_bhi_state() (git-fixes).
- x86/bugs: Remove CONFIG_BHI_MITIGATION_AUTO and spectre_bhi=auto (git-fixes).
- Record
SUSE-SU-2025:1183-1- Updated
- 2026-11-02
OSVSUSE-SU-2025:1195-1 No score
Security update for the Linux Kernel
The SUSE Linux Enterprise 15 SP4 kernel was updated to receive various security bugfixes.
The following security bugs were fixed:
- CVE-2022-49053: scsi: target: tcmu: Fix possible page UAF (bsc#1237918).
- CVE-2022-49465: blk-throttle: Set BIO_THROTTLED when bio has been throttled (bsc#1238919).
- CVE-2022-49739: gfs2: Always check inode size of inline inodes (bsc#1240207).
- CVE-2023-52935: mm/khugepaged: fix ->anon_vma race (bsc#1240276).
- CVE-2024-53064: idpf: fix idpf_vc_core_init error path (bsc#1233558 bsc#1234464).
- CVE-2024-56651: can: hi311x: hi3110_can_ist(): fix potential use-after-free (bsc#1235528).
- CVE-2024-58083: KVM: Explicitly verify target vCPU is online in kvm_get_vcpu() (bsc#1239036).
- CVE-2025-21693: mm: zswap: properly synchronize freeing resources during CPU hotunplug (bsc#1237029).
- CVE-2025-21714: RDMA/mlx5: Fix implicit ODP use after free (bsc#1237890).
- CVE-2025-21732: RDMA/mlx5: Fix a race for an ODP MR which leads to CQE with error (bsc#1237877).
- CVE-2025-21753: btrfs: fix use-after-free when attempting to join an aborted transaction (bsc#1237875).
- CVE-2025-21772: partitions: mac: fix handling of bogus partition table (bsc#1238911).
The following non-security bugs were fixed:
- ACPI: processor: idle: Return an error if both P_LVL{2,3} idle states are invalid (bsc#1237530).
- RDMA/mana_ib: Prefer struct_size over open coded arithmetic (bsc#1239016).
- RDMA/mana_ib: Use v2 version of cfg_rx_steer_req to enable RX coalescing (bsc#1239016).
- RDMA/mlx5: Fix implicit ODP hang on parent deregistration (git-fixes)
- btrfs: defrag: do not use merged extent map for their generation check (bsc#1239968).
- btrfs: fix defrag not merging contiguous extents due to merged extent maps (bsc#1239968).
- btrfs: fix extent map merging not happening for adjacent extents (bsc#1239968).
- btrfs: send: allow cloning non-aligned extent if it ends at i_size (bsc#1239969).
- btrfs: send: fix invalid clone operation for file that got its size decreased (bsc#1239969).
- gfs2: Fix inode height consistency check (git-fixes).
- mm/mmu_notifier.c: fix race in mmu_interval_notifier_remove() (bsc#1239126).
- mm: zswap: move allocations during CPU init outside the lock (git-fixes).
- net: mana: Add flex array to struct mana_cfg_rx_steer_req_v2 (bsc#1239016).
- net: mana: Allow variable size indirection table (bsc#1239016).
- net: mana: Avoid open coded arithmetic (bsc#1239016).
- net: mana: Fix error handling in mana_create_txq/rxq's NAPI cleanup (bsc#1240195).
- net: mana: Support holes in device list reply msg (bsc#1240133).
- Record
SUSE-SU-2025:1195-1- Updated
- 2026-11-02
OSVSUSE-SU-2025:1241-1 No score
Security update for the Linux Kernel
The SUSE Linux Enterprise 15 SP5 kernel was updated to receive various security bugfixes.
The following security bugs were fixed:
- CVE-2022-49053: scsi: target: tcmu: Fix possible page UAF (bsc#1237918).
- CVE-2022-49465: blk-throttle: Set BIO_THROTTLED when bio has been throttled (bsc#1238919).
- CVE-2022-49739: gfs2: Always check inode size of inline inodes (bsc#1240207).
- CVE-2023-52935: mm/khugepaged: fix ->anon_vma race (bsc#1240276).
- CVE-2024-53124: net: fix data-races around sk->sk_forward_alloc (bsc#1234074).
- CVE-2024-53176: smb: During unmount, ensure all cached dir instances drop their dentry (bsc#1234894).
- CVE-2024-53178: smb: Do not leak cfid when reconnect races with open_cached_dir (bsc#1234895).
- CVE-2024-56651: can: hi311x: hi3110_can_ist(): fix potential use-after-free (bsc#1235528).
- CVE-2024-57996: net_sched: sch_sfq: do not allow 1 packet limit (bsc#1239076).
- CVE-2024-58013: Bluetooth: MGMT: Fix slab-use-after-free Read in mgmt_remove_adv_monitor_sync (bsc#1239095).
- CVE-2024-58014: wifi: brcmsmac: add gain range check to wlc_phy_iqcal_gainparams_nphy() (bsc#1239109).
- CVE-2025-21693: mm: zswap: properly synchronize freeing resources during CPU hotunplug (bsc#1237029).
- CVE-2025-21718: net: rose: fix timer races against user threads (bsc#1239073).
- CVE-2025-21772: partitions: mac: fix handling of bogus partition table (bsc#1238911).
- CVE-2025-21780: drm/amdgpu: avoid buffer overflow attach in smu_sys_set_pp_table() (bsc#1239115).
The following non-security bugs were fixed:
- ACPI: processor: idle: Return an error if both P_LVL{2,3} idle states are invalid (bsc#1237530).
- btrfs: defrag: do not use merged extent map for their generation check (bsc#1239968).
- btrfs: fix defrag not merging contiguous extents due to merged extent maps (bsc#1239968).
- btrfs: fix extent map merging not happening for adjacent extents (bsc#1239968).
- btrfs: send: allow cloning non-aligned extent if it ends at i_size (bsc#1239969).
- btrfs: send: fix invalid clone operation for file that got its size decreased (bsc#1239969).
- cifs: Add a laundromat thread for cached directories (git-fixes).
- cifs: fix potential null pointer use in destroy_workqueue in init_cifs error path (git-fixes).
- gfs2: Fix inode height consistency check (git-fixes).
- mm: zswap: move allocations during CPU init outside the lock (git-fixes).
- mm/mmu_notifier.c: fix race in mmu_interval_notifier_remove() (bsc#1239126).
- net: mana: Add flex array to struct mana_cfg_rx_steer_req_v2 (bsc#1239016).
- net: mana: Allow variable size indirection table (bsc#1239016).
- net: mana: Avoid open coded arithmetic (bsc#1239016).
- net: mana: Support holes in device list reply msg (bsc#1240133).
- RDMA/mana_ib: Prefer struct_size over open coded arithmetic (bsc#1239016).
- RDMA/mana_ib: Use v2 version of cfg_rx_steer_req to enable RX coalescing (bsc#1239016).
- sched/membarrier: Fix redundant load of membarrier_state (bsc#1232743).
- smb: client: destroy cfid_put_wq on module exit (git-fixes).
- smb: client: disable directory caching when dir_cache_timeout is zero (git-fixes).
- smb: client: do not start laundromat thread on nohandlecache (git-fixes).
- smb: client: make laundromat a delayed worker (git-fixes).
- smb: client: properly close cfids on umount (bsc#1231432, bsc#1232299, bsc#1235599, bsc#1234896).
- smb3: allow controlling length of time directory entries are cached with dir leases (git-fixes).
- smb3: do not start laundromat thread when dir leases disabled (git-fixes).
- smb3: retrying on failed server close (git-fixes).
- tpm: send_data: Wait longer for the TPM to become ready (bsc#1235870).
- Record
SUSE-SU-2025:1241-1- Updated
- 2026-11-02
OSVSUSE-SU-2025:20190-1 No score
Security update for the Linux Kernel
The SUSE Linux Enterprise Micro 6.0 and 6.1 RT kernel was updated to receive various security bugfixes.
The following security bugs were fixed:
- CVE-2023-52927: netfilter: allow exp not to be removed in nf_ct_find_expectation (bsc#1239644).
- CVE-2024-26708: mptcp: fix inconsistent state on fastopen race (bsc#1222672).
- CVE-2024-35910: tcp: properly terminate timers for kernel sockets (bsc#1224489).
- CVE-2024-40980: drop_monitor: replace spin_lock by raw_spin_lock (bsc#1227937).
- CVE-2024-41005: netpoll: Fix race condition in netpoll_owner_active (bsc#1227858).
- CVE-2024-44974: mptcp: pm: avoid possible UaF when selecting endp (bsc#1230235).
- CVE-2024-45009: mptcp: pm: only decrement add_addr_accepted for MPJ req (bsc#1230438).
- CVE-2024-45010: mptcp: pm: only mark 'subflow' endp as available (bsc#1230439).
- CVE-2024-46782: ila: call nf_unregister_net_hooks() sooner (bsc#1230769).
- CVE-2024-46858: mptcp: pm: Fix uaf in __timer_delete_sync (bsc#1231088).
- CVE-2024-47408: net/smc: check smcd_v2_ext_offset when receiving proposal msg (bsc#1235711).
- CVE-2024-47794: kABI: bpf: Prevent tailcall infinite loop caused by freplace kABI workaround (bsc#1235712).
- CVE-2024-49571: net/smc: check iparea_offset and ipv6_prefixes_cnt when receiving proposal msg (bsc#1235733).
- CVE-2024-49940: kABI fix for l2tp: prevent possible tunnel refcount underflow (bsc#1232812).
- CVE-2024-50029: Bluetooth: hci_conn: Fix UAF in hci_enhanced_setup_sync (bsc#1231949).
- CVE-2024-50036: net: do not delay dst_entries_add() in dst_release() (bsc#1231912).
- CVE-2024-50056: usb: gadget: uvc: Fix ERR_PTR dereference in uvc_v4l2.c (bsc#1232389).
- CVE-2024-50085: mptcp: pm: fix UaF read in mptcp_pm_nl_rm_addr_or_subflow (bsc#1232508).
- CVE-2024-50140: net: sched: use RCU read-side critical section in taprio_dump() (bsc#1233060).
- CVE-2024-50142: xfrm: validate new SA's prefixlen using SA family when sel.family is unset (bsc#1233028).
- CVE-2024-50185: kABI fix for mptcp: handle consistently DSS corruption (bsc#1233109).
- CVE-2024-50251: netfilter: nft_payload: sanitize offset and length before calling skb_checksum() (bsc#1233248).
- CVE-2024-50258: net: fix crash when config small gso_max_size/gso_ipv4_max_size (bsc#1233221).
- CVE-2024-50294: rxrpc: Fix missing locking causing hanging calls (bsc#1233483).
- CVE-2024-50304: ipv4: ip_tunnel: Fix suspicious RCU usage warning in ip_tunnel_find() (bsc#1233522).
- CVE-2024-53057: net/sched: stop qdisc_tree_reduce_backlog on TC_H_ROOT (bsc#1233551).
- CVE-2024-53123: mptcp: error out earlier on disconnect (bsc#1234070).
- CVE-2024-53140: netlink: terminate outstanding dump on socket close (bsc#1234222).
- CVE-2024-53147: exfat: fix out-of-bounds access of directory entries (bsc#1234857).
- CVE-2024-53176: smb: During unmount, ensure all cached dir instances drop their dentry (bsc#1234894).
- CVE-2024-53177: smb: prevent use-after-free due to open_cached_dir error paths (bsc#1234896).
- CVE-2024-53178: smb: Do not leak cfid when reconnect races with open_cached_dir (bsc#1234895).
- CVE-2024-53680: ipvs: fix UB due to uninitialized stack access in ip_vs_protocol_init() (bsc#1235715).
- CVE-2024-54683: netfilter: IDLETIMER: Fix for possible ABBA deadlock (bsc#1235729).
- CVE-2024-56592: bpf: Call free_htab_elem() after htab_unlock_bucket() (bsc#1235244).
- CVE-2024-56633: selftests/bpf: Add apply_bytes test to test_txmsg_redir_wait_sndmem in test_sockmap (bsc#1235485).
- CVE-2024-56638: kABI fix for "netfilter: nft_inner: incorrect percpu area handling under softirq" (bsc#1235524).
- CVE-2024-56640: net/smc: fix LGR and link use-after-free issue (bsc#1235436).
- CVE-2024-56647: net: Fix icmp host relookup triggering ip_rt_bug (bsc#1235435).
- CVE-2024-56658: net: defer final 'struct net' free in netns dismantle (bsc#1235441).
- CVE-2024-56702: bpf: Add tracepoints with null-able arguments (bsc#1235501).
- CVE-2024-56703: ipv6: Fix soft lockups in fib6_select_path under high next hop churn…
- Record
SUSE-SU-2025:20190-1- Updated
- 2026-11-02
OSVSUSE-SU-2025:20192-1 No score
Security update for the Linux Kernel
The SUSE Linux Enterprise Micro 6.0 and 6.1 kernel was updated to receive various security bugfixes.
The following security bugs were fixed:
- CVE-2023-52927: netfilter: allow exp not to be removed in nf_ct_find_expectation (bsc#1239644).
- CVE-2024-26708: mptcp: fix inconsistent state on fastopen race (bsc#1222672).
- CVE-2024-27415: netfilter: br_netfilter: skip conntrack input hook for promisc packets (bsc#1224757).
- CVE-2024-35910: kABI fix for tcp: properly terminate timers for kernel sockets (bsc#1224489).
- CVE-2024-40980: drop_monitor: replace spin_lock by raw_spin_lock (bsc#1227937).
- CVE-2024-41005: netpoll: Fix race condition in netpoll_owner_active (bsc#1227858).
- CVE-2024-44974: mptcp: pm: avoid possible UaF when selecting endp (bsc#1230235).
- CVE-2024-45009: mptcp: pm: only decrement add_addr_accepted for MPJ req (bsc#1230438).
- CVE-2024-45010: mptcp: pm: only mark 'subflow' endp as available (bsc#1230439).
- CVE-2024-46782: ila: call nf_unregister_net_hooks() sooner (bsc#1230769).
- CVE-2024-46858: mptcp: pm: Fix uaf in __timer_delete_sync (bsc#1231088).
- CVE-2024-47408: net/smc: check smcd_v2_ext_offset when receiving proposal msg (bsc#1235711).
- CVE-2024-47794: kABI: bpf: Prevent tailcall infinite loop caused by freplace kABI workaround (bsc#1235712).
- CVE-2024-49571: net/smc: check iparea_offset and ipv6_prefixes_cnt when receiving proposal msg (bsc#1235733).
- CVE-2024-49940: l2tp: prevent possible tunnel refcount underflow (bsc#1232812).
- CVE-2024-50029: Bluetooth: hci_conn: Fix UAF in hci_enhanced_setup_sync (bsc#1231949).
- CVE-2024-50036: net: do not delay dst_entries_add() in dst_release() (bsc#1231912).
- CVE-2024-50038: netfilter: xtables: fix typo causing some targets not to load on IPv6 (bsc#1231910).
- CVE-2024-50056: usb: gadget: uvc: Fix ERR_PTR dereference in uvc_v4l2.c (bsc#1232389).
- CVE-2024-50085: mptcp: pm: fix UaF read in mptcp_pm_nl_rm_addr_or_subflow (bsc#1232508).
- CVE-2024-50140: net: sched: use RCU read-side critical section in taprio_dump() (bsc#1233060).
- CVE-2024-50142: xfrm: validate new SA's prefixlen using SA family when sel.family is unset (bsc#1233028).
- CVE-2024-50185: kABI fix for mptcp: handle consistently DSS corruption (bsc#1233109).
- CVE-2024-50251: netfilter: nft_payload: sanitize offset and length before calling skb_checksum() (bsc#1233248).
- CVE-2024-50258: net: fix crash when config small gso_max_size/gso_ipv4_max_size (bsc#1233221).
- CVE-2024-50294: rxrpc: Fix missing locking causing hanging calls (bsc#1233483).
- CVE-2024-50304: ipv4: ip_tunnel: Fix suspicious RCU usage warning in ip_tunnel_find() (bsc#1233522).
- CVE-2024-53057: net/sched: stop qdisc_tree_reduce_backlog on TC_H_ROOT (bsc#1233551).
- CVE-2024-53123: mptcp: error out earlier on disconnect (bsc#1234070).
- CVE-2024-53124: net: fix data-races around sk->sk_forward_alloc (bsc#1234074).
- CVE-2024-53139: sctp: fix possible UAF in sctp_v6_available() (bsc#1234157).
- CVE-2024-53140: netlink: terminate outstanding dump on socket close (bsc#1234222).
- CVE-2024-53147: exfat: fix out-of-bounds access of directory entries (bsc#1234857).
- CVE-2024-53176: smb: During unmount, ensure all cached dir instances drop their dentry (bsc#1234894).
- CVE-2024-53177: smb: prevent use-after-free due to open_cached_dir error paths (bsc#1234896).
- CVE-2024-53178: smb: Do not leak cfid when reconnect races with open_cached_dir (bsc#1234895).
- CVE-2024-53680: ipvs: fix UB due to uninitialized stack access in ip_vs_protocol_init() (bsc#1235715).
- CVE-2024-54683: netfilter: IDLETIMER: Fix for possible ABBA deadlock (bsc#1235729).
- CVE-2024-56592: bpf: Call free_htab_elem() after htab_unlock_bucket() (bsc#1235244).
- CVE-2024-56633: selftests/bpf: Add apply_bytes test to test_txmsg_redir_wait_sndmem in test_sockmap (bsc#1235485).
- CVE-2024-56638: kABI fix for "netfilter: nft_inner: incorrect percpu area handling under softirq" (bsc#1235524).
- CVE-2024-56640: net/smc: fix LGR and link use-after-free…
- Record
SUSE-SU-2025:20192-1- Updated
- 2026-11-02
OSVSUSE-SU-2025:20260-1 No score
Security update for the Linux Kernel
The SUSE Linux Enterprise Micro 6.0 and 6.1 RT kernel was updated to receive various security bugfixes.
The following security bugs were fixed:
- CVE-2023-52927: netfilter: allow exp not to be removed in nf_ct_find_expectation (bsc#1239644).
- CVE-2024-26708: mptcp: fix inconsistent state on fastopen race (bsc#1222672).
- CVE-2024-35910: tcp: properly terminate timers for kernel sockets (bsc#1224489).
- CVE-2024-40980: drop_monitor: replace spin_lock by raw_spin_lock (bsc#1227937).
- CVE-2024-41005: netpoll: Fix race condition in netpoll_owner_active (bsc#1227858).
- CVE-2024-44974: mptcp: pm: avoid possible UaF when selecting endp (bsc#1230235).
- CVE-2024-45009: mptcp: pm: only decrement add_addr_accepted for MPJ req (bsc#1230438).
- CVE-2024-45010: mptcp: pm: only mark 'subflow' endp as available (bsc#1230439).
- CVE-2024-46782: ila: call nf_unregister_net_hooks() sooner (bsc#1230769).
- CVE-2024-46858: mptcp: pm: Fix uaf in __timer_delete_sync (bsc#1231088).
- CVE-2024-47408: net/smc: check smcd_v2_ext_offset when receiving proposal msg (bsc#1235711).
- CVE-2024-47794: kABI: bpf: Prevent tailcall infinite loop caused by freplace kABI workaround (bsc#1235712).
- CVE-2024-49571: net/smc: check iparea_offset and ipv6_prefixes_cnt when receiving proposal msg (bsc#1235733).
- CVE-2024-49940: kABI fix for l2tp: prevent possible tunnel refcount underflow (bsc#1232812).
- CVE-2024-50029: Bluetooth: hci_conn: Fix UAF in hci_enhanced_setup_sync (bsc#1231949).
- CVE-2024-50036: net: do not delay dst_entries_add() in dst_release() (bsc#1231912).
- CVE-2024-50056: usb: gadget: uvc: Fix ERR_PTR dereference in uvc_v4l2.c (bsc#1232389).
- CVE-2024-50085: mptcp: pm: fix UaF read in mptcp_pm_nl_rm_addr_or_subflow (bsc#1232508).
- CVE-2024-50140: net: sched: use RCU read-side critical section in taprio_dump() (bsc#1233060).
- CVE-2024-50142: xfrm: validate new SA's prefixlen using SA family when sel.family is unset (bsc#1233028).
- CVE-2024-50185: kABI fix for mptcp: handle consistently DSS corruption (bsc#1233109).
- CVE-2024-50251: netfilter: nft_payload: sanitize offset and length before calling skb_checksum() (bsc#1233248).
- CVE-2024-50258: net: fix crash when config small gso_max_size/gso_ipv4_max_size (bsc#1233221).
- CVE-2024-50294: rxrpc: Fix missing locking causing hanging calls (bsc#1233483).
- CVE-2024-50304: ipv4: ip_tunnel: Fix suspicious RCU usage warning in ip_tunnel_find() (bsc#1233522).
- CVE-2024-53057: net/sched: stop qdisc_tree_reduce_backlog on TC_H_ROOT (bsc#1233551).
- CVE-2024-53123: mptcp: error out earlier on disconnect (bsc#1234070).
- CVE-2024-53140: netlink: terminate outstanding dump on socket close (bsc#1234222).
- CVE-2024-53147: exfat: fix out-of-bounds access of directory entries (bsc#1234857).
- CVE-2024-53176: smb: During unmount, ensure all cached dir instances drop their dentry (bsc#1234894).
- CVE-2024-53177: smb: prevent use-after-free due to open_cached_dir error paths (bsc#1234896).
- CVE-2024-53178: smb: Do not leak cfid when reconnect races with open_cached_dir (bsc#1234895).
- CVE-2024-53680: ipvs: fix UB due to uninitialized stack access in ip_vs_protocol_init() (bsc#1235715).
- CVE-2024-54683: netfilter: IDLETIMER: Fix for possible ABBA deadlock (bsc#1235729).
- CVE-2024-56592: bpf: Call free_htab_elem() after htab_unlock_bucket() (bsc#1235244).
- CVE-2024-56633: selftests/bpf: Add apply_bytes test to test_txmsg_redir_wait_sndmem in test_sockmap (bsc#1235485).
- CVE-2024-56638: kABI fix for "netfilter: nft_inner: incorrect percpu area handling under softirq" (bsc#1235524).
- CVE-2024-56640: net/smc: fix LGR and link use-after-free issue (bsc#1235436).
- CVE-2024-56647: net: Fix icmp host relookup triggering ip_rt_bug (bsc#1235435).
- CVE-2024-56658: net: defer final 'struct net' free in netns dismantle (bsc#1235441).
- CVE-2024-56702: bpf: Add tracepoints with null-able arguments (bsc#1235501).
- CVE-2024-56703: ipv6: Fix soft lockups in fib6_select_path under high next hop churn…
- Record
SUSE-SU-2025:20260-1- Updated
- 2026-11-02
OSVSUSE-SU-2025:20270-1 No score
Security update for the Linux Kernel
The SUSE Linux Enterprise Micro 6.0 and 6.1 kernel was updated to receive various security bugfixes.
The following security bugs were fixed:
- CVE-2023-52927: netfilter: allow exp not to be removed in nf_ct_find_expectation (bsc#1239644).
- CVE-2024-26708: mptcp: fix inconsistent state on fastopen race (bsc#1222672).
- CVE-2024-27415: netfilter: br_netfilter: skip conntrack input hook for promisc packets (bsc#1224757).
- CVE-2024-35910: kABI fix for tcp: properly terminate timers for kernel sockets (bsc#1224489).
- CVE-2024-40980: drop_monitor: replace spin_lock by raw_spin_lock (bsc#1227937).
- CVE-2024-41005: netpoll: Fix race condition in netpoll_owner_active (bsc#1227858).
- CVE-2024-44974: mptcp: pm: avoid possible UaF when selecting endp (bsc#1230235).
- CVE-2024-45009: mptcp: pm: only decrement add_addr_accepted for MPJ req (bsc#1230438).
- CVE-2024-45010: mptcp: pm: only mark 'subflow' endp as available (bsc#1230439).
- CVE-2024-46782: ila: call nf_unregister_net_hooks() sooner (bsc#1230769).
- CVE-2024-46858: mptcp: pm: Fix uaf in __timer_delete_sync (bsc#1231088).
- CVE-2024-47408: net/smc: check smcd_v2_ext_offset when receiving proposal msg (bsc#1235711).
- CVE-2024-47794: kABI: bpf: Prevent tailcall infinite loop caused by freplace kABI workaround (bsc#1235712).
- CVE-2024-49571: net/smc: check iparea_offset and ipv6_prefixes_cnt when receiving proposal msg (bsc#1235733).
- CVE-2024-49940: l2tp: prevent possible tunnel refcount underflow (bsc#1232812).
- CVE-2024-50029: Bluetooth: hci_conn: Fix UAF in hci_enhanced_setup_sync (bsc#1231949).
- CVE-2024-50036: net: do not delay dst_entries_add() in dst_release() (bsc#1231912).
- CVE-2024-50038: netfilter: xtables: fix typo causing some targets not to load on IPv6 (bsc#1231910).
- CVE-2024-50056: usb: gadget: uvc: Fix ERR_PTR dereference in uvc_v4l2.c (bsc#1232389).
- CVE-2024-50085: mptcp: pm: fix UaF read in mptcp_pm_nl_rm_addr_or_subflow (bsc#1232508).
- CVE-2024-50140: net: sched: use RCU read-side critical section in taprio_dump() (bsc#1233060).
- CVE-2024-50142: xfrm: validate new SA's prefixlen using SA family when sel.family is unset (bsc#1233028).
- CVE-2024-50185: kABI fix for mptcp: handle consistently DSS corruption (bsc#1233109).
- CVE-2024-50251: netfilter: nft_payload: sanitize offset and length before calling skb_checksum() (bsc#1233248).
- CVE-2024-50258: net: fix crash when config small gso_max_size/gso_ipv4_max_size (bsc#1233221).
- CVE-2024-50294: rxrpc: Fix missing locking causing hanging calls (bsc#1233483).
- CVE-2024-50304: ipv4: ip_tunnel: Fix suspicious RCU usage warning in ip_tunnel_find() (bsc#1233522).
- CVE-2024-53057: net/sched: stop qdisc_tree_reduce_backlog on TC_H_ROOT (bsc#1233551).
- CVE-2024-53123: mptcp: error out earlier on disconnect (bsc#1234070).
- CVE-2024-53124: net: fix data-races around sk->sk_forward_alloc (bsc#1234074).
- CVE-2024-53139: sctp: fix possible UAF in sctp_v6_available() (bsc#1234157).
- CVE-2024-53140: netlink: terminate outstanding dump on socket close (bsc#1234222).
- CVE-2024-53147: exfat: fix out-of-bounds access of directory entries (bsc#1234857).
- CVE-2024-53176: smb: During unmount, ensure all cached dir instances drop their dentry (bsc#1234894).
- CVE-2024-53177: smb: prevent use-after-free due to open_cached_dir error paths (bsc#1234896).
- CVE-2024-53178: smb: Do not leak cfid when reconnect races with open_cached_dir (bsc#1234895).
- CVE-2024-53680: ipvs: fix UB due to uninitialized stack access in ip_vs_protocol_init() (bsc#1235715).
- CVE-2024-54683: netfilter: IDLETIMER: Fix for possible ABBA deadlock (bsc#1235729).
- CVE-2024-56592: bpf: Call free_htab_elem() after htab_unlock_bucket() (bsc#1235244).
- CVE-2024-56633: selftests/bpf: Add apply_bytes test to test_txmsg_redir_wait_sndmem in test_sockmap (bsc#1235485).
- CVE-2024-56638: kABI fix for "netfilter: nft_inner: incorrect percpu area handling under softirq" (bsc#1235524).
- CVE-2024-56640: net/smc: fix LGR and link use-after-free…
- Record
SUSE-SU-2025:20270-1- Updated
- 2026-11-02
OSVUSN-7445-1 No score
linux, linux-aws, linux-gcp, linux-hwe-6.11, linux-lowlatency, linux-lowlatency-hwe-6.11, linux-oem-6.11, linux-oracle, linux-raspi, linux-realtime vulnerabilities
Several security issues were discovered in the Linux kernel. An attacker could possibly use these to compromise the system. This update corrects flaws in the following subsystems:
- GPIO subsystem;
- GPU drivers;
- IRQ chip drivers;
- Network drivers;
- Mellanox network drivers;
- x86 platform drivers;
- i.MX PM domains;
- SCSI subsystem;
- USB Serial drivers;
- AFS file system;
- GFS2 file system;
- File systems infrastructure;
- Proc file system;
- SMB network file system;
- Timer subsystem;
- Kernel CPU control infrastructure;
- Memory management;
- Networking core;
- Ethtool driver;
- IEEE 802.15.4 subsystem;
- Open vSwitch;
- Network traffic control;
- VMware vSockets driver; (CVE-2025-21685, CVE-2025-21684, CVE-2025-21756, CVE-2025-21670, CVE-2024-57949, CVE-2025-21677, CVE-2025-21680, CVE-2025-21703, CVE-2024-57952, CVE-2025-21674, CVE-2025-21701, CVE-2025-21691, CVE-2025-21689, CVE-2025-21668, CVE-2025-21665, CVE-2025-21683, CVE-2025-21675, CVE-2025-21672, CVE-2024-57948, CVE-2025-21669, CVE-2025-21673, CVE-2025-21692, CVE-2025-21699, CVE-2025-21702, CVE-2025-21682, CVE-2025-21690, CVE-2025-21681, CVE-2025-21695, CVE-2025-21696, CVE-2025-21700, CVE-2025-21678, CVE-2025-21676, CVE-2024-57950, CVE-2025-21666, CVE-2025-21694, CVE-2025-21693, CVE-2025-21993, CVE-2024-57951, CVE-2025-21697, CVE-2025-21667)
- Record
USN-7445-1- Updated
- 2026-11-02
OSVUSN-7448-1 No score
linux-azure, linux-azure-6.11 vulnerabilities
It was discovered that the CIFS network file system implementation in the Linux kernel did not properly verify the target namespace when handling upcalls. An attacker could use this to expose sensitive information. (CVE-2025-2312)
Several security issues were discovered in the Linux kernel. An attacker could possibly use these to compromise the system. This update corrects flaws in the following subsystems:
- GPIO subsystem;
- GPU drivers;
- IRQ chip drivers;
- Network drivers;
- Mellanox network drivers;
- x86 platform drivers;
- i.MX PM domains;
- SCSI subsystem;
- USB Serial drivers;
- AFS file system;
- GFS2 file system;
- File systems infrastructure;
- Proc file system;
- SMB network file system;
- Timer subsystem;
- Kernel CPU control infrastructure;
- Memory management;
- Networking core;
- Ethtool driver;
- IEEE 802.15.4 subsystem;
- Open vSwitch;
- Network traffic control;
- VMware vSockets driver; (CVE-2025-21694, CVE-2025-21993, CVE-2025-21684, CVE-2025-21681, CVE-2025-21675, CVE-2025-21672, CVE-2025-21696, CVE-2025-21691, CVE-2025-21683, CVE-2025-21666, CVE-2025-21682, CVE-2025-21697, CVE-2025-21668, CVE-2025-21701, CVE-2025-21670, CVE-2025-21676, CVE-2025-21695, CVE-2025-21692, CVE-2025-21674, CVE-2025-21699, CVE-2024-57948, CVE-2025-21677, CVE-2024-57951, CVE-2025-21702, CVE-2025-21700, CVE-2024-57949, CVE-2025-21669, CVE-2025-21703, CVE-2025-21756, CVE-2025-21667, CVE-2024-57952, CVE-2024-57950, CVE-2025-21685, CVE-2025-21693, CVE-2025-21678, CVE-2025-21665, CVE-2025-21680, CVE-2025-21689, CVE-2025-21690, CVE-2025-21673)
- Record
USN-7448-1- Updated
- 2026-11-02
OSVUSN-8781-1 No score
linux-nvidia-tegra vulnerabilities
It was discovered that some Arm processors could complete a broadcast translation lookaside buffer (TLB) invalidation before memory writes made through the invalidated translation were globally observed. A local attacker could possibly use this to write to memory after permission to do so had been revoked, bypassing memory protections or escalating privileges. (CVE-2025-10263)
Several security issues were discovered in the Linux kernel. An attacker could possibly use these to compromise the system. This update corrects flaws in the following subsystems:
- ARM64 architecture;
- User-space API (UAPI);
- Kernel build system;
- ARM32 architecture;
- PowerPC architecture;
- RISC-V architecture;
- S390 architecture;
- User-Mode Linux (UML);
- x86 architecture;
- Cryptographic API;
- Intel NPU Driver;
- Compute Acceleration Framework;
- ACPI drivers;
- Drivers core;
- DRBD Distributed Replicated Block Device drivers;
- Rados block device (RBD) driver;
- Ublk userspace block driver;
- Compressed RAM block device driver;
- Bluetooth drivers;
- Hardware crypto device drivers;
- CXL (Compute Express Link) drivers;
- Arm Firmware Framework for ARMv8-A(FFA);
- EFI core;
- FPGA Framework;
- GPU drivers;
- HID subsystem;
- Hardware monitoring drivers;
- I2C subsystem;
- I3C subsystem;
- InfiniBand drivers;
- Input Device core drivers;
- Input Device (Mouse) drivers;
- IOMMU subsystem;
- Multiple devices driver;
- Media drivers;
- Fastrpc Driver;
- Network drivers;
- Mellanox network drivers;
- Microsoft Azure Network Adapter (MANA) driver;
- MediaTek network drivers;
- NVME drivers;
- Operating Performance Points (OPP) driver;
- PCI subsystem;
- PTP clock framework;
- RPMSG subsystem;
- SCSI subsystem;
- SoundWire subsystem;
- SPI subsystem;
- Greybus lights staging drivers;
- Media staging drivers;
- NVIDIA Tegra embedded controller (NVEC) staging driver;
- Realtek RTL8723BS SDIO drivers;
- TCM subsystem;
- Trusted Execution Environment drivers;
- Thunderbolt and USB4 drivers;
- TTY drivers;
- USB Gadget drivers;
- USB Dual Role (OTG-ready) Controller drivers;
- USB Serial drivers;
- vDPA drivers;
- VFIO drivers;
- Virtio Host (VHOST) subsystem;
- Virtio drivers;
- Xen hypervisor drivers;
- 9P distributed file system;
- AFS file system;
- File systems infrastructure;
- BTRFS file system;
- Ceph distributed file system;
- exFAT file system;
- F2FS file system;
- GFS2 file system;
- HFS file system;
- HFS+ file system;
- JFS file system;
- Network file systems library;
- Network file system (NFS) client;
- Network file system (NFS) server daemon;
- NTFS3 file system;
- OCFS2 file system;
- OrangeFS file system;
- SMB network file system;
- BPF subsystem;
- File system encryption (fscrypt);
- Software nodes and device properties;
- IPv4 networking;
- KVM subsystem;
- Mellanox drivers;
- Memory management;
- Networking core;
- Netfilter;
- Socket messages infrastructure;
- MediaTek SoC drivers;
- Sun RPC protocol;
- Network traffic control;
- IPv6 networking;
- Amateur Radio drivers;
- Bluetooth subsystem;
- IP tunnels definitions;
- KCM (Kernel Connection Multiplexor) sockets driver;
- MultiProtocol Label Switching driver;
- TCP network protocol;
- XFRM subsystem;
- Tracing infrastructure;
- io_uring subsystem;
- Control group (cgroup);
- Perf events;
- IRQ subsystem;
- Locking primitives;
- KProbes tracing;
- 9P file system network protocol;
- B.A.T.M.A.N. meshing protocol;
- Ethernet bridge;
- CAN network layer;
- Ceph Core library;
- Handshake API;
- HSR network protocol;
- IFE protocol;
- L2TP protocol;
- MAC80211 subsystem;
- IEEE 802.15.4 subsystem;
- Multipath TCP;
- NFC subsystem;
- Open vSwitch;
- Phonet protocol;
- RDS protocol;
- RxRPC session sockets;
- SCTP protocol;
- SMC…
- Record
USN-8781-1- Updated
- 2026-11-06
Affected products
Affected packages
| Package | Affected | Fixed |
|---|---|---|
kernelAlmaLinux:10 From an advisory covering 88 CVEs |
before 6.12.0-124.8.1.el10_1 | 6.12.0-124.8.1.el10_1 |
kernel-64kAlmaLinux:10 From an advisory covering 88 CVEs |
before 6.12.0-124.8.1.el10_1 | 6.12.0-124.8.1.el10_1 |
kernel-64k-coreAlmaLinux:10 From an advisory covering 88 CVEs |
before 6.12.0-124.8.1.el10_1 | 6.12.0-124.8.1.el10_1 |
kernel-64k-debugAlmaLinux:10 From an advisory covering 88 CVEs |
before 6.12.0-124.8.1.el10_1 | 6.12.0-124.8.1.el10_1 |
kernel-64k-debug-coreAlmaLinux:10 From an advisory covering 88 CVEs |
before 6.12.0-124.8.1.el10_1 | 6.12.0-124.8.1.el10_1 |
kernel-64k-debug-develAlmaLinux:10 From an advisory covering 88 CVEs |
before 6.12.0-124.8.1.el10_1 | 6.12.0-124.8.1.el10_1 |
kernel-64k-debug-devel-matchedAlmaLinux:10 From an advisory covering 88 CVEs |
before 6.12.0-124.8.1.el10_1 | 6.12.0-124.8.1.el10_1 |
kernel-64k-debug-modulesAlmaLinux:10 From an advisory covering 88 CVEs |
before 6.12.0-124.8.1.el10_1 | 6.12.0-124.8.1.el10_1 |
kernel-64k-debug-modules-coreAlmaLinux:10 From an advisory covering 88 CVEs |
before 6.12.0-124.8.1.el10_1 | 6.12.0-124.8.1.el10_1 |
kernel-64k-debug-modules-extraAlmaLinux:10 From an advisory covering 88 CVEs |
before 6.12.0-124.8.1.el10_1 | 6.12.0-124.8.1.el10_1 |
Show 290 moreShow less
| Package | Affected | Fixed |
|---|---|---|
kernel-64k-develAlmaLinux:10 From an advisory covering 88 CVEs |
before 6.12.0-124.8.1.el10_1 | 6.12.0-124.8.1.el10_1 |
kernel-64k-devel-matchedAlmaLinux:10 From an advisory covering 88 CVEs |
before 6.12.0-124.8.1.el10_1 | 6.12.0-124.8.1.el10_1 |
kernel-64k-modulesAlmaLinux:10 From an advisory covering 88 CVEs |
before 6.12.0-124.8.1.el10_1 | 6.12.0-124.8.1.el10_1 |
kernel-64k-modules-coreAlmaLinux:10 From an advisory covering 88 CVEs |
before 6.12.0-124.8.1.el10_1 | 6.12.0-124.8.1.el10_1 |
kernel-64k-modules-extraAlmaLinux:10 From an advisory covering 88 CVEs |
before 6.12.0-124.8.1.el10_1 | 6.12.0-124.8.1.el10_1 |
kernel-abi-stablelistsAlmaLinux:10 From an advisory covering 88 CVEs |
before 6.12.0-124.8.1.el10_1 | 6.12.0-124.8.1.el10_1 |
kernel-coreAlmaLinux:10 From an advisory covering 88 CVEs |
before 6.12.0-124.8.1.el10_1 | 6.12.0-124.8.1.el10_1 |
kernel-cross-headersAlmaLinux:10 From an advisory covering 88 CVEs |
before 6.12.0-124.8.1.el10_1 | 6.12.0-124.8.1.el10_1 |
kernel-debugAlmaLinux:10 From an advisory covering 88 CVEs |
before 6.12.0-124.8.1.el10_1 | 6.12.0-124.8.1.el10_1 |
kernel-debug-coreAlmaLinux:10 From an advisory covering 88 CVEs |
before 6.12.0-124.8.1.el10_1 | 6.12.0-124.8.1.el10_1 |
kernel-debug-develAlmaLinux:10 From an advisory covering 88 CVEs |
before 6.12.0-124.8.1.el10_1 | 6.12.0-124.8.1.el10_1 |
kernel-debug-devel-matchedAlmaLinux:10 From an advisory covering 88 CVEs |
before 6.12.0-124.8.1.el10_1 | 6.12.0-124.8.1.el10_1 |
kernel-debug-modulesAlmaLinux:10 From an advisory covering 88 CVEs |
before 6.12.0-124.8.1.el10_1 | 6.12.0-124.8.1.el10_1 |
kernel-debug-modules-coreAlmaLinux:10 From an advisory covering 88 CVEs |
before 6.12.0-124.8.1.el10_1 | 6.12.0-124.8.1.el10_1 |
kernel-debug-modules-extraAlmaLinux:10 From an advisory covering 88 CVEs |
before 6.12.0-124.8.1.el10_1 | 6.12.0-124.8.1.el10_1 |
kernel-debug-uki-virtAlmaLinux:10 From an advisory covering 88 CVEs |
before 6.12.0-124.8.1.el10_1 | 6.12.0-124.8.1.el10_1 |
kernel-develAlmaLinux:10 From an advisory covering 88 CVEs |
before 6.12.0-124.8.1.el10_1 | 6.12.0-124.8.1.el10_1 |
kernel-devel-matchedAlmaLinux:10 From an advisory covering 88 CVEs |
before 6.12.0-124.8.1.el10_1 | 6.12.0-124.8.1.el10_1 |
kernel-docAlmaLinux:10 From an advisory covering 88 CVEs |
before 6.12.0-124.8.1.el10_1 | 6.12.0-124.8.1.el10_1 |
kernel-headersAlmaLinux:10 From an advisory covering 88 CVEs |
before 6.12.0-124.8.1.el10_1 | 6.12.0-124.8.1.el10_1 |
kernel-modulesAlmaLinux:10 From an advisory covering 88 CVEs |
before 6.12.0-124.8.1.el10_1 | 6.12.0-124.8.1.el10_1 |
kernel-modules-coreAlmaLinux:10 From an advisory covering 88 CVEs |
before 6.12.0-124.8.1.el10_1 | 6.12.0-124.8.1.el10_1 |
kernel-modules-extraAlmaLinux:10 From an advisory covering 88 CVEs |
before 6.12.0-124.8.1.el10_1 | 6.12.0-124.8.1.el10_1 |
kernel-modules-extra-matchedAlmaLinux:10 From an advisory covering 88 CVEs |
before 6.12.0-124.8.1.el10_1 | 6.12.0-124.8.1.el10_1 |
kernel-rtAlmaLinux:10 From an advisory covering 88 CVEs |
before 6.12.0-124.8.1.el10_1 | 6.12.0-124.8.1.el10_1 |
kernel-rt-64kAlmaLinux:10 From an advisory covering 88 CVEs |
before 6.12.0-124.8.1.el10_1 | 6.12.0-124.8.1.el10_1 |
kernel-rt-64k-coreAlmaLinux:10 From an advisory covering 88 CVEs |
before 6.12.0-124.8.1.el10_1 | 6.12.0-124.8.1.el10_1 |
kernel-rt-64k-debugAlmaLinux:10 From an advisory covering 88 CVEs |
before 6.12.0-124.8.1.el10_1 | 6.12.0-124.8.1.el10_1 |
kernel-rt-64k-debug-coreAlmaLinux:10 From an advisory covering 88 CVEs |
before 6.12.0-124.8.1.el10_1 | 6.12.0-124.8.1.el10_1 |
kernel-rt-64k-debug-develAlmaLinux:10 From an advisory covering 88 CVEs |
before 6.12.0-124.8.1.el10_1 | 6.12.0-124.8.1.el10_1 |
kernel-rt-64k-debug-modulesAlmaLinux:10 From an advisory covering 88 CVEs |
before 6.12.0-124.8.1.el10_1 | 6.12.0-124.8.1.el10_1 |
kernel-rt-64k-debug-modules-coreAlmaLinux:10 From an advisory covering 88 CVEs |
before 6.12.0-124.8.1.el10_1 | 6.12.0-124.8.1.el10_1 |
kernel-rt-64k-debug-modules-extraAlmaLinux:10 From an advisory covering 88 CVEs |
before 6.12.0-124.8.1.el10_1 | 6.12.0-124.8.1.el10_1 |
kernel-rt-64k-develAlmaLinux:10 From an advisory covering 88 CVEs |
before 6.12.0-124.8.1.el10_1 | 6.12.0-124.8.1.el10_1 |
kernel-rt-64k-modulesAlmaLinux:10 From an advisory covering 88 CVEs |
before 6.12.0-124.8.1.el10_1 | 6.12.0-124.8.1.el10_1 |
kernel-rt-64k-modules-coreAlmaLinux:10 From an advisory covering 88 CVEs |
before 6.12.0-124.8.1.el10_1 | 6.12.0-124.8.1.el10_1 |
kernel-rt-64k-modules-extraAlmaLinux:10 From an advisory covering 88 CVEs |
before 6.12.0-124.8.1.el10_1 | 6.12.0-124.8.1.el10_1 |
kernel-rt-coreAlmaLinux:10 From an advisory covering 88 CVEs |
before 6.12.0-124.8.1.el10_1 | 6.12.0-124.8.1.el10_1 |
kernel-rt-debugAlmaLinux:10 From an advisory covering 88 CVEs |
before 6.12.0-124.8.1.el10_1 | 6.12.0-124.8.1.el10_1 |
kernel-rt-debug-coreAlmaLinux:10 From an advisory covering 88 CVEs |
before 6.12.0-124.8.1.el10_1 | 6.12.0-124.8.1.el10_1 |
kernel-rt-debug-develAlmaLinux:10 From an advisory covering 88 CVEs |
before 6.12.0-124.8.1.el10_1 | 6.12.0-124.8.1.el10_1 |
kernel-rt-debug-modulesAlmaLinux:10 From an advisory covering 88 CVEs |
before 6.12.0-124.8.1.el10_1 | 6.12.0-124.8.1.el10_1 |
kernelAzure Linux:2 |
through 5.15.200.1-1 | None known |
kernelAzure Linux:3 |
through 6.6.161.1-1 | None known |
linux-ltsAlpaquita:23 |
6.1.134-r0 and later | None known |
linux-ltsAlpaquita:25 |
6.6.89-r0 up to 6.12.41-r0 | 6.12.41-r0 |
linux-ltsAlpaquita:stream |
6.12.92-r1 up to 6.18.35-r1 | 6.18.35-r1 |
kernelTuxCare:AlmaLinux:9.6 From an advisory covering 100 CVEs |
before 5.14.0-570.62.1.el9_6.tuxcare.5.els1 | 5.14.0-570.62.1.el9_6.tuxcare.5.els1 |
kernel-abi-stablelistsTuxCare:AlmaLinux:9.6 From an advisory covering 100 CVEs |
before 5.14.0-570.62.1.el9_6.tuxcare.5.els1 | 5.14.0-570.62.1.el9_6.tuxcare.5.els1 |
kernel-coreTuxCare:AlmaLinux:9.6 From an advisory covering 100 CVEs |
before 5.14.0-570.62.1.el9_6.tuxcare.5.els1 | 5.14.0-570.62.1.el9_6.tuxcare.5.els1 |
kernel-cross-headersTuxCare:AlmaLinux:9.6 From an advisory covering 100 CVEs |
before 5.14.0-570.62.1.el9_6.tuxcare.5.els1 | 5.14.0-570.62.1.el9_6.tuxcare.5.els1 |
kernel-debugTuxCare:AlmaLinux:9.6 From an advisory covering 100 CVEs |
before 5.14.0-570.62.1.el9_6.tuxcare.5.els1 | 5.14.0-570.62.1.el9_6.tuxcare.5.els1 |
kernel-debug-coreTuxCare:AlmaLinux:9.6 From an advisory covering 100 CVEs |
before 5.14.0-570.62.1.el9_6.tuxcare.5.els1 | 5.14.0-570.62.1.el9_6.tuxcare.5.els1 |
kernel-debug-develTuxCare:AlmaLinux:9.6 From an advisory covering 100 CVEs |
before 5.14.0-570.62.1.el9_6.tuxcare.5.els1 | 5.14.0-570.62.1.el9_6.tuxcare.5.els1 |
kernel-debug-devel-matchedTuxCare:AlmaLinux:9.6 From an advisory covering 100 CVEs |
before 5.14.0-570.62.1.el9_6.tuxcare.5.els1 | 5.14.0-570.62.1.el9_6.tuxcare.5.els1 |
kernel-debug-modulesTuxCare:AlmaLinux:9.6 From an advisory covering 100 CVEs |
before 5.14.0-570.62.1.el9_6.tuxcare.5.els1 | 5.14.0-570.62.1.el9_6.tuxcare.5.els1 |
kernel-debug-modules-coreTuxCare:AlmaLinux:9.6 From an advisory covering 100 CVEs |
before 5.14.0-570.62.1.el9_6.tuxcare.5.els1 | 5.14.0-570.62.1.el9_6.tuxcare.5.els1 |
kernel-debug-modules-extraTuxCare:AlmaLinux:9.6 From an advisory covering 100 CVEs |
before 5.14.0-570.62.1.el9_6.tuxcare.5.els1 | 5.14.0-570.62.1.el9_6.tuxcare.5.els1 |
kernel-debug-modules-internalTuxCare:AlmaLinux:9.6 From an advisory covering 100 CVEs |
before 5.14.0-570.62.1.el9_6.tuxcare.5.els1 | 5.14.0-570.62.1.el9_6.tuxcare.5.els1 |
kernel-debug-modules-partnerTuxCare:AlmaLinux:9.6 From an advisory covering 100 CVEs |
before 5.14.0-570.62.1.el9_6.tuxcare.5.els1 | 5.14.0-570.62.1.el9_6.tuxcare.5.els1 |
kernel-debug-uki-virtTuxCare:AlmaLinux:9.6 From an advisory covering 100 CVEs |
before 5.14.0-570.62.1.el9_6.tuxcare.5.els1 | 5.14.0-570.62.1.el9_6.tuxcare.5.els1 |
kernel-debug-uki-virt-addonsTuxCare:AlmaLinux:9.6 From an advisory covering 100 CVEs |
before 5.14.0-570.62.1.el9_6.tuxcare.5.els1 | 5.14.0-570.62.1.el9_6.tuxcare.5.els1 |
kernel-develTuxCare:AlmaLinux:9.6 From an advisory covering 100 CVEs |
before 5.14.0-570.62.1.el9_6.tuxcare.5.els1 | 5.14.0-570.62.1.el9_6.tuxcare.5.els1 |
kernel-devel-matchedTuxCare:AlmaLinux:9.6 From an advisory covering 100 CVEs |
before 5.14.0-570.62.1.el9_6.tuxcare.5.els1 | 5.14.0-570.62.1.el9_6.tuxcare.5.els1 |
kernel-docTuxCare:AlmaLinux:9.6 From an advisory covering 100 CVEs |
before 5.14.0-570.62.1.el9_6.tuxcare.5.els1 | 5.14.0-570.62.1.el9_6.tuxcare.5.els1 |
kernel-headersTuxCare:AlmaLinux:9.6 From an advisory covering 100 CVEs |
before 5.14.0-570.62.1.el9_6.tuxcare.5.els1 | 5.14.0-570.62.1.el9_6.tuxcare.5.els1 |
kernel-ipaclones-internalTuxCare:AlmaLinux:9.6 From an advisory covering 100 CVEs |
before 5.14.0-570.62.1.el9_6.tuxcare.5.els1 | 5.14.0-570.62.1.el9_6.tuxcare.5.els1 |
kernel-modulesTuxCare:AlmaLinux:9.6 From an advisory covering 100 CVEs |
before 5.14.0-570.62.1.el9_6.tuxcare.5.els1 | 5.14.0-570.62.1.el9_6.tuxcare.5.els1 |
kernel-modules-coreTuxCare:AlmaLinux:9.6 From an advisory covering 100 CVEs |
before 5.14.0-570.62.1.el9_6.tuxcare.5.els1 | 5.14.0-570.62.1.el9_6.tuxcare.5.els1 |
kernel-modules-extraTuxCare:AlmaLinux:9.6 From an advisory covering 100 CVEs |
before 5.14.0-570.62.1.el9_6.tuxcare.5.els1 | 5.14.0-570.62.1.el9_6.tuxcare.5.els1 |
kernel-modules-internalTuxCare:AlmaLinux:9.6 From an advisory covering 100 CVEs |
before 5.14.0-570.62.1.el9_6.tuxcare.5.els1 | 5.14.0-570.62.1.el9_6.tuxcare.5.els1 |
kernel-modules-partnerTuxCare:AlmaLinux:9.6 From an advisory covering 100 CVEs |
before 5.14.0-570.62.1.el9_6.tuxcare.5.els1 | 5.14.0-570.62.1.el9_6.tuxcare.5.els1 |
kernel-rtTuxCare:AlmaLinux:9.6 From an advisory covering 100 CVEs |
before 5.14.0-570.62.1.el9_6.tuxcare.5.els1 | 5.14.0-570.62.1.el9_6.tuxcare.5.els1 |
kernel-rt-coreTuxCare:AlmaLinux:9.6 From an advisory covering 100 CVEs |
before 5.14.0-570.62.1.el9_6.tuxcare.5.els1 | 5.14.0-570.62.1.el9_6.tuxcare.5.els1 |
kernel-rt-debugTuxCare:AlmaLinux:9.6 From an advisory covering 100 CVEs |
before 5.14.0-570.62.1.el9_6.tuxcare.5.els1 | 5.14.0-570.62.1.el9_6.tuxcare.5.els1 |
kernel-rt-debug-coreTuxCare:AlmaLinux:9.6 From an advisory covering 100 CVEs |
before 5.14.0-570.62.1.el9_6.tuxcare.5.els1 | 5.14.0-570.62.1.el9_6.tuxcare.5.els1 |
kernel-rt-debug-develTuxCare:AlmaLinux:9.6 From an advisory covering 100 CVEs |
before 5.14.0-570.62.1.el9_6.tuxcare.5.els1 | 5.14.0-570.62.1.el9_6.tuxcare.5.els1 |
kernel-rt-debug-devel-matchedTuxCare:AlmaLinux:9.6 From an advisory covering 100 CVEs |
before 5.14.0-570.62.1.el9_6.tuxcare.5.els1 | 5.14.0-570.62.1.el9_6.tuxcare.5.els1 |
kernel-rt-debug-kvmTuxCare:AlmaLinux:9.6 From an advisory covering 100 CVEs |
before 5.14.0-570.62.1.el9_6.tuxcare.5.els1 | 5.14.0-570.62.1.el9_6.tuxcare.5.els1 |
kernel-rt-debug-modulesTuxCare:AlmaLinux:9.6 From an advisory covering 100 CVEs |
before 5.14.0-570.62.1.el9_6.tuxcare.5.els1 | 5.14.0-570.62.1.el9_6.tuxcare.5.els1 |
kernel-rt-debug-modules-coreTuxCare:AlmaLinux:9.6 From an advisory covering 100 CVEs |
before 5.14.0-570.62.1.el9_6.tuxcare.5.els1 | 5.14.0-570.62.1.el9_6.tuxcare.5.els1 |
kernel-rt-debug-modules-extraTuxCare:AlmaLinux:9.6 From an advisory covering 100 CVEs |
before 5.14.0-570.62.1.el9_6.tuxcare.5.els1 | 5.14.0-570.62.1.el9_6.tuxcare.5.els1 |
kernel-rt-debug-modules-internalTuxCare:AlmaLinux:9.6 From an advisory covering 100 CVEs |
before 5.14.0-570.62.1.el9_6.tuxcare.5.els1 | 5.14.0-570.62.1.el9_6.tuxcare.5.els1 |
kernel-rt-debug-modules-partnerTuxCare:AlmaLinux:9.6 From an advisory covering 100 CVEs |
before 5.14.0-570.62.1.el9_6.tuxcare.5.els1 | 5.14.0-570.62.1.el9_6.tuxcare.5.els1 |
kernel-rt-develTuxCare:AlmaLinux:9.6 From an advisory covering 100 CVEs |
before 5.14.0-570.62.1.el9_6.tuxcare.5.els1 | 5.14.0-570.62.1.el9_6.tuxcare.5.els1 |
kernel-rt-devel-matchedTuxCare:AlmaLinux:9.6 From an advisory covering 100 CVEs |
before 5.14.0-570.62.1.el9_6.tuxcare.5.els1 | 5.14.0-570.62.1.el9_6.tuxcare.5.els1 |
kernel-rt-kvmTuxCare:AlmaLinux:9.6 From an advisory covering 100 CVEs |
before 5.14.0-570.62.1.el9_6.tuxcare.5.els1 | 5.14.0-570.62.1.el9_6.tuxcare.5.els1 |
kernel-rt-modulesTuxCare:AlmaLinux:9.6 From an advisory covering 100 CVEs |
before 5.14.0-570.62.1.el9_6.tuxcare.5.els1 | 5.14.0-570.62.1.el9_6.tuxcare.5.els1 |
kernel-rt-modules-coreTuxCare:AlmaLinux:9.6 From an advisory covering 100 CVEs |
before 5.14.0-570.62.1.el9_6.tuxcare.5.els1 | 5.14.0-570.62.1.el9_6.tuxcare.5.els1 |
kernel-rt-modules-extraTuxCare:AlmaLinux:9.6 From an advisory covering 100 CVEs |
before 5.14.0-570.62.1.el9_6.tuxcare.5.els1 | 5.14.0-570.62.1.el9_6.tuxcare.5.els1 |
kernel-rt-modules-internalTuxCare:AlmaLinux:9.6 From an advisory covering 100 CVEs |
before 5.14.0-570.62.1.el9_6.tuxcare.5.els1 | 5.14.0-570.62.1.el9_6.tuxcare.5.els1 |
kernel-rt-modules-partnerTuxCare:AlmaLinux:9.6 From an advisory covering 100 CVEs |
before 5.14.0-570.62.1.el9_6.tuxcare.5.els1 | 5.14.0-570.62.1.el9_6.tuxcare.5.els1 |
kernel-selftests-internalTuxCare:AlmaLinux:9.6 From an advisory covering 100 CVEs |
before 5.14.0-570.62.1.el9_6.tuxcare.5.els1 | 5.14.0-570.62.1.el9_6.tuxcare.5.els1 |
kernel-toolsTuxCare:AlmaLinux:9.6 From an advisory covering 100 CVEs |
before 5.14.0-570.62.1.el9_6.tuxcare.5.els1 | 5.14.0-570.62.1.el9_6.tuxcare.5.els1 |
kernel-tools-libsTuxCare:AlmaLinux:9.6 From an advisory covering 100 CVEs |
before 5.14.0-570.62.1.el9_6.tuxcare.5.els1 | 5.14.0-570.62.1.el9_6.tuxcare.5.els1 |
kernel-tools-libs-develTuxCare:AlmaLinux:9.6 From an advisory covering 100 CVEs |
before 5.14.0-570.62.1.el9_6.tuxcare.5.els1 | 5.14.0-570.62.1.el9_6.tuxcare.5.els1 |
kernel-uki-virtTuxCare:AlmaLinux:9.6 From an advisory covering 100 CVEs |
before 5.14.0-570.62.1.el9_6.tuxcare.5.els1 | 5.14.0-570.62.1.el9_6.tuxcare.5.els1 |
kernel-uki-virt-addonsTuxCare:AlmaLinux:9.6 From an advisory covering 100 CVEs |
before 5.14.0-570.62.1.el9_6.tuxcare.5.els1 | 5.14.0-570.62.1.el9_6.tuxcare.5.els1 |
libperfTuxCare:AlmaLinux:9.6 From an advisory covering 100 CVEs |
before 5.14.0-570.62.1.el9_6.tuxcare.5.els1 | 5.14.0-570.62.1.el9_6.tuxcare.5.els1 |
KernelLinux |
5.11.0 up to 6.12.12 | 6.12.12 |
linuxDebian:12 |
All versions, plus listed versions 6.1.106-16.1.106-26.1.106-36.1.112-16.1.115-1 Show 45 moreShow less6.1.119-16.1.123-16.1.124-16.1.128-16.1.129-16.1.133-16.1.135-16.1.137-16.1.139-16.1.140-16.1.147-16.1.148-16.1.153-16.1.158-16.1.159-16.1.162-16.1.164-16.1.170-16.1.170-26.1.170-36.1.172-16.1.174-16.1.176-16.1.177-16.1.180-16.1.27-16.1.37-16.1.38-16.1.38-26.1.38-2~bpo11+16.1.38-36.1.38-46.1.38-4~bpo11+16.1.52-16.1.55-16.1.55-1~bpo11+16.1.64-16.1.66-16.1.67-16.1.69-16.1.69-1~bpo11+16.1.76-16.1.76-1~bpo11+16.1.82-16.1.85-1 |
None known |
linuxDebian:13 |
before 6.12.12-1 | 6.12.12-1 |
linuxDebian:14 |
before 6.12.12-1 | 6.12.12-1 |
kernelopenEuler:22.03-LTS-SP3 From an advisory covering 22 CVEs |
before 5.10.0-293.0.0.195.oe2203sp3 | 5.10.0-293.0.0.195.oe2203sp3 |
kernelopenEuler:22.03-LTS-SP4 From an advisory covering 20 CVEs |
before 5.10.0-293.0.0.196.oe2203sp4 | 5.10.0-293.0.0.196.oe2203sp4 |
kernelopenEuler:24.03-LTS From an advisory covering 15 CVEs |
before 6.6.0-125.0.0.112.oe2403 | 6.6.0-125.0.0.112.oe2403 |
kernelopenEuler:24.03-LTS-SP1 From an advisory covering 14 CVEs |
before 6.6.0-125.0.0.124.oe2403sp1 | 6.6.0-125.0.0.124.oe2403sp1 |
kernelopenEuler:24.03-LTS-SP2 From an advisory covering 31 CVEs |
before 6.6.0-125.0.0.125.oe2403sp2 | 6.6.0-125.0.0.125.oe2403sp2 |
kernel-64k-debug-debuginfoRed Hat:enterprise_linux:10.1 From an advisory covering 123 CVEs |
before 0:6.12.0-124.8.1.el10_1 | 0:6.12.0-124.8.1.el10_1 |
kernel-64k-debug-develRed Hat:enterprise_linux:10.1 From an advisory covering 123 CVEs |
before 0:6.12.0-124.8.1.el10_1 | 0:6.12.0-124.8.1.el10_1 |
kernel-64k-debug-devel-matchedRed Hat:enterprise_linux:10.1 From an advisory covering 123 CVEs |
before 0:6.12.0-124.8.1.el10_1 | 0:6.12.0-124.8.1.el10_1 |
kernel-64k-debuginfoRed Hat:enterprise_linux:10.1 From an advisory covering 123 CVEs |
before 0:6.12.0-124.8.1.el10_1 | 0:6.12.0-124.8.1.el10_1 |
kernel-64k-develRed Hat:enterprise_linux:10.1 From an advisory covering 123 CVEs |
before 0:6.12.0-124.8.1.el10_1 | 0:6.12.0-124.8.1.el10_1 |
kernel-64k-devel-matchedRed Hat:enterprise_linux:10.1 From an advisory covering 123 CVEs |
before 0:6.12.0-124.8.1.el10_1 | 0:6.12.0-124.8.1.el10_1 |
kernel-debug-debuginfoRed Hat:enterprise_linux:10.1 From an advisory covering 123 CVEs |
before 0:6.12.0-124.8.1.el10_1 | 0:6.12.0-124.8.1.el10_1 |
kernel-debug-develRed Hat:enterprise_linux:10.1 From an advisory covering 123 CVEs |
before 0:6.12.0-124.8.1.el10_1 | 0:6.12.0-124.8.1.el10_1 |
kernel-debug-devel-matchedRed Hat:enterprise_linux:10.1 From an advisory covering 123 CVEs |
before 0:6.12.0-124.8.1.el10_1 | 0:6.12.0-124.8.1.el10_1 |
kernel-debuginfoRed Hat:enterprise_linux:10.1 From an advisory covering 123 CVEs |
before 0:6.12.0-124.8.1.el10_1 | 0:6.12.0-124.8.1.el10_1 |
kernel-debuginfo-common-aarch64Red Hat:enterprise_linux:10.1 From an advisory covering 123 CVEs |
before 0:6.12.0-124.8.1.el10_1 | 0:6.12.0-124.8.1.el10_1 |
kernel-debuginfo-common-ppc64leRed Hat:enterprise_linux:10.1 From an advisory covering 123 CVEs |
before 0:6.12.0-124.8.1.el10_1 | 0:6.12.0-124.8.1.el10_1 |
kernel-debuginfo-common-s390xRed Hat:enterprise_linux:10.1 From an advisory covering 123 CVEs |
before 0:6.12.0-124.8.1.el10_1 | 0:6.12.0-124.8.1.el10_1 |
kernel-debuginfo-common-x86_64Red Hat:enterprise_linux:10.1 From an advisory covering 123 CVEs |
before 0:6.12.0-124.8.1.el10_1 | 0:6.12.0-124.8.1.el10_1 |
kernel-develRed Hat:enterprise_linux:10.1 From an advisory covering 123 CVEs |
before 0:6.12.0-124.8.1.el10_1 | 0:6.12.0-124.8.1.el10_1 |
kernel-devel-matchedRed Hat:enterprise_linux:10.1 From an advisory covering 123 CVEs |
before 0:6.12.0-124.8.1.el10_1 | 0:6.12.0-124.8.1.el10_1 |
kernel-docRed Hat:enterprise_linux:10.1 From an advisory covering 123 CVEs |
before 0:6.12.0-124.8.1.el10_1 | 0:6.12.0-124.8.1.el10_1 |
kernel-rt-64k-debug-debuginfoRed Hat:enterprise_linux:10.1 From an advisory covering 123 CVEs |
before 0:6.12.0-124.8.1.el10_1 | 0:6.12.0-124.8.1.el10_1 |
kernel-rt-64k-debuginfoRed Hat:enterprise_linux:10.1 From an advisory covering 123 CVEs |
before 0:6.12.0-124.8.1.el10_1 | 0:6.12.0-124.8.1.el10_1 |
kernel-rt-debug-debuginfoRed Hat:enterprise_linux:10.1 From an advisory covering 123 CVEs |
before 0:6.12.0-124.8.1.el10_1 | 0:6.12.0-124.8.1.el10_1 |
kernel-rt-debuginfoRed Hat:enterprise_linux:10.1 From an advisory covering 123 CVEs |
before 0:6.12.0-124.8.1.el10_1 | 0:6.12.0-124.8.1.el10_1 |
kernel-tools-debuginfoRed Hat:enterprise_linux:10.1 From an advisory covering 123 CVEs |
before 0:6.12.0-124.8.1.el10_1 | 0:6.12.0-124.8.1.el10_1 |
kernel-zfcpdump-debuginfoRed Hat:enterprise_linux:10.1 From an advisory covering 123 CVEs |
before 0:6.12.0-124.8.1.el10_1 | 0:6.12.0-124.8.1.el10_1 |
kernel-zfcpdump-develRed Hat:enterprise_linux:10.1 From an advisory covering 123 CVEs |
before 0:6.12.0-124.8.1.el10_1 | 0:6.12.0-124.8.1.el10_1 |
kernel-zfcpdump-devel-matchedRed Hat:enterprise_linux:10.1 From an advisory covering 123 CVEs |
before 0:6.12.0-124.8.1.el10_1 | 0:6.12.0-124.8.1.el10_1 |
libperf-debuginfoRed Hat:enterprise_linux:10.1 From an advisory covering 123 CVEs |
before 0:6.12.0-124.8.1.el10_1 | 0:6.12.0-124.8.1.el10_1 |
perfRed Hat:enterprise_linux:10.1 From an advisory covering 123 CVEs |
before 0:6.12.0-124.8.1.el10_1 | 0:6.12.0-124.8.1.el10_1 |
perf-debuginfoRed Hat:enterprise_linux:10.1 From an advisory covering 123 CVEs |
before 0:6.12.0-124.8.1.el10_1 | 0:6.12.0-124.8.1.el10_1 |
python3-perfRed Hat:enterprise_linux:10.1 From an advisory covering 123 CVEs |
before 0:6.12.0-124.8.1.el10_1 | 0:6.12.0-124.8.1.el10_1 |
python3-perf-debuginfoRed Hat:enterprise_linux:10.1 From an advisory covering 123 CVEs |
before 0:6.12.0-124.8.1.el10_1 | 0:6.12.0-124.8.1.el10_1 |
rtlaRed Hat:enterprise_linux:10.1 From an advisory covering 123 CVEs |
before 0:6.12.0-124.8.1.el10_1 | 0:6.12.0-124.8.1.el10_1 |
rvRed Hat:enterprise_linux:10.1 From an advisory covering 123 CVEs |
before 0:6.12.0-124.8.1.el10_1 | 0:6.12.0-124.8.1.el10_1 |
kernelRed Hat:enterprise_linux:10.1 From an advisory covering 123 CVEs |
before 0:6.12.0-124.8.1.el10_1 | 0:6.12.0-124.8.1.el10_1 |
kernel-64kRed Hat:enterprise_linux:10.1 From an advisory covering 123 CVEs |
before 0:6.12.0-124.8.1.el10_1 | 0:6.12.0-124.8.1.el10_1 |
kernel-64k-coreRed Hat:enterprise_linux:10.1 From an advisory covering 123 CVEs |
before 0:6.12.0-124.8.1.el10_1 | 0:6.12.0-124.8.1.el10_1 |
kernel-64k-debugRed Hat:enterprise_linux:10.1 From an advisory covering 123 CVEs |
before 0:6.12.0-124.8.1.el10_1 | 0:6.12.0-124.8.1.el10_1 |
kernel-64k-debug-coreRed Hat:enterprise_linux:10.1 From an advisory covering 123 CVEs |
before 0:6.12.0-124.8.1.el10_1 | 0:6.12.0-124.8.1.el10_1 |
kernel-64k-debug-modulesRed Hat:enterprise_linux:10.1 From an advisory covering 123 CVEs |
before 0:6.12.0-124.8.1.el10_1 | 0:6.12.0-124.8.1.el10_1 |
kernel-64k-debug-modules-coreRed Hat:enterprise_linux:10.1 From an advisory covering 123 CVEs |
before 0:6.12.0-124.8.1.el10_1 | 0:6.12.0-124.8.1.el10_1 |
kernel-64k-debug-modules-extraRed Hat:enterprise_linux:10.1 From an advisory covering 123 CVEs |
before 0:6.12.0-124.8.1.el10_1 | 0:6.12.0-124.8.1.el10_1 |
kernel-64k-modulesRed Hat:enterprise_linux:10.1 From an advisory covering 123 CVEs |
before 0:6.12.0-124.8.1.el10_1 | 0:6.12.0-124.8.1.el10_1 |
kernel-64k-modules-coreRed Hat:enterprise_linux:10.1 From an advisory covering 123 CVEs |
before 0:6.12.0-124.8.1.el10_1 | 0:6.12.0-124.8.1.el10_1 |
kernel-64k-modules-extraRed Hat:enterprise_linux:10.1 From an advisory covering 123 CVEs |
before 0:6.12.0-124.8.1.el10_1 | 0:6.12.0-124.8.1.el10_1 |
kernel-abi-stablelistsRed Hat:enterprise_linux:10.1 From an advisory covering 123 CVEs |
before 0:6.12.0-124.8.1.el10_1 | 0:6.12.0-124.8.1.el10_1 |
kernel-coreRed Hat:enterprise_linux:10.1 From an advisory covering 123 CVEs |
before 0:6.12.0-124.8.1.el10_1 | 0:6.12.0-124.8.1.el10_1 |
kernel-debugRed Hat:enterprise_linux:10.1 From an advisory covering 123 CVEs |
before 0:6.12.0-124.8.1.el10_1 | 0:6.12.0-124.8.1.el10_1 |
kernel-debug-coreRed Hat:enterprise_linux:10.1 From an advisory covering 123 CVEs |
before 0:6.12.0-124.8.1.el10_1 | 0:6.12.0-124.8.1.el10_1 |
kernel-debug-modulesRed Hat:enterprise_linux:10.1 From an advisory covering 123 CVEs |
before 0:6.12.0-124.8.1.el10_1 | 0:6.12.0-124.8.1.el10_1 |
kernel-debug-modules-coreRed Hat:enterprise_linux:10.1 From an advisory covering 123 CVEs |
before 0:6.12.0-124.8.1.el10_1 | 0:6.12.0-124.8.1.el10_1 |
kernel-debug-modules-extraRed Hat:enterprise_linux:10.1 From an advisory covering 123 CVEs |
before 0:6.12.0-124.8.1.el10_1 | 0:6.12.0-124.8.1.el10_1 |
kernel-debug-uki-virtRed Hat:enterprise_linux:10.1 From an advisory covering 123 CVEs |
before 0:6.12.0-124.8.1.el10_1 | 0:6.12.0-124.8.1.el10_1 |
kernel-modulesRed Hat:enterprise_linux:10.1 From an advisory covering 123 CVEs |
before 0:6.12.0-124.8.1.el10_1 | 0:6.12.0-124.8.1.el10_1 |
kernelRocky Linux:10 From an advisory covering 88 CVEs |
before 0:6.12.0-124.8.1.el10_1 | 0:6.12.0-124.8.1.el10_1 |
kernelRocky Linux:9 From an advisory covering 111 CVEs |
before 0:5.14.0-611.5.1.el9_7 | 0:5.14.0-611.5.1.el9_7 |
linuxRoot:Debian:12 |
before 6.1.190-1.aikido.167 | 6.1.190-1.aikido.167 |
rootio-linuxRoot:Debian:12 |
before 6.1.190-1.aikido.167 | 6.1.190-1.aikido.167 |
linuxRoot:Ubuntu:22.04 |
before 5.15.0-203.213.aikido.119 | 5.15.0-203.213.aikido.119 |
rootio-linuxRoot:Ubuntu:22.04 |
before 5.15.0-203.213.aikido.119 | 5.15.0-203.213.aikido.119 |
linuxRoot:Ubuntu:24.04 |
before 6.8.0-149.149.aikido.91 | 6.8.0-149.149.aikido.91 |
rootio-linuxRoot:Ubuntu:24.04 |
before 6.8.0-149.149.aikido.91 | 6.8.0-149.149.aikido.91 |
kernel-cocoSUSE:Linux Enterprise Module for Confidential Computing Technical Preview 15 SP6 From an advisory covering 433 CVEs |
before 6.4.0-15061.21.coco15sp6.1 | 6.4.0-15061.21.coco15sp6.1 |
kernel-coco_debugSUSE:Linux Enterprise Module for Confidential Computing Technical Preview 15 SP6 From an advisory covering 433 CVEs |
before 6.4.0-15061.21.coco15sp6.1 | 6.4.0-15061.21.coco15sp6.1 |
kernel-source-cocoSUSE:Linux Enterprise Module for Confidential Computing Technical Preview 15 SP6 From an advisory covering 433 CVEs |
before 6.4.0-15061.21.coco15sp6.1 | 6.4.0-15061.21.coco15sp6.1 |
kernel-syms-cocoSUSE:Linux Enterprise Module for Confidential Computing Technical Preview 15 SP6 From an advisory covering 433 CVEs |
before 6.4.0-15061.21.coco15sp6.1 | 6.4.0-15061.21.coco15sp6.1 |
kernel-azureSUSE:Linux Enterprise Module for Public Cloud 15 SP7 From an advisory covering 329 CVEs |
before 6.4.0-150700.20.3.1 | 6.4.0-150700.20.3.1 |
kernel-source-azureSUSE:Linux Enterprise Module for Public Cloud 15 SP7 From an advisory covering 329 CVEs |
before 6.4.0-150700.20.3.1 | 6.4.0-150700.20.3.1 |
kernel-syms-azureSUSE:Linux Enterprise Module for Public Cloud 15 SP7 From an advisory covering 329 CVEs |
before 6.4.0-150700.20.3.1 | 6.4.0-150700.20.3.1 |
kernel-rtSUSE:Linux Enterprise Micro 5.5 From an advisory covering 605 CVEs |
before 5.14.21-150500.13.91.1 | 5.14.21-150500.13.91.1 |
kernel-source-rtSUSE:Linux Enterprise Micro 5.5 From an advisory covering 605 CVEs |
before 5.14.21-150500.13.91.1 | 5.14.21-150500.13.91.1 |
kernel-azureSUSE:Linux Enterprise Module for Public Cloud 15 SP6 From an advisory covering 186 CVEs |
before 6.4.0-150600.8.34.2 | 6.4.0-150600.8.34.2 |
kernel-source-azureSUSE:Linux Enterprise Module for Public Cloud 15 SP6 From an advisory covering 186 CVEs |
before 6.4.0-150600.8.34.2 | 6.4.0-150600.8.34.2 |
kernel-syms-azureSUSE:Linux Enterprise Module for Public Cloud 15 SP6 From an advisory covering 186 CVEs |
before 6.4.0-150600.8.34.1 | 6.4.0-150600.8.34.1 |
kernel-azureopenSUSE:Leap 15.6 From an advisory covering 186 CVEs |
before 6.4.0-150600.8.34.2 | 6.4.0-150600.8.34.2 |
kernel-source-azureopenSUSE:Leap 15.6 From an advisory covering 186 CVEs |
before 6.4.0-150600.8.34.2 | 6.4.0-150600.8.34.2 |
kernel-syms-azureopenSUSE:Leap 15.6 From an advisory covering 186 CVEs |
before 6.4.0-150600.8.34.1 | 6.4.0-150600.8.34.1 |
kernel-livepatch-SLE15-SP6-RT_Update_10SUSE:Linux Enterprise Live Patching 15 SP6 From an advisory covering 189 CVEs |
before 1-150600.1.5.1 | 1-150600.1.5.1 |
kernel-rtSUSE:Real Time Module 15 SP6 From an advisory covering 189 CVEs |
before 6.4.0-150600.10.34.1 | 6.4.0-150600.10.34.1 |
kernel-rt_debugSUSE:Real Time Module 15 SP6 From an advisory covering 189 CVEs |
before 6.4.0-150600.10.34.1 | 6.4.0-150600.10.34.1 |
kernel-source-rtSUSE:Real Time Module 15 SP6 From an advisory covering 189 CVEs |
before 6.4.0-150600.10.34.1 | 6.4.0-150600.10.34.1 |
kernel-syms-rtSUSE:Real Time Module 15 SP6 From an advisory covering 189 CVEs |
before 6.4.0-150600.10.34.1 | 6.4.0-150600.10.34.1 |
kernel-rtopenSUSE:Leap 15.6 From an advisory covering 189 CVEs |
before 6.4.0-150600.10.34.1 | 6.4.0-150600.10.34.1 |
kernel-rt_debugopenSUSE:Leap 15.6 From an advisory covering 189 CVEs |
before 6.4.0-150600.10.34.1 | 6.4.0-150600.10.34.1 |
kernel-source-rtopenSUSE:Leap 15.6 From an advisory covering 189 CVEs |
before 6.4.0-150600.10.34.1 | 6.4.0-150600.10.34.1 |
kernel-syms-rtopenSUSE:Leap 15.6 From an advisory covering 189 CVEs |
before 6.4.0-150600.10.34.1 | 6.4.0-150600.10.34.1 |
kernel-64kbSUSE:Linux Enterprise Module for Basesystem 15 SP6 From an advisory covering 189 CVEs |
before 6.4.0-150600.23.47.2 | 6.4.0-150600.23.47.2 |
kernel-defaultSUSE:Linux Enterprise Module for Basesystem 15 SP6 From an advisory covering 189 CVEs |
before 6.4.0-150600.23.47.2 | 6.4.0-150600.23.47.2 |
kernel-default-baseSUSE:Linux Enterprise Module for Basesystem 15 SP6 From an advisory covering 189 CVEs |
before 6.4.0-150600.23.47.2.150600.12.20.2 | 6.4.0-150600.23.47.2.150600.12.20.2 |
kernel-sourceSUSE:Linux Enterprise Module for Basesystem 15 SP6 From an advisory covering 189 CVEs |
before 6.4.0-150600.23.47.2 | 6.4.0-150600.23.47.2 |
kernel-zfcpdumpSUSE:Linux Enterprise Module for Basesystem 15 SP6 From an advisory covering 189 CVEs |
before 6.4.0-150600.23.47.2 | 6.4.0-150600.23.47.2 |
kernel-docsSUSE:Linux Enterprise Module for Development Tools 15 SP6 From an advisory covering 189 CVEs |
before 6.4.0-150600.23.47.1 | 6.4.0-150600.23.47.1 |
kernel-obs-buildSUSE:Linux Enterprise Module for Development Tools 15 SP6 From an advisory covering 189 CVEs |
before 6.4.0-150600.23.47.1 | 6.4.0-150600.23.47.1 |
kernel-sourceSUSE:Linux Enterprise Module for Development Tools 15 SP6 From an advisory covering 189 CVEs |
before 6.4.0-150600.23.47.2 | 6.4.0-150600.23.47.2 |
kernel-symsSUSE:Linux Enterprise Module for Development Tools 15 SP6 From an advisory covering 189 CVEs |
before 6.4.0-150600.23.47.1 | 6.4.0-150600.23.47.1 |
kernel-defaultSUSE:Linux Enterprise Module for Legacy 15 SP6 From an advisory covering 189 CVEs |
before 6.4.0-150600.23.47.2 | 6.4.0-150600.23.47.2 |
kernel-defaultSUSE:Linux Enterprise Live Patching 15 SP6 From an advisory covering 189 CVEs |
before 6.4.0-150600.23.47.2 | 6.4.0-150600.23.47.2 |
kernel-livepatch-SLE15-SP6_Update_10SUSE:Linux Enterprise Live Patching 15 SP6 From an advisory covering 189 CVEs |
before 1-150600.13.5.1 | 1-150600.13.5.1 |
kernel-defaultSUSE:Linux Enterprise High Availability Extension 15 SP6 From an advisory covering 189 CVEs |
before 6.4.0-150600.23.47.2 | 6.4.0-150600.23.47.2 |
kernel-defaultSUSE:Linux Enterprise Workstation Extension 15 SP6 From an advisory covering 189 CVEs |
before 6.4.0-150600.23.47.2 | 6.4.0-150600.23.47.2 |
dtb-aarch64openSUSE:Leap 15.6 From an advisory covering 189 CVEs |
before 6.4.0-150600.23.47.1 | 6.4.0-150600.23.47.1 |
kernel-64kbopenSUSE:Leap 15.6 From an advisory covering 189 CVEs |
before 6.4.0-150600.23.47.2 | 6.4.0-150600.23.47.2 |
kernel-debugopenSUSE:Leap 15.6 From an advisory covering 189 CVEs |
before 6.4.0-150600.23.47.2 | 6.4.0-150600.23.47.2 |
kernel-defaultopenSUSE:Leap 15.6 From an advisory covering 189 CVEs |
before 6.4.0-150600.23.47.2 | 6.4.0-150600.23.47.2 |
kernel-default-baseopenSUSE:Leap 15.6 From an advisory covering 189 CVEs |
before 6.4.0-150600.23.47.2.150600.12.20.2 | 6.4.0-150600.23.47.2.150600.12.20.2 |
kernel-docsopenSUSE:Leap 15.6 From an advisory covering 189 CVEs |
before 6.4.0-150600.23.47.1 | 6.4.0-150600.23.47.1 |
kernel-kvmsmallopenSUSE:Leap 15.6 From an advisory covering 189 CVEs |
before 6.4.0-150600.23.47.2 | 6.4.0-150600.23.47.2 |
kernel-obs-buildopenSUSE:Leap 15.6 From an advisory covering 189 CVEs |
before 6.4.0-150600.23.47.1 | 6.4.0-150600.23.47.1 |
kernel-obs-qaopenSUSE:Leap 15.6 From an advisory covering 189 CVEs |
before 6.4.0-150600.23.47.1 | 6.4.0-150600.23.47.1 |
kernel-sourceopenSUSE:Leap 15.6 From an advisory covering 189 CVEs |
before 6.4.0-150600.23.47.2 | 6.4.0-150600.23.47.2 |
kernel-symsopenSUSE:Leap 15.6 From an advisory covering 189 CVEs |
before 6.4.0-150600.23.47.1 | 6.4.0-150600.23.47.1 |
kernel-zfcpdumpopenSUSE:Leap 15.6 From an advisory covering 189 CVEs |
before 6.4.0-150600.23.47.2 | 6.4.0-150600.23.47.2 |
kernel-rtSUSE:Linux Enterprise Micro 5.3 From an advisory covering 530 CVEs |
before 5.14.21-150400.15.115.1 | 5.14.21-150400.15.115.1 |
kernel-source-rtSUSE:Linux Enterprise Micro 5.3 From an advisory covering 530 CVEs |
before 5.14.21-150400.15.115.1 | 5.14.21-150400.15.115.1 |
kernel-rtSUSE:Linux Enterprise Micro 5.4 From an advisory covering 530 CVEs |
before 5.14.21-150400.15.115.1 | 5.14.21-150400.15.115.1 |
kernel-source-rtSUSE:Linux Enterprise Micro 5.4 From an advisory covering 530 CVEs |
before 5.14.21-150400.15.115.1 | 5.14.21-150400.15.115.1 |
kernel-defaultSUSE:Linux Enterprise Micro 5.3 From an advisory covering 62 CVEs |
before 5.14.21-150400.24.161.1 | 5.14.21-150400.24.161.1 |
kernel-default-baseSUSE:Linux Enterprise Micro 5.3 From an advisory covering 62 CVEs |
before 5.14.21-150400.24.161.1.150400.24.80.1 | 5.14.21-150400.24.161.1.150400.24.80.1 |
kernel-defaultSUSE:Linux Enterprise Micro 5.4 From an advisory covering 62 CVEs |
before 5.14.21-150400.24.161.1 | 5.14.21-150400.24.161.1 |
kernel-default-baseSUSE:Linux Enterprise Micro 5.4 From an advisory covering 62 CVEs |
before 5.14.21-150400.24.161.1.150400.24.80.1 | 5.14.21-150400.24.161.1.150400.24.80.1 |
kernel-defaultSUSE:Linux Enterprise Live Patching 15 SP4 From an advisory covering 62 CVEs |
before 5.14.21-150400.24.161.1 | 5.14.21-150400.24.161.1 |
kernel-livepatch-SLE15-SP4_Update_39SUSE:Linux Enterprise Live Patching 15 SP4 From an advisory covering 62 CVEs |
before 1-150400.9.3.1 | 1-150400.9.3.1 |
kernel-defaultSUSE:Linux Enterprise High Availability Extension 15 SP4 From an advisory covering 62 CVEs |
before 5.14.21-150400.24.161.1 | 5.14.21-150400.24.161.1 |
kernel-64kbSUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS From an advisory covering 62 CVEs |
before 5.14.21-150400.24.161.1 | 5.14.21-150400.24.161.1 |
kernel-defaultSUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS From an advisory covering 62 CVEs |
before 5.14.21-150400.24.161.1 | 5.14.21-150400.24.161.1 |
kernel-default-baseSUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS From an advisory covering 62 CVEs |
before 5.14.21-150400.24.161.1.150400.24.80.1 | 5.14.21-150400.24.161.1.150400.24.80.1 |
kernel-docsSUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS From an advisory covering 62 CVEs |
before 5.14.21-150400.24.161.1 | 5.14.21-150400.24.161.1 |
kernel-obs-buildSUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS From an advisory covering 62 CVEs |
before 5.14.21-150400.24.161.1 | 5.14.21-150400.24.161.1 |
kernel-sourceSUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS From an advisory covering 62 CVEs |
before 5.14.21-150400.24.161.1 | 5.14.21-150400.24.161.1 |
kernel-symsSUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS From an advisory covering 62 CVEs |
before 5.14.21-150400.24.161.1 | 5.14.21-150400.24.161.1 |
kernel-64kbSUSE:Linux Enterprise High Performance Computing 15 SP4-LTSS From an advisory covering 62 CVEs |
before 5.14.21-150400.24.161.1 | 5.14.21-150400.24.161.1 |
kernel-defaultSUSE:Linux Enterprise High Performance Computing 15 SP4-LTSS From an advisory covering 62 CVEs |
before 5.14.21-150400.24.161.1 | 5.14.21-150400.24.161.1 |
kernel-default-baseSUSE:Linux Enterprise High Performance Computing 15 SP4-LTSS From an advisory covering 62 CVEs |
before 5.14.21-150400.24.161.1.150400.24.80.1 | 5.14.21-150400.24.161.1.150400.24.80.1 |
linux-hwe-edgeUbuntu:16.04:LTS |
All versions, plus listed versions 4.8.0-28.30~16.04.14.8.0-30.32~16.04.14.8.0-32.34~16.04.14.8.0-34.36~16.04.14.10.0-14.16~16.04.1 Show 18 moreShow less4.10.0-19.21~16.04.14.10.0-20.22~16.04.14.10.0-21.23~16.04.14.10.0-22.24~16.04.14.10.0-24.28~16.04.14.10.0-26.30~16.04.14.11.0-13.19~16.04.14.11.0-14.20~16.04.14.13.0-16.19~16.04.34.13.0-17.20~16.04.14.13.0-19.22~16.04.14.13.0-21.24~16.04.14.13.0-25.29~16.04.24.15.0-13.14~16.04.14.15.0-15.16~16.04.14.15.0-20.21~16.04.14.15.0-22.24~16.04.14.15.0-23.25~16.04.1 |
None known |
linux-aws-5.0Ubuntu:18.04:LTS |
All versions, plus listed versions 5.0.0-1021.24~18.04.15.0.0-1022.25~18.04.15.0.0-1023.26~18.04.15.0.0-1024.27~18.04.15.0.0-1025.285.0.0-1027.30 |
None known |
linux-aws-5.3Ubuntu:18.04:LTS |
All versions, plus listed versions 5.3.0-1016.17~18.04.15.3.0-1017.18~18.04.15.3.0-1019.21~18.04.15.3.0-1023.25~18.04.15.3.0-1028.30~18.04.1 Show 5 moreShow less5.3.0-1030.32~18.04.15.3.0-1032.34~18.04.25.3.0-1033.355.3.0-1034.365.3.0-1035.37 |
None known |
linux-azureUbuntu:18.04:LTS |
All versions, plus listed versions 4.15.0-1002.24.15.0-1003.34.15.0-1004.44.15.0-1008.84.15.0-1009.9 Show 39 moreShow less4.15.0-1012.124.15.0-1013.134.15.0-1014.144.15.0-1018.184.15.0-1019.194.15.0-1021.214.15.0-1022.234.15.0-1023.244.15.0-1025.264.15.0-1028.294.15.0-1030.314.15.0-1031.324.15.0-1032.334.15.0-1035.364.15.0-1036.384.15.0-1037.394.18.0-1011.11~18.04.14.18.0-1013.13~18.04.14.18.0-1014.14~18.04.14.18.0-1018.18~18.04.14.18.0-1019.19~18.04.14.18.0-1020.20~18.04.14.18.0-1023.24~18.04.14.18.0-1024.25~18.04.14.18.0-1025.27~18.04.15.0.0-1014.14~18.04.15.0.0-1016.17~18.04.15.0.0-1018.19~18.04.15.0.0-1020.21~18.04.15.0.0-1022.23~18.04.15.0.0-1023.24~18.04.15.0.0-1025.27~18.04.15.0.0-1027.29~18.04.15.0.0-1028.30~18.04.15.0.0-1029.31~18.04.15.0.0-1031.335.0.0-1032.345.0.0-1035.375.0.0-1036.38 |
None known |
linux-azure-5.3Ubuntu:18.04:LTS |
All versions, plus listed versions 5.3.0-1007.8~18.04.15.3.0-1008.9~18.04.15.3.0-1009.10~18.04.15.3.0-1010.11~18.04.15.3.0-1012.13~18.04.1 Show 11 moreShow less5.3.0-1013.14~18.04.15.3.0-1016.17~18.04.15.3.0-1018.19~18.04.15.3.0-1019.20~18.04.15.3.0-1020.21~18.04.15.3.0-1022.23~18.04.15.3.0-1028.29~18.04.15.3.0-1031.32~18.04.15.3.0-1032.33~18.04.15.3.0-1034.35~18.04.15.3.0-1035.36 |
None known |
linux-azure-edgeUbuntu:18.04:LTS |
All versions, plus listed versions 4.18.0-1006.6~18.04.14.18.0-1007.7~18.04.14.18.0-1008.8~18.04.15.0.0-1012.12~18.04.2 |
None known |
linux-gcpUbuntu:18.04:LTS |
All versions, plus listed versions 4.15.0-1001.14.15.0-1003.34.15.0-1005.54.15.0-1006.64.15.0-1008.8 Show 33 moreShow less4.15.0-1009.94.15.0-1010.104.15.0-1014.144.15.0-1015.154.15.0-1017.184.15.0-1018.194.15.0-1019.204.15.0-1021.224.15.0-1023.244.15.0-1024.254.15.0-1025.264.15.0-1026.274.15.0-1027.284.15.0-1028.294.15.0-1029.314.15.0-1030.324.15.0-1032.344.15.0-1033.354.15.0-1034.364.15.0-1036.384.15.0-1037.394.15.0-1040.424.15.0-1042.454.15.0-1044.705.0.0-1020.20~18.04.15.0.0-1021.21~18.04.15.0.0-1025.26~18.04.15.0.0-1026.27~18.04.15.0.0-1028.29~18.04.15.0.0-1029.30~18.04.15.0.0-1031.325.0.0-1033.345.0.0-1034.35 |
None known |
linux-gcp-5.3Ubuntu:18.04:LTS |
All versions, plus listed versions 5.3.0-1008.9~18.04.15.3.0-1009.10~18.04.15.3.0-1010.11~18.04.15.3.0-1012.13~18.04.15.3.0-1014.15~18.04.1 Show 8 moreShow less5.3.0-1016.17~18.04.15.3.0-1017.18~18.04.15.3.0-1018.19~18.04.15.3.0-1020.22~18.04.15.3.0-1026.28~18.04.15.3.0-1029.31~18.04.15.3.0-1030.32~18.04.15.3.0-1032.34~18.04.1 |
None known |
linux-gke-4.15Ubuntu:18.04:LTS |
All versions, plus listed versions 4.15.0-1030.324.15.0-1032.344.15.0-1033.354.15.0-1034.364.15.0-1036.38 Show 28 moreShow less4.15.0-1037.394.15.0-1040.424.15.0-1041.434.15.0-1042.444.15.0-1044.464.15.0-1045.484.15.0-1046.494.15.0-1048.514.15.0-1049.524.15.0-1050.534.15.0-1052.554.15.0-1055.584.15.0-1057.604.15.0-1058.614.15.0-1059.624.15.0-1063.664.15.0-1064.674.15.0-1066.694.15.0-1067.704.15.0-1069.724.15.0-1070.734.15.0-1072.764.15.0-1073.784.15.0-1074.794.15.0-1076.814.15.0-1077.824.15.0-1078.834.15.0-1079.84 |
None known |
linux-gke-5.4Ubuntu:18.04:LTS |
All versions, plus listed versions 5.4.0-1025.25~18.04.15.4.0-1027.28~18.04.15.4.0-1029.31~18.04.15.4.0-1030.32~18.04.15.4.0-1032.34~18.04.1 Show 32 moreShow less5.4.0-1033.35~18.04.15.4.0-1035.37~18.04.15.4.0-1036.38~18.04.15.4.0-1037.39~18.04.15.4.0-1039.41~18.04.15.4.0-1040.42~18.04.15.4.0-1042.44~18.04.15.4.0-1043.45~18.04.15.4.0-1044.46~18.04.15.4.0-1046.48~18.04.15.4.0-1049.52~18.04.15.4.0-1051.54~18.04.15.4.0-1052.55~18.04.15.4.0-1053.56~18.04.15.4.0-1054.57~18.04.15.4.0-1055.58~18.04.15.4.0-1056.59~18.04.15.4.0-1057.60~18.04.15.4.0-1059.62~18.04.15.4.0-1061.64~18.04.15.4.0-1062.65~18.04.15.4.0-1063.66~18.04.15.4.0-1065.68~18.04.15.4.0-1066.69~18.04.15.4.0-1067.70~18.04.15.4.0-1068.71~18.04.15.4.0-1071.76~18.04.35.4.0-1072.77~18.04.15.4.0-1074.79~18.04.15.4.0-1076.82~18.04.15.4.0-1078.84~18.04.15.4.0-1080.86~18.04.1 |
None known |
linux-gkeop-5.4Ubuntu:18.04:LTS |
All versions, plus listed versions 5.4.0-1001.15.4.0-1003.35.4.0-1004.55.4.0-1005.65.4.0-1007.8~18.04.1 Show 32 moreShow less5.4.0-1008.9~18.04.15.4.0-1009.10~18.04.15.4.0-1010.11~18.04.15.4.0-1011.12~18.04.25.4.0-1012.13~18.04.15.4.0-1013.14~18.04.15.4.0-1014.15~18.04.15.4.0-1015.16~18.04.15.4.0-1016.17~18.04.15.4.0-1018.19~18.04.15.4.0-1021.22~18.04.15.4.0-1022.23~18.04.15.4.0-1023.24~18.04.15.4.0-1024.25~18.04.15.4.0-1025.26~18.04.15.4.0-1026.27~18.04.15.4.0-1027.28~18.04.15.4.0-1029.30~18.04.25.4.0-1031.32~18.04.15.4.0-1032.33~18.04.15.4.0-1033.34~18.04.15.4.0-1034.35~18.04.15.4.0-1036.37~18.04.15.4.0-1037.38~18.04.15.4.0-1038.39~18.04.15.4.0-1039.40~18.04.15.4.0-1040.41~18.04.15.4.0-1043.44~18.04.15.4.0-1046.48~18.04.15.4.0-1048.51~18.04.15.4.0-1049.52~18.04.15.4.0-1051.54~18.04.1 |
None known |
linux-hweUbuntu:18.04:LTS |
All versions, plus listed versions 4.18.0-13.14~18.04.14.18.0-14.15~18.04.14.18.0-15.16~18.04.14.18.0-16.17~18.04.14.18.0-17.18~18.04.1 Show 38 moreShow less4.18.0-18.19~18.04.14.18.0-20.21~18.04.14.18.0-21.22~18.04.14.18.0-22.23~18.04.14.18.0-24.25~18.04.14.18.0-25.26~18.04.15.0.0-23.24~18.04.15.0.0-25.26~18.04.15.0.0-27.28~18.04.15.0.0-29.31~18.04.15.0.0-31.33~18.04.15.0.0-32.34~18.04.25.0.0-35.38~18.04.15.0.0-36.39~18.04.15.0.0-37.40~18.04.15.3.0-26.28~18.04.15.3.0-28.30~18.04.15.3.0-40.32~18.04.15.3.0-42.34~18.04.15.3.0-45.37~18.04.15.3.0-46.38~18.04.15.3.0-51.44~18.04.25.3.0-53.47~18.04.15.3.0-59.53~18.04.15.3.0-61.55~18.04.15.3.0-62.56~18.04.15.3.0-64.58~18.04.15.3.0-65.595.3.0-66.605.3.0-67.615.3.0-68.635.3.0-69.655.3.0-70.665.3.0-72.685.3.0-73.695.3.0-74.705.3.0-75.715.3.0-76.72 |
None known |
linux-hwe-edgeUbuntu:18.04:LTS |
All versions, plus listed versions 5.0.0-15.16~18.04.15.0.0-16.17~18.04.15.0.0-17.18~18.04.15.0.0-19.20~18.04.15.0.0-20.21~18.04.1 Show 5 moreShow less5.3.0-19.20~18.04.25.3.0-22.24~18.04.15.3.0-23.25~18.04.15.3.0-23.25~18.04.25.3.0-24.26~18.04.2 |
None known |
linux-oemUbuntu:18.04:LTS |
All versions, plus listed versions 4.15.0-1002.34.15.0-1004.54.15.0-1006.94.15.0-1008.114.15.0-1009.12 Show 45 moreShow less4.15.0-1012.154.15.0-1013.164.15.0-1015.184.15.0-1017.204.15.0-1018.214.15.0-1021.244.15.0-1024.294.15.0-1026.314.15.0-1028.334.15.0-1030.354.15.0-1033.384.15.0-1034.394.15.0-1035.404.15.0-1036.414.15.0-1038.434.15.0-1039.444.15.0-1043.484.15.0-1045.504.15.0-1050.574.15.0-1056.654.15.0-1057.664.15.0-1059.684.15.0-1063.724.15.0-1064.734.15.0-1065.754.15.0-1066.764.15.0-1067.774.15.0-1069.794.15.0-1073.834.15.0-1076.864.15.0-1079.894.15.0-1080.904.15.0-1081.914.15.0-1087.974.15.0-1090.1004.15.0-1091.1014.15.0-1093.1034.15.0-1094.1044.15.0-1096.1064.15.0-1097.1074.15.0-1099.1094.15.0-1100.1104.15.0-1101.1124.15.0-1102.1134.15.0-1103.114 |
None known |
linux-oracle-5.0Ubuntu:18.04:LTS |
All versions, plus listed versions 5.0.0-1007.12~18.04.15.0.0-1008.13~18.04.15.0.0-1009.14~18.04.15.0.0-1010.15~18.04.15.0.0-1011.165.0.0-1013.185.0.0-1014.19 |
None known |
linux-oracle-5.3Ubuntu:18.04:LTS |
All versions, plus listed versions 5.3.0-1011.12~18.04.15.3.0-1013.14~18.04.15.3.0-1014.15~18.04.15.3.0-1016.18~18.04.15.3.0-1018.20~18.04.1 Show 4 moreShow less5.3.0-1024.26~18.04.15.3.0-1027.29~18.04.15.3.0-1028.30~18.04.15.3.0-1030.32~18.04.1 |
None known |
linux-aws-5.11Ubuntu:20.04:LTS |
All versions, plus listed versions 5.11.0-1009.9~20.04.25.11.0-1014.15~20.04.15.11.0-1016.17~20.04.15.11.0-1017.18~20.04.15.11.0-1019.20~20.04.1 Show 7 moreShow less5.11.0-1020.21~20.04.25.11.0-1021.22~20.04.25.11.0-1022.23~20.04.15.11.0-1023.24~20.04.15.11.0-1025.27~20.04.15.11.0-1027.30~20.04.15.11.0-1028.31~20.04.1 |
None known |
linux-aws-5.13Ubuntu:20.04:LTS |
All versions, plus listed versions 5.13.0-1008.9~20.04.25.13.0-1011.12~20.04.15.13.0-1012.13~20.04.15.13.0-1014.15~20.04.15.13.0-1017.19~20.04.1 Show 8 moreShow less5.13.0-1019.21~20.04.15.13.0-1021.23~20.04.25.13.0-1022.24~20.04.15.13.0-1023.25~20.04.15.13.0-1025.27~20.04.15.13.0-1028.31~20.04.15.13.0-1029.32~20.04.15.13.0-1031.35~20.04.1 |
None known |
linux-aws-5.15Ubuntu:Pro:20.04:LTS |
All versions, plus listed versions 5.15.0-1014.18~20.04.15.15.0-1015.19~20.04.15.15.0-1017.21~20.04.15.15.0-1019.23~20.04.15.15.0-1020.24~20.04.1 Show 45 moreShow less5.15.0-1021.25~20.04.15.15.0-1022.26~20.04.15.15.0-1023.27~20.04.15.15.0-1026.30~20.04.25.15.0-1027.31~20.04.15.15.0-1028.32~20.04.15.15.0-1030.34~20.04.15.15.0-1031.35~20.04.15.15.0-1033.37~20.04.15.15.0-1034.38~20.04.15.15.0-1035.39~20.04.15.15.0-1036.40~20.04.15.15.0-1037.41~20.04.15.15.0-1038.43~20.04.15.15.0-1039.44~20.04.15.15.0-1040.45~20.04.15.15.0-1041.46~20.04.15.15.0-1043.48~20.04.15.15.0-1044.49~20.04.15.15.0-1045.50~20.04.15.15.0-1047.52~20.04.15.15.0-1048.53~20.04.15.15.0-1049.54~20.04.15.15.0-1050.55~20.04.15.15.0-1051.56~20.04.15.15.0-1052.57~20.04.15.15.0-1053.58~20.04.15.15.0-1055.60~20.04.15.15.0-1056.61~20.04.15.15.0-1057.63~20.04.15.15.0-1058.64~20.04.15.15.0-1061.67~20.04.15.15.0-1062.68~20.04.15.15.0-1063.69~20.04.15.15.0-1064.70~20.04.15.15.0-1065.71~20.04.15.15.0-1066.72~20.04.15.15.0-1067.73~20.04.15.15.0-1068.74~20.04.15.15.0-1069.75~20.04.15.15.0-1070.76~20.04.15.15.0-1071.77~20.04.15.15.0-1072.78~20.04.15.15.0-1073.79~20.04.15.15.0-1075.82~20.04.1 |
None known |
linux-aws-5.8Ubuntu:20.04:LTS |
All versions, plus listed versions 5.8.0-1035.37~20.04.15.8.0-1038.40~20.04.15.8.0-1041.43~20.04.15.8.0-1042.44~20.04.1 |
None known |
linux-azure-5.11Ubuntu:20.04:LTS |
All versions, plus listed versions 5.11.0-1007.7~20.04.25.11.0-1012.13~20.04.15.11.0-1013.14~20.04.15.11.0-1015.16~20.04.15.11.0-1017.18~20.04.1 Show 8 moreShow less5.11.0-1019.20~20.04.15.11.0-1020.21~20.04.15.11.0-1021.22~20.04.15.11.0-1022.23~20.04.15.11.0-1023.24~20.04.15.11.0-1025.27~20.04.15.11.0-1027.30~20.04.15.11.0-1028.31~20.04.2 |
None known |
linux-azure-5.13Ubuntu:20.04:LTS |
All versions, plus listed versions 5.13.0-1009.10~20.04.25.13.0-1012.14~20.04.15.13.0-1013.15~20.04.15.13.0-1014.16~20.04.15.13.0-1017.19~20.04.1 Show 7 moreShow less5.13.0-1021.24~20.04.15.13.0-1022.26~20.04.15.13.0-1023.27~20.04.15.13.0-1025.29~20.04.15.13.0-1028.33~20.04.15.13.0-1029.34~20.04.15.13.0-1031.37~20.04.1 |
None known |
linux-azure-5.15Ubuntu:Pro:20.04:LTS |
All versions, plus listed versions 5.15.0-1007.8~20.04.15.15.0-1008.9~20.04.15.15.0-1013.16~20.04.15.15.0-1014.17~20.04.15.15.0-1017.20~20.04.1 Show 45 moreShow less5.15.0-1019.24~20.04.15.15.0-1020.25~20.04.15.15.0-1021.26~20.04.15.15.0-1022.27~20.04.15.15.0-1023.29~20.04.15.15.0-1029.36~20.04.15.15.0-1030.37~20.04.15.15.0-1031.38~20.04.15.15.0-1033.40~20.04.15.15.0-1034.41~20.04.15.15.0-1035.42~20.04.15.15.0-1036.43~20.04.15.15.0-1037.44~20.04.15.15.0-1038.45~20.04.15.15.0-1039.46~20.04.15.15.0-1040.47~20.04.15.15.0-1041.48~20.04.15.15.0-1042.49~20.04.15.15.0-1043.50~20.04.15.15.0-1045.52~20.04.15.15.0-1046.53~20.04.15.15.0-1047.54~20.04.15.15.0-1049.56~20.04.15.15.0-1050.57~20.04.15.15.0-1051.59~20.04.15.15.0-1052.60~20.04.15.15.0-1053.61~20.04.15.15.0-1054.62~20.04.15.15.0-1056.64~20.04.15.15.0-1057.65~20.04.15.15.0-1058.66~20.04.25.15.0-1059.67~20.04.15.15.0-1060.69~20.04.15.15.0-1061.70~20.04.15.15.0-1063.72~20.04.15.15.0-1064.73~20.04.15.15.0-1065.74~20.04.15.15.0-1067.76~20.04.15.15.0-1068.77~20.04.15.15.0-1070.79~20.04.15.15.0-1071.80~20.04.15.15.0-1072.81~20.04.15.15.0-1073.82~20.04.15.15.0-1074.83~20.04.15.15.0-1075.84~20.04.1 |
None known |
linux-azure-5.8Ubuntu:20.04:LTS |
All versions, plus listed versions 5.8.0-1033.35~20.04.15.8.0-1036.38~20.04.15.8.0-1039.42~20.04.15.8.0-1040.43~20.04.15.8.0-1041.44~20.04.15.8.0-1042.45~20.04.15.8.0-1043.46~20.04.1 |
None known |
linux-azure-fdeUbuntu:20.04:LTS |
All versions, plus listed versions 5.4.0-1063.66+cvm2.25.4.0-1063.66+cvm3.25.4.0-1064.67+cvm1.15.4.0-1065.68+cvm2.15.4.0-1067.70+cvm1.1 Show 21 moreShow less5.4.0-1068.71+cvm1.15.4.0-1069.72+cvm1.15.4.0-1070.73+cvm1.15.4.0-1072.75+cvm1.15.4.0-1073.76+cvm1.15.4.0-1074.77+cvm1.15.4.0-1076.79+cvm1.15.4.0-1078.81+cvm1.15.4.0-1080.83+cvm1.15.4.0-1083.87+cvm1.15.4.0-1085.90+cvm1.15.4.0-1085.90+cvm2.15.4.0-1086.91+cvm1.15.4.0-1089.94+cvm1.25.4.0-1090.95+cvm1.15.4.0-1091.96+cvm1.15.4.0-1092.97+cvm1.15.4.0-1095.101+cvm1.15.4.0-1098.104+cvm1.15.4.0-1100.106+cvm1.15.4.0-1103.109+cvm1.1 |
None known |
linux-azure-fde-5.15Ubuntu:Pro:20.04:LTS |
All versions, plus listed versions 5.15.0-1019.24~20.04.1.15.15.0-1020.25~20.04.1.15.15.0-1021.26~20.04.1.15.15.0-1029.36~20.04.1.15.15.0-1030.37~20.04.1.1 Show 45 moreShow less5.15.0-1031.38~20.04.1.15.15.0-1033.40~20.04.1.15.15.0-1034.41~20.04.1.25.15.0-1035.42~20.04.1.15.15.0-1036.43~20.04.1.15.15.0-1037.44~20.04.1.15.15.0-1038.45~20.04.1.15.15.0-1039.46~20.04.1.15.15.0-1040.47~20.04.1.15.15.0-1041.48~20.04.1.15.15.0-1042.49~20.04.1.15.15.0-1043.50~20.04.1.15.15.0-1046.53~20.04.1.15.15.0-1047.54~20.04.1.15.15.0-1049.56~20.04.1.15.15.0-1050.57~20.04.1.15.15.0-1051.59~20.04.1.15.15.0-1052.60~20.04.1.15.15.0-1053.61~20.04.1.15.15.0-1054.62~20.04.1.15.15.0-1056.64~20.04.1.15.15.0-1057.65~20.04.1.15.15.0-1058.66~20.04.2.15.15.0-1059.67~20.04.1.15.15.0-1060.69~20.04.1.15.15.0-1061.70~20.04.1.15.15.0-1063.72~20.04.1.15.15.0-1064.73~20.04.1.15.15.0-1065.74~20.04.1.15.15.0-1067.76~20.04.1.15.15.0-1068.77~20.04.1.15.15.0-1070.79~20.04.1.15.15.0-1071.80~20.04.1.15.15.0-1072.81~20.04.1.15.15.0-1073.82~20.04.1.15.15.0-1074.83~20.04.1.15.15.0-1076.85~20.04.1.15.15.0-1078.87~20.04.1.15.15.0-1081.90~20.04.1.15.15.0-1082.91~20.04.1.15.15.0-1086.95~20.04.1.15.15.0-1087.96~20.04.1.15.15.0-1088.97~20.04.1.15.15.0-1089.98~20.04.1.15.15.0-1091.100~20.04.1.1 |
None known |
linux-gcp-5.11Ubuntu:20.04:LTS |
All versions, plus listed versions 5.11.0-1009.10~20.04.15.11.0-1014.16~20.04.15.11.0-1017.19~20.04.15.11.0-1018.20~20.04.25.11.0-1020.22~20.04.1 Show 7 moreShow less5.11.0-1021.23~20.04.15.11.0-1022.24~20.04.15.11.0-1023.25~20.04.15.11.0-1024.26~20.04.15.11.0-1026.29~20.04.15.11.0-1028.32~20.04.15.11.0-1029.33~20.04.3 |
None known |
linux-gcp-5.13Ubuntu:20.04:LTS |
All versions, plus listed versions 5.13.0-1008.9~20.04.35.13.0-1012.15~20.04.15.13.0-1013.16~20.04.15.13.0-1015.18~20.04.15.13.0-1019.23~20.04.1 Show 8 moreShow less5.13.0-1021.25~20.04.15.13.0-1023.28~20.04.15.13.0-1024.29~20.04.15.13.0-1025.30~20.04.15.13.0-1027.32~20.04.15.13.0-1030.36~20.04.15.13.0-1031.37~20.04.15.13.0-1033.40~20.04.1 |
None known |
linux-gcp-5.15Ubuntu:Pro:20.04:LTS |
All versions, plus listed versions 5.15.0-1006.9~20.04.15.15.0-1012.17~20.04.15.15.0-1013.18~20.04.15.15.0-1016.21~20.04.15.15.0-1017.23~20.04.2 Show 45 moreShow less5.15.0-1018.24~20.04.15.15.0-1021.28~20.04.15.15.0-1022.29~20.04.15.15.0-1025.32~20.04.25.15.0-1026.33~20.04.15.15.0-1027.34~20.04.15.15.0-1029.36~20.04.15.15.0-1030.37~20.04.15.15.0-1031.38~20.04.15.15.0-1032.40~20.04.15.15.0-1033.41~20.04.15.15.0-1034.42~20.04.15.15.0-1035.43~20.04.15.15.0-1036.44~20.04.15.15.0-1037.45~20.04.15.15.0-1038.46~20.04.15.15.0-1039.47~20.04.15.15.0-1040.48~20.04.15.15.0-1041.49~20.04.15.15.0-1042.50~20.04.15.15.0-1044.52~20.04.15.15.0-1045.53~20.04.25.15.0-1046.54~20.04.15.15.0-1047.55~20.04.15.15.0-1048.56~20.04.15.15.0-1049.57~20.04.15.15.0-1051.59~20.04.15.15.0-1052.60~20.04.15.15.0-1053.61~20.04.15.15.0-1054.62~20.04.15.15.0-1055.63~20.04.15.15.0-1058.66~20.04.15.15.0-1059.67~20.04.15.15.0-1060.68~20.04.15.15.0-1062.70~20.04.15.15.0-1065.73~20.04.15.15.0-1066.74~20.04.15.15.0-1067.75~20.04.15.15.0-1068.76~20.04.15.15.0-1069.77~20.04.15.15.0-1070.78~20.04.15.15.0-1071.79~20.04.15.15.0-1072.80~20.04.15.15.0-1073.81~20.04.15.15.0-1074.83~20.04.1 |
None known |
linux-gcp-5.8Ubuntu:20.04:LTS |
All versions, plus listed versions 5.8.0-1032.34~20.04.15.8.0-1035.37~20.04.15.8.0-1038.40~20.04.15.8.0-1039.41 |
None known |
linux-gkeUbuntu:20.04:LTS |
All versions, plus listed versions 5.4.0-1033.355.4.0-1035.375.4.0-1036.385.4.0-1037.395.4.0-1039.41 Show 45 moreShow less5.4.0-1041.435.4.0-1042.445.4.0-1043.455.4.0-1044.465.4.0-1046.485.4.0-1049.525.4.0-1051.545.4.0-1052.555.4.0-1053.565.4.0-1054.575.4.0-1055.585.4.0-1056.595.4.0-1057.605.4.0-1059.625.4.0-1061.645.4.0-1062.655.4.0-1063.665.4.0-1065.685.4.0-1066.695.4.0-1067.705.4.0-1068.715.4.0-1071.765.4.0-1072.775.4.0-1074.795.4.0-1076.825.4.0-1078.845.4.0-1080.865.4.0-1081.875.4.0-1083.895.4.0-1084.905.4.0-1086.935.4.0-1087.945.4.0-1090.975.4.0-1091.985.4.0-1094.1015.4.0-1095.1025.4.0-1096.1035.4.0-1097.1045.4.0-1098.1055.4.0-1099.1065.4.0-1100.1075.4.0-1101.1085.4.0-1102.1095.4.0-1103.1105.4.0-1104.111 |
None known |
linux-gke-5.15Ubuntu:20.04:LTS |
All versions, plus listed versions 5.15.0-1011.14~20.04.15.15.0-1014.17~20.04.15.15.0-1015.18~20.04.15.15.0-1016.19~20.04.15.15.0-1019.23~20.04.1 Show 13 moreShow less5.15.0-1020.25~20.04.15.15.0-1023.28~20.04.25.15.0-1027.32~20.04.15.15.0-1028.33~20.04.15.15.0-1029.34~20.04.15.15.0-1031.36~20.04.15.15.0-1032.37~20.04.15.15.0-1033.38~20.04.15.15.0-1034.39~20.04.15.15.0-1036.41~20.04.15.15.0-1037.42~20.04.15.15.0-1038.43~20.04.15.15.0-1039.44~20.04.1 |
None known |
linux-gkeopUbuntu:20.04:LTS |
All versions, plus listed versions 5.4.0-1008.95.4.0-1009.105.4.0-1010.115.4.0-1011.125.4.0-1012.13 Show 45 moreShow less5.4.0-1013.145.4.0-1014.155.4.0-1015.165.4.0-1016.175.4.0-1018.195.4.0-1021.225.4.0-1022.235.4.0-1023.245.4.0-1024.255.4.0-1025.265.4.0-1026.275.4.0-1027.285.4.0-1029.305.4.0-1031.325.4.0-1032.335.4.0-1033.345.4.0-1034.355.4.0-1036.375.4.0-1037.385.4.0-1038.395.4.0-1039.405.4.0-1040.415.4.0-1043.445.4.0-1046.485.4.0-1048.515.4.0-1049.525.4.0-1051.545.4.0-1052.555.4.0-1053.565.4.0-1054.575.4.0-1056.605.4.0-1057.615.4.0-1060.645.4.0-1061.655.4.0-1062.665.4.0-1064.685.4.0-1065.695.4.0-1066.705.4.0-1067.715.4.0-1068.725.4.0-1069.735.4.0-1070.745.4.0-1071.755.4.0-1072.765.4.0-1073.77 |
None known |
linux-gkeop-5.15Ubuntu:20.04:LTS |
All versions, plus listed versions 5.15.0-1003.5~20.04.25.15.0-1005.7~20.04.15.15.0-1007.10~20.04.15.15.0-1008.12~20.04.15.15.0-1011.15~20.04.2 Show 40 moreShow less5.15.0-1012.16~20.04.15.15.0-1013.17~20.04.15.15.0-1015.19~20.04.15.15.0-1016.21~20.04.15.15.0-1017.22~20.04.15.15.0-1018.23~20.04.15.15.0-1019.24~20.04.15.15.0-1020.25~20.04.15.15.0-1021.26~20.04.15.15.0-1022.27~20.04.15.15.0-1023.28~20.04.15.15.0-1024.29~20.04.15.15.0-1025.30~20.04.15.15.0-1026.31~20.04.15.15.0-1027.32~20.04.15.15.0-1028.33~20.04.15.15.0-1030.35~20.04.15.15.0-1031.37~20.04.15.15.0-1032.38~20.04.15.15.0-1033.39~20.04.15.15.0-1034.40~20.04.15.15.0-1035.41~20.04.15.15.0-1036.42~20.04.15.15.0-1037.43~20.04.15.15.0-1038.44~20.04.15.15.0-1039.45~20.04.15.15.0-1040.46~20.04.15.15.0-1043.50~20.04.15.15.0-1044.51~20.04.15.15.0-1045.52~20.04.15.15.0-1046.53~20.04.15.15.0-1047.54~20.04.15.15.0-1048.55~20.04.15.15.0-1049.56~20.04.15.15.0-1050.57~20.04.15.15.0-1051.58~20.04.15.15.0-1052.59~20.04.15.15.0-1053.60~20.04.15.15.0-1054.61~20.04.15.15.0-1055.62~20.04.1 |
None known |
linux-hwe-5.11Ubuntu:20.04:LTS |
All versions, plus listed versions 5.11.0-22.23~20.04.15.11.0-25.27~20.04.15.11.0-27.29~20.04.15.11.0-34.36~20.04.15.11.0-36.40~20.04.1 Show 7 moreShow less5.11.0-37.41~20.04.25.11.0-38.42~20.04.15.11.0-40.44~20.04.25.11.0-41.45~20.04.15.11.0-43.47~20.04.25.11.0-44.48~20.04.25.11.0-46.51~20.04.1 |
None known |
linux-hwe-5.13Ubuntu:20.04:LTS |
All versions, plus listed versions 5.13.0-21.21~20.04.15.13.0-22.22~20.04.15.13.0-23.23~20.04.25.13.0-25.26~20.04.15.13.0-27.29~20.04.1 Show 11 moreShow less5.13.0-28.31~20.04.15.13.0-30.33~20.04.15.13.0-35.40~20.04.15.13.0-37.42~20.04.15.13.0-39.44~20.04.15.13.0-40.45~20.04.15.13.0-41.46~20.04.15.13.0-44.49~20.04.15.13.0-48.54~20.04.15.13.0-51.58~20.04.15.13.0-52.59~20.04.1 |
None known |
linux-hwe-5.15Ubuntu:Pro:20.04:LTS |
All versions, plus listed versions 5.15.0-33.34~20.04.15.15.0-41.44~20.04.15.15.0-43.46~20.04.15.15.0-46.49~20.04.15.15.0-48.54~20.04.1 Show 45 moreShow less5.15.0-50.56~20.04.15.15.0-52.58~20.04.15.15.0-53.59~20.04.15.15.0-56.62~20.04.15.15.0-57.63~20.04.15.15.0-58.64~20.04.15.15.0-60.66~20.04.15.15.0-67.74~20.04.15.15.0-69.76~20.04.15.15.0-70.77~20.04.15.15.0-71.78~20.04.15.15.0-72.79~20.04.15.15.0-73.80~20.04.15.15.0-75.82~20.04.15.15.0-76.83~20.04.15.15.0-78.85~20.04.15.15.0-79.86~20.04.25.15.0-82.91~20.04.15.15.0-83.92~20.04.15.15.0-84.93~20.04.15.15.0-86.96~20.04.15.15.0-87.97~20.04.15.15.0-88.98~20.04.15.15.0-89.99~20.04.15.15.0-91.101~20.04.15.15.0-92.102~20.04.15.15.0-94.104~20.04.15.15.0-97.107~20.04.15.15.0-100.110~20.04.15.15.0-101.111~20.04.15.15.0-102.112~20.04.15.15.0-105.115~20.04.15.15.0-106.116~20.04.15.15.0-107.117~20.04.15.15.0-113.123~20.04.15.15.0-116.126~20.04.15.15.0-117.127~20.04.15.15.0-118.128~20.04.15.15.0-119.129~20.04.15.15.0-121.131~20.04.15.15.0-122.132~20.04.15.15.0-124.134~20.04.15.15.0-125.135~20.04.15.15.0-126.136~20.04.15.15.0-127.137~20.04.1 |
None known |
linux-hwe-5.8Ubuntu:20.04:LTS |
All versions, plus listed versions 5.8.0-23.24~20.04.15.8.0-25.26~20.04.15.8.0-28.30~20.04.15.8.0-29.31~20.04.15.8.0-31.33~20.04.1 Show 16 moreShow less5.8.0-33.36~20.04.15.8.0-34.37~20.04.25.8.0-36.40~20.04.15.8.0-38.43~20.04.15.8.0-40.45~20.04.15.8.0-41.46~20.04.15.8.0-43.49~20.04.15.8.0-44.50~20.04.15.8.0-45.51~20.04.15.8.0-48.54~20.04.15.8.0-49.55~20.04.15.8.0-50.56~20.04.15.8.0-53.60~20.04.15.8.0-55.62~20.04.15.8.0-59.66~20.04.15.8.0-63.71~20.04.1 |
None known |
linux-ibm-5.15Ubuntu:Pro:20.04:LTS |
All versions, plus listed versions 5.15.0-1033.36~20.04.15.15.0-1034.37~20.04.15.15.0-1035.38~20.04.15.15.0-1036.39~20.04.15.15.0-1037.40~20.04.1 Show 45 moreShow less5.15.0-1038.41~20.04.15.15.0-1040.43~20.04.15.15.0-1041.44~20.04.15.15.0-1042.45~20.04.15.15.0-1043.46~20.04.15.15.0-1044.47~20.04.15.15.0-1045.48~20.04.15.15.0-1046.49~20.04.15.15.0-1047.50~20.04.15.15.0-1048.51~20.04.15.15.0-1049.52~20.04.15.15.0-1050.53~20.04.15.15.0-1053.56~20.04.15.15.0-1054.57~20.04.15.15.0-1055.58~20.04.15.15.0-1057.60~20.04.15.15.0-1058.61~20.04.15.15.0-1059.62~20.04.15.15.0-1060.63~20.04.15.15.0-1061.64~20.04.15.15.0-1062.65~20.04.15.15.0-1063.66~20.04.15.15.0-1064.67~20.04.15.15.0-1065.68~20.04.15.15.0-1066.69~20.04.15.15.0-1067.70~20.04.15.15.0-1068.71~20.04.15.15.0-1069.72~20.04.15.15.0-1074.77~20.04.15.15.0-1075.78~20.04.15.15.0-1076.79~20.04.15.15.0-1078.81~20.04.15.15.0-1079.82~20.04.15.15.0-1080.83~20.04.15.15.0-1081.84~20.04.15.15.0-1083.86~20.04.15.15.0-1085.88~20.04.15.15.0-1086.89~20.04.15.15.0-1087.90~20.04.15.15.0-1089.92~20.04.15.15.0-1090.93~20.04.15.15.0-1091.94~20.04.15.15.0-1092.95~20.04.15.15.0-1093.96~20.04.15.15.0-1094.97~20.04.1 |
None known |
linux-intel-5.13Ubuntu:20.04:LTS |
All versions, plus listed versions 5.13.0-1007.75.13.0-1008.85.13.0-1009.95.13.0-1010.105.13.0-1011.115.13.0-1014.155.13.0-1017.19 |
None known |
linux-intel-iotg-5.15Ubuntu:Pro:20.04:LTS |
All versions, plus listed versions 5.15.0-1003.5~20.04.15.15.0-1008.11~20.04.15.15.0-1010.14~20.04.15.15.0-1015.20~20.04.25.15.0-1016.21~20.04.1 Show 45 moreShow less5.15.0-1017.22~20.04.15.15.0-1018.23~20.04.15.15.0-1021.26~20.04.15.15.0-1023.28~20.04.15.15.0-1025.30~20.04.15.15.0-1026.31~20.04.15.15.0-1027.32~20.04.15.15.0-1030.35~20.04.15.15.0-1031.36~20.04.15.15.0-1033.38~20.04.15.15.0-1034.39~20.04.15.15.0-1036.41~20.04.15.15.0-1037.42~20.04.15.15.0-1038.43~20.04.15.15.0-1040.46~20.04.15.15.0-1043.49~20.04.15.15.0-1045.51~20.04.15.15.0-1046.52~20.04.15.15.0-1048.54~20.04.15.15.0-1049.55~20.04.15.15.0-1050.56~20.04.15.15.0-1051.57~20.04.15.15.0-1052.58~20.04.15.15.0-1055.61~20.04.15.15.0-1058.64~20.04.15.15.0-1059.65~20.04.15.15.0-1060.66~20.04.15.15.0-1061.67~20.04.15.15.0-1062.68~20.04.15.15.0-1063.69~20.04.15.15.0-1064.70~20.04.15.15.0-1065.71~20.04.15.15.0-1066.72~20.04.15.15.0-1067.73~20.04.15.15.0-1071.77~20.04.15.15.0-1072.78~20.04.15.15.0-1073.79~20.04.25.15.0-1074.80~20.04.15.15.0-1077.83~20.04.15.15.0-1078.84~20.04.15.15.0-1079.85~20.04.15.15.0-1083.89~20.04.15.15.0-1084.90~20.04.15.15.0-1085.91~20.04.15.15.0-1086.92~20.04.1 |
None known |
linux-lowlatency-hwe-5.15Ubuntu:Pro:20.04:LTS |
All versions, plus listed versions 5.15.0-33.34~20.04.15.15.0-42.45~20.04.15.15.0-43.46~20.04.15.15.0-46.49~20.04.15.15.0-48.54~20.04.1 Show 45 moreShow less5.15.0-50.56~20.04.15.15.0-52.58~20.04.15.15.0-53.59~20.04.15.15.0-56.62~20.04.15.15.0-58.64~20.04.15.15.0-60.66~20.04.15.15.0-67.74~20.04.15.15.0-69.76~20.04.15.15.0-70.77~20.04.15.15.0-71.78~20.04.15.15.0-72.79~20.04.15.15.0-73.80~20.04.15.15.0-75.82~20.04.15.15.0-76.83~20.04.15.15.0-78.85~20.04.15.15.0-79.88~20.04.15.15.0-82.91~20.04.15.15.0-83.92~20.04.15.15.0-84.93~20.04.15.15.0-86.95~20.04.15.15.0-87.96~20.04.15.15.0-88.98~20.04.15.15.0-89.99~20.04.15.15.0-91.101~20.04.15.15.0-92.102~20.04.15.15.0-94.104~20.04.15.15.0-97.107~20.04.15.15.0-100.110~20.04.15.15.0-101.111~20.04.15.15.0-102.112~20.04.15.15.0-105.115~20.04.15.15.0-106.116~20.04.15.15.0-107.117~20.04.15.15.0-110.120~20.04.15.15.0-113.123~20.04.15.15.0-116.126~20.04.15.15.0-117.127~20.04.15.15.0-118.128~20.04.15.15.0-119.129~20.04.15.15.0-121.131~20.04.15.15.0-122.132~20.04.15.15.0-124.134~20.04.15.15.0-125.135~20.04.15.15.0-126.136~20.04.15.15.0-127.137~20.04.1 |
None known |
linux-nvidia-tegra-5.15Ubuntu:Pro:20.04:LTS |
All versions, plus listed versions 5.15.0-1009.9~20.04.15.15.0-1010.10~20.04.15.15.0-1012.12~20.04.15.15.0-1014.14~20.04.15.15.0-1015.15~20.04.1 Show 37 moreShow less5.15.0-1016.16~20.04.15.15.0-1017.17~20.04.15.15.0-1018.18~20.04.15.15.0-1019.19~20.04.15.15.0-1020.20~20.04.15.15.0-1022.22~20.04.15.15.0-1025.25~20.04.15.15.0-1027.27~20.04.15.15.0-1030.30~20.04.15.15.0-1032.32~20.04.15.15.0-1039.39~20.04.15.15.0-1040.40~20.04.15.15.0-1041.41~20.04.15.15.0-1042.42~20.04.15.15.0-1043.43~20.04.15.15.0-1044.44~20.04.15.15.0-1045.45~20.04.15.15.0-1046.46~20.04.15.15.0-1047.47~20.04.15.15.0-1048.48~20.04.15.15.0-1049.49~20.04.15.15.0-1050.50~20.04.15.15.0-1051.51~20.04.15.15.0-1052.52~20.04.25.15.0-1053.53~20.04.15.15.0-1055.55~20.04.15.15.0-1057.57~20.04.15.15.0-1058.58~20.04.15.15.0-1060.60~20.04.15.15.0-1061.61~20.04.15.15.0-1063.63~20.04.15.15.0-1064.66~20.04.15.15.0-1065.67~20.04.15.15.0-1066.68~20.04.15.15.0-1067.69~20.04.15.15.0-1068.70~20.04.15.15.0-1070.72~20.04.1 |
None known |
linux-oem-5.10Ubuntu:20.04:LTS |
All versions, plus listed versions 5.10.0-1008.95.10.0-1011.125.10.0-1013.145.10.0-1014.155.10.0-1016.17 Show 21 moreShow less5.10.0-1017.185.10.0-1019.205.10.0-1021.225.10.0-1022.235.10.0-1023.245.10.0-1025.265.10.0-1026.275.10.0-1029.305.10.0-1032.335.10.0-1033.345.10.0-1034.355.10.0-1038.405.10.0-1044.465.10.0-1045.475.10.0-1049.515.10.0-1050.525.10.0-1051.535.10.0-1052.545.10.0-1053.555.10.0-1055.585.10.0-1057.61 |
None known |
linux-oem-5.13Ubuntu:20.04:LTS |
All versions, plus listed versions 5.13.0-1009.105.13.0-1010.115.13.0-1012.165.13.0-1014.185.13.0-1017.21 Show 7 moreShow less5.13.0-1019.235.13.0-1020.245.13.0-1021.255.13.0-1022.265.13.0-1026.325.13.0-1028.355.13.0-1029.36 |
None known |
linux-oem-5.14Ubuntu:20.04:LTS |
All versions, plus listed versions 5.14.0-1004.45.14.0-1005.55.14.0-1007.75.14.0-1008.85.14.0-1010.10 Show 30 moreShow less5.14.0-1011.115.14.0-1013.135.14.0-1018.195.14.0-1020.225.14.0-1022.245.14.0-1024.265.14.0-1027.305.14.0-1029.325.14.0-1031.345.14.0-1032.355.14.0-1033.365.14.0-1034.375.14.0-1036.405.14.0-1038.425.14.0-1042.475.14.0-1044.495.14.0-1045.515.14.0-1046.535.14.0-1047.545.14.0-1048.555.14.0-1049.565.14.0-1050.575.14.0-1051.585.14.0-1052.595.14.0-1054.615.14.0-1055.625.14.0-1056.635.14.0-1057.645.14.0-1058.665.14.0-1059.67 |
None known |
linux-oem-5.6Ubuntu:20.04:LTS |
All versions, plus listed versions 5.6.0-1007.75.6.0-1008.85.6.0-1010.105.6.0-1011.115.6.0-1013.13 Show 24 moreShow less5.6.0-1017.175.6.0-1018.185.6.0-1020.205.6.0-1021.215.6.0-1023.235.6.0-1026.265.6.0-1027.275.6.0-1028.285.6.0-1031.325.6.0-1032.335.6.0-1033.355.6.0-1034.365.6.0-1035.375.6.0-1036.395.6.0-1039.435.6.0-1042.465.6.0-1047.515.6.0-1048.525.6.0-1050.545.6.0-1052.565.6.0-1053.575.6.0-1054.585.6.0-1055.595.6.0-1056.60 |
None known |
linux-oracle-5.11Ubuntu:20.04:LTS |
All versions, plus listed versions 5.11.0-1008.8~20.04.15.11.0-1013.14~20.04.15.11.0-1016.17~20.04.15.11.0-1017.18~20.04.15.11.0-1019.20~20.04.1 Show 7 moreShow less5.11.0-1020.21~20.04.15.11.0-1021.22~20.04.15.11.0-1022.23~20.04.15.11.0-1023.24~20.04.15.11.0-1025.27~20.04.15.11.0-1027.30~20.04.15.11.0-1028.31~20.04.1 |
None known |
linux-oracle-5.13Ubuntu:20.04:LTS |
All versions, plus listed versions 5.13.0-1011.13~20.04.25.13.0-1015.19~20.04.15.13.0-1016.20~20.04.15.13.0-1018.22~20.04.15.13.0-1021.26~20.04.1 Show 7 moreShow less5.13.0-1025.30~20.04.15.13.0-1027.32~20.04.15.13.0-1028.33~20.04.15.13.0-1030.35~20.04.15.13.0-1033.39~20.04.15.13.0-1034.40~20.04.15.13.0-1036.43~20.04.1 |
None known |
linux-oracle-5.15Ubuntu:Pro:20.04:LTS |
All versions, plus listed versions 5.15.0-1007.9~20.04.15.15.0-1013.17~20.04.15.15.0-1016.20~20.04.15.15.0-1017.22~20.04.15.15.0-1018.23~20.04.1 Show 45 moreShow less5.15.0-1019.24~20.04.15.15.0-1021.27~20.04.15.15.0-1022.28~20.04.15.15.0-1025.31~20.04.25.15.0-1027.33~20.04.15.15.0-1029.35~20.04.15.15.0-1030.36~20.04.15.15.0-1032.38~20.04.15.15.0-1033.39~20.04.15.15.0-1034.40~20.04.15.15.0-1035.41~20.04.15.15.0-1036.42~20.04.15.15.0-1037.43~20.04.15.15.0-1038.44~20.04.15.15.0-1039.45~20.04.15.15.0-1040.46~20.04.15.15.0-1041.47~20.04.15.15.0-1042.48~20.04.15.15.0-1044.50~20.04.15.15.0-1045.51~20.04.15.15.0-1046.52~20.04.15.15.0-1047.53~20.04.15.15.0-1048.54~20.04.15.15.0-1049.55~20.04.15.15.0-1050.56~20.04.15.15.0-1051.57~20.04.15.15.0-1052.58~20.04.15.15.0-1053.59~20.04.15.15.0-1054.60~20.04.15.15.0-1055.61~20.04.15.15.0-1058.64~20.04.15.15.0-1059.65~20.04.15.15.0-1061.67~20.04.15.15.0-1062.68~20.04.15.15.0-1063.69~20.04.15.15.0-1065.71~20.04.15.15.0-1066.72~20.04.15.15.0-1067.73~20.04.15.15.0-1068.74~20.04.15.15.0-1069.75~20.04.15.15.0-1070.76~20.04.15.15.0-1071.77~20.04.15.15.0-1072.78~20.04.15.15.0-1073.79~20.04.15.15.0-1074.80~20.04.1 |
None known |
linux-oracle-5.8Ubuntu:20.04:LTS |
All versions, plus listed versions 5.8.0-1031.32~20.04.25.8.0-1033.34~20.04.15.8.0-1034.35~20.04.25.8.0-1037.38~20.04.15.8.0-1038.39~20.04.1 |
None known |
History
| Recorded | Changed | Sources |
|---|---|---|
| affected | OSV | |
| affected | OSV | |
| affected | OSV | |
| affected | OSV | |
| affected | OSV | |
| facts | OSV | |
| first indexed | CVE List, EUVD, GitHub Advisories, NVD, OSV |
Dates are when Every CVE recorded each change. Upstream dates may differ.
In short
CVE-2025-21693 is a high vulnerability (CVSS 7.8) in Linux, published February 10, 2025. No source lists public exploit code. EPSS puts the chance of exploitation in the next 30 days at 0.20%, the 10th percentile. Fixed in linux-lts 6.12.41-r0.
References
git.kernel.org/stable/c/8d29ff5d50304daa41dc3cfdda4a9d1e46cf5be1
git.kernel.org/stable/c/12dcb0ef540629a281533f9dedc1b6b8e14cfb65
nvd.nist.gov/vuln/detail/CVE-2025-21693
github.com/advisories/GHSA-jqr2-rwpf-xrf3
access.redhat.com/errata/RHSA-2025:20095
access.redhat.com/security/cve/CVE-2024-28956
Show 194 moreShow less
access.redhat.com/security/cve/CVE-2024-36350
access.redhat.com/security/cve/CVE-2024-36357
access.redhat.com/security/cve/CVE-2024-49570
access.redhat.com/security/cve/CVE-2024-52332
access.redhat.com/security/cve/CVE-2024-53147
access.redhat.com/security/cve/CVE-2024-53216
access.redhat.com/security/cve/CVE-2024-53222
access.redhat.com/security/cve/CVE-2024-53241
access.redhat.com/security/cve/CVE-2024-54456
access.redhat.com/security/cve/CVE-2024-56662
access.redhat.com/security/cve/CVE-2024-56675
access.redhat.com/security/cve/CVE-2024-56690
access.redhat.com/security/cve/CVE-2024-57901
access.redhat.com/security/cve/CVE-2024-57902
access.redhat.com/security/cve/CVE-2024-57941
bugzilla.redhat.com/2331326
bugzilla.redhat.com/2333985
bugzilla.redhat.com/2334373
bugzilla.redhat.com/2334415
bugzilla.redhat.com/2334547
bugzilla.redhat.com/2334548
bugzilla.redhat.com/2334676
bugzilla.redhat.com/2337121
bugzilla.redhat.com/2338185
bugzilla.redhat.com/2338211
bugzilla.redhat.com/2338813
bugzilla.redhat.com/2338821
bugzilla.redhat.com/2338828
bugzilla.redhat.com/2338998
bugzilla.redhat.com/2339130
bugzilla.redhat.com/2339141
bugzilla.redhat.com/2343172
errata.almalinux.org/10/ALSA-2025-20095.html
errata.almalinux.org/9/ALSA-2025-20518.html
redhat.com/security/data/cve/CVE-2022-48830.html
redhat.com/security/data/cve/CVE-2022-49024.html
redhat.com/security/data/cve/CVE-2022-49269.html
redhat.com/security/data/cve/CVE-2022-49353.html
redhat.com/security/data/cve/CVE-2022-49357.html
redhat.com/security/data/cve/CVE-2022-49432.html
redhat.com/security/data/cve/CVE-2022-49437.html
redhat.com/security/data/cve/CVE-2022-49443.html
redhat.com/security/data/cve/CVE-2022-49623.html
redhat.com/security/data/cve/CVE-2022-49627.html
redhat.com/security/data/cve/CVE-2022-49643.html
redhat.com/security/data/cve/CVE-2022-49648.html
redhat.com/security/data/cve/CVE-2022-49657.html
redhat.com/security/data/cve/CVE-2022-49670.html
redhat.com/security/data/cve/CVE-2022-49672.html
redhat.com/security/data/cve/CVE-2022-49845.html
redhat.com/security/data/cve/CVE-2024-36350.html
docs.bell-sw.com/security/cves/CVE-2025-21693
errata.tuxcare.com/els_os/tuxcare9.6esu/CLSA-2026-1779434490.html
github.com/CVEProject/cvelistV5/tree/main/cves/2025/21xxx/CVE-2025-21693.json
git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
security-tracker.debian.org/tracker/CVE-2025-21693
openeuler.org/zh/security/security-bulletins/detail?id=openEuler-SA-2025-2772
nvd.nist.gov/vuln/detail/CVE-2021-47653
nvd.nist.gov/vuln/detail/CVE-2022-49267
nvd.nist.gov/vuln/detail/CVE-2022-49470
nvd.nist.gov/vuln/detail/CVE-2023-53305
nvd.nist.gov/vuln/detail/CVE-2023-53365
nvd.nist.gov/vuln/detail/CVE-2023-53510
nvd.nist.gov/vuln/detail/CVE-2024-58007
nvd.nist.gov/vuln/detail/CVE-2024-58095
nvd.nist.gov/vuln/detail/CVE-2025-21945
nvd.nist.gov/vuln/detail/CVE-2025-37786
nvd.nist.gov/vuln/detail/CVE-2025-37899
nvd.nist.gov/vuln/detail/CVE-2025-37994
nvd.nist.gov/vuln/detail/CVE-2025-37997
nvd.nist.gov/vuln/detail/CVE-2025-38084
nvd.nist.gov/vuln/detail/CVE-2025-38477
nvd.nist.gov/vuln/detail/CVE-2025-39817
openeuler.org/zh/security/security-bulletins/detail?id=openEuler-SA-2025-2773
openeuler.org/zh/security/security-bulletins/detail?id=openEuler-SA-2025-2774
openeuler.org/zh/security/security-bulletins/detail?id=openEuler-SA-2025-2775
openeuler.org/zh/security/security-bulletins/detail?id=openEuler-SA-2025-2776
docs.redhat.com/en/documentation/red_hat_enterprise_linux/10/html/10.1_release_notes/index
issues.redhat.com/browse/RHEL-101826
issues.redhat.com/browse/RHEL-104231
issues.redhat.com/browse/RHEL-58218
issues.redhat.com/browse/RHEL-79278
issues.redhat.com/browse/RHEL-79711
issues.redhat.com/browse/RHEL-83595
issues.redhat.com/browse/RHEL-92226
issues.redhat.com/browse/RHEL-95446
security.access.redhat.com/data/csaf/v2/advisories/2025/rhsa-2025_20095.json
cve.org/CVERecord?id=CVE-2024-28956
intel.com/content/www/us/en/security-center/advisory/intel-sa-01153.html
vusec.net/projects/training-solo
cve.org/CVERecord?id=CVE-2024-36350
amd.com/en/resources/product-security/bulletin/amd-sb-7029.html
cve.org/CVERecord?id=CVE-2024-36357
cve.org/CVERecord?id=CVE-2024-49570
lore.kernel.org/linux-cve-announce/2025022601-CVE-2024-49570-d2e7@gregkh/T
cve.org/CVERecord?id=CVE-2024-52332
lore.kernel.org/linux-cve-announce/2025011122-CVE-2024-52332-9d2f@gregkh/T
cve.org/CVERecord?id=CVE-2024-53147
lore.kernel.org/linux-cve-announce/2024122426-CVE-2024-53147-bea5@gregkh/T
cve.org/CVERecord?id=CVE-2024-53216
git.kernel.org/pub/scm/linux/security/vulns.git/plain/cve/published/2024/CVE-2024-53216.mbox
cve.org/CVERecord?id=CVE-2024-53222
lore.kernel.org/linux-cve-announce/2024122734-CVE-2024-53222-6c79@gregkh/T
cve.org/CVERecord?id=CVE-2024-53241
cve.org/CVERecord?id=CVE-2024-54456
lore.kernel.org/linux-cve-announce/2025022602-CVE-2024-54456-e8a9@gregkh/T
cve.org/CVERecord?id=CVE-2024-56662
lore.kernel.org/linux-cve-announce/2024122752-CVE-2024-56662-b7e7@gregkh/T
cve.org/CVERecord?id=CVE-2024-56675
lore.kernel.org/linux-cve-announce/2024122756-CVE-2024-56675-e996@gregkh/T
cve.org/CVERecord?id=CVE-2024-56690
lore.kernel.org/linux-cve-announce/2024122834-CVE-2024-56690-b77f@gregkh/T
cve.org/CVERecord?id=CVE-2024-57901
lore.kernel.org/linux-cve-announce/2025011516-CVE-2024-57901-1f9e@gregkh/T
cve.org/CVERecord?id=CVE-2024-57902
lore.kernel.org/linux-cve-announce/2025011516-CVE-2024-57902-7ddb@gregkh/T
cve.org/CVERecord?id=CVE-2024-57941
lore.kernel.org/linux-cve-announce/2025012128-CVE-2024-57941-8779@gregkh/T
cve.org/CVERecord?id=CVE-2024-57942
lore.kernel.org/linux-cve-announce/2025012129-CVE-2024-57942-bedc@gregkh/T
lore.kernel.org/linux-cve-announce/2025022633-CVE-2024-57977-88ac@gregkh/T
lore.kernel.org/linux-cve-announce/2025022635-CVE-2024-57981-bba6@gregkh/T
lore.kernel.org/linux-cve-announce/2025022635-CVE-2024-57982-c76a@gregkh/T
lore.kernel.org/linux-cve-announce/2025022636-CVE-2024-57984-191f@gregkh/T
lore.kernel.org/linux-cve-announce/2025022636-CVE-2024-57986-6166@gregkh/T
git.kernel.org/stable/c/6b63308c28987c6010b1180c72a6db4df6c68033
git.kernel.org/stable/c/8efff2aa2d95dc437ab67c5b4a9f1d3f367baa10
git.kernel.org/stable/c/a7085c3ae43b86d4b3d1b8275e6a67f14257e3b7
git.kernel.org/stable/c/c9a40292a44e78f71258b8522655bffaf5753bdb
docs.redhat.com/en/documentation/red_hat_enterprise_linux/9/html/9.7_release_notes/index
issues.redhat.com/browse/RHEL-331
issues.redhat.com/browse/RHEL-52839
issues.redhat.com/browse/RHEL-68997
issues.redhat.com/browse/RHEL-73706
issues.redhat.com/browse/RHEL-81900
issues.redhat.com/browse/RHEL-86487
issues.redhat.com/browse/RHEL-90133
issues.redhat.com/browse/RHEL-94578
security.access.redhat.com/data/csaf/v2/advisories/2025/rhsa-2025_20518.json
git.kernel.org/pub/scm/linux/security/vulns.git/tree/cve/published/2024/CVE-2024-50195.mbox
errata.rockylinux.org/RLSA-2025:20095
errata.rockylinux.org/RLSA-2025:20518
suse.com/support/update/announcement/2025/suse-su-202501919-1
bugzilla.suse.com/1207948
bugzilla.suse.com/1215199
bugzilla.suse.com/1215211
bugzilla.suse.com/1218470
bugzilla.suse.com/1221651
bugzilla.suse.com/1222649
bugzilla.suse.com/1223047
bugzilla.suse.com/1223096
bugzilla.suse.com/1223809
bugzilla.suse.com/1224013
bugzilla.suse.com/1224489
bugzilla.suse.com/1224597
bugzilla.suse.com/1224610
bugzilla.suse.com/1224757
bugzilla.suse.com/1225533
bugzilla.suse.com/1225606
bugzilla.suse.com/1225742
suse.com/security/cve/CVE-2023-52831
suse.com/security/cve/CVE-2023-52926
suse.com/security/cve/CVE-2023-52927
suse.com/security/cve/CVE-2023-53034
suse.com/security/cve/CVE-2024-26634
suse.com/security/cve/CVE-2024-26873
suse.com/security/cve/CVE-2024-27018
suse.com/security/cve/CVE-2024-27415
suse.com/security/cve/CVE-2024-28956
suse.com/security/cve/CVE-2024-35826
suse.com/security/cve/CVE-2024-35840
suse.com/security/cve/CVE-2024-35910
suse.com/security/cve/CVE-2024-38606
suse.com/security/cve/CVE-2024-41005
suse.com/security/cve/CVE-2024-41077
suse.com/security/cve/CVE-2024-41149
ubuntu.com/security/CVE-2025-21693
git.kernel.org/linus/12dcb0ef540629a281533f9dedc1b6b8e14cfb65
ubuntu.com/security/notices/USN-7445-1
ubuntu.com/security/notices/USN-7448-1
ubuntu.com/security/notices/USN-8781-1
ubuntu.com/security/CVE-2024-57948
ubuntu.com/security/CVE-2024-57949
ubuntu.com/security/CVE-2024-57950
ubuntu.com/security/CVE-2024-57951
ubuntu.com/security/CVE-2024-57952
ubuntu.com/security/CVE-2025-21665
ubuntu.com/security/CVE-2025-21666
ubuntu.com/security/CVE-2025-21667
ubuntu.com/security/CVE-2025-21668
ubuntu.com/security/CVE-2025-21669
ubuntu.com/security/CVE-2025-21670
ubuntu.com/security/CVE-2025-21672
ubuntu.com/security/CVE-2025-21673
Left out here: 491 package rows, 582 versions, 4,225 references and the rest of 20 source descriptions. The JSON record has them.