Every CVESearch/Get API key

CVE-2025-39791

dm: dm-crypt: Do not partially accept write BIOs with zoned targets

7.8 HighFix available

In the Linux kernel, the following vulnerability has been resolved:

dm: dm-crypt: Do not partially accept write BIOs with zoned targets

Read and write operations issued to a dm-crypt target may be split according to the dm-crypt internal limits defined by the max_read_size and max_write_size module parameters (default is 128 KB). The intent is to improve processing time of large BIOs by splitting them into smaller operations that can be parallelized on different CPUs.

For zoned dm-crypt targets, this BIO splitting is still done but without the parallel execution to ensure that the issuing order of write operations to the underlying devices remains sequential. However, the splitting itself causes other problems:

  1. Since dm-crypt relies on the block layer zone write plugging to handle zone append emulation using regular write operations, the reminder of a split write BIO will always be plugged into the target zone write plugged. Once the on-going write BIO finishes, this reminder BIO is unplugged and issued from the zone write plug work. If this reminder BIO itself needs to be split, the reminder will be re-issued and plugged again, but that causes a call to a blk_queue_enter(), which may block if a queue freeze operation was initiated. This results in a deadlock as DM submission still holds BIOs that the queue freeze side is waiting for.

  2. dm-crypt relies on the emulation done by the block layer using regular write operations for processing zone append operations. This still requires to properly return the written sector as the BIO sector of the original BIO. However, this can be done correctly only and only if there is a single clone BIO used for processing the original zone append operation issued by the user. If the size of a zone append operation is larger than dm-crypt max_write_size, then the orginal BIO will be split and processed as a chain of regular write operations. Such chaining result in an incorrect written sector being returned to the zone append issuer using the original BIO sector. This in turn results in file system data corruptions using xfs or btrfs.

Fix this by modifying get_max_request_size() to always return the size of the BIO to avoid it being split with dm_accpet_partial_bio() in crypt_map(). get_max_request_size() is renamed to get_max_request_sectors() to clarify the unit of the value returned and its interface is changed to take a struct dm_target pointer and a pointer to the struct bio being processed. In addition to this change, to ensure that crypt_alloc_buffer() works correctly, set the dm-crypt device max_hw_sectors limit to be at most BIO_MAX_VECS << PAGE_SECTORS_SHIFT (1 MB with a 4KB page architecture). This forces DM core to split write BIOs before passing them to crypt_map(), and thus guaranteeing that dm-crypt can always accept an entire write BIO without needing to split it.

This change does not have any effect on the read path of dm-crypt. Read operations can still be split and the BIO fragments processed in parallel. There is also no impact on the performance of the write path given that all zone write BIOs were already processed inline instead of in parallel.

This change also does not affect in any way regular dm-crypt block devices.

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

0.14%Up 0.1 points since Sep 12, 2025
90%50%10%1%

What each source reports

CVE List Score used7.8

dm: dm-crypt: Do not partially accept write BIOs with zoned targets

In the Linux kernel, the following vulnerability has been resolved:

dm: dm-crypt: Do not partially accept write BIOs with zoned targets

Read and write operations issued to a dm-crypt target may be split according to the dm-crypt internal limits defined by the max_read_size and max_write_size module parameters (default is 128 KB). The intent is to improve processing time of large BIOs by splitting them into smaller operations that can be parallelized on different CPUs.

For zoned dm-crypt targets, this BIO splitting is still done but without the parallel execution to ensure that the issuing order of write operations to the underlying devices remains sequential. However, the splitting itself causes other problems:

  1. Since dm-crypt relies on the block layer zone write plugging to handle zone append emulation using regular write operations, the reminder of a split write BIO will always be plugged into the target zone write plugged. Once the on-going write BIO finishes, this reminder BIO is unplugged and issued from the zone write plug work. If this reminder BIO itself needs to be split, the reminder will be re-issued and plugged again, but that causes a call to a blk_queue_enter(), which may block if a queue freeze operation was initiated. This results in a deadlock as DM submission still holds BIOs that the queue freeze side is waiting for.

  2. dm-crypt relies on the emulation done by the block layer using regular write operations for processing zone append operations. This still requires to properly return the written sector as the BIO sector of the original BIO. However, this can be done correctly only and only if there is a single clone BIO used for processing the original zone append operation issued by the user. If the size of a zone append operation is larger than dm-crypt max_write_size, then the orginal BIO will be split and processed as a chain of regular write operations. Such chaining result in an incorrect written sector being returned to the zone append issuer using the original BIO sector. This in turn results in file system data corruptions using xfs or btrfs.

Fix this by modifying get_max_request_size() to always return the size of the BIO to avoid it being split with dm_accpet_partial_bio() in crypt_map(). get_max_request_size() is renamed to get_max_request_sectors() to clarify the unit of the value returned and its interface is changed to take a struct dm_target pointer and a pointer to the struct bio being processed. In addition to this change, to ensure that crypt_alloc_buffer() works correctly, set the dm-crypt device max_hw_sectors limit to be at most BIO_MAX_VECS << PAGE_SECTORS_SHIFT (1 MB with a 4KB page architecture). This forces DM core to split write BIOs before passing them to crypt_map(), and thus guaranteeing that dm-crypt can always accept an entire write BIO without needing to split it.

This change does not have any effect on the read path of dm-crypt. Read operations can still be split and the BIO fragments processed in parallel. There is also no impact on the performance of the write path given that all zone write BIOs were already processed inline instead of in parallel.

This change also does not affect in any way regular dm-crypt block devices.

Record
CVE-2025-39791
CVSS 3.1
7.8 HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Updated
2026-11-02
EUVDEUVD-2025-289227.8

In the Linux kernel, the following vulnerability has been resolved:

dm: dm-crypt: Do not partially accept write BIOs with zoned targets

Read and write operations issued to a dm-crypt target may be split according to the dm-crypt internal limits defined by the max_read_size and max_write_size module parameters (default is 128 KB). The intent is to improve processing time of large BIOs by splitting them into smaller operations that can be parallelized on different CPUs.

For zoned dm-crypt targets, this BIO splitting is still done but without the parallel execution to ensure that the issuing order of write operations to the underlying devices remains sequential. However, the splitting itself causes other problems:

  1. Since dm-crypt relies on the block layer zone write plugging to handle zone append emulation using regular write operations, the reminder of a split write BIO will always be plugged into the target zone write plugged. Once the on-going write BIO finishes, this reminder BIO is unplugged and issued from the zone write plug work. If this reminder BIO itself needs to be split, the reminder will be re-issued and plugged again, but that causes a call to a blk_queue_enter(), which may block if a queue freeze operation was initiated. This results in a deadlock as DM submission still holds BIOs that the queue freeze side is waiting for.

  2. dm-crypt relies on the emulation done by the block layer using regular write operations for processing zone append operations. This still requires to properly return the written sector as the BIO sector of the original BIO. However, this can be done correctly only and only if there is a single clone BIO used for processing the original zone append operation issued by the user. If the size of a zone append operation is larger than dm-crypt max_write_size, then the orginal BIO will be split and processed as a chain of regular write operations. Such chaining result in an incorrect written sector being returned to the zone append issuer using the original BIO sector. This in turn results in file system data corruptions using xfs or btrfs.

Fix this by modifying get_max_request_size() to always return the size of the BIO to avoid it being split with dm_accpet_partial_bio() in crypt_map(). get_max_request_size() is renamed to get_max_request_sectors() to clarify the unit of the value returned and its interface is changed to take a struct dm_target pointer and a pointer to the struct bio being processed. In addition to this change, to ensure that crypt_alloc_buffer() works correctly, set the dm-crypt device max_hw_sectors limit to be at most BIO_MAX_VECS << PAGE_SECTORS_SHIFT (1 MB with a 4KB page architecture). This forces DM core to split write BIOs before passing them to crypt_map(), and thus guaranteeing that dm-crypt can always accept an entire write BIO without needing to split it.

This change does not have any effect on the read path of dm-crypt. Read operations can still be split and the BIO fragments processed in parallel. There is also no impact on the performance of the write path given that all zone write BIOs were already processed inline instead of in parallel.

This change also does not affect in any way regular dm-crypt block devices.

Record
EUVD-2025-28922
CVSS 3.1
7.8 HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Updated
2026-11-02
GitHub AdvisoriesGHSA-96wf-6gfh-q6gv5.5

In the Linux kernel, the following vulnerability has been resolved: dm: dm-crypt: Do not...

In the Linux kernel, the following vulnerability has been resolved:

dm: dm-crypt: Do not partially accept write BIOs with zoned targets

Read and write operations issued to a dm-crypt target may be split according to the dm-crypt internal limits defined by the max_read_size and max_write_size module parameters (default is 128 KB). The intent is to improve processing time of large BIOs by splitting them into smaller operations that can be parallelized on different CPUs.

For zoned dm-crypt targets, this BIO splitting is still done but without the parallel execution to ensure that the issuing order of write operations to the underlying devices remains sequential. However, the splitting itself causes other problems:

  1. Since dm-crypt relies on the block layer zone write plugging to handle zone append emulation using regular write operations, the reminder of a split write BIO will always be plugged into the target zone write plugged. Once the on-going write BIO finishes, this reminder BIO is unplugged and issued from the zone write plug work. If this reminder BIO itself needs to be split, the reminder will be re-issued and plugged again, but that causes a call to a blk_queue_enter(), which may block if a queue freeze operation was initiated. This results in a deadlock as DM submission still holds BIOs that the queue freeze side is waiting for.

  2. dm-crypt relies on the emulation done by the block layer using regular write operations for processing zone append operations. This still requires to properly return the written sector as the BIO sector of the original BIO. However, this can be done correctly only and only if there is a single clone BIO used for processing the original zone append operation issued by the user. If the size of a zone append operation is larger than dm-crypt max_write_size, then the orginal BIO will be split and processed as a chain of regular write operations. Such chaining result in an incorrect written sector being returned to the zone append issuer using the original BIO sector. This in turn results in file system data corruptions using xfs or btrfs.

Fix this by modifying get_max_request_size() to always return the size of the BIO to avoid it being split with dm_accpet_partial_bio() in crypt_map(). get_max_request_size() is renamed to get_max_request_sectors() to clarify the unit of the value returned and its interface is changed to take a struct dm_target pointer and a pointer to the struct bio being processed. In addition to this change, to ensure that crypt_alloc_buffer() works correctly, set the dm-crypt device max_hw_sectors limit to be at most BIO_MAX_VECS << PAGE_SECTORS_SHIFT (1 MB with a 4KB page architecture). This forces DM core to split write BIOs before passing them to crypt_map(), and thus guaranteeing that dm-crypt can always accept an entire write BIO without needing to split it.

This change does not have any effect on the read path of dm-crypt. Read operations can still be split and the BIO fragments processed in parallel. There is also no impact on the performance of the write path given that all zone write BIOs were already processed inline instead of in parallel.

This change also does not affect in any way regular dm-crypt block devices.

Record
GHSA-96wf-6gfh-q6gv
CVSS 3.1
5.5 MediumCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Weakness
CWE-667
Updated
2026-11-02
NVD7.8

In the Linux kernel, the following vulnerability has been resolved:

dm: dm-crypt: Do not partially accept write BIOs with zoned targets

Read and write operations issued to a dm-crypt target may be split according to the dm-crypt internal limits defined by the max_read_size and max_write_size module parameters (default is 128 KB). The intent is to improve processing time of large BIOs by splitting them into smaller operations that can be parallelized on different CPUs.

For zoned dm-crypt targets, this BIO splitting is still done but without the parallel execution to ensure that the issuing order of write operations to the underlying devices remains sequential. However, the splitting itself causes other problems:

  1. Since dm-crypt relies on the block layer zone write plugging to handle zone append emulation using regular write operations, the reminder of a split write BIO will always be plugged into the target zone write plugged. Once the on-going write BIO finishes, this reminder BIO is unplugged and issued from the zone write plug work. If this reminder BIO itself needs to be split, the reminder will be re-issued and plugged again, but that causes a call to a blk_queue_enter(), which may block if a queue freeze operation was initiated. This results in a deadlock as DM submission still holds BIOs that the queue freeze side is waiting for.

  2. dm-crypt relies on the emulation done by the block layer using regular write operations for processing zone append operations. This still requires to properly return the written sector as the BIO sector of the original BIO. However, this can be done correctly only and only if there is a single clone BIO used for processing the original zone append operation issued by the user. If the size of a zone append operation is larger than dm-crypt max_write_size, then the orginal BIO will be split and processed as a chain of regular write operations. Such chaining result in an incorrect written sector being returned to the zone append issuer using the original BIO sector. This in turn results in file system data corruptions using xfs or btrfs.

Fix this by modifying get_max_request_size() to always return the size of the BIO to avoid it being split with dm_accpet_partial_bio() in crypt_map(). get_max_request_size() is renamed to get_max_request_sectors() to clarify the unit of the value returned and its interface is changed to take a struct dm_target pointer and a pointer to the struct bio being processed. In addition to this change, to ensure that crypt_alloc_buffer() works correctly, set the dm-crypt device max_hw_sectors limit to be at most BIO_MAX_VECS << PAGE_SECTORS_SHIFT (1 MB with a 4KB page architecture). This forces DM core to split write BIOs before passing them to crypt_map(), and thus guaranteeing that dm-crypt can always accept an entire write BIO without needing to split it.

This change does not have any effect on the read path of dm-crypt. Read operations can still be split and the BIO fragments processed in parallel. There is also no impact on the performance of the write path given that all zone write BIOs were already processed inline instead of in parallel.

This change also does not affect in any way regular dm-crypt block devices.

Record
CVE-2025-39791
CVSS 3.1
7.8 HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CVSS 3.1
5.5 MediumCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Weakness
CWE-667
Updated
2026-11-02
OSVBELL-CVE-2025-397915.5
Record
BELL-CVE-2025-39791
CVSS 3.1
5.5 MediumCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Updated
2026-11-02
OSV7.8

dm: dm-crypt: Do not partially accept write BIOs with zoned targets

In the Linux kernel, the following vulnerability has been resolved:

dm: dm-crypt: Do not partially accept write BIOs with zoned targets

Read and write operations issued to a dm-crypt target may be split according to the dm-crypt internal limits defined by the max_read_size and max_write_size module parameters (default is 128 KB). The intent is to improve processing time of large BIOs by splitting them into smaller operations that can be parallelized on different CPUs.

For zoned dm-crypt targets, this BIO splitting is still done but without the parallel execution to ensure that the issuing order of write operations to the underlying devices remains sequential. However, the splitting itself causes other problems:

  1. Since dm-crypt relies on the block layer zone write plugging to handle zone append emulation using regular write operations, the reminder of a split write BIO will always be plugged into the target zone write plugged. Once the on-going write BIO finishes, this reminder BIO is unplugged and issued from the zone write plug work. If this reminder BIO itself needs to be split, the reminder will be re-issued and plugged again, but that causes a call to a blk_queue_enter(), which may block if a queue freeze operation was initiated. This results in a deadlock as DM submission still holds BIOs that the queue freeze side is waiting for.

  2. dm-crypt relies on the emulation done by the block layer using regular write operations for processing zone append operations. This still requires to properly return the written sector as the BIO sector of the original BIO. However, this can be done correctly only and only if there is a single clone BIO used for processing the original zone append operation issued by the user. If the size of a zone append operation is larger than dm-crypt max_write_size, then the orginal BIO will be split and processed as a chain of regular write operations. Such chaining result in an incorrect written sector being returned to the zone append issuer using the original BIO sector. This in turn results in file system data corruptions using xfs or btrfs.

Fix this by modifying get_max_request_size() to always return the size of the BIO to avoid it being split with dm_accpet_partial_bio() in crypt_map(). get_max_request_size() is renamed to get_max_request_sectors() to clarify the unit of the value returned and its interface is changed to take a struct dm_target pointer and a pointer to the struct bio being processed. In addition to this change, to ensure that crypt_alloc_buffer() works correctly, set the dm-crypt device max_hw_sectors limit to be at most BIO_MAX_VECS << PAGE_SECTORS_SHIFT (1 MB with a 4KB page architecture). This forces DM core to split write BIOs before passing them to crypt_map(), and thus guaranteeing that dm-crypt can always accept an entire write BIO without needing to split it.

This change does not have any effect on the read path of dm-crypt. Read operations can still be split and the BIO fragments processed in parallel. There is also no impact on the performance of the write path given that all zone write BIOs were already processed inline instead of in parallel.

This change also does not affect in any way regular dm-crypt block devices.

Record
CVE-2025-39791
CVSS 3.1
7.8 HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Updated
2026-11-02
Show 7 moreShow less
OSVDEBIAN-CVE-2025-397915.5

In the Linux kernel, the following vulnerability has been resolved: dm: dm-crypt: Do not partially accept write BIOs with zoned targets Read and write operations issued to a dm-crypt target may be split according to the dm-crypt internal limits defined by the max_read_size and max_write_size module parameters (default is 128 KB). The intent is to improve processing time of large BIOs by splitting them into smaller operations that can be parallelized on different CPUs. For zoned dm-crypt targets, this BIO splitting is still done but without the parallel execution to ensure that the issuing order of write operations to the underlying devices remains sequential. However, the splitting itself causes other problems: 1) Since dm-crypt relies on the block layer zone write plugging to handle zone append emulation using regular write operations, the reminder of a split write BIO will always be plugged into the target zone write plugged. Once the on-going write BIO finishes, this reminder BIO is unplugged and issued from the zone write plug work. If this reminder BIO itself needs to be split, the reminder will be re-issued and plugged again, but that causes a call to a blk_queue_enter(), which may block if a queue freeze operation was initiated. This results in a deadlock as DM submission still holds BIOs that the queue freeze side is waiting for. 2) dm-crypt relies on the emulation done by the block layer using regular write operations for processing zone append operations. This still requires to properly return the written sector as the BIO sector of the original BIO. However, this can be done correctly only and only if there is a single clone BIO used for processing the original zone append operation issued by the user. If the size of a zone append operation is larger than dm-crypt max_write_size, then the orginal BIO will be split and processed as a chain of regular write operations. Such chaining result in an incorrect written sector being returned to the zone append issuer using the original BIO sector. This in turn results in file system data corruptions using xfs or btrfs. Fix this by modifying get_max_request_size() to always return the size of the BIO to avoid it being split with dm_accpet_partial_bio() in crypt_map(). get_max_request_size() is renamed to get_max_request_sectors() to clarify the unit of the value returned and its interface is changed to take a struct dm_target pointer and a pointer to the struct bio being processed. In addition to this change, to ensure that crypt_alloc_buffer() works correctly, set the dm-crypt device max_hw_sectors limit to be at most BIO_MAX_VECS << PAGE_SECTORS_SHIFT (1 MB with a 4KB page architecture). This forces DM core to split write BIOs before passing them to crypt_map(), and thus guaranteeing that dm-crypt can always accept an entire write BIO without needing to split it. This change does not have any effect on the read path of dm-crypt. Read operations can still be split and the BIO fragments processed in parallel. There is also no impact on the performance of the write path given that all zone write BIOs were already processed inline instead of in parallel. This change also does not affect in any way regular dm-crypt block devices.

Record
DEBIAN-CVE-2025-39791
CVSS 3.1
5.5 MediumCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Updated
2026-11-02
OSVUBUNTU-CVE-2025-397915.5

In the Linux kernel, the following vulnerability has been resolved: dm: dm-crypt: Do not partially accept write BIOs with zoned targets Read and write operations issued to a dm-crypt target may be split according to the dm-crypt internal limits defined by the max_read_size and max_write_size module parameters (default is 128 KB). The intent is to improve processing time of large BIOs by splitting them into smaller operations that can be parallelized on different CPUs. For zoned dm-crypt targets, this BIO splitting is still done but without the parallel execution to ensure that the issuing order of write operations to the underlying devices remains sequential. However, the splitting itself causes other problems: 1) Since dm-crypt relies on the block layer zone write plugging to handle zone append emulation using regular write operations, the reminder of a split write BIO will always be plugged into the target zone write plugged. Once the on-going write BIO finishes, this reminder BIO is unplugged and issued from the zone write plug work. If this reminder BIO itself needs to be split, the reminder will be re-issued and plugged again, but that causes a call to a blk_queue_enter(), which may block if a queue freeze operation was initiated. This results in a deadlock as DM submission still holds BIOs that the queue freeze side is waiting for. 2) dm-crypt relies on the emulation done by the block layer using regular write operations for processing zone append operations. This still requires to properly return the written sector as the BIO sector of the original BIO. However, this can be done correctly only and only if there is a single clone BIO used for processing the original zone append operation issued by the user. If the size of a zone append operation is larger than dm-crypt max_write_size, then the orginal BIO will be split and processed as a chain of regular write operations. Such chaining result in an incorrect written sector being returned to the zone append issuer using the original BIO sector. This in turn results in file system data corruptions using xfs or btrfs. Fix this by modifying get_max_request_size() to always return the size of the BIO to avoid it being split with dm_accpet_partial_bio() in crypt_map(). get_max_request_size() is renamed to get_max_request_sectors() to clarify the unit of the value returned and its interface is changed to take a struct dm_target pointer and a pointer to the struct bio being processed. In addition to this change, to ensure that crypt_alloc_buffer() works correctly, set the dm-crypt device max_hw_sectors limit to be at most BIO_MAX_VECS << PAGE_SECTORS_SHIFT (1 MB with a 4KB page architecture). This forces DM core to split write BIOs before passing them to crypt_map(), and thus guaranteeing that dm-crypt can always accept an entire write BIO without needing to split it. This change does not have any effect on the read path of dm-crypt. Read operations can still be split and the BIO fragments processed in parallel. There is also no impact on the performance of the write path given that all zone write BIOs were already processed inline instead of in parallel. This change also does not affect in any way regular dm-crypt block devices.

Record
UBUNTU-CVE-2025-39791
CVSS 3.1
5.5 MediumCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
CVSS 3.1
7.8 HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Updated
2026-11-02
OSVopenSUSE-SU-2025:20081-1No score

Security update for the Linux Kernel

The SUSE Linux Enterprise Server 16.0 and SUSE Linux Micro 6.2 kernel was updated to receive various security bugfixes.

The following security bugs were fixed:

  • CVE-2024-53164: net: sched: fix ordering of qlen adjustment (bsc#1234863).
  • CVE-2024-57891: sched_ext: Fix invalid irq restore in scx_ops_bypass() (bsc#1235953).
  • CVE-2024-57951: hrtimers: Handle CPU state correctly on hotplug (bsc#1237108).
  • CVE-2024-57952: Revert "libfs: fix infinite directory reads for offset dir" (bsc#1237131).
  • CVE-2024-58090: sched/core: Prevent rescheduling when interrupts are disabled (bsc#1240324).
  • CVE-2025-22034: mm/rmap: avoid -EBUSY from make_device_exclusive() (bsc#1241435).
  • CVE-2025-22077: Revert "smb: client: fix TCP timers deadlock after rmmod" (bsc#1241403).
  • CVE-2025-23141: KVM: x86: Acquire SRCU in KVM_GET_MP_STATE to protect guest memory accesses (bsc#1242782).
  • CVE-2025-37821: sched/eevdf: Fix se->slice being set to U64_MAX and resulting (bsc#1242864).
  • CVE-2025-37849: KVM: arm64: Tear down vGIC on failed vCPU creation (bsc#1243000).
  • CVE-2025-37856: btrfs: harden block_group::bg_list against list_del() races (bsc#1243068).
  • CVE-2025-37861: scsi: mpi3mr: Synchronous access b/w reset and tm thread for reply queue (bsc#1243055).
  • CVE-2025-37864: net: dsa: clean up FDB, MDB, VLAN entries on unbind (bsc#1242965).
  • CVE-2025-38006: net: mctp: Do not access ifa_index when missing (bsc#1244930).
  • CVE-2025-38008: mm/page_alloc: fix race condition in unaccepted memory handling (bsc#1244939).
  • CVE-2025-38019: mlxsw: spectrum_router: Fix use-after-free when deleting GRE net devices (bsc#1245000).
  • CVE-2025-38034: btrfs: correct the order of prelim_ref arguments in btrfs__prelim_ref (bsc#1244792).
  • CVE-2025-38038: cpufreq: amd-pstate: Remove unnecessary driver_lock in set_boost (bsc#1244812).
  • CVE-2025-38058: __legitimize_mnt(): check for MNT_SYNC_UMOUNT should be under mount_lock (bsc#1245151).
  • CVE-2025-38062: kABI: restore layout of struct msi_desc (bsc#1245216).
  • CVE-2025-38075: scsi: target: iscsi: Fix timeout on deleted connection (bsc#1244734).
  • CVE-2025-38101: ring-buffer: Fix buffer locking in ring_buffer_subbuf_order_set() (bsc#1245659).
  • CVE-2025-38103: HID: usbhid: Eliminate recurrent out-of-bounds bug in usbhid_parse() (bsc#1245663).
  • CVE-2025-38106: io_uring/sqpoll: do not put task_struct on tctx setup failure (bsc#1245664).
  • CVE-2025-38117: hci_dev centralize extra lock (bsc#1245695).
  • CVE-2025-38119: scsi: core: ufs: Fix a hang in the error handler (bsc#1245700).
  • CVE-2025-38125: net: stmmac: make sure that ptp_rate is not 0 before configuring EST (bsc#1245710).
  • CVE-2025-38146: net: openvswitch: Fix the dead loop of MPLS parse (bsc#1245767).
  • CVE-2025-38160: clk: bcm: rpi: Add NULL check in raspberrypi_clk_register() (bsc#1245780).
  • CVE-2025-38168: perf: arm-ni: Unregister PMUs on probe failure (bsc#1245763).
  • CVE-2025-38180: net: atm: fix /proc/net/atm/lec handling (bsc#1245970).
  • CVE-2025-38182: ublk: santizize the arguments from userspace when adding a device (bsc#1245937).
  • CVE-2025-38184: tipc: fix null-ptr-deref when acquiring remote ip of ethernet bearer (bsc#1245956).
  • CVE-2025-38185: atm: atmtcp: Free invalid length skb in atmtcp_c_send() (bsc#1246012).
  • CVE-2025-38190: atm: Revert atm_account_tx() if copy_from_iter_full() fails (bsc#1245973).
  • CVE-2025-38201: netfilter: nft_set_pipapo: clamp maximum map bucket size to INT_MAX (bsc#1245977).
  • CVE-2025-38205: drm/amd/display: Avoid divide by zero by initializing dummy pitch to 1 (bsc#1246005).
  • CVE-2025-38208: smb: client: add NULL check in automount_fullpath (bsc#1245815).
  • CVE-2025-38216: iommu/vt-d: Restore context entry setup order for aliased devices (bsc#1245963).
  • CVE-2025-38220: ext4: only dirty folios when data journaling regular files (bsc#1245966).
  • CVE-2025-38222: ext4: inline: fix len overflow in ext4_prepare_inline_data (bsc#1245976).
  • CVE-2025-38242: mm: userfaultfd: fix race of userfaultfd_move and swap…
Record
openSUSE-SU-2025:20081-1
Updated
2026-11-02
OSVSUSE-SU-2025:21074-1No score

Security update for the Linux Kernel

The SUSE Linux Enterprise Server 16.0 and SUSE Linux Micro 6.2 kernel was updated to receive various security bugfixes.

The following security bugs were fixed:

  • CVE-2024-53164: net: sched: fix ordering of qlen adjustment (bsc#1234863).
  • CVE-2024-57891: sched_ext: Fix invalid irq restore in scx_ops_bypass() (bsc#1235953).
  • CVE-2024-57951: hrtimers: Handle CPU state correctly on hotplug (bsc#1237108).
  • CVE-2024-57952: Revert "libfs: fix infinite directory reads for offset dir" (bsc#1237131).
  • CVE-2024-58090: sched/core: Prevent rescheduling when interrupts are disabled (bsc#1240324).
  • CVE-2025-22034: mm/rmap: avoid -EBUSY from make_device_exclusive() (bsc#1241435).
  • CVE-2025-22077: Revert "smb: client: fix TCP timers deadlock after rmmod" (bsc#1241403).
  • CVE-2025-23141: KVM: x86: Acquire SRCU in KVM_GET_MP_STATE to protect guest memory accesses (bsc#1242782).
  • CVE-2025-37821: sched/eevdf: Fix se->slice being set to U64_MAX and resulting (bsc#1242864).
  • CVE-2025-37849: KVM: arm64: Tear down vGIC on failed vCPU creation (bsc#1243000).
  • CVE-2025-37856: btrfs: harden block_group::bg_list against list_del() races (bsc#1243068).
  • CVE-2025-37861: scsi: mpi3mr: Synchronous access b/w reset and tm thread for reply queue (bsc#1243055).
  • CVE-2025-37864: net: dsa: clean up FDB, MDB, VLAN entries on unbind (bsc#1242965).
  • CVE-2025-38006: net: mctp: Do not access ifa_index when missing (bsc#1244930).
  • CVE-2025-38008: mm/page_alloc: fix race condition in unaccepted memory handling (bsc#1244939).
  • CVE-2025-38019: mlxsw: spectrum_router: Fix use-after-free when deleting GRE net devices (bsc#1245000).
  • CVE-2025-38034: btrfs: correct the order of prelim_ref arguments in btrfs__prelim_ref (bsc#1244792).
  • CVE-2025-38038: cpufreq: amd-pstate: Remove unnecessary driver_lock in set_boost (bsc#1244812).
  • CVE-2025-38058: __legitimize_mnt(): check for MNT_SYNC_UMOUNT should be under mount_lock (bsc#1245151).
  • CVE-2025-38062: kABI: restore layout of struct msi_desc (bsc#1245216).
  • CVE-2025-38075: scsi: target: iscsi: Fix timeout on deleted connection (bsc#1244734).
  • CVE-2025-38101: ring-buffer: Fix buffer locking in ring_buffer_subbuf_order_set() (bsc#1245659).
  • CVE-2025-38103: HID: usbhid: Eliminate recurrent out-of-bounds bug in usbhid_parse() (bsc#1245663).
  • CVE-2025-38106: io_uring/sqpoll: do not put task_struct on tctx setup failure (bsc#1245664).
  • CVE-2025-38117: hci_dev centralize extra lock (bsc#1245695).
  • CVE-2025-38119: scsi: core: ufs: Fix a hang in the error handler (bsc#1245700).
  • CVE-2025-38125: net: stmmac: make sure that ptp_rate is not 0 before configuring EST (bsc#1245710).
  • CVE-2025-38146: net: openvswitch: Fix the dead loop of MPLS parse (bsc#1245767).
  • CVE-2025-38160: clk: bcm: rpi: Add NULL check in raspberrypi_clk_register() (bsc#1245780).
  • CVE-2025-38168: perf: arm-ni: Unregister PMUs on probe failure (bsc#1245763).
  • CVE-2025-38180: net: atm: fix /proc/net/atm/lec handling (bsc#1245970).
  • CVE-2025-38182: ublk: santizize the arguments from userspace when adding a device (bsc#1245937).
  • CVE-2025-38184: tipc: fix null-ptr-deref when acquiring remote ip of ethernet bearer (bsc#1245956).
  • CVE-2025-38185: atm: atmtcp: Free invalid length skb in atmtcp_c_send() (bsc#1246012).
  • CVE-2025-38190: atm: Revert atm_account_tx() if copy_from_iter_full() fails (bsc#1245973).
  • CVE-2025-38201: netfilter: nft_set_pipapo: clamp maximum map bucket size to INT_MAX (bsc#1245977).
  • CVE-2025-38205: drm/amd/display: Avoid divide by zero by initializing dummy pitch to 1 (bsc#1246005).
  • CVE-2025-38208: smb: client: add NULL check in automount_fullpath (bsc#1245815).
  • CVE-2025-38216: iommu/vt-d: Restore context entry setup order for aliased devices (bsc#1245963).
  • CVE-2025-38220: ext4: only dirty folios when data journaling regular files (bsc#1245966).
  • CVE-2025-38222: ext4: inline: fix len overflow in ext4_prepare_inline_data (bsc#1245976).
  • CVE-2025-38242: mm: userfaultfd: fix race of userfaultfd_move and swap…
Record
SUSE-SU-2025:21074-1
Updated
2026-11-02
OSVSUSE-SU-2025:21139-1No score

Security update for the Linux Kernel

The SUSE Linux Enterprise Server 16.0 and SUSE Linux Micro 6.2 kernel was updated to receive various security bugfixes.

The following security bugs were fixed:

  • CVE-2024-53164: net: sched: fix ordering of qlen adjustment (bsc#1234863).
  • CVE-2024-57891: sched_ext: Fix invalid irq restore in scx_ops_bypass() (bsc#1235953).
  • CVE-2024-57951: hrtimers: Handle CPU state correctly on hotplug (bsc#1237108).
  • CVE-2024-57952: Revert "libfs: fix infinite directory reads for offset dir" (bsc#1237131).
  • CVE-2024-58090: sched/core: Prevent rescheduling when interrupts are disabled (bsc#1240324).
  • CVE-2025-22034: mm/rmap: avoid -EBUSY from make_device_exclusive() (bsc#1241435).
  • CVE-2025-22077: Revert "smb: client: fix TCP timers deadlock after rmmod" (bsc#1241403).
  • CVE-2025-23141: KVM: x86: Acquire SRCU in KVM_GET_MP_STATE to protect guest memory accesses (bsc#1242782).
  • CVE-2025-37821: sched/eevdf: Fix se->slice being set to U64_MAX and resulting (bsc#1242864).
  • CVE-2025-37849: KVM: arm64: Tear down vGIC on failed vCPU creation (bsc#1243000).
  • CVE-2025-37856: btrfs: harden block_group::bg_list against list_del() races (bsc#1243068).
  • CVE-2025-37861: scsi: mpi3mr: Synchronous access b/w reset and tm thread for reply queue (bsc#1243055).
  • CVE-2025-37864: net: dsa: clean up FDB, MDB, VLAN entries on unbind (bsc#1242965).
  • CVE-2025-38006: net: mctp: Do not access ifa_index when missing (bsc#1244930).
  • CVE-2025-38008: mm/page_alloc: fix race condition in unaccepted memory handling (bsc#1244939).
  • CVE-2025-38019: mlxsw: spectrum_router: Fix use-after-free when deleting GRE net devices (bsc#1245000).
  • CVE-2025-38034: btrfs: correct the order of prelim_ref arguments in btrfs__prelim_ref (bsc#1244792).
  • CVE-2025-38038: cpufreq: amd-pstate: Remove unnecessary driver_lock in set_boost (bsc#1244812).
  • CVE-2025-38058: __legitimize_mnt(): check for MNT_SYNC_UMOUNT should be under mount_lock (bsc#1245151).
  • CVE-2025-38062: kABI: restore layout of struct msi_desc (bsc#1245216).
  • CVE-2025-38075: scsi: target: iscsi: Fix timeout on deleted connection (bsc#1244734).
  • CVE-2025-38101: ring-buffer: Fix buffer locking in ring_buffer_subbuf_order_set() (bsc#1245659).
  • CVE-2025-38103: HID: usbhid: Eliminate recurrent out-of-bounds bug in usbhid_parse() (bsc#1245663).
  • CVE-2025-38106: io_uring/sqpoll: do not put task_struct on tctx setup failure (bsc#1245664).
  • CVE-2025-38117: hci_dev centralize extra lock (bsc#1245695).
  • CVE-2025-38119: scsi: core: ufs: Fix a hang in the error handler (bsc#1245700).
  • CVE-2025-38125: net: stmmac: make sure that ptp_rate is not 0 before configuring EST (bsc#1245710).
  • CVE-2025-38146: net: openvswitch: Fix the dead loop of MPLS parse (bsc#1245767).
  • CVE-2025-38160: clk: bcm: rpi: Add NULL check in raspberrypi_clk_register() (bsc#1245780).
  • CVE-2025-38168: perf: arm-ni: Unregister PMUs on probe failure (bsc#1245763).
  • CVE-2025-38180: net: atm: fix /proc/net/atm/lec handling (bsc#1245970).
  • CVE-2025-38182: ublk: santizize the arguments from userspace when adding a device (bsc#1245937).
  • CVE-2025-38184: tipc: fix null-ptr-deref when acquiring remote ip of ethernet bearer (bsc#1245956).
  • CVE-2025-38185: atm: atmtcp: Free invalid length skb in atmtcp_c_send() (bsc#1246012).
  • CVE-2025-38190: atm: Revert atm_account_tx() if copy_from_iter_full() fails (bsc#1245973).
  • CVE-2025-38201: netfilter: nft_set_pipapo: clamp maximum map bucket size to INT_MAX (bsc#1245977).
  • CVE-2025-38205: drm/amd/display: Avoid divide by zero by initializing dummy pitch to 1 (bsc#1246005).
  • CVE-2025-38208: smb: client: add NULL check in automount_fullpath (bsc#1245815).
  • CVE-2025-38216: iommu/vt-d: Restore context entry setup order for aliased devices (bsc#1245963).
  • CVE-2025-38220: ext4: only dirty folios when data journaling regular files (bsc#1245966).
  • CVE-2025-38222: ext4: inline: fix len overflow in ext4_prepare_inline_data (bsc#1245976).
  • CVE-2025-38242: mm: userfaultfd: fix race of userfaultfd_move and swap…
Record
SUSE-SU-2025:21139-1
Updated
2026-11-02
OSVSUSE-SU-2025:21179-1No score

Security update for the Linux Kernel

The SUSE Linux Enterprise Server 16.0 and SUSE Linux Micro 6.2 kernel was updated to receive various security bugfixes.

The following security bugs were fixed:

  • CVE-2024-53164: net: sched: fix ordering of qlen adjustment (bsc#1234863).
  • CVE-2024-57891: sched_ext: Fix invalid irq restore in scx_ops_bypass() (bsc#1235953).
  • CVE-2024-57951: hrtimers: Handle CPU state correctly on hotplug (bsc#1237108).
  • CVE-2024-57952: Revert "libfs: fix infinite directory reads for offset dir" (bsc#1237131).
  • CVE-2024-58090: sched/core: Prevent rescheduling when interrupts are disabled (bsc#1240324).
  • CVE-2025-22034: mm/rmap: avoid -EBUSY from make_device_exclusive() (bsc#1241435).
  • CVE-2025-22077: Revert "smb: client: fix TCP timers deadlock after rmmod" (bsc#1241403).
  • CVE-2025-23141: KVM: x86: Acquire SRCU in KVM_GET_MP_STATE to protect guest memory accesses (bsc#1242782).
  • CVE-2025-37821: sched/eevdf: Fix se->slice being set to U64_MAX and resulting (bsc#1242864).
  • CVE-2025-37849: KVM: arm64: Tear down vGIC on failed vCPU creation (bsc#1243000).
  • CVE-2025-37856: btrfs: harden block_group::bg_list against list_del() races (bsc#1243068).
  • CVE-2025-37861: scsi: mpi3mr: Synchronous access b/w reset and tm thread for reply queue (bsc#1243055).
  • CVE-2025-37864: net: dsa: clean up FDB, MDB, VLAN entries on unbind (bsc#1242965).
  • CVE-2025-38006: net: mctp: Do not access ifa_index when missing (bsc#1244930).
  • CVE-2025-38008: mm/page_alloc: fix race condition in unaccepted memory handling (bsc#1244939).
  • CVE-2025-38019: mlxsw: spectrum_router: Fix use-after-free when deleting GRE net devices (bsc#1245000).
  • CVE-2025-38034: btrfs: correct the order of prelim_ref arguments in btrfs__prelim_ref (bsc#1244792).
  • CVE-2025-38038: cpufreq: amd-pstate: Remove unnecessary driver_lock in set_boost (bsc#1244812).
  • CVE-2025-38058: __legitimize_mnt(): check for MNT_SYNC_UMOUNT should be under mount_lock (bsc#1245151).
  • CVE-2025-38062: kABI: restore layout of struct msi_desc (bsc#1245216).
  • CVE-2025-38075: scsi: target: iscsi: Fix timeout on deleted connection (bsc#1244734).
  • CVE-2025-38101: ring-buffer: Fix buffer locking in ring_buffer_subbuf_order_set() (bsc#1245659).
  • CVE-2025-38103: HID: usbhid: Eliminate recurrent out-of-bounds bug in usbhid_parse() (bsc#1245663).
  • CVE-2025-38106: io_uring/sqpoll: do not put task_struct on tctx setup failure (bsc#1245664).
  • CVE-2025-38117: hci_dev centralize extra lock (bsc#1245695).
  • CVE-2025-38119: scsi: core: ufs: Fix a hang in the error handler (bsc#1245700).
  • CVE-2025-38125: net: stmmac: make sure that ptp_rate is not 0 before configuring EST (bsc#1245710).
  • CVE-2025-38146: net: openvswitch: Fix the dead loop of MPLS parse (bsc#1245767).
  • CVE-2025-38160: clk: bcm: rpi: Add NULL check in raspberrypi_clk_register() (bsc#1245780).
  • CVE-2025-38168: perf: arm-ni: Unregister PMUs on probe failure (bsc#1245763).
  • CVE-2025-38180: net: atm: fix /proc/net/atm/lec handling (bsc#1245970).
  • CVE-2025-38182: ublk: santizize the arguments from userspace when adding a device (bsc#1245937).
  • CVE-2025-38184: tipc: fix null-ptr-deref when acquiring remote ip of ethernet bearer (bsc#1245956).
  • CVE-2025-38185: atm: atmtcp: Free invalid length skb in atmtcp_c_send() (bsc#1246012).
  • CVE-2025-38190: atm: Revert atm_account_tx() if copy_from_iter_full() fails (bsc#1245973).
  • CVE-2025-38201: netfilter: nft_set_pipapo: clamp maximum map bucket size to INT_MAX (bsc#1245977).
  • CVE-2025-38205: drm/amd/display: Avoid divide by zero by initializing dummy pitch to 1 (bsc#1246005).
  • CVE-2025-38208: smb: client: add NULL check in automount_fullpath (bsc#1245815).
  • CVE-2025-38216: iommu/vt-d: Restore context entry setup order for aliased devices (bsc#1245963).
  • CVE-2025-38220: ext4: only dirty folios when data journaling regular files (bsc#1245966).
  • CVE-2025-38222: ext4: inline: fix len overflow in ext4_prepare_inline_data (bsc#1245976).
  • CVE-2025-38242: mm: userfaultfd: fix race of userfaultfd_move and swap…
Record
SUSE-SU-2025:21179-1
Updated
2026-11-02
OSVSUSE-SU-2026:20560-1No score

Security update for the Linux Kernel

The SUSE Linux Enterprise Server 16.0 and SUSE Linux Micro 6.2 kernel was updated to receive various security bugfixes.

The following security bugs were fixed:

  • CVE-2024-53164: net: sched: fix ordering of qlen adjustment (bsc#1234863).
  • CVE-2024-57891: sched_ext: Fix invalid irq restore in scx_ops_bypass() (bsc#1235953).
  • CVE-2024-57951: hrtimers: Handle CPU state correctly on hotplug (bsc#1237108).
  • CVE-2024-57952: Revert "libfs: fix infinite directory reads for offset dir" (bsc#1237131).
  • CVE-2024-58090: sched/core: Prevent rescheduling when interrupts are disabled (bsc#1240324).
  • CVE-2025-22034: mm/rmap: avoid -EBUSY from make_device_exclusive() (bsc#1241435).
  • CVE-2025-22077: Revert "smb: client: fix TCP timers deadlock after rmmod" (bsc#1241403).
  • CVE-2025-23141: KVM: x86: Acquire SRCU in KVM_GET_MP_STATE to protect guest memory accesses (bsc#1242782).
  • CVE-2025-37821: sched/eevdf: Fix se->slice being set to U64_MAX and resulting (bsc#1242864).
  • CVE-2025-37849: KVM: arm64: Tear down vGIC on failed vCPU creation (bsc#1243000).
  • CVE-2025-37856: btrfs: harden block_group::bg_list against list_del() races (bsc#1243068).
  • CVE-2025-37861: scsi: mpi3mr: Synchronous access b/w reset and tm thread for reply queue (bsc#1243055).
  • CVE-2025-37864: net: dsa: clean up FDB, MDB, VLAN entries on unbind (bsc#1242965).
  • CVE-2025-38006: net: mctp: Do not access ifa_index when missing (bsc#1244930).
  • CVE-2025-38008: mm/page_alloc: fix race condition in unaccepted memory handling (bsc#1244939).
  • CVE-2025-38019: mlxsw: spectrum_router: Fix use-after-free when deleting GRE net devices (bsc#1245000).
  • CVE-2025-38034: btrfs: correct the order of prelim_ref arguments in btrfs__prelim_ref (bsc#1244792).
  • CVE-2025-38038: cpufreq: amd-pstate: Remove unnecessary driver_lock in set_boost (bsc#1244812).
  • CVE-2025-38058: __legitimize_mnt(): check for MNT_SYNC_UMOUNT should be under mount_lock (bsc#1245151).
  • CVE-2025-38062: kABI: restore layout of struct msi_desc (bsc#1245216).
  • CVE-2025-38075: scsi: target: iscsi: Fix timeout on deleted connection (bsc#1244734).
  • CVE-2025-38101: ring-buffer: Fix buffer locking in ring_buffer_subbuf_order_set() (bsc#1245659).
  • CVE-2025-38103: HID: usbhid: Eliminate recurrent out-of-bounds bug in usbhid_parse() (bsc#1245663).
  • CVE-2025-38106: io_uring/sqpoll: do not put task_struct on tctx setup failure (bsc#1245664).
  • CVE-2025-38117: hci_dev centralize extra lock (bsc#1245695).
  • CVE-2025-38119: scsi: core: ufs: Fix a hang in the error handler (bsc#1245700).
  • CVE-2025-38125: net: stmmac: make sure that ptp_rate is not 0 before configuring EST (bsc#1245710).
  • CVE-2025-38146: net: openvswitch: Fix the dead loop of MPLS parse (bsc#1245767).
  • CVE-2025-38160: clk: bcm: rpi: Add NULL check in raspberrypi_clk_register() (bsc#1245780).
  • CVE-2025-38168: perf: arm-ni: Unregister PMUs on probe failure (bsc#1245763).
  • CVE-2025-38180: net: atm: fix /proc/net/atm/lec handling (bsc#1245970).
  • CVE-2025-38182: ublk: santizize the arguments from userspace when adding a device (bsc#1245937).
  • CVE-2025-38184: tipc: fix null-ptr-deref when acquiring remote ip of ethernet bearer (bsc#1245956).
  • CVE-2025-38185: atm: atmtcp: Free invalid length skb in atmtcp_c_send() (bsc#1246012).
  • CVE-2025-38190: atm: Revert atm_account_tx() if copy_from_iter_full() fails (bsc#1245973).
  • CVE-2025-38201: netfilter: nft_set_pipapo: clamp maximum map bucket size to INT_MAX (bsc#1245977).
  • CVE-2025-38205: drm/amd/display: Avoid divide by zero by initializing dummy pitch to 1 (bsc#1246005).
  • CVE-2025-38208: smb: client: add NULL check in automount_fullpath (bsc#1245815).
  • CVE-2025-38216: iommu/vt-d: Restore context entry setup order for aliased devices (bsc#1245963).
  • CVE-2025-38220: ext4: only dirty folios when data journaling regular files (bsc#1245966).
  • CVE-2025-38222: ext4: inline: fix len overflow in ext4_prepare_inline_data (bsc#1245976).
  • CVE-2025-38242: mm: userfaultfd: fix race of userfaultfd_move and swap…
Record
SUSE-SU-2026:20560-1
Updated
2026-11-02

Affected products

Affected packages

Affected packages
PackageAffectedFixed
linux-lts
Alpaquita:25
6.12.41-r0 up to 6.12.44-r0
6.12.44-r0
linux-lts
Alpaquita:stream
6.12.92-r1 up to 6.18.35-r1
6.18.35-r1
Kernel
Linux
6.10.0 up to 6.12.44, 6.13.0 up to 6.16.4
6.12.446.16.4
linux
Debian:13
before 6.12.48-1, plus listed versions
6.12.38-16.12.41-16.12.43-16.12.43-1~bpo12+1
6.12.48-1
linux
Debian:14
before 6.16.5-1, plus listed versions
6.12.100-16.12.101-16.12.105-16.12.107-16.12.111-1
Show 45 moreShow less
6.12.113-16.12.38-16.12.41-16.12.43-16.12.43-1~bpo12+16.12.48-16.12.57-16.12.57-1~bpo12+16.12.63-16.12.63-1~bpo12+16.12.69-16.12.69-1~bpo12+16.12.73-16.12.73-1~bpo12+16.12.74-16.12.74-26.12.74-2~bpo12+16.12.85-16.12.85-1~bpo12+16.12.86-16.12.86-1~bpo12+16.12.88-16.12.88-1~bpo12+16.12.90-16.12.90-1~bpo12+16.12.90-26.12.90-2~bpo12+16.12.94-16.12.94-1~bpo12+16.12.95-16.12.95-1~bpo12+16.12.96-16.13.10-1~exp16.13.11-1~exp16.13.2-1~exp16.13.3-1~exp16.13.4-1~exp16.13.5-1~exp16.13.6-1~exp16.13.7-1~exp16.13.8-1~exp16.13.9-1~exp16.13~rc6-1~exp16.13~rc7-1~exp16.14.3-1~exp1
6.16.5-1
linux
Debian:13
From an advisory covering 126 CVEs
before 6.12.48-1, plus listed versions
6.12.38-16.12.41-16.12.43-16.12.43-1~bpo12+1
6.12.48-1
kernel-64kb
SUSE:Linux Micro 6.2
From an advisory covering 573 CVEs
before 6.12.0-160000.6.1
6.12.0-160000.6.1
kernel-default
SUSE:Linux Micro 6.2
From an advisory covering 573 CVEs
before 6.12.0-160000.6.1
6.12.0-160000.6.1
kernel-default-base
SUSE:Linux Micro 6.2
From an advisory covering 573 CVEs
before 6.12.0-160000.6.1.160000.2.4
6.12.0-160000.6.1.160000.2.4
kernel-rt
SUSE:Linux Micro 6.2
From an advisory covering 573 CVEs
before 6.12.0-160000.6.1
6.12.0-160000.6.1
Show 134 moreShow less
Affected packages
PackageAffectedFixed
kernel-source
SUSE:Linux Micro 6.2
From an advisory covering 573 CVEs
before 6.12.0-160000.6.1
6.12.0-160000.6.1
kernel-64kb
SUSE:Linux Enterprise Server 16.0
From an advisory covering 573 CVEs
before 6.12.0-160000.6.1
6.12.0-160000.6.1
kernel-default
SUSE:Linux Enterprise Server 16.0
From an advisory covering 573 CVEs
before 6.12.0-160000.6.1
6.12.0-160000.6.1
kernel-default-base
SUSE:Linux Enterprise Server 16.0
From an advisory covering 573 CVEs
before 6.12.0-160000.6.1.160000.2.4
6.12.0-160000.6.1.160000.2.4
kernel-docs
SUSE:Linux Enterprise Server 16.0
From an advisory covering 573 CVEs
before 6.12.0-160000.6.1
6.12.0-160000.6.1
kernel-kvmsmall
SUSE:Linux Enterprise Server 16.0
From an advisory covering 573 CVEs
before 6.12.0-160000.6.1
6.12.0-160000.6.1
kernel-obs-qa
SUSE:Linux Enterprise Server 16.0
From an advisory covering 573 CVEs
before 6.12.0-160000.6.1
6.12.0-160000.6.1
kernel-source
SUSE:Linux Enterprise Server 16.0
From an advisory covering 573 CVEs
before 6.12.0-160000.6.1
6.12.0-160000.6.1
kernel-syms
SUSE:Linux Enterprise Server 16.0
From an advisory covering 573 CVEs
before 6.12.0-160000.6.1
6.12.0-160000.6.1
kernel-zfcpdump
SUSE:Linux Enterprise Server 16.0
From an advisory covering 573 CVEs
before 6.12.0-160000.6.1
6.12.0-160000.6.1
kernel-64kb
SUSE:Linux Enterprise Server for SAP applications 16.0
From an advisory covering 573 CVEs
before 6.12.0-160000.6.1
6.12.0-160000.6.1
kernel-default
SUSE:Linux Enterprise Server for SAP applications 16.0
From an advisory covering 573 CVEs
before 6.12.0-160000.6.1
6.12.0-160000.6.1
kernel-default-base
SUSE:Linux Enterprise Server for SAP applications 16.0
From an advisory covering 573 CVEs
before 6.12.0-160000.6.1.160000.2.4
6.12.0-160000.6.1.160000.2.4
kernel-docs
SUSE:Linux Enterprise Server for SAP applications 16.0
From an advisory covering 573 CVEs
before 6.12.0-160000.6.1
6.12.0-160000.6.1
kernel-kvmsmall
SUSE:Linux Enterprise Server for SAP applications 16.0
From an advisory covering 573 CVEs
before 6.12.0-160000.6.1
6.12.0-160000.6.1
kernel-obs-qa
SUSE:Linux Enterprise Server for SAP applications 16.0
From an advisory covering 573 CVEs
before 6.12.0-160000.6.1
6.12.0-160000.6.1
kernel-source
SUSE:Linux Enterprise Server for SAP applications 16.0
From an advisory covering 573 CVEs
before 6.12.0-160000.6.1
6.12.0-160000.6.1
kernel-syms
SUSE:Linux Enterprise Server for SAP applications 16.0
From an advisory covering 573 CVEs
before 6.12.0-160000.6.1
6.12.0-160000.6.1
kernel-zfcpdump
SUSE:Linux Enterprise Server for SAP applications 16.0
From an advisory covering 573 CVEs
before 6.12.0-160000.6.1
6.12.0-160000.6.1
kernel-default
SUSE:Linux Enterprise High Availability Extension 16.0
From an advisory covering 573 CVEs
before 6.12.0-160000.6.1
6.12.0-160000.6.1
kernel-obs-build
SUSE:Linux Micro Extras 6.2
From an advisory covering 573 CVEs
before 6.12.0-160000.6.1
6.12.0-160000.6.1
kernel-syms
SUSE:Linux Micro Extras 6.2
From an advisory covering 573 CVEs
before 6.12.0-160000.6.1
6.12.0-160000.6.1
linux-hwe-edge
Ubuntu: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 less
4.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.0
Ubuntu: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.3
Ubuntu: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 less
5.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-azure
Ubuntu: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 less
4.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.3
Ubuntu: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 less
5.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-edge
Ubuntu: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-gcp
Ubuntu: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 less
4.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.3
Ubuntu: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 less
5.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.15
Ubuntu: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 less
4.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.4
Ubuntu: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 less
5.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.4
Ubuntu: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 less
5.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-hwe
Ubuntu: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 less
4.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-edge
Ubuntu: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 less
5.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-oem
Ubuntu: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 less
4.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.0
Ubuntu: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.3
Ubuntu: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 less
5.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.11
Ubuntu: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 less
5.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.13
Ubuntu: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 less
5.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.8
Ubuntu: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.11
Ubuntu: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 less
5.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.13
Ubuntu: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 less
5.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.8
Ubuntu: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-fde
Ubuntu: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 less
5.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-gcp-5.11
Ubuntu: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 less
5.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.13
Ubuntu: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 less
5.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.8
Ubuntu: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-gke
Ubuntu: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 less
5.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.15
Ubuntu: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 less
5.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-gkeop
Ubuntu: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 less
5.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.15
Ubuntu: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 less
5.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.11
Ubuntu: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 less
5.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.13
Ubuntu: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 less
5.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.8
Ubuntu: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 less
5.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-intel-5.13
Ubuntu: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-oem-5.10
Ubuntu: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 less
5.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.13
Ubuntu: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 less
5.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.14
Ubuntu: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 less
5.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.6
Ubuntu: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 less
5.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.11
Ubuntu: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 less
5.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.13
Ubuntu: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 less
5.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.8
Ubuntu: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
linux-raspi2
Ubuntu:20.04:LTS
All versions, plus listed versions
5.3.0-1007.85.3.0-1014.165.3.0-1015.175.3.0-1017.195.4.0-1004.45.4.0-1006.6
None known
linux-riscv
Ubuntu:20.04:LTS
All versions, plus listed versions
5.4.0-24.285.4.0-26.305.4.0-27.315.4.0-28.325.4.0-30.34
Show 7 moreShow less
5.4.0-31.355.4.0-33.375.4.0-34.385.4.0-36.415.4.0-37.425.4.0-39.445.4.0-40.45
None known
linux-riscv-5.11
Ubuntu:20.04:LTS
All versions, plus listed versions
5.11.0-1015.16~20.04.15.11.0-1017.18~20.04.15.11.0-1018.19~20.04.25.11.0-1020.21~20.04.15.11.0-1021.22~20.04.1
Show 8 moreShow less
5.11.0-1022.23~20.04.15.11.0-1023.24~20.04.15.11.0-1024.25~20.04.15.11.0-1026.28~20.04.15.11.0-1028.31~20.04.15.11.0-1029.32~20.04.15.11.0-1030.345.11.0-1031.35
None known
linux-riscv-5.8
Ubuntu:20.04:LTS
All versions, plus listed versions
5.8.0-14.16~20.04.15.8.0-14.16~20.04.35.8.0-16.18~20.04.15.8.0-17.19~20.04.15.8.0-18.20~20.04.1
Show 5 moreShow less
5.8.0-20.22~20.04.15.8.0-22.24~20.04.15.8.0-25.27~20.04.15.8.0-26.28~20.04.15.8.0-29.31~20.04.1
None known
linux-allwinner-5.19
Ubuntu:22.04:LTS
All versions, plus listed versions
5.19.0-1007.7~22.04.15.19.0-1009.9~22.04.15.19.0-1010.10~22.04.15.19.0-1011.11~22.04.15.19.0-1012.12~22.04.15.19.0-1013.13~22.04.15.19.0-1014.14~22.04.15.19.0-1015.15~22.04.1
None known
linux-aws-5.19
Ubuntu:22.04:LTS
All versions, plus listed versions
5.19.0-1019.20~22.04.15.19.0-1020.21~22.04.15.19.0-1022.23~22.04.15.19.0-1023.24~22.04.15.19.0-1024.25~22.04.1
Show 5 moreShow less
5.19.0-1025.26~22.04.15.19.0-1026.27~22.04.15.19.0-1027.28~22.04.15.19.0-1028.29~22.04.15.19.0-1029.30~22.04.1
None known
linux-aws-6.2
Ubuntu:22.04:LTS
All versions, plus listed versions
6.2.0-1005.5~22.04.16.2.0-1006.6~22.04.16.2.0-1007.7~22.04.16.2.0-1008.8~22.04.16.2.0-1009.9~22.04.3
Show 9 moreShow less
6.2.0-1010.10~22.04.16.2.0-1011.11~22.04.16.2.0-1012.12~22.04.16.2.0-1013.13~22.04.16.2.0-1014.14~22.04.16.2.0-1015.15~22.04.16.2.0-1016.16~22.04.16.2.0-1017.17~22.04.16.2.0-1018.18~22.04.1
None known
linux-aws-6.5
Ubuntu:22.04:LTS
All versions, plus listed versions
6.5.0-1008.8~22.04.16.5.0-1010.10~22.04.16.5.0-1011.11~22.04.16.5.0-1012.12~22.04.16.5.0-1014.14~22.04.1
Show 9 moreShow less
6.5.0-1015.15~22.04.16.5.0-1016.16~22.04.16.5.0-1017.17~22.04.26.5.0-1018.18~22.04.16.5.0-1020.20~22.04.16.5.0-1021.21~22.04.16.5.0-1022.22~22.04.16.5.0-1023.23~22.04.16.5.0-1024.24~22.04.1
None known
linux-azure-5.19
Ubuntu:22.04:LTS
All versions, plus listed versions
5.19.0-1020.21~22.04.15.19.0-1021.22~22.04.15.19.0-1022.23~22.04.15.19.0-1023.24~22.04.15.19.0-1025.28~22.04.15.19.0-1026.29~22.04.15.19.0-1027.30~22.04.2
None known
linux-azure-6.2
Ubuntu:22.04:LTS
All versions, plus listed versions
6.2.0-1005.5~22.04.16.2.0-1006.6~22.04.16.2.0-1007.7~22.04.16.2.0-1008.8~22.04.16.2.0-1009.9~22.04.3
Show 8 moreShow less
6.2.0-1011.11~22.04.16.2.0-1012.12~22.04.16.2.0-1014.14~22.04.16.2.0-1015.15~22.04.16.2.0-1016.16~22.04.16.2.0-1017.17~22.04.16.2.0-1018.18~22.04.16.2.0-1019.19~22.04.1
None known
linux-azure-6.5
Ubuntu:22.04:LTS
All versions, plus listed versions
6.5.0-1007.7~22.04.16.5.0-1009.9~22.04.16.5.0-1010.10~22.04.16.5.0-1011.11~22.04.16.5.0-1015.15~22.04.1
Show 9 moreShow less
6.5.0-1016.16~22.04.16.5.0-1017.17~22.04.16.5.0-1018.19~22.04.26.5.0-1019.20~22.04.16.5.0-1021.22~22.04.16.5.0-1022.23~22.04.16.5.0-1023.24~22.04.16.5.0-1024.25~22.04.16.5.0-1025.26~22.04.1
None known
linux-azure-fde-5.19
Ubuntu:22.04:LTS
All versions, plus listed versions
5.19.0-1025.28~22.04.1.15.19.0-1026.29~22.04.1.15.19.0-1027.30~22.04.2.1
None known
linux-azure-fde-6.2
Ubuntu:22.04:LTS
All versions, plus listed versions
6.2.0-1008.8~22.04.1.16.2.0-1009.9~22.04.3.16.2.0-1011.11~22.04.1.16.2.0-1012.12~22.04.1.16.2.0-1014.14~22.04.1.1
Show 5 moreShow less
6.2.0-1015.15~22.04.1.16.2.0-1016.16~22.04.1.16.2.0-1017.17~22.04.1.16.2.0-1018.18~22.04.1.16.2.0-1019.19~22.04.1.1
None known
linux-gcp-5.19
Ubuntu:22.04:LTS
All versions, plus listed versions
5.19.0-1020.22~22.04.25.19.0-1021.23~22.04.15.19.0-1022.24~22.04.15.19.0-1024.26~22.04.15.19.0-1025.27~22.04.15.19.0-1026.28~22.04.15.19.0-1027.29~22.04.15.19.0-1030.32~22.04.1
None known
linux-gcp-6.2
Ubuntu:22.04:LTS
All versions, plus listed versions
6.2.0-1009.9~22.04.36.2.0-1010.10~22.04.16.2.0-1011.11~22.04.16.2.0-1011.11~22.04.36.2.0-1012.12~22.04.1
Show 7 moreShow less
6.2.0-1013.13~22.04.16.2.0-1014.14~22.04.16.2.0-1016.18~22.04.16.2.0-1017.19~22.04.16.2.0-1018.20~22.04.16.2.0-1019.21~22.04.16.2.0-1021.23~22.04.1
None known
linux-gcp-6.5
Ubuntu:22.04:LTS
All versions, plus listed versions
6.5.0-1010.10~22.04.36.5.0-1011.11~22.04.16.5.0-1013.13~22.04.16.5.0-1014.14~22.04.16.5.0-1015.15~22.04.1
Show 8 moreShow less
6.5.0-1016.16~22.04.16.5.0-1017.17~22.04.16.5.0-1018.18~22.04.16.5.0-1020.20~22.04.16.5.0-1022.24~22.04.16.5.0-1023.25~22.04.16.5.0-1024.26~22.04.16.5.0-1025.27~22.04.1
None known
linux-hwe-5.19
Ubuntu:22.04:LTS
All versions, plus listed versions
5.19.0-28.29~22.04.15.19.0-32.33~22.04.15.19.0-35.36~22.04.15.19.0-38.39~22.04.15.19.0-40.41~22.04.1
Show 6 moreShow less
5.19.0-41.42~22.04.15.19.0-42.43~22.04.15.19.0-43.44~22.04.15.19.0-45.46~22.04.15.19.0-46.47~22.04.15.19.0-50.50
None known
linux-hwe-6.2
Ubuntu:22.04:LTS
All versions, plus listed versions
6.2.0-25.25~22.04.26.2.0-26.26~22.04.16.2.0-31.31~22.04.16.2.0-32.32~22.04.16.2.0-33.33~22.04.1
Show 5 moreShow less
6.2.0-34.34~22.04.16.2.0-35.35~22.04.16.2.0-36.37~22.04.16.2.0-37.38~22.04.16.2.0-39.40~22.04.1
None known
linux-hwe-6.5
Ubuntu:22.04:LTS
All versions, plus listed versions
6.5.0-14.14~22.04.16.5.0-15.15~22.04.16.5.0-17.17~22.04.16.5.0-18.18~22.04.16.5.0-21.21~22.04.1
Show 8 moreShow less
6.5.0-25.25~22.04.16.5.0-26.26~22.04.16.5.0-27.28~22.04.16.5.0-28.29~22.04.16.5.0-35.35~22.04.16.5.0-41.41~22.04.26.5.0-44.44~22.04.16.5.0-45.45~22.04.1
None known
linux-intel-iot-realtime
Ubuntu:22.04:LTS
All versions, plus listed versions
5.15.0-1073.75
None known
linux-lowlatency-hwe-5.19
Ubuntu:22.04:LTS
All versions, plus listed versions
5.19.0-1017.18~22.04.15.19.0-1018.19~22.04.15.19.0-1021.22~22.04.15.19.0-1022.23~22.04.15.19.0-1023.24~22.04.1
Show 5 moreShow less
5.19.0-1024.25~22.04.15.19.0-1025.26~22.04.15.19.0-1027.28~22.04.15.19.0-1028.29~22.04.15.19.0-1030.30
None known
linux-lowlatency-hwe-6.2
Ubuntu:22.04:LTS
All versions, plus listed versions
6.2.0-1008.8~22.04.16.2.0-1009.9~22.04.16.2.0-1011.11~22.04.16.2.0-1012.12~22.04.16.2.0-1013.13~22.04.1
Show 5 moreShow less
6.2.0-1014.14~22.04.16.2.0-1015.15~22.04.16.2.0-1016.16~22.04.16.2.0-1017.17~22.04.16.2.0-1018.18~22.04.1
None known
linux-lowlatency-hwe-6.5
Ubuntu:22.04:LTS
All versions, plus listed versions
6.5.0-14.14.1~22.04.16.5.0-15.15.1.1~22.04.16.5.0-17.17.1.1.1~22.04.16.5.0-21.21.1~22.04.16.5.0-25.25.1~22.04.1
Show 8 moreShow less
6.5.0-26.26.1~22.04.16.5.0-27.28.1~22.04.16.5.0-28.29.1~22.04.16.5.0-35.35.1~22.04.16.5.0-41.41.1~22.04.16.5.0-42.42.1~22.04.16.5.0-44.44.1~22.04.16.5.0-45.45.1~22.04.1
None known
linux-nvidia-6.2
Ubuntu:22.04:LTS
All versions, plus listed versions
6.2.0-1003.3~22.04.16.2.0-1009.96.2.0-1010.106.2.0-1011.116.2.0-1012.126.2.0-1013.136.2.0-1015.15
None known
linux-nvidia-6.5
Ubuntu:22.04:LTS
All versions, plus listed versions
6.5.0-1004.46.5.0-1007.76.5.0-1013.136.5.0-1014.146.5.0-1015.15
Show 6 moreShow less
6.5.0-1018.186.5.0-1019.196.5.0-1021.226.5.0-1022.236.5.0-1023.246.5.0-1024.25
None known
linux-oem-5.17
Ubuntu:22.04:LTS
All versions, plus listed versions
5.17.0-1003.35.17.0-1004.45.17.0-1006.65.17.0-1011.125.17.0-1012.13
Show 21 moreShow less
5.17.0-1013.145.17.0-1014.155.17.0-1015.165.17.0-1016.175.17.0-1017.185.17.0-1018.195.17.0-1019.205.17.0-1020.215.17.0-1021.225.17.0-1024.255.17.0-1025.265.17.0-1026.275.17.0-1027.285.17.0-1028.295.17.0-1029.305.17.0-1030.315.17.0-1031.325.17.0-1032.335.17.0-1033.345.17.0-1034.355.17.0-1035.36
None known
linux-oem-6.0
Ubuntu:22.04:LTS
All versions, plus listed versions
6.0.0-1006.66.0.0-1007.76.0.0-1008.86.0.0-1009.96.0.0-1010.10
Show 11 moreShow less
6.0.0-1011.116.0.0-1012.126.0.0-1013.136.0.0-1014.146.0.0-1015.156.0.0-1016.166.0.0-1017.176.0.0-1018.186.0.0-1019.196.0.0-1020.206.0.0-1021.21
None known
linux-oem-6.1
Ubuntu:22.04:LTS
All versions, plus listed versions
6.1.0-1004.46.1.0-1006.66.1.0-1007.76.1.0-1008.86.1.0-1009.9
Show 22 moreShow less
6.1.0-1010.106.1.0-1012.126.1.0-1013.136.1.0-1014.146.1.0-1015.156.1.0-1016.166.1.0-1017.176.1.0-1019.196.1.0-1020.206.1.0-1021.216.1.0-1022.226.1.0-1023.236.1.0-1024.246.1.0-1025.256.1.0-1026.266.1.0-1027.276.1.0-1028.286.1.0-1029.296.1.0-1033.336.1.0-1034.346.1.0-1035.356.1.0-1036.36
None known
linux-oem-6.5
Ubuntu:22.04:LTS
All versions, plus listed versions
6.5.0-1003.36.5.0-1004.46.5.0-1006.66.5.0-1007.76.5.0-1008.8
Show 14 moreShow less
6.5.0-1009.106.5.0-1011.126.5.0-1013.146.5.0-1014.156.5.0-1015.166.5.0-1016.176.5.0-1018.196.5.0-1019.206.5.0-1020.216.5.0-1022.236.5.0-1023.246.5.0-1024.256.5.0-1025.266.5.0-1027.28
None known
linux-oracle-6.5
Ubuntu:22.04:LTS
All versions, plus listed versions
6.5.0-1013.13~22.04.46.5.0-1014.14~22.04.16.5.0-1015.15~22.04.16.5.0-1016.16~22.04.16.5.0-1018.18~22.04.1
Show 8 moreShow less
6.5.0-1019.19~22.04.16.5.0-1020.20~22.04.16.5.0-1021.21~22.04.16.5.0-1023.23~22.04.16.5.0-1024.24~22.04.16.5.0-1025.25~22.04.16.5.0-1026.26~22.04.16.5.0-1027.27~22.04.1
None known
linux-realtime
Ubuntu:22.04:LTS
All versions, plus listed versions
5.15.0-1032.35
None known
linux-riscv
Ubuntu:22.04:LTS
All versions, plus listed versions
5.13.0-1004.45.13.0-1006.6+22.04.15.13.0-1007.7+22.04.15.13.0-1010.11+22.04.15.15.0-1004.4
Show 18 moreShow less
5.15.0-1005.55.15.0-1006.65.15.0-1007.75.15.0-1008.85.15.0-1011.125.15.0-1012.135.15.0-1014.165.15.0-1015.175.15.0-1016.185.15.0-1017.195.15.0-1018.215.15.0-1019.225.15.0-1020.235.15.0-1022.265.15.0-1023.275.15.0-1026.305.15.0-1027.315.15.0-1028.32
None known
linux-riscv-5.19
Ubuntu:22.04:LTS
All versions, plus listed versions
5.19.0-1012.13~22.04.15.19.0-1015.16~22.04.15.19.0-1016.17~22.04.15.19.0-1017.18~22.04.15.19.0-1018.19~22.04.15.19.0-1019.21~22.04.15.19.0-1020.22~22.04.15.19.0-1021.23~22.04.1
None known
linux-riscv-6.5
Ubuntu:22.04:LTS
All versions, plus listed versions
6.5.0-17.17.1.1~22.04.16.5.0-21.21.1~22.04.16.5.0-25.25.1~22.04.16.5.0-26.26.1~22.04.16.5.0-27.28.1~22.04.1
Show 5 moreShow less
6.5.0-28.29.1~22.04.16.5.0-35.35.1~22.04.16.5.0-40.40.1~22.04.16.5.0-42.42.1~22.04.16.5.0-45.45.1~22.04.1
None known
linux-starfive-5.19
Ubuntu:22.04:LTS
All versions, plus listed versions
5.19.0-1014.16~22.04.15.19.0-1015.17~22.04.15.19.0-1016.18~22.04.15.19.0-1017.19~22.04.15.19.0-1018.20~22.04.15.19.0-1019.21~22.04.15.19.0-1020.22~22.04.1
None known
linux-starfive-6.2
Ubuntu:22.04:LTS
All versions, plus listed versions
6.2.0-1006.7~22.04.16.2.0-1007.8~22.04.16.2.0-1009.10~22.04.1
None known
linux-starfive-6.5
Ubuntu:22.04:LTS
All versions, plus listed versions
6.5.0-1007.8~22.04.16.5.0-1008.9~22.04.16.5.0-1009.10~22.04.16.5.0-1010.11~22.04.16.5.0-1011.12~22.04.1
Show 6 moreShow less
6.5.0-1012.13~22.04.16.5.0-1014.15~22.04.16.5.0-1015.16~22.04.16.5.0-1016.17~22.04.16.5.0-1017.18~22.04.16.5.0-1018.19~22.04.1
None known
linux-aws-6.14
Ubuntu:24.04:LTS
All versions, plus listed versions
6.14.0-1007.7~24.04.16.14.0-1009.9~24.04.16.14.0-1010.10~24.04.16.14.0-1011.11~24.04.16.14.0-1012.12~24.04.1
Show 6 moreShow less
6.14.0-1013.13~24.04.16.14.0-1014.14~24.04.16.14.0-1015.15~24.04.16.14.0-1016.16~24.04.16.14.0-1017.17~24.04.16.14.0-1018.18~24.04.1
None known
linux-azure-6.11
Ubuntu:24.04:LTS
All versions, plus listed versions
6.11.0-1008.8~24.04.16.11.0-1012.12~24.04.16.11.0-1013.13~24.04.16.11.0-1014.14~24.04.16.11.0-1015.15~24.04.16.11.0-1017.17~24.04.16.11.0-1018.18~24.04.1
None known
linux-azure-6.14
Ubuntu:24.04:LTS
All versions, plus listed versions
6.14.0-1010.10~24.04.16.14.0-1012.12~24.04.16.14.0-1013.13~24.04.16.14.0-1014.14~24.04.16.14.0-1017.17~24.04.1
None known
linux-azure-fde-6.14
Ubuntu:24.04:LTS
All versions, plus listed versions
6.14.0-1012.12~24.04.16.14.0-1013.13~24.04.16.14.0-1014.14~24.04.16.14.0-1015.15~24.04.16.14.0-1017.17~24.04.1
None known
linux-azure-nvidia-6.14
Ubuntu:24.04:LTS
All versions, plus listed versions
6.14.0-1003.36.14.0-1006.66.14.0-1007.7
None known
linux-gcp-6.11
Ubuntu:24.04:LTS
All versions, plus listed versions
6.11.0-1006.6~24.04.26.11.0-1011.11~24.04.16.11.0-1013.13~24.04.16.11.0-1014.14~24.04.16.11.0-1015.15~24.04.16.11.0-1016.16~24.04.16.11.0-1017.17~24.04.1
None known
linux-gcp-6.14
Ubuntu:24.04:LTS
All versions, plus listed versions
6.14.0-1007.7~24.04.16.14.0-1011.11~24.04.16.14.0-1012.12~24.04.16.14.0-1014.15~24.04.16.14.0-1015.16~24.04.1
Show 6 moreShow less
6.14.0-1016.17~24.04.16.14.0-1017.18~24.04.16.14.0-1018.19~24.04.16.14.0-1019.20~24.04.16.14.0-1020.21~24.04.16.14.0-1021.22~24.04.1
None known
linux-hwe-6.11
Ubuntu:24.04:LTS
All versions, plus listed versions
6.11.0-17.17~24.04.26.11.0-19.19~24.04.16.11.0-21.21~24.04.16.11.0-24.24~24.04.16.11.0-25.25~24.04.16.11.0-26.26~24.04.16.11.0-28.28~24.04.16.11.0-29.29~24.04.1
None known
linux-hwe-6.14
Ubuntu:24.04:LTS
All versions, plus listed versions
6.14.0-24.24~24.04.36.14.0-27.27~24.04.16.14.0-28.28~24.04.16.14.0-29.29~24.04.16.14.0-32.32~24.04.1
Show 5 moreShow less
6.14.0-33.33~24.04.16.14.0-34.34~24.04.16.14.0-35.35~24.04.16.14.0-36.36~24.04.16.14.0-37.37~24.04.1
None known
linux-intel
Ubuntu:24.04:LTS
All versions, plus listed versions
6.8.0-1005.126.8.0-1006.136.8.0-1007.14
None known
linux-lowlatency-hwe-6.11
Ubuntu:24.04:LTS
All versions, plus listed versions
6.11.0-1009.10~24.04.16.11.0-1011.12~24.04.16.11.0-1012.13~24.04.16.11.0-1013.14~24.04.16.11.0-1014.15~24.04.16.11.0-1015.16~24.04.26.11.0-1016.17~24.04.1
None known
linux-nvidia-6.11
Ubuntu:24.04:LTS
All versions, plus listed versions
6.11.0-1002.26.11.0-1003.36.11.0-1007.76.11.0-1010.106.11.0-1011.116.11.0-1012.126.11.0-1013.136.11.0-1016.16
None known
linux-oem-6.11
Ubuntu:24.04:LTS
All versions, plus listed versions
6.11.0-1007.76.11.0-1008.86.11.0-1009.96.11.0-1010.106.11.0-1011.11
Show 13 moreShow less
6.11.0-1012.126.11.0-1013.136.11.0-1015.156.11.0-1016.166.11.0-1017.176.11.0-1018.186.11.0-1020.206.11.0-1021.216.11.0-1022.226.11.0-1023.236.11.0-1024.246.11.0-1025.256.11.0-1027.27
None known
linux-oem-6.14
Ubuntu:24.04:LTS
All versions, plus listed versions
6.14.0-1004.46.14.0-1005.56.14.0-1006.66.14.0-1007.76.14.0-1008.8
Show 11 moreShow less
6.14.0-1010.106.14.0-1011.116.14.0-1012.126.14.0-1013.136.14.0-1014.146.14.0-1015.156.14.0-1016.166.14.0-1017.176.14.0-1018.186.14.0-1019.196.14.0-1020.20
None known
linux-oem-6.8
Ubuntu:24.04:LTS
All versions, plus listed versions
6.8.0-1003.36.8.0-1004.46.8.0-1005.56.8.0-1006.66.8.0-1007.7
Show 21 moreShow less
6.8.0-1008.86.8.0-1009.96.8.0-1010.106.8.0-1011.116.8.0-1012.126.8.0-1013.136.8.0-1014.146.8.0-1016.166.8.0-1017.176.8.0-1018.186.8.0-1019.196.8.0-1020.206.8.0-1024.246.8.0-1025.256.8.0-1026.266.8.0-1027.276.8.0-1028.286.8.0-1029.296.8.0-1030.306.8.0-1031.316.8.0-1032.32
None known
linux-oracle-6.14
Ubuntu:24.04:LTS
All versions, plus listed versions
6.14.0-1007.7~24.04.16.14.0-1009.9~24.04.16.14.0-1010.10~24.04.16.14.0-1011.11~24.04.16.14.0-1012.12~24.04.1
Show 6 moreShow less
6.14.0-1013.13~24.04.16.14.0-1014.14~24.04.16.14.0-1015.15~24.04.16.14.0-1016.16~24.04.16.14.0-1017.17~24.04.16.14.0-1018.18~24.04.1
None known
linux-raspi-realtime
Ubuntu:24.04:LTS
All versions, plus listed versions
6.8.0-2019.20
None known
linux-realtime
Ubuntu:24.04:LTS
All versions, plus listed versions
6.8.1-1015.16
None known
linux-riscv
Ubuntu:24.04:LTS
All versions, plus listed versions
6.5.0-9.9.16.8.0-20.20.16.8.0-28.28.16.8.0-31.31.16.8.0-35.35.1
Show 19 moreShow less
6.8.0-36.36.16.8.0-38.38.16.8.0-39.39.16.8.0-40.40.16.8.0-41.41.16.8.0-44.44.16.8.0-47.47.16.8.0-48.48.16.8.0-49.49.16.8.0-50.51.16.8.0-51.52.16.8.0-52.53.16.8.0-53.55.16.8.0-55.57.16.8.0-56.58.16.8.0-57.59.16.8.0-58.60.16.8.0-59.61.16.8.0-60.63.1
None known
linux-riscv-6.14
Ubuntu:24.04:LTS
All versions, plus listed versions
6.14.0-22.22.1~24.04.16.14.0-23.23.1~24.04.16.14.0-24.24.1~24.04.16.14.0-27.27.1~24.04.16.14.0-28.28.1~24.04.1
Show 7 moreShow less
6.14.0-29.29.1~24.04.16.14.0-32.32.1~24.04.16.14.0-33.33.1~24.04.16.14.0-34.34.1~24.04.16.14.0-35.35.1~24.04.16.14.0-36.36.1~24.04.16.14.0-37.37.1~24.04.1
None known
linux-realtime-6.14
Ubuntu:Pro:Realtime:24.04:LTS
All versions, plus listed versions
6.14.0-1003.3~24.04.36.14.0-1010.10~24.04.16.14.0-1011.11~24.04.16.14.0-1012.12~24.04.16.14.0-1013.13~24.04.1
Show 4 moreShow less
6.14.0-1014.14~24.04.16.14.0-1015.15~24.04.16.14.0-1016.16~24.04.16.14.0-1017.17~24.04.1
None known
linux-azure-fde
Ubuntu:25.10
All versions, plus listed versions
6.17.0-1003.36.17.0-1004.46.17.0-1005.56.17.0-1007.76.17.0-1008.8
Show 5 moreShow less
6.17.0-1010.106.17.0-1012.126.17.0-1014.146.17.0-1015.156.17.0-1017.17
None known
dtb-aarch64
openSUSE:Leap 16.0
From an advisory covering 573 CVEs
before 6.12.0-160000.6.1
6.12.0-160000.6.1
kernel-64kb
openSUSE:Leap 16.0
From an advisory covering 573 CVEs
before 6.12.0-160000.6.1
6.12.0-160000.6.1
kernel-default
openSUSE:Leap 16.0
From an advisory covering 573 CVEs
before 6.12.0-160000.6.1
6.12.0-160000.6.1
kernel-default-base
openSUSE:Leap 16.0
From an advisory covering 573 CVEs
before 6.12.0-160000.6.1.160000.2.4
6.12.0-160000.6.1.160000.2.4
kernel-docs
openSUSE:Leap 16.0
From an advisory covering 573 CVEs
before 6.12.0-160000.6.1
6.12.0-160000.6.1
kernel-kvmsmall
openSUSE:Leap 16.0
From an advisory covering 573 CVEs
before 6.12.0-160000.6.1
6.12.0-160000.6.1
kernel-obs-build
openSUSE:Leap 16.0
From an advisory covering 573 CVEs
before 6.12.0-160000.6.1
6.12.0-160000.6.1
kernel-obs-qa
openSUSE:Leap 16.0
From an advisory covering 573 CVEs
before 6.12.0-160000.6.1
6.12.0-160000.6.1
kernel-rt
openSUSE:Leap 16.0
From an advisory covering 573 CVEs
before 6.12.0-160000.6.1
6.12.0-160000.6.1
kernel-source
openSUSE:Leap 16.0
From an advisory covering 573 CVEs
before 6.12.0-160000.6.1
6.12.0-160000.6.1
kernel-syms
openSUSE:Leap 16.0
From an advisory covering 573 CVEs
before 6.12.0-160000.6.1
6.12.0-160000.6.1
kernel-zfcpdump
openSUSE:Leap 16.0
From an advisory covering 573 CVEs
before 6.12.0-160000.6.1
6.12.0-160000.6.1

History

History
RecordedChangedSources
affected, aliases
affected, facts
affectedOSV
first indexedCVE List, EUVD, GitHub Advisories, NVD, OSV

Dates are when Every CVE recorded each change. Upstream dates may differ.

In short

CVE-2025-39791 is a high vulnerability (CVSS 7.8) in Linux, published September 11, 2025. No source lists public exploit code. EPSS puts the chance of exploitation in the next 30 days at 0.14%, the 3rd percentile. Fixed in linux-lts 6.12.44-r0.

References

Show 194 moreShow less
This page doesn't list everything

Left out here: 44 versions, 1,058 references and the rest of 5 source descriptions. The JSON record has them.

PagesAll vulnerabilitiesBrowseDocsSourcesGuideGet API key
MoveEnter Open