CVE-2024-38636
f2fs: multidev: fix to recognize valid zero block address
In the Linux kernel, the following vulnerability has been resolved:
f2fs: multidev: fix to recognize valid zero block address
As reported by Yi Zhang in mailing list [1], kernel warning was catched during zbd/010 test as below:
./check zbd/010 zbd/010 (test gap zone support with F2FS) [failed] runtime ... 3.752s something found in dmesg: [ 4378.146781] run blktests zbd/010 at 2024-02-18 11:31:13 [ 4378.192349] null_blk: module loaded [ 4378.209860] null_blk: disk nullb0 created [ 4378.413285] scsi_debug:sdebug_driver_probe: scsi_debug: trim poll_queues to 0. poll_q/nr_hw = (0/1) [ 4378.422334] scsi host15: scsi_debug: version 0191 [20210520] dev_size_mb=1024, opts=0x0, submit_queues=1, statistics=0 [ 4378.434922] scsi 15:0:0:0: Direct-Access-ZBC Linux scsi_debug 0191 PQ: 0 ANSI: 7 [ 4378.443343] scsi 15:0:0:0: Power-on or device reset occurred [ 4378.449371] sd 15:0:0:0: Attached scsi generic sg5 type 20 [ 4378.449418] sd 15:0:0:0: [sdf] Host-managed zoned block device ... (See '/mnt/tests/gitlab.com/api/v4/projects/19168116/repository/archive.zip/storage/blktests/blk/blktests/results/nodev/zbd/010.dmesg'
WARNING: CPU: 22 PID: 44011 at fs/iomap/iter.c:51 CPU: 22 PID: 44011 Comm: fio Not tainted 6.8.0-rc3+ #1 RIP: 0010:iomap_iter+0x32b/0x350 Call Trace: <TASK> __iomap_dio_rw+0x1df/0x830 f2fs_file_read_iter+0x156/0x3d0 [f2fs] aio_read+0x138/0x210 io_submit_one+0x188/0x8c0 __x64_sys_io_submit+0x8c/0x1a0 do_syscall_64+0x86/0x170 entry_SYSCALL_64_after_hwframe+0x6e/0x76
Shinichiro Kawasaki helps to analyse this issue and proposes a potential fixing patch in [2].
Quoted from reply of Shinichiro Kawasaki:
"I confirmed that the trigger commit is dbf8e63f48af as Yi reported. I took a look in the commit, but it looks fine to me. So I thought the cause is not in the commit diff.
I found the WARN is printed when the f2fs is set up with multiple devices, and read requests are mapped to the very first block of the second device in the direct read path. In this case, f2fs_map_blocks() and f2fs_map_blocks_cached() modify map->m_pblk as the physical block address from each block device. It becomes zero when it is mapped to the first block of the device. However, f2fs_iomap_begin() assumes that map->m_pblk is the physical block address of the whole f2fs, across the all block devices. It compares map->m_pblk against NULL_ADDR == 0, then go into the unexpected branch and sets the invalid iomap->length. The WARN catches the invalid iomap->length.
This WARN is printed even for non-zoned block devices, by following steps.
- Create two (non-zoned) null_blk devices memory backed with 128MB size each: nullb0 and nullb1.
mkfs.f2fs /dev/nullb0 -c /dev/nullb1
mount -t f2fs /dev/nullb0 "${mount_dir}"
dd if=/dev/zero of="${mount_dir}/test.dat" bs=1M count=192
dd if="${mount_dir}/test.dat" of=/dev/null bs=1M count=192 iflag=direct
..."
So, the root cause of this issue is: when multi-devices feature is on, f2fs_map_blocks() may return zero blkaddr in non-primary device, which is a verified valid block address, however, f2fs_iomap_begin() treats it as an invalid block address, and then it triggers the warning in iomap framework code.
Finally, as discussed, we decide to use a more simple and direct way that checking (map.m_flags & F2FS_MAP_MAPPED) condition instead of (map.m_pblk != NULL_ADDR) to fix this issue.
Thanks a lot for the effort of Yi Zhang and Shinichiro Kawasaki on this issue.
[1] https://lore.kernel.org/linux-f2fs-devel/CAHj4cs-kfojYC9i0G73PRkYzcxCTex=-vugRFeP40g_URGvnfQ@mail.gmail.com/ [2] https://lore.kernel.org/linux-f2fs-devel/gngdj77k4picagsfdtiaa7gpgnup6fsgwzsltx6milmhegmjff@iax2n4wvrqye/
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
- None
- Integrity
- None
- Availability
- High
Exploit likelihood
What each source reports
NVD Score used
5.5
In the Linux kernel, the following vulnerability has been resolved:
f2fs: multidev: fix to recognize valid zero block address
As reported by Yi Zhang in mailing list [1], kernel warning was catched during zbd/010 test as below:
./check zbd/010 zbd/010 (test gap zone support with F2FS) [failed] runtime ... 3.752s something found in dmesg: [ 4378.146781] run blktests zbd/010 at 2024-02-18 11:31:13 [ 4378.192349] null_blk: module loaded [ 4378.209860] null_blk: disk nullb0 created [ 4378.413285] scsi_debug:sdebug_driver_probe: scsi_debug: trim poll_queues to 0. poll_q/nr_hw = (0/1) [ 4378.422334] scsi host15: scsi_debug: version 0191 [20210520] dev_size_mb=1024, opts=0x0, submit_queues=1, statistics=0 [ 4378.434922] scsi 15:0:0:0: Direct-Access-ZBC Linux scsi_debug 0191 PQ: 0 ANSI: 7 [ 4378.443343] scsi 15:0:0:0: Power-on or device reset occurred [ 4378.449371] sd 15:0:0:0: Attached scsi generic sg5 type 20 [ 4378.449418] sd 15:0:0:0: [sdf] Host-managed zoned block device ... (See '/mnt/tests/gitlab.com/api/v4/projects/19168116/repository/archive.zip/storage/blktests/blk/blktests/results/nodev/zbd/010.dmesg'
WARNING: CPU: 22 PID: 44011 at fs/iomap/iter.c:51 CPU: 22 PID: 44011 Comm: fio Not tainted 6.8.0-rc3+ #1 RIP: 0010:iomap_iter+0x32b/0x350 Call Trace: <TASK> __iomap_dio_rw+0x1df/0x830 f2fs_file_read_iter+0x156/0x3d0 [f2fs] aio_read+0x138/0x210 io_submit_one+0x188/0x8c0 __x64_sys_io_submit+0x8c/0x1a0 do_syscall_64+0x86/0x170 entry_SYSCALL_64_after_hwframe+0x6e/0x76
Shinichiro Kawasaki helps to analyse this issue and proposes a potential fixing patch in [2].
Quoted from reply of Shinichiro Kawasaki:
"I confirmed that the trigger commit is dbf8e63f48af as Yi reported. I took a look in the commit, but it looks fine to me. So I thought the cause is not in the commit diff.
I found the WARN is printed when the f2fs is set up with multiple devices, and read requests are mapped to the very first block of the second device in the direct read path. In this case, f2fs_map_blocks() and f2fs_map_blocks_cached() modify map->m_pblk as the physical block address from each block device. It becomes zero when it is mapped to the first block of the device. However, f2fs_iomap_begin() assumes that map->m_pblk is the physical block address of the whole f2fs, across the all block devices. It compares map->m_pblk against NULL_ADDR == 0, then go into the unexpected branch and sets the invalid iomap->length. The WARN catches the invalid iomap->length.
This WARN is printed even for non-zoned block devices, by following steps.
- Create two (non-zoned) null_blk devices memory backed with 128MB size each: nullb0 and nullb1.
mkfs.f2fs /dev/nullb0 -c /dev/nullb1
mount -t f2fs /dev/nullb0 "${mount_dir}"
dd if=/dev/zero of="${mount_dir}/test.dat" bs=1M count=192
dd if="${mount_dir}/test.dat" of=/dev/null bs=1M count=192 iflag=direct
..."
So, the root cause of this issue is: when multi-devices feature is on, f2fs_map_blocks() may return zero blkaddr in non-primary device, which is a verified valid block address, however, f2fs_iomap_begin() treats it as an invalid block address, and then it triggers the warning in iomap framework code.
Finally, as discussed, we decide to use a more simple and direct way that checking (map.m_flags & F2FS_MAP_MAPPED) condition instead of (map.m_pblk != NULL_ADDR) to fix this issue.
Thanks a lot for the effort of Yi Zhang and Shinichiro Kawasaki on this issue.
[1] https://lore.kernel.org/linux-f2fs-devel/CAHj4cs-kfojYC9i0G73PRkYzcxCTex=-vugRFeP40g_URGvnfQ@mail.gmail.com/ [2] https://lore.kernel.org/linux-f2fs-devel/gngdj77k4picagsfdtiaa7gpgnup6fsgwzsltx6milmhegmjff@iax2n4wvrqye/
- Record
CVE-2024-38636- CVSS 3.1
- 5.5 Medium
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H - Updated
- 2026-11-02
CVE List No score
f2fs: multidev: fix to recognize valid zero block address
In the Linux kernel, the following vulnerability has been resolved:
f2fs: multidev: fix to recognize valid zero block address
As reported by Yi Zhang in mailing list [1], kernel warning was catched during zbd/010 test as below:
./check zbd/010 zbd/010 (test gap zone support with F2FS) [failed] runtime ... 3.752s something found in dmesg: [ 4378.146781] run blktests zbd/010 at 2024-02-18 11:31:13 [ 4378.192349] null_blk: module loaded [ 4378.209860] null_blk: disk nullb0 created [ 4378.413285] scsi_debug:sdebug_driver_probe: scsi_debug: trim poll_queues to 0. poll_q/nr_hw = (0/1) [ 4378.422334] scsi host15: scsi_debug: version 0191 [20210520] dev_size_mb=1024, opts=0x0, submit_queues=1, statistics=0 [ 4378.434922] scsi 15:0:0:0: Direct-Access-ZBC Linux scsi_debug 0191 PQ: 0 ANSI: 7 [ 4378.443343] scsi 15:0:0:0: Power-on or device reset occurred [ 4378.449371] sd 15:0:0:0: Attached scsi generic sg5 type 20 [ 4378.449418] sd 15:0:0:0: [sdf] Host-managed zoned block device ... (See '/mnt/tests/gitlab.com/api/v4/projects/19168116/repository/archive.zip/storage/blktests/blk/blktests/results/nodev/zbd/010.dmesg'
WARNING: CPU: 22 PID: 44011 at fs/iomap/iter.c:51 CPU: 22 PID: 44011 Comm: fio Not tainted 6.8.0-rc3+ #1 RIP: 0010:iomap_iter+0x32b/0x350 Call Trace: <TASK> __iomap_dio_rw+0x1df/0x830 f2fs_file_read_iter+0x156/0x3d0 [f2fs] aio_read+0x138/0x210 io_submit_one+0x188/0x8c0 __x64_sys_io_submit+0x8c/0x1a0 do_syscall_64+0x86/0x170 entry_SYSCALL_64_after_hwframe+0x6e/0x76
Shinichiro Kawasaki helps to analyse this issue and proposes a potential fixing patch in [2].
Quoted from reply of Shinichiro Kawasaki:
"I confirmed that the trigger commit is dbf8e63f48af as Yi reported. I took a look in the commit, but it looks fine to me. So I thought the cause is not in the commit diff.
I found the WARN is printed when the f2fs is set up with multiple devices, and read requests are mapped to the very first block of the second device in the direct read path. In this case, f2fs_map_blocks() and f2fs_map_blocks_cached() modify map->m_pblk as the physical block address from each block device. It becomes zero when it is mapped to the first block of the device. However, f2fs_iomap_begin() assumes that map->m_pblk is the physical block address of the whole f2fs, across the all block devices. It compares map->m_pblk against NULL_ADDR == 0, then go into the unexpected branch and sets the invalid iomap->length. The WARN catches the invalid iomap->length.
This WARN is printed even for non-zoned block devices, by following steps.
- Create two (non-zoned) null_blk devices memory backed with 128MB size each: nullb0 and nullb1.
mkfs.f2fs /dev/nullb0 -c /dev/nullb1
mount -t f2fs /dev/nullb0 "${mount_dir}"
dd if=/dev/zero of="${mount_dir}/test.dat" bs=1M count=192
dd if="${mount_dir}/test.dat" of=/dev/null bs=1M count=192 iflag=direct
..."
So, the root cause of this issue is: when multi-devices feature is on, f2fs_map_blocks() may return zero blkaddr in non-primary device, which is a verified valid block address, however, f2fs_iomap_begin() treats it as an invalid block address, and then it triggers the warning in iomap framework code.
Finally, as discussed, we decide to use a more simple and direct way that checking (map.m_flags & F2FS_MAP_MAPPED) condition instead of (map.m_pblk != NULL_ADDR) to fix this issue.
Thanks a lot for the effort of Yi Zhang and Shinichiro Kawasaki on this issue.
[1] https://lore.kernel.org/linux-f2fs-devel/CAHj4cs-kfojYC9i0G73PRkYzcxCTex=-vugRFeP40g_URGvnfQ@mail.gmail.com/ [2] https://lore.kernel.org/linux-f2fs-devel/gngdj77k4picagsfdtiaa7gpgnup6fsgwzsltx6milmhegmjff@iax2n4wvrqye/
- Record
CVE-2024-38636- Updated
- 2026-11-02
EUVDEUVD-2024-37499 No score
In the Linux kernel, the following vulnerability has been resolved:
f2fs: multidev: fix to recognize valid zero block address
As reported by Yi Zhang in mailing list [1], kernel warning was catched during zbd/010 test as below:
./check zbd/010 zbd/010 (test gap zone support with F2FS) [failed] runtime ... 3.752s something found in dmesg: [ 4378.146781] run blktests zbd/010 at 2024-02-18 11:31:13 [ 4378.192349] null_blk: module loaded [ 4378.209860] null_blk: disk nullb0 created [ 4378.413285] scsi_debug:sdebug_driver_probe: scsi_debug: trim poll_queues to 0. poll_q/nr_hw = (0/1) [ 4378.422334] scsi host15: scsi_debug: version 0191 [20210520] dev_size_mb=1024, opts=0x0, submit_queues=1, statistics=0 [ 4378.434922] scsi 15:0:0:0: Direct-Access-ZBC Linux scsi_debug 0191 PQ: 0 ANSI: 7 [ 4378.443343] scsi 15:0:0:0: Power-on or device reset occurred [ 4378.449371] sd 15:0:0:0: Attached scsi generic sg5 type 20 [ 4378.449418] sd 15:0:0:0: [sdf] Host-managed zoned block device ... (See '/mnt/tests/gitlab.com/api/v4/projects/19168116/repository/archive.zip/storage/blktests/blk/blktests/results/nodev/zbd/010.dmesg'
WARNING: CPU: 22 PID: 44011 at fs/iomap/iter.c:51 CPU: 22 PID: 44011 Comm: fio Not tainted 6.8.0-rc3+ #1 RIP: 0010:iomap_iter+0x32b/0x350 Call Trace: <TASK> __iomap_dio_rw+0x1df/0x830 f2fs_file_read_iter+0x156/0x3d0 [f2fs] aio_read+0x138/0x210 io_submit_one+0x188/0x8c0 __x64_sys_io_submit+0x8c/0x1a0 do_syscall_64+0x86/0x170 entry_SYSCALL_64_after_hwframe+0x6e/0x76
Shinichiro Kawasaki helps to analyse this issue and proposes a potential fixing patch in [2].
Quoted from reply of Shinichiro Kawasaki:
"I confirmed that the trigger commit is dbf8e63f48af as Yi reported. I took a look in the commit, but it looks fine to me. So I thought the cause is not in the commit diff.
I found the WARN is printed when the f2fs is set up with multiple devices, and read requests are mapped to the very first block of the second device in the direct read path. In this case, f2fs_map_blocks() and f2fs_map_blocks_cached() modify map->m_pblk as the physical block address from each block device. It becomes zero when it is mapped to the first block of the device. However, f2fs_iomap_begin() assumes that map->m_pblk is the physical block address of the whole f2fs, across the all block devices. It compares map->m_pblk against NULL_ADDR == 0, then go into the unexpected branch and sets the invalid iomap->length. The WARN catches the invalid iomap->length.
This WARN is printed even for non-zoned block devices, by following steps.
- Create two (non-zoned) null_blk devices memory backed with 128MB size each: nullb0 and nullb1.
mkfs.f2fs /dev/nullb0 -c /dev/nullb1
mount -t f2fs /dev/nullb0 "${mount_dir}"
dd if=/dev/zero of="${mount_dir}/test.dat" bs=1M count=192
dd if="${mount_dir}/test.dat" of=/dev/null bs=1M count=192 iflag=direct
..."
So, the root cause of this issue is: when multi-devices feature is on, f2fs_map_blocks() may return zero blkaddr in non-primary device, which is a verified valid block address, however, f2fs_iomap_begin() treats it as an invalid block address, and then it triggers the warning in iomap framework code.
Finally, as discussed, we decide to use a more simple and direct way that checking (map.m_flags & F2FS_MAP_MAPPED) condition instead of (map.m_pblk != NULL_ADDR) to fix this issue.
Thanks a lot for the effort of Yi Zhang and Shinichiro Kawasaki on this issue.
[1] https://lore.kernel.org/linux-f2fs-devel/CAHj4cs-kfojYC9i0G73PRkYzcxCTex=-vugRFeP40g_URGvnfQ@mail.gmail.com/ [2] https://lore.kernel.org/linux-f2fs-devel/gngdj77k4picagsfdtiaa7gpgnup6fsgwzsltx6milmhegmjff@iax2n4wvrqye/
- Record
EUVD-2024-37499- Updated
- 2026-11-02
GitHub AdvisoriesGHSA-pwgj-c4vj-63r9
5.5
In the Linux kernel, the following vulnerability has been resolved: f2fs: multidev: fix to...
In the Linux kernel, the following vulnerability has been resolved:
f2fs: multidev: fix to recognize valid zero block address
As reported by Yi Zhang in mailing list [1], kernel warning was catched during zbd/010 test as below:
./check zbd/010 zbd/010 (test gap zone support with F2FS) [failed] runtime ... 3.752s something found in dmesg: [ 4378.146781] run blktests zbd/010 at 2024-02-18 11:31:13 [ 4378.192349] null_blk: module loaded [ 4378.209860] null_blk: disk nullb0 created [ 4378.413285] scsi_debug:sdebug_driver_probe: scsi_debug: trim poll_queues to 0. poll_q/nr_hw = (0/1) [ 4378.422334] scsi host15: scsi_debug: version 0191 [20210520] dev_size_mb=1024, opts=0x0, submit_queues=1, statistics=0 [ 4378.434922] scsi 15:0:0:0: Direct-Access-ZBC Linux scsi_debug 0191 PQ: 0 ANSI: 7 [ 4378.443343] scsi 15:0:0:0: Power-on or device reset occurred [ 4378.449371] sd 15:0:0:0: Attached scsi generic sg5 type 20 [ 4378.449418] sd 15:0:0:0: [sdf] Host-managed zoned block device ... (See '/mnt/tests/gitlab.com/api/v4/projects/19168116/repository/archive.zip/storage/blktests/blk/blktests/results/nodev/zbd/010.dmesg'
WARNING: CPU: 22 PID: 44011 at fs/iomap/iter.c:51 CPU: 22 PID: 44011 Comm: fio Not tainted 6.8.0-rc3+ #1 RIP: 0010:iomap_iter+0x32b/0x350 Call Trace: <TASK> __iomap_dio_rw+0x1df/0x830 f2fs_file_read_iter+0x156/0x3d0 [f2fs] aio_read+0x138/0x210 io_submit_one+0x188/0x8c0 __x64_sys_io_submit+0x8c/0x1a0 do_syscall_64+0x86/0x170 entry_SYSCALL_64_after_hwframe+0x6e/0x76
Shinichiro Kawasaki helps to analyse this issue and proposes a potential fixing patch in [2].
Quoted from reply of Shinichiro Kawasaki:
"I confirmed that the trigger commit is dbf8e63f48af as Yi reported. I took a look in the commit, but it looks fine to me. So I thought the cause is not in the commit diff.
I found the WARN is printed when the f2fs is set up with multiple devices, and read requests are mapped to the very first block of the second device in the direct read path. In this case, f2fs_map_blocks() and f2fs_map_blocks_cached() modify map->m_pblk as the physical block address from each block device. It becomes zero when it is mapped to the first block of the device. However, f2fs_iomap_begin() assumes that map->m_pblk is the physical block address of the whole f2fs, across the all block devices. It compares map->m_pblk against NULL_ADDR == 0, then go into the unexpected branch and sets the invalid iomap->length. The WARN catches the invalid iomap->length.
This WARN is printed even for non-zoned block devices, by following steps.
- Create two (non-zoned) null_blk devices memory backed with 128MB size each: nullb0 and nullb1.
mkfs.f2fs /dev/nullb0 -c /dev/nullb1
mount -t f2fs /dev/nullb0 "${mount_dir}"
dd if=/dev/zero of="${mount_dir}/test.dat" bs=1M count=192
dd if="${mount_dir}/test.dat" of=/dev/null bs=1M count=192 iflag=direct
..."
So, the root cause of this issue is: when multi-devices feature is on, f2fs_map_blocks() may return zero blkaddr in non-primary device, which is a verified valid block address, however, f2fs_iomap_begin() treats it as an invalid block address, and then it triggers the warning in iomap framework code.
Finally, as discussed, we decide to use a more simple and direct way that checking (map.m_flags & F2FS_MAP_MAPPED) condition instead of (map.m_pblk != NULL_ADDR) to fix this issue.
Thanks a lot for the effort of Yi Zhang and Shinichiro Kawasaki on this issue.
[1] https://lore.kernel.org/linux-f2fs-devel/CAHj4cs-kfojYC9i0G73PRkYzcxCTex=-vugRFeP40g_URGvnfQ@mail.gmail.com/ [2] https://lore.kernel.org/linux-f2fs-devel/gngdj77k4picagsfdtiaa7gpgnup6fsgwzsltx6milmhegmjff@iax2n4wvrqye/
- Record
GHSA-pwgj-c4vj-63r9- CVSS 3.1
- 5.5 Medium
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H - Updated
- 2026-11-02
OSVBELL-CVE-2024-38636
5.5
- Record
BELL-CVE-2024-38636- CVSS 3.1
- 5.5 Medium
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H - Updated
- 2026-11-02
OSVDEBIAN-CVE-2024-38636
5.5
In the Linux kernel, the following vulnerability has been resolved: f2fs: multidev: fix to recognize valid zero block address As reported by Yi Zhang in mailing list [1], kernel warning was catched during zbd/010 test as below: ./check zbd/010 zbd/010 (test gap zone support with F2FS) [failed] runtime ... 3.752s something found in dmesg: [ 4378.146781] run blktests zbd/010 at 2024-02-18 11:31:13 [ 4378.192349] null_blk: module loaded [ 4378.209860] null_blk: disk nullb0 created [ 4378.413285] scsi_debug:sdebug_driver_probe: scsi_debug: trim poll_queues to 0. poll_q/nr_hw = (0/1) [ 4378.422334] scsi host15: scsi_debug: version 0191 [20210520] dev_size_mb=1024, opts=0x0, submit_queues=1, statistics=0 [ 4378.434922] scsi 15:0:0:0: Direct-Access-ZBC Linux scsi_debug 0191 PQ: 0 ANSI: 7 [ 4378.443343] scsi 15:0:0:0: Power-on or device reset occurred [ 4378.449371] sd 15:0:0:0: Attached scsi generic sg5 type 20 [ 4378.449418] sd 15:0:0:0: [sdf] Host-managed zoned block device ... (See '/mnt/tests/gitlab.com/api/v4/projects/19168116/repository/archive.zip/storage/blktests/blk/blktests/results/nodev/zbd/010.dmesg' WARNING: CPU: 22 PID: 44011 at fs/iomap/iter.c:51 CPU: 22 PID: 44011 Comm: fio Not tainted 6.8.0-rc3+ #1 RIP: 0010:iomap_iter+0x32b/0x350 Call Trace: <TASK> __iomap_dio_rw+0x1df/0x830 f2fs_file_read_iter+0x156/0x3d0 [f2fs] aio_read+0x138/0x210 io_submit_one+0x188/0x8c0 __x64_sys_io_submit+0x8c/0x1a0 do_syscall_64+0x86/0x170 entry_SYSCALL_64_after_hwframe+0x6e/0x76 Shinichiro Kawasaki helps to analyse this issue and proposes a potential fixing patch in [2]. Quoted from reply of Shinichiro Kawasaki: "I confirmed that the trigger commit is dbf8e63f48af as Yi reported. I took a look in the commit, but it looks fine to me. So I thought the cause is not in the commit diff. I found the WARN is printed when the f2fs is set up with multiple devices, and read requests are mapped to the very first block of the second device in the direct read path. In this case, f2fs_map_blocks() and f2fs_map_blocks_cached() modify map->m_pblk as the physical block address from each block device. It becomes zero when it is mapped to the first block of the device. However, f2fs_iomap_begin() assumes that map->m_pblk is the physical block address of the whole f2fs, across the all block devices. It compares map->m_pblk against NULL_ADDR == 0, then go into the unexpected branch and sets the invalid iomap->length. The WARN catches the invalid iomap->length. This WARN is printed even for non-zoned block devices, by following steps. - Create two (non-zoned) null_blk devices memory backed with 128MB size each: nullb0 and nullb1. # mkfs.f2fs /dev/nullb0 -c /dev/nullb1 # mount -t f2fs /dev/nullb0 "${mount_dir}" # dd if=/dev/zero of="${mount_dir}/test.dat" bs=1M count=192 # dd if="${mount_dir}/test.dat" of=/dev/null bs=1M count=192 iflag=direct ..." So, the root cause of this issue is: when multi-devices feature is on, f2fs_map_blocks() may return zero blkaddr in non-primary device, which is a verified valid block address, however, f2fs_iomap_begin() treats it as an invalid block address, and then it triggers the warning in iomap framework code. Finally, as discussed, we decide to use a more simple and direct way that checking (map.m_flags & F2FS_MAP_MAPPED) condition instead of (map.m_pblk != NULL_ADDR) to fix this issue. Thanks a lot for the effort of Yi Zhang and Shinichiro Kawasaki on this issue. [1] https://lore.kernel.org/linux-f2fs-devel/CAHj4cs-kfojYC9i0G73PRkYzcxCTex=-vugRFeP40g_URGvnfQ@mail.gmail.com/ [2] https://lore.kernel.org/linux-f2fs-devel/gngdj77k4picagsfdtiaa7gpgnup6fsgwzsltx6milmhegmjff@iax2n4wvrqye/
- Record
DEBIAN-CVE-2024-38636- CVSS 3.1
- 5.5 Medium
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H - Updated
- 2026-11-02
Show 17 moreShow less
OSVOESA-2024-1766
0.0
kernel security update
The Linux Kernel, the operating system core itself.
Security Fix(es):
In the Linux kernel, the following vulnerability has been resolved:
tpm_tis_spi: Account for SPI header when allocating TPM SPI xfer buffer
The TPM SPI transfer mechanism uses MAX_SPI_FRAMESIZE for computing the maximum transfer length and the size of the transfer buffer. As such, it does not account for the 4 bytes of header that prepends the SPI data frame. This can result in out-of-bounds accesses and was confirmed with KASAN.
Introduce SPI_HDRSIZE to account for the header and use to allocate the transfer buffer.(CVE-2024-36477)
In the Linux kernel, the following vulnerability has been resolved:
net: fix out-of-bounds access in ops_init
net_alloc_generic is called by net_alloc, which is called without any locking. It reads max_gen_ptrs, which is changed under pernet_ops_rwsem. It is read twice, first to allocate an array, then to set s.len, which is later used to limit the bounds of the array access.
It is possible that the array is allocated and another thread is registering a new pernet ops, increments max_gen_ptrs, which is then used to set s.len with a larger than allocated length for the variable array.
Fix it by reading max_gen_ptrs only once in net_alloc_generic. If max_gen_ptrs is later incremented, it will be caught in net_assign_generic.(CVE-2024-36883)
In the Linux kernel, the following vulnerability has been resolved:
gpiolib: cdev: fix uninitialised kfifo
If a line is requested with debounce, and that results in debouncing in software, and the line is subsequently reconfigured to enable edge detection then the allocation of the kfifo to contain edge events is overlooked. This results in events being written to and read from an uninitialised kfifo. Read events are returned to userspace.
Initialise the kfifo in the case where the software debounce is already active.(CVE-2024-36898)
In the Linux kernel, the following vulnerability has been resolved:
ipv6: fib6_rules: avoid possible NULL dereference in fib6_rule_action()
syzbot is able to trigger the following crash [1], caused by unsafe ip6_dst_idev() use.
Indeed ip6_dst_idev() can return NULL, and must always be checked.
[1]
Oops: general protection fault, probably for non-canonical address 0xdffffc0000000000: 0000 [#1] PREEMPT SMP KASAN PTI KASAN: null-ptr-deref in range [0x0000000000000000-0x0000000000000007] CPU: 0 PID: 31648 Comm: syz-executor.0 Not tainted 6.9.0-rc4-next-20240417-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/27/2024 RIP: 0010:__fib6_rule_action net/ipv6/fib6_rules.c:237 [inline] RIP: 0010:fib6_rule_action+0x241/0x7b0 net/ipv6/fib6_rules.c:267 Code: 02 00 00 49 8d 9f d8 00 00 00 48 89 d8 48 c1 e8 03 42 80 3c 20 00 74 08 48 89 df e8 f9 32 bf f7 48 8b 1b 48 89 d8 48 c1 e8 03 <42> 80 3c 20 00 74 08 48 89 df e8 e0 32 bf f7 4c 8b 03 48 89 ef 4c RSP: 0018:ffffc9000fc1f2f0 EFLAGS: 00010246 RAX: 0000000000000000 RBX: 0000000000000000 RCX: 1a772f98c8186700 RDX: 0000000000000003 RSI: ffffffff8bcac4e0 RDI: ffffffff8c1f9760 RBP: ffff8880673fb980 R08: ffffffff8fac15ef R09: 1ffffffff1f582bd R10: dffffc0000000000 R11: fffffbfff1f582be R12: dffffc0000000000 R13: 0000000000000080 R14: ffff888076509000 R15: ffff88807a029a00 FS: 00007f55e82ca6c0(0000) GS:ffff8880b9400000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000001b31d23000 CR3: 0000000022b66000 CR4: 00000000003506f0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: <TASK> fib_rules_lookup+0x62c/0xdb0 net/core/fib_rules.c:317 fib6_rule_lookup+0x1fd/0x790 net/ipv6/fib6_rules.c:108 ip6_route_output_flags_noref net/ipv6/route.c:2637 [inline] ip6_route_output_flags+0x38e/0x610 net/ipv6/route.c:2649 ip6_route_output include/net/ip6_route.h:93 [inline] …
- Record
OESA-2024-1766- CVSS 3.1
- 0.0 None
CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:N - Updated
- 2026-11-02
OSVUBUNTU-CVE-2024-38636
5.5
In the Linux kernel, the following vulnerability has been resolved: f2fs: multidev: fix to recognize valid zero block address As reported by Yi Zhang in mailing list [1], kernel warning was catched during zbd/010 test as below: ./check zbd/010 zbd/010 (test gap zone support with F2FS) [failed] runtime ... 3.752s something found in dmesg: [ 4378.146781] run blktests zbd/010 at 2024-02-18 11:31:13 [ 4378.192349] null_blk: module loaded [ 4378.209860] null_blk: disk nullb0 created [ 4378.413285] scsi_debug:sdebug_driver_probe: scsi_debug: trim poll_queues to 0. poll_q/nr_hw = (0/1) [ 4378.422334] scsi host15: scsi_debug: version 0191 [20210520] dev_size_mb=1024, opts=0x0, submit_queues=1, statistics=0 [ 4378.434922] scsi 15:0:0:0: Direct-Access-ZBC Linux scsi_debug 0191 PQ: 0 ANSI: 7 [ 4378.443343] scsi 15:0:0:0: Power-on or device reset occurred [ 4378.449371] sd 15:0:0:0: Attached scsi generic sg5 type 20 [ 4378.449418] sd 15:0:0:0: [sdf] Host-managed zoned block device ... (See '/mnt/tests/gitlab.com/api/v4/projects/19168116/repository/archive.zip/storage/blktests/blk/blktests/results/nodev/zbd/010.dmesg' WARNING: CPU: 22 PID: 44011 at fs/iomap/iter.c:51 CPU: 22 PID: 44011 Comm: fio Not tainted 6.8.0-rc3+ #1 RIP: 0010:iomap_iter+0x32b/0x350 Call Trace: <TASK> __iomap_dio_rw+0x1df/0x830 f2fs_file_read_iter+0x156/0x3d0 [f2fs] aio_read+0x138/0x210 io_submit_one+0x188/0x8c0 __x64_sys_io_submit+0x8c/0x1a0 do_syscall_64+0x86/0x170 entry_SYSCALL_64_after_hwframe+0x6e/0x76 Shinichiro Kawasaki helps to analyse this issue and proposes a potential fixing patch in [2]. Quoted from reply of Shinichiro Kawasaki: "I confirmed that the trigger commit is dbf8e63f48af as Yi reported. I took a look in the commit, but it looks fine to me. So I thought the cause is not in the commit diff. I found the WARN is printed when the f2fs is set up with multiple devices, and read requests are mapped to the very first block of the second device in the direct read path. In this case, f2fs_map_blocks() and f2fs_map_blocks_cached() modify map->m_pblk as the physical block address from each block device. It becomes zero when it is mapped to the first block of the device. However, f2fs_iomap_begin() assumes that map->m_pblk is the physical block address of the whole f2fs, across the all block devices. It compares map->m_pblk against NULL_ADDR == 0, then go into the unexpected branch and sets the invalid iomap->length. The WARN catches the invalid iomap->length. This WARN is printed even for non-zoned block devices, by following steps. - Create two (non-zoned) null_blk devices memory backed with 128MB size each: nullb0 and nullb1. # mkfs.f2fs /dev/nullb0 -c /dev/nullb1 # mount -t f2fs /dev/nullb0 "${mount_dir}" # dd if=/dev/zero of="${mount_dir}/test.dat" bs=1M count=192 # dd if="${mount_dir}/test.dat" of=/dev/null bs=1M count=192 iflag=direct ..." So, the root cause of this issue is: when multi-devices feature is on, f2fs_map_blocks() may return zero blkaddr in non-primary device, which is a verified valid block address, however, f2fs_iomap_begin() treats it as an invalid block address, and then it triggers the warning in iomap framework code. Finally, as discussed, we decide to use a more simple and direct way that checking (map.m_flags & F2FS_MAP_MAPPED) condition instead of (map.m_pblk != NULL_ADDR) to fix this issue. Thanks a lot for the effort of Yi Zhang and Shinichiro Kawasaki on this issue. [1] https://lore.kernel.org/linux-f2fs-devel/CAHj4cs-kfojYC9i0G73PRkYzcxCTex=-vugRFeP40g_URGvnfQ@mail.gmail.com/ [2] https://lore.kernel.org/linux-f2fs-devel/gngdj77k4picagsfdtiaa7gpgnup6fsgwzsltx6milmhegmjff@iax2n4wvrqye/
- Record
UBUNTU-CVE-2024-38636- CVSS 3.1
- 5.5 Medium
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H - Updated
- 2026-11-02
OSV No score
f2fs: multidev: fix to recognize valid zero block address
In the Linux kernel, the following vulnerability has been resolved:
f2fs: multidev: fix to recognize valid zero block address
As reported by Yi Zhang in mailing list [1], kernel warning was catched during zbd/010 test as below:
./check zbd/010 zbd/010 (test gap zone support with F2FS) [failed] runtime ... 3.752s something found in dmesg: [ 4378.146781] run blktests zbd/010 at 2024-02-18 11:31:13 [ 4378.192349] null_blk: module loaded [ 4378.209860] null_blk: disk nullb0 created [ 4378.413285] scsi_debug:sdebug_driver_probe: scsi_debug: trim poll_queues to 0. poll_q/nr_hw = (0/1) [ 4378.422334] scsi host15: scsi_debug: version 0191 [20210520] dev_size_mb=1024, opts=0x0, submit_queues=1, statistics=0 [ 4378.434922] scsi 15:0:0:0: Direct-Access-ZBC Linux scsi_debug 0191 PQ: 0 ANSI: 7 [ 4378.443343] scsi 15:0:0:0: Power-on or device reset occurred [ 4378.449371] sd 15:0:0:0: Attached scsi generic sg5 type 20 [ 4378.449418] sd 15:0:0:0: [sdf] Host-managed zoned block device ... (See '/mnt/tests/gitlab.com/api/v4/projects/19168116/repository/archive.zip/storage/blktests/blk/blktests/results/nodev/zbd/010.dmesg'
WARNING: CPU: 22 PID: 44011 at fs/iomap/iter.c:51 CPU: 22 PID: 44011 Comm: fio Not tainted 6.8.0-rc3+ #1 RIP: 0010:iomap_iter+0x32b/0x350 Call Trace: <TASK> __iomap_dio_rw+0x1df/0x830 f2fs_file_read_iter+0x156/0x3d0 [f2fs] aio_read+0x138/0x210 io_submit_one+0x188/0x8c0 __x64_sys_io_submit+0x8c/0x1a0 do_syscall_64+0x86/0x170 entry_SYSCALL_64_after_hwframe+0x6e/0x76
Shinichiro Kawasaki helps to analyse this issue and proposes a potential fixing patch in [2].
Quoted from reply of Shinichiro Kawasaki:
"I confirmed that the trigger commit is dbf8e63f48af as Yi reported. I took a look in the commit, but it looks fine to me. So I thought the cause is not in the commit diff.
I found the WARN is printed when the f2fs is set up with multiple devices, and read requests are mapped to the very first block of the second device in the direct read path. In this case, f2fs_map_blocks() and f2fs_map_blocks_cached() modify map->m_pblk as the physical block address from each block device. It becomes zero when it is mapped to the first block of the device. However, f2fs_iomap_begin() assumes that map->m_pblk is the physical block address of the whole f2fs, across the all block devices. It compares map->m_pblk against NULL_ADDR == 0, then go into the unexpected branch and sets the invalid iomap->length. The WARN catches the invalid iomap->length.
This WARN is printed even for non-zoned block devices, by following steps.
- Create two (non-zoned) null_blk devices memory backed with 128MB size each: nullb0 and nullb1.
mkfs.f2fs /dev/nullb0 -c /dev/nullb1
mount -t f2fs /dev/nullb0 "${mount_dir}"
dd if=/dev/zero of="${mount_dir}/test.dat" bs=1M count=192
dd if="${mount_dir}/test.dat" of=/dev/null bs=1M count=192 iflag=direct
..."
So, the root cause of this issue is: when multi-devices feature is on, f2fs_map_blocks() may return zero blkaddr in non-primary device, which is a verified valid block address, however, f2fs_iomap_begin() treats it as an invalid block address, and then it triggers the warning in iomap framework code.
Finally, as discussed, we decide to use a more simple and direct way that checking (map.m_flags & F2FS_MAP_MAPPED) condition instead of (map.m_pblk != NULL_ADDR) to fix this issue.
Thanks a lot for the effort of Yi Zhang and Shinichiro Kawasaki on this issue.
[1] https://lore.kernel.org/linux-f2fs-devel/CAHj4cs-kfojYC9i0G73PRkYzcxCTex=-vugRFeP40g_URGvnfQ@mail.gmail.com/ [2] https://lore.kernel.org/linux-f2fs-devel/gngdj77k4picagsfdtiaa7gpgnup6fsgwzsltx6milmhegmjff@iax2n4wvrqye/
- Record
CVE-2024-38636- Updated
- 2026-11-02
OSVMGASA-2024-0263 No score
Updated kernel kmod-xtables-addons kmod-virtualbox dwarves packages fix security vulnerabilities
Upstream kernel version 6.6.37 fix bugs and vulnerabilities. The dwarves, kmod-virtualbox and kmod-xtables-addons packages have been updated to work with this new kernel. For information about the vulnerabilities see the links.
- Record
MGASA-2024-0263- Updated
- 2026-11-02
OSVMGASA-2024-0266 No score
Updated kernel-linus packages fix security vulnerabilities
Vanilla upstream kernel version 6.6.37 fix bugs and vulnerabilities. For information about the vulnerabilities see the links.
- Record
MGASA-2024-0266- Updated
- 2026-11-02
OSVSUSE-SU-2024:2571-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-2024-39371: io_uring: check for non-NULL file pointer in io_file_can_poll() (bsc#1226990).
- CVE-2023-52846: hsr: Prevent use after free in prp_create_tagged_frame() (bsc#1225098).
- CVE-2024-38610: drivers/virt/acrn: fix PFNMAP PTE checks in acrn_vm_ram_map() (bsc#1226758).
- CVE-2024-37354: btrfs: fix crash on racing fsync and size-extending write into prealloc (bsc#1227101).
- CVE-2024-36919: scsi: bnx2fc: Remove spin_lock_bh while releasing resources after upload (bsc#1225767).
- CVE-2024-38559: scsi: qedf: Ensure the copied buf is NUL terminated (bsc#1226785).
- CVE-2024-38570: gfs2: Fix potential glock use-after-free on unmount (bsc#1226775).
- CVE-2024-36904: tcp: Use refcount_inc_not_zero() in tcp_twsk_unique() (bsc#1225732).
- CVE-2023-52840: Fix use after free in rmi_unregister_function() (bsc#1224928).
- CVE-2024-38545: RDMA/hns: Fix UAF for cq async event (bsc#1226595).
- CVE-2023-52834: atl1c: Work around the DMA RX overflow issue (bsc#1225599).
- CVE-2023-52875: Add check for mtk_alloc_clk_data (bsc#1225096).
- CVE-2023-52865: Add check for mtk_alloc_clk_data (bsc#1225086).
- CVE-2023-52821: Fixed a possible null pointer dereference (bsc#1225022).
- CVE-2023-52867: Fixed possible buffer overflow (bsc#1225009).
- CVE-2024-38578: ecryptfs: Fix buffer size for tag 66 packet (bsc#1226634,).
- CVE-2024-36964: fs/9p: only translate RWX permissions for plain 9P2000 (bsc#1225866).
- CVE-2023-52759: Ignore negated quota changes (bsc#1225560).
- CVE-2023-52796: Add ipvlan_route_v6_outbound() helper (bsc#1224930).
- CVE-2023-52807: Fixed out-of-bounds access may occur when coalesce info is read via debugfs (bsc#1225097).
- CVE-2023-52864: Fixed opening of char device (bsc#1225132).
- CVE-2024-36926: Fixed LPAR panics during boot up with a frozen PE (bsc#1222011).
- CVE-2023-52871: Handle a second device without data corruption (bsc#1225534)
- CVE-2023-52795: Fixed use after free in vhost_vdpa_probe() (bsc#1225085).
- CVE-2023-52881: tcp: do not accept ACK of bytes we never sent (bsc#1225611).
- CVE-2024-37353: virtio: fixed a double free in vp_del_vqs() (bsc#1226875).
- CVE-2024-39301: net/9p: fix uninit-value in p9_client_rpc() (bsc#1226994).
- CVE-2024-35843: iommu/vt-d: Use device rbtree in iopf reporting path (bsc#1224751).
- CVE-2024-37078: nilfs2: fix potential kernel bug due to lack of writeback flag waiting (bsc#1227066).
- CVE-2024-35247: fpga: region: add owner module and take its refcount (bsc#1226948).
- CVE-2024-36479: fpga: bridge: add owner module and take its refcount (bsc#1226949).
- CVE-2024-37021: fpga: manager: add owner module and take its refcount (bsc#1226950).
- CVE-2024-36281: net/mlx5: Use mlx5_ipsec_rx_status_destroy to correctly delete status rules (bsc#1226799).
- CVE-2024-38580: epoll: be better about file lifetimes (bsc#1226610).
- CVE-2024-36478: null_blk: fix null-ptr-dereference while configuring 'power' and 'submit_queues' (bsc#1226841).
- CVE-2024-38636: f2fs: multidev: fix to recognize valid zero block address (bsc#1226879).
- CVE-2024-38661: s390/ap: Fix crash in AP internal function modify_bitmap() (bsc#1226996).
- CVE-2024-38564: bpf: Add BPF_PROG_TYPE_CGROUP_SKB attach type enforcement in BPF_LINK_CREATE (bsc#1226789).
- CVE-2024-38560: scsi: bfa: Ensure the copied buf is NUL terminated (bsc#1226786).
- CVE-2024-36978: net: sched: sch_multiq: fix possible OOB write in multiq_tune() (bsc#1226514).
- CVE-2024-36917: block: fix overflow in blk_ioctl_discard() (bsc#1225770).
- CVE-2024-38627: stm class: Fix a double free in stm_register_device() (bsc#1226857).
- CVE-2024-38603: drivers/perf: hisi: hns3: Actually use devm_add_action_or_reset() (bsc#1226842).
- CVE-2024-38553: net: fec: remove .ndo_poll_controller to avoid deadlock (bsc#1226744).
- CVE-2024-38555: net/mlx5: Discard command completions in internal error (bsc#1226607).
- CVE-2024-38556:…
- Record
SUSE-SU-2024:2571-1- Updated
- 2026-11-02
OSVSUSE-SU-2024:2896-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-2024-41014: xfs: add bounds checking to xlog_recover_process_data (bsc#1228408).
- CVE-2024-41013: xfs: do not walk off the end of a directory data block (bsc#1228405).
- CVE-2024-41017: jfs: do not walk off the end of ealist (bsc#1228403).
- CVE-2024-40972: ext4: fold quota accounting into ext4_xattr_inode_lookup_create() (bsc#1227910).
- CVE-2024-39276: ext4: fix mb_cache_entry's e_refcnt leak in ext4_xattr_block_cache_find() (bsc#1226993).
- CVE-2024-40925: block: fix request.queuelist usage in flush (bsc#1227789).
- CVE-2024-40998: ext4: fix uninitialized ratelimit_state->lock access in __ext4_fill_super() (bsc#1227866).
- CVE-2024-39494: ima: Fix use-after-free on a dentry's dname.name (bsc#1227716).
- CVE-2024-39496: btrfs: zoned: fix use-after-free due to race with dev replace (bsc#1227719).
- CVE-2024-41091: tun: add missing verification for short frame (bsc#1228327).
- CVE-2024-41090: tap: add missing verification for short frame (bsc#1228328).
- CVE-2024-40999: net: ena: Add validation for completion descriptors consistency (bsc#1227913).
- CVE-2024-40966: kABI: tty: add the option to have a tty reject a new ldisc (bsc#1227886).
- CVE-2024-40975: platform/x86: x86-android-tablets: Unregister devices in reverse order (bsc#1227926).
- CVE-2024-40970: Avoid hw_desc array overrun in dw-axi-dmac (bsc#1227899).
- CVE-2024-40947: ima: Avoid blocking in RCU read-side critical section (bsc#1227803).
- CVE-2024-40908: bpf: Set run context for rawtp test_run callback (bsc#1227783).
- CVE-2024-40960: ipv6: prevent possible NULL dereference in rt6_probe() (bsc#1227813).
- CVE-2024-40935: cachefiles: flush all requests after setting CACHEFILES_DEAD (bsc#1227797).
- CVE-2024-40961: ipv6: prevent possible NULL deref in fib6_nh_init() (bsc#1227814).
- CVE-2024-39504: netfilter: nft_inner: validate mandatory meta and payload (bsc#1227757).
- CVE-2024-41006: netrom: Fix a memory leak in nr_heartbeat_expiry() (bsc#1227862).
- CVE-2024-40937: gve: Clear napi->skb before dev_kfree_skb_any() (bsc#1227836).
- CVE-2024-39507: net: hns3: fix kernel crash problem in concurrent scenario (bsc#1227730).
- CVE-2024-40940: net/mlx5: Fix tainted pointer delete is case of flow rules creation fail (bsc#1227800).
- CVE-2024-40928: net: ethtool: fix the error condition in ethtool_get_phy_stats_ethtool() (bsc#1227788).
- CVE-2024-26944: btrfs: zoned: fix lock ordering in btrfs_zone_activate() (bsc#1223731).
- CVE-2024-40923: vmxnet3: disable rx data ring on dma allocation failure (bsc#1227786).
- CVE-2024-40931: mptcp: ensure snd_una is properly initialized on connect (bsc#1227780).
- CVE-2024-40919: bnxt_en: Adjust logging of firmware messages in case of released token in __hwrm_send() (bsc#1227779).
- CVE-2024-39487: bonding: Fix out-of-bounds read in bond_option_arp_ip_targets_set() (bsc#1227573)
- CVE-2024-35908: tls: get psock ref after taking rxlock to avoid leak (bsc#1224490)
- CVE-2024-35899: netfilter: nf_tables: flush pending destroy work before exit_net release (bsc#1224499)
- CVE-2024-35934: net/smc: reduce rtnl pressure in smc_pnet_create_pnetids_list() (bsc#1224641)
- CVE-2024-35893: net/sched: act_skbmod: prevent kernel-infoleak (bsc#1224512)
- CVE-2024-40901: scsi: mpt3sas: Avoid test/set_bit() operating in non-allocated memory (bsc#1227762).
- CVE-2024-39472: xfs: fix log recovery buffer allocation for the legacy h_size fixup (bsc#1227432).
- CVE-2024-40953: KVM: Fix a data race on last_boosted_vcpu in kvm_vcpu_on_spin() (bsc#1227806).
- CVE-2024-27404: mptcp: fix data races on remote_id (bsc#1224422)
- CVE-2024-27020: netfilter: nf_tables: Fix potential data-race in __nft_expr_type_get() (bsc#1223815)
- CVE-2024-27019: netfilter: nf_tables: Fix potential data-race in __nft_obj_type_get() (bsc#1223813)
- CVE-2024-40948: mm/page_table_check: fix crash on ZONE_DEVICE (bsc#1227801). -…
- Record
SUSE-SU-2024:2896-1- Updated
- 2026-11-02
OSVSUSE-SU-2024:2973-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-0160: Fixed deadlock flaw in BPF that could allow a local user to potentially crash the system (bsc#1209657).
- CVE-2023-38417: wifi: iwlwifi: bump FW API to 90 for BZ/SC devices (bsc#1225600).
- CVE-2023-47210: wifi: iwlwifi: bump FW API to 90 for BZ/SC devices (bsc#1225601).
- CVE-2023-52435: net: prevent mss overflow in skb_segment() (bsc#1220138).
- CVE-2023-52458: Fixed check that partition length needs to be aligned with block size (bsc#1220428).
- CVE-2023-52503: Fixed tee/amdtee use-after-free vulnerability in amdtee_close_session (bsc#1220915).
- CVE-2023-52618: Fixed string overflow in block/rnbd-srv (bsc#1221615).
- CVE-2023-52622: ext4: avoid online resizing failures due to oversized flex bg (bsc#1222080).
- CVE-2023-52631: Fixed an NULL dereference bug (bsc#1222264 CVE-2023-52631).
- CVE-2023-52640: Fixed out-of-bounds in ntfs_listxattr (bsc#1222301).
- CVE-2023-52641: Fixed NULL ptr dereference checking at the end of attr_allocate_frame() (bsc#1222303)
- CVE-2023-52645: Fixed pmdomain/mediatek race conditions with genpd (bsc#1223033).
- CVE-2023-52652: Fixed NTB for possible name leak in ntb_register_device() (bsc#1223686).
- CVE-2023-52656: Dropped any code related to SCM_RIGHTS (bsc#1224187).
- CVE-2023-52672: pipe: wakeup wr_wait after setting max_usage (bsc#1224614).
- CVE-2023-52674: Add clamp() in scarlett2_mixer_ctl_put() (bsc#1224727).
- CVE-2023-52659: Fixed to pfn_to_kaddr() not treated as a 64-bit type (bsc#1224442)
- CVE-2023-52680: Fixed missing error checks to *_ctl_get() (bsc#1224608).
- CVE-2023-52692: Fixed missing error check to scarlett2_usb_set_config() (bsc#1224628).
- CVE-2023-52698: Fixed memory leak in netlbl_calipso_add_pass() (CVE-2023-52698 bsc#1224621)
- CVE-2023-52699: sysv: don't call sb_bread() with pointers_lock held (bsc#1224659).
- CVE-2023-52735: bpf, sockmap: Don't let sock_map_{close,destroy,unhash} call itself (bsc#1225475).
- CVE-2023-52751: smb: client: fix use-after-free in smb2_query_info_compound() (bsc#1225489).
- CVE-2023-52757: Fixed potential deadlock when releasing mids (bsc#1225548).
- CVE-2023-52771: Fixed delete_endpoint() vs parent unregistration race (bsc#1225007).
- CVE-2023-52772: Fixed use-after-free in unix_stream_read_actor() (bsc#1224989).
- CVE-2023-52775: net/smc: avoid data corruption caused by decline (bsc#1225088).
- CVE-2023-52786: ext4: fix racy may inline data check in dio write (bsc#1224939).
- CVE-2023-52787: blk-mq: make sure active queue usage is held for bio_integrity_prep() (bsc#1225105).
- CVE-2023-52837: nbd: fix uaf in nbd_open (bsc#1224935).
- CVE-2023-52843: llc: verify mac len before reading mac header (bsc#1224951).
- CVE-2023-52845: tipc: Change nla_policy for bearer-related names to NLA_NUL_STRING (bsc#1225585).
- CVE-2023-52855: usb: dwc2: fix possible NULL pointer dereference caused by driver concurrency (bsc#1225583).
- CVE-2023-52860: Fixed null pointer dereference in hisi_hns3 (bsc#1224936).
- CVE-2023-52875: Add check for mtk_alloc_clk_data (bsc#1225096).
- CVE-2023-52881: tcp: do not accept ACK of bytes we never sent (bsc#1225611).
- CVE-2023-6238: Fixed kcalloc() arguments order (bsc#1217384).
- CVE-2024-21823: Fixed safety flag to struct ends (bsc#1223625).
- CVE-2024-23848: Fixed media/cec for possible use-after-free in cec_queue_msg_fh (bsc#1219104).
- CVE-2024-25739: Fixed possible crash in create_empty_lvol() in drivers/mtd/ubi/vtbl.c (bsc#1219834).
- CVE-2024-26601: Fixed ext4 buddy bitmap corruption via fast commit replay (bsc#1220342).
- CVE-2024-26614: Fixed the initialization of accept_queue's spinlocks (bsc#1221293).
- CVE-2024-26615: net/smc: fix illegal rmb_desc access in SMC-D connection dump (bsc#1220942).
- CVE-2024-26623: pds_core: Prevent race issues involving the adminq (bsc#1221057).
- CVE-2024-26625: Call sock_orphan() at release time (bsc#1221086) -…
- Record
SUSE-SU-2024:2973-1- Updated
- 2026-11-02
OSVSUSE-SU-2025:20008-1 No score
Security update for the Linux Kernel
The SUSE Linux Enterprise Micro 6.0 kernel was updated to receive various security bugfixes.
The following security bugs were fixed:
- CVE-2024-41014: xfs: add bounds checking to xlog_recover_process_data (bsc#1228408).
- CVE-2024-41013: xfs: do not walk off the end of a directory data block (bsc#1228405).
- CVE-2024-41017: jfs: do not walk off the end of ealist (bsc#1228403).
- CVE-2024-40972: ext4: fold quota accounting into ext4_xattr_inode_lookup_create() (bsc#1227910).
- CVE-2024-39276: ext4: fix mb_cache_entry's e_refcnt leak in ext4_xattr_block_cache_find() (bsc#1226993).
- CVE-2024-40925: block: fix request.queuelist usage in flush (bsc#1227789).
- CVE-2024-40998: ext4: fix uninitialized ratelimit_state->lock access in __ext4_fill_super() (bsc#1227866).
- CVE-2024-39494: ima: Fix use-after-free on a dentry's dname.name (bsc#1227716).
- CVE-2024-39496: btrfs: zoned: fix use-after-free due to race with dev replace (bsc#1227719).
- CVE-2024-41091: tun: add missing verification for short frame (bsc#1228327).
- CVE-2024-41090: tap: add missing verification for short frame (bsc#1228328).
- CVE-2024-40999: net: ena: Add validation for completion descriptors consistency (bsc#1227913).
- CVE-2024-40966: kABI: tty: add the option to have a tty reject a new ldisc (bsc#1227886).
- CVE-2024-40975: platform/x86: x86-android-tablets: Unregister devices in reverse order (bsc#1227926).
- CVE-2024-40970: Avoid hw_desc array overrun in dw-axi-dmac (bsc#1227899).
- CVE-2024-40947: ima: Avoid blocking in RCU read-side critical section (bsc#1227803).
- CVE-2024-40908: bpf: Set run context for rawtp test_run callback (bsc#1227783).
- CVE-2024-40960: ipv6: prevent possible NULL dereference in rt6_probe() (bsc#1227813).
- CVE-2024-40935: cachefiles: flush all requests after setting CACHEFILES_DEAD (bsc#1227797).
- CVE-2024-40961: ipv6: prevent possible NULL deref in fib6_nh_init() (bsc#1227814).
- CVE-2024-39504: netfilter: nft_inner: validate mandatory meta and payload (bsc#1227757).
- CVE-2024-41006: netrom: Fix a memory leak in nr_heartbeat_expiry() (bsc#1227862).
- CVE-2024-40937: gve: Clear napi->skb before dev_kfree_skb_any() (bsc#1227836).
- CVE-2024-39507: net: hns3: fix kernel crash problem in concurrent scenario (bsc#1227730).
- CVE-2024-40940: net/mlx5: Fix tainted pointer delete is case of flow rules creation fail (bsc#1227800).
- CVE-2024-40928: net: ethtool: fix the error condition in ethtool_get_phy_stats_ethtool() (bsc#1227788).
- CVE-2024-26944: btrfs: zoned: fix lock ordering in btrfs_zone_activate() (bsc#1223731).
- CVE-2024-40923: vmxnet3: disable rx data ring on dma allocation failure (bsc#1227786).
- CVE-2024-40931: mptcp: ensure snd_una is properly initialized on connect (bsc#1227780).
- CVE-2024-40919: bnxt_en: Adjust logging of firmware messages in case of released token in __hwrm_send() (bsc#1227779).
- CVE-2024-39487: bonding: Fix out-of-bounds read in bond_option_arp_ip_targets_set() (bsc#1227573)
- CVE-2024-35908: tls: get psock ref after taking rxlock to avoid leak (bsc#1224490)
- CVE-2024-35899: netfilter: nf_tables: flush pending destroy work before exit_net release (bsc#1224499)
- CVE-2024-35934: net/smc: reduce rtnl pressure in smc_pnet_create_pnetids_list() (bsc#1224641)
- CVE-2024-35893: net/sched: act_skbmod: prevent kernel-infoleak (bsc#1224512)
- CVE-2024-40901: scsi: mpt3sas: Avoid test/set_bit() operating in non-allocated memory (bsc#1227762).
- CVE-2024-39472: xfs: fix log recovery buffer allocation for the legacy h_size fixup (bsc#1227432).
- CVE-2024-40953: KVM: Fix a data race on last_boosted_vcpu in kvm_vcpu_on_spin() (bsc#1227806).
- CVE-2024-27404: mptcp: fix data races on remote_id (bsc#1224422)
- CVE-2024-27020: netfilter: nf_tables: Fix potential data-race in __nft_expr_type_get() (bsc#1223815)
- CVE-2024-27019: netfilter: nf_tables: Fix potential data-race in __nft_obj_type_get() (bsc#1223813)
- CVE-2024-40948: mm/page_table_check: fix crash on ZONE_DEVICE (bsc#1227801).
- CVE-2024-35890:…
- Record
SUSE-SU-2025:20008-1- Updated
- 2026-11-02
OSVSUSE-SU-2025:20028-1 No score
Security update for the Linux Kernel
The SUSE Linux Enterprise Micro 6.0 RT kernel was updated to receive various security bugfixes.
The following security bugs were fixed:
- CVE-2024-41014: xfs: add bounds checking to xlog_recover_process_data (bsc#1228408).
- CVE-2024-41013: xfs: do not walk off the end of a directory data block (bsc#1228405).
- CVE-2024-41017: jfs: do not walk off the end of ealist (bsc#1228403).
- CVE-2024-40972: ext4: fold quota accounting into ext4_xattr_inode_lookup_create() (bsc#1227910).
- CVE-2024-39276: ext4: fix mb_cache_entry's e_refcnt leak in ext4_xattr_block_cache_find() (bsc#1226993).
- CVE-2024-40925: block: fix request.queuelist usage in flush (bsc#1227789).
- CVE-2024-40998: ext4: fix uninitialized ratelimit_state->lock access in __ext4_fill_super() (bsc#1227866).
- CVE-2024-41011: drm/amdkfd: do not allow mapping the MMIO HDP page with large pages (bsc#1228114).
- CVE-2024-39494: ima: Fix use-after-free on a dentry's dname.name (bsc#1227716).
- CVE-2024-39496: btrfs: zoned: fix use-after-free due to race with dev replace (bsc#1227719).
- CVE-2024-41091: tun: add missing verification for short frame (bsc#1228327).
- CVE-2024-41090: tap: add missing verification for short frame (bsc#1228328).
- CVE-2024-40999: net: ena: Add validation for completion descriptors consistency (bsc#1227913).
- CVE-2024-40966: kABI: tty: add the option to have a tty reject a new ldisc (bsc#1227886).
- CVE-2024-40975: platform/x86: x86-android-tablets: Unregister devices in reverse order (bsc#1227926).
- CVE-2024-40970: Avoid hw_desc array overrun in dw-axi-dmac (bsc#1227899).
- CVE-2024-40947: ima: Avoid blocking in RCU read-side critical section (bsc#1227803).
- CVE-2024-40908: bpf: Set run context for rawtp test_run callback (bsc#1227783).
- CVE-2024-40960: ipv6: prevent possible NULL dereference in rt6_probe() (bsc#1227813).
- CVE-2024-40935: cachefiles: flush all requests after setting CACHEFILES_DEAD (bsc#1227797).
- CVE-2024-40961: ipv6: prevent possible NULL deref in fib6_nh_init() (bsc#1227814).
- CVE-2024-39504: netfilter: nft_inner: validate mandatory meta and payload (bsc#1227757).
- CVE-2024-41006: netrom: Fix a memory leak in nr_heartbeat_expiry() (bsc#1227862).
- CVE-2024-40937: gve: Clear napi->skb before dev_kfree_skb_any() (bsc#1227836).
- CVE-2024-39507: net: hns3: fix kernel crash problem in concurrent scenario (bsc#1227730).
- CVE-2024-40940: net/mlx5: Fix tainted pointer delete is case of flow rules creation fail (bsc#1227800).
- CVE-2024-40928: net: ethtool: fix the error condition in ethtool_get_phy_stats_ethtool() (bsc#1227788).
- CVE-2024-26944: btrfs: zoned: fix lock ordering in btrfs_zone_activate() (bsc#1223731).
- CVE-2024-40923: vmxnet3: disable rx data ring on dma allocation failure (bsc#1227786).
- CVE-2024-40931: mptcp: ensure snd_una is properly initialized on connect (bsc#1227780).
- CVE-2024-40919: bnxt_en: Adjust logging of firmware messages in case of released token in __hwrm_send() (bsc#1227779).
- CVE-2024-39487: bonding: Fix out-of-bounds read in bond_option_arp_ip_targets_set() (bsc#1227573)
- CVE-2024-35908: tls: get psock ref after taking rxlock to avoid leak (bsc#1224490)
- CVE-2024-35899: netfilter: nf_tables: flush pending destroy work before exit_net release (bsc#1224499)
- CVE-2024-35934: net/smc: reduce rtnl pressure in smc_pnet_create_pnetids_list() (bsc#1224641)
- CVE-2024-35893: net/sched: act_skbmod: prevent kernel-infoleak (bsc#1224512)
- CVE-2024-40901: scsi: mpt3sas: Avoid test/set_bit() operating in non-allocated memory (bsc#1227762).
- CVE-2024-39472: xfs: fix log recovery buffer allocation for the legacy h_size fixup (bsc#1227432).
- CVE-2024-40953: KVM: Fix a data race on last_boosted_vcpu in kvm_vcpu_on_spin() (bsc#1227806).
- CVE-2024-27404: mptcp: fix data races on remote_id (bsc#1224422)
- CVE-2024-27020: netfilter: nf_tables: Fix potential data-race in __nft_expr_type_get() (bsc#1223815)
- CVE-2024-27019: netfilter: nf_tables: Fix potential data-race in __nft_obj_type_get()…
- Record
SUSE-SU-2025:20028-1- Updated
- 2026-11-02
OSVUSN-6999-1 No score
linux, linux-aws, linux-gcp, linux-gke, linux-ibm, linux-lowlatency, linux-oem-6.8, linux-oracle vulnerabilities
Chenyuan Yang discovered that the CEC driver driver in the Linux kernel contained a use-after-free vulnerability. A local attacker could use this to cause a denial of service (system crash) or possibly execute arbitrary code. (CVE-2024-23848)
It was discovered that the JFS file system contained an out-of-bounds read vulnerability when printing xattr debug information. A local attacker could use this to cause a denial of service (system crash). (CVE-2024-40902)
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;
- MIPS architecture;
- PA-RISC architecture;
- PowerPC architecture;
- RISC-V architecture;
- x86 architecture;
- Block layer subsystem;
- ACPI drivers;
- Drivers core;
- Null block device driver;
- Character device driver;
- TPM device driver;
- Clock framework and drivers;
- CPU frequency scaling framework;
- Hardware crypto device drivers;
- CXL (Compute Express Link) drivers;
- Buffer Sharing and Synchronization framework;
- DMA engine subsystem;
- EFI core;
- FPGA Framework;
- GPU drivers;
- Greybus drivers;
- HID subsystem;
- HW tracing;
- I2C subsystem;
- IIO subsystem;
- InfiniBand drivers;
- Input Device (Mouse) drivers;
- Mailbox framework;
- Media drivers;
- Microchip PCI driver;
- VMware VMCI Driver;
- Network drivers;
- PCI subsystem;
- x86 platform drivers;
- PTP clock framework;
- S/390 drivers;
- SCSI drivers;
- SoundWire subsystem;
- Sonic Silicon Backplane drivers;
- Greybus lights staging drivers;
- Thermal drivers;
- TTY drivers;
- USB subsystem;
- VFIO drivers;
- Framebuffer layer;
- Watchdog drivers;
- 9P distributed file system;
- BTRFS file system;
- File systems infrastructure;
- Ext4 file system;
- F2FS file system;
- JFS file system;
- Network file system server daemon;
- NILFS2 file system;
- NTFS3 file system;
- SMB network file system;
- Tracing file system;
- Tracing infrastructure;
- io_uring subsystem;
- Core kernel;
- BPF subsystem;
- Kernel debugger infrastructure;
- DMA mapping infrastructure;
- IRQ subsystem;
- Memory management;
- 9P file system network protocol;
- Amateur Radio drivers;
- B.A.T.M.A.N. meshing protocol;
- Ethernet bridge;
- Networking core;
- Ethtool driver;
- IPv4 networking;
- IPv6 networking;
- MAC80211 subsystem;
- Multipath TCP;
- Netfilter;
- NET/ROM layer;
- NFC subsystem;
- Network traffic control;
- Sun RPC protocol;
- TIPC protocol;
- TLS protocol;
- Unix domain sockets;
- Wireless networking;
- XFRM subsystem;
- AppArmor security module;
- Integrity Measurement Architecture(IMA) framework;
- Landlock security;
- Linux Security Modules (LSM) Framework;
- SELinux security module;
- Simplified Mandatory Access Control Kernel framework;
- ALSA framework;
- HD-audio driver;
- SOF drivers;
- KVM core; (CVE-2024-40911, CVE-2024-37356, CVE-2024-40935, CVE-2024-40944, CVE-2024-41003, CVE-2024-40990, CVE-2024-40952, CVE-2024-40940, CVE-2024-40930, CVE-2024-40985, CVE-2024-40941, CVE-2024-38630, CVE-2024-39466, CVE-2024-40933, CVE-2024-38624, CVE-2024-40924, CVE-2024-40945, CVE-2024-40899, CVE-2024-38622, CVE-2024-40979, CVE-2024-36484, CVE-2024-41004, CVE-2024-39474, CVE-2022-48772, CVE-2024-36244, CVE-2024-38664, CVE-2024-40925, CVE-2024-40980, CVE-2024-39480, CVE-2024-36270, CVE-2024-40936, CVE-2024-40904, CVE-2024-38635, CVE-2024-40927, CVE-2024-36481, CVE-2024-40929, CVE-2024-40958, CVE-2024-36978, CVE-2024-40992, CVE-2024-40908, CVE-2024-39504, CVE-2024-41001, CVE-2024-40967, CVE-2023-52884, CVE-2024-40997, CVE-2024-40903, CVE-2024-40913, CVE-2024-34030, CVE-2024-39473, CVE-2024-40966, CVE-2024-40951, CVE-2024-40902, CVE-2024-40982, CVE-2024-40923, CVE-2024-39467, CVE-2024-40910, CVE-2024-40909, CVE-2024-39463,…
- Record
USN-6999-1- Updated
- 2026-11-02
OSVUSN-6999-2 No score
linux-raspi vulnerabilities
Chenyuan Yang discovered that the CEC driver driver in the Linux kernel contained a use-after-free vulnerability. A local attacker could use this to cause a denial of service (system crash) or possibly execute arbitrary code. (CVE-2024-23848)
It was discovered that the JFS file system contained an out-of-bounds read vulnerability when printing xattr debug information. A local attacker could use this to cause a denial of service (system crash). (CVE-2024-40902)
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;
- MIPS architecture;
- PA-RISC architecture;
- PowerPC architecture;
- RISC-V architecture;
- x86 architecture;
- Block layer subsystem;
- ACPI drivers;
- Drivers core;
- Null block device driver;
- Character device driver;
- TPM device driver;
- Clock framework and drivers;
- CPU frequency scaling framework;
- Hardware crypto device drivers;
- CXL (Compute Express Link) drivers;
- Buffer Sharing and Synchronization framework;
- DMA engine subsystem;
- EFI core;
- FPGA Framework;
- GPU drivers;
- Greybus drivers;
- HID subsystem;
- HW tracing;
- I2C subsystem;
- IIO subsystem;
- InfiniBand drivers;
- Input Device (Mouse) drivers;
- Mailbox framework;
- Media drivers;
- Microchip PCI driver;
- VMware VMCI Driver;
- Network drivers;
- PCI subsystem;
- x86 platform drivers;
- PTP clock framework;
- S/390 drivers;
- SCSI drivers;
- SoundWire subsystem;
- Sonic Silicon Backplane drivers;
- Greybus lights staging drivers;
- Thermal drivers;
- TTY drivers;
- USB subsystem;
- VFIO drivers;
- Framebuffer layer;
- Watchdog drivers;
- 9P distributed file system;
- BTRFS file system;
- File systems infrastructure;
- Ext4 file system;
- F2FS file system;
- JFS file system;
- Network file system server daemon;
- NILFS2 file system;
- NTFS3 file system;
- SMB network file system;
- Tracing file system;
- IOMMU subsystem;
- Tracing infrastructure;
- io_uring subsystem;
- Core kernel;
- BPF subsystem;
- Kernel debugger infrastructure;
- DMA mapping infrastructure;
- IRQ subsystem;
- Memory management;
- 9P file system network protocol;
- Amateur Radio drivers;
- B.A.T.M.A.N. meshing protocol;
- Ethernet bridge;
- Networking core;
- Ethtool driver;
- IPv4 networking;
- IPv6 networking;
- MAC80211 subsystem;
- Multipath TCP;
- Netfilter;
- NET/ROM layer;
- NFC subsystem;
- Network traffic control;
- Sun RPC protocol;
- TIPC protocol;
- TLS protocol;
- Unix domain sockets;
- Wireless networking;
- XFRM subsystem;
- AppArmor security module;
- Integrity Measurement Architecture(IMA) framework;
- Landlock security;
- Linux Security Modules (LSM) Framework;
- SELinux security module;
- Simplified Mandatory Access Control Kernel framework;
- ALSA framework;
- HD-audio driver;
- SOF drivers;
- KVM core; (CVE-2024-40978, CVE-2024-39504, CVE-2024-39483, CVE-2024-36478, CVE-2024-40928, CVE-2024-36971, CVE-2024-40947, CVE-2024-31076, CVE-2024-40934, CVE-2024-40909, CVE-2024-40962, CVE-2024-38635, CVE-2024-38632, CVE-2024-40912, CVE-2024-40967, CVE-2024-39492, CVE-2024-40974, CVE-2024-39466, CVE-2024-40939, CVE-2024-40988, CVE-2024-40951, CVE-2024-41005, CVE-2024-40968, CVE-2024-39493, CVE-2024-40949, CVE-2022-48772, CVE-2024-40944, CVE-2024-40998, CVE-2024-39490, CVE-2024-39467, CVE-2024-42078, CVE-2024-40953, CVE-2024-40990, CVE-2024-40902, CVE-2024-39461, CVE-2024-39301, CVE-2024-36978, CVE-2024-39475, CVE-2024-39496, CVE-2024-40901, CVE-2024-40985, CVE-2024-33621, CVE-2024-38663, CVE-2024-39497, CVE-2024-40937, CVE-2024-40941, CVE-2024-40987, CVE-2024-40918, CVE-2024-32936, CVE-2024-40999, CVE-2024-40938, CVE-2024-39488, CVE-2024-39510, CVE-2024-40924, CVE-2024-38661, CVE-2024-40989, CVE-2024-39509,…
- Record
USN-6999-2- Updated
- 2026-11-02
OSVUSN-7004-1 No score
linux-azure vulnerabilities
Chenyuan Yang discovered that the CEC driver driver in the Linux kernel contained a use-after-free vulnerability. A local attacker could use this to cause a denial of service (system crash) or possibly execute arbitrary code. (CVE-2024-23848)
It was discovered that the JFS file system contained an out-of-bounds read vulnerability when printing xattr debug information. A local attacker could use this to cause a denial of service (system crash). (CVE-2024-40902)
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;
- MIPS architecture;
- PA-RISC architecture;
- PowerPC architecture;
- RISC-V architecture;
- x86 architecture;
- Block layer subsystem;
- ACPI drivers;
- Drivers core;
- Null block device driver;
- Character device driver;
- TPM device driver;
- Clock framework and drivers;
- CPU frequency scaling framework;
- Hardware crypto device drivers;
- CXL (Compute Express Link) drivers;
- Buffer Sharing and Synchronization framework;
- DMA engine subsystem;
- EFI core;
- FPGA Framework;
- GPU drivers;
- Greybus drivers;
- HID subsystem;
- HW tracing;
- I2C subsystem;
- IIO subsystem;
- InfiniBand drivers;
- Input Device (Mouse) drivers;
- Mailbox framework;
- Media drivers;
- Microchip PCI driver;
- VMware VMCI Driver;
- Network drivers;
- PCI subsystem;
- x86 platform drivers;
- PTP clock framework;
- S/390 drivers;
- SCSI drivers;
- SoundWire subsystem;
- Sonic Silicon Backplane drivers;
- Greybus lights staging drivers;
- Thermal drivers;
- TTY drivers;
- USB subsystem;
- VFIO drivers;
- Framebuffer layer;
- Watchdog drivers;
- 9P distributed file system;
- BTRFS file system;
- File systems infrastructure;
- Ext4 file system;
- F2FS file system;
- JFS file system;
- Network file system server daemon;
- NILFS2 file system;
- NTFS3 file system;
- SMB network file system;
- Tracing file system;
- IOMMU subsystem;
- Tracing infrastructure;
- io_uring subsystem;
- Core kernel;
- BPF subsystem;
- Kernel debugger infrastructure;
- DMA mapping infrastructure;
- IRQ subsystem;
- Memory management;
- 9P file system network protocol;
- Amateur Radio drivers;
- B.A.T.M.A.N. meshing protocol;
- Ethernet bridge;
- Networking core;
- Ethtool driver;
- IPv4 networking;
- IPv6 networking;
- MAC80211 subsystem;
- Multipath TCP;
- Netfilter;
- NET/ROM layer;
- NFC subsystem;
- Network traffic control;
- Sun RPC protocol;
- TIPC protocol;
- TLS protocol;
- Unix domain sockets;
- Wireless networking;
- XFRM subsystem;
- AppArmor security module;
- Integrity Measurement Architecture(IMA) framework;
- Landlock security;
- Linux Security Modules (LSM) Framework;
- SELinux security module;
- Simplified Mandatory Access Control Kernel framework;
- ALSA framework;
- HD-audio driver;
- SOF drivers;
- KVM core; (CVE-2024-36270, CVE-2024-38627, CVE-2024-39508, CVE-2024-41001, CVE-2024-38634, CVE-2024-40979, CVE-2024-40903, CVE-2024-34030, CVE-2024-38621, CVE-2024-34027, CVE-2024-39504, CVE-2024-38385, CVE-2024-36288, CVE-2024-39301, CVE-2024-38628, CVE-2024-42270, CVE-2024-39507, CVE-2024-36286, CVE-2024-40960, CVE-2024-36479, CVE-2024-41002, CVE-2024-36974, CVE-2024-40943, CVE-2024-40976, CVE-2024-38662, CVE-2024-40995, CVE-2024-39497, CVE-2024-31076, CVE-2024-39371, CVE-2024-40983, CVE-2024-40985, CVE-2024-38618, CVE-2024-40914, CVE-2024-40989, CVE-2024-40973, CVE-2024-38663, CVE-2024-39463, CVE-2024-38633, CVE-2024-36978, CVE-2024-40970, CVE-2024-40932, CVE-2024-39480, CVE-2024-39471, CVE-2024-40962, CVE-2024-40986, CVE-2024-40937, CVE-2024-39469, CVE-2024-40904, CVE-2024-39466, CVE-2024-38388, CVE-2024-39494, CVE-2024-41004, CVE-2024-38381, CVE-2022-48772, CVE-2024-33847, CVE-2024-40969, CVE-2024-40957,…
- Record
USN-7004-1- Updated
- 2026-11-02
OSVUSN-7005-1 No score
linux-nvidia, linux-nvidia-lowlatency vulnerabilities
Chenyuan Yang discovered that the CEC driver driver in the Linux kernel contained a use-after-free vulnerability. A local attacker could use this to cause a denial of service (system crash) or possibly execute arbitrary code. (CVE-2024-23848)
It was discovered that the JFS file system contained an out-of-bounds read vulnerability when printing xattr debug information. A local attacker could use this to cause a denial of service (system crash). (CVE-2024-40902)
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;
- MIPS architecture;
- PA-RISC architecture;
- PowerPC architecture;
- RISC-V architecture;
- x86 architecture;
- Block layer subsystem;
- ACPI drivers;
- Drivers core;
- Null block device driver;
- Character device driver;
- Clock framework and drivers;
- CPU frequency scaling framework;
- Hardware crypto device drivers;
- CXL (Compute Express Link) drivers;
- Buffer Sharing and Synchronization framework;
- DMA engine subsystem;
- EFI core;
- FPGA Framework;
- GPU drivers;
- Greybus drivers;
- HID subsystem;
- HW tracing;
- I2C subsystem;
- IIO subsystem;
- InfiniBand drivers;
- Input Device (Mouse) drivers;
- Mailbox framework;
- Media drivers;
- Microchip PCI driver;
- VMware VMCI Driver;
- Network drivers;
- PCI subsystem;
- x86 platform drivers;
- PTP clock framework;
- S/390 drivers;
- SCSI drivers;
- SoundWire subsystem;
- Sonic Silicon Backplane drivers;
- Greybus lights staging drivers;
- Thermal drivers;
- TTY drivers;
- USB subsystem;
- VFIO drivers;
- Framebuffer layer;
- Watchdog drivers;
- 9P distributed file system;
- BTRFS file system;
- File systems infrastructure;
- Ext4 file system;
- F2FS file system;
- JFS file system;
- Network file system server daemon;
- NILFS2 file system;
- NTFS3 file system;
- SMB network file system;
- Tracing file system;
- IOMMU subsystem;
- Tracing infrastructure;
- io_uring subsystem;
- Core kernel;
- BPF subsystem;
- Kernel debugger infrastructure;
- DMA mapping infrastructure;
- IRQ subsystem;
- Memory management;
- 9P file system network protocol;
- Amateur Radio drivers;
- B.A.T.M.A.N. meshing protocol;
- Ethernet bridge;
- Networking core;
- Ethtool driver;
- IPv4 networking;
- IPv6 networking;
- MAC80211 subsystem;
- Multipath TCP;
- Netfilter;
- NET/ROM layer;
- NFC subsystem;
- Network traffic control;
- Sun RPC protocol;
- TIPC protocol;
- TLS protocol;
- Unix domain sockets;
- Wireless networking;
- XFRM subsystem;
- AppArmor security module;
- Integrity Measurement Architecture(IMA) framework;
- Landlock security;
- Linux Security Modules (LSM) Framework;
- SELinux security module;
- Simplified Mandatory Access Control Kernel framework;
- ALSA framework;
- HD-audio driver;
- SOF drivers;
- KVM core; (CVE-2024-40963, CVE-2024-40994, CVE-2024-36481, CVE-2024-39301, CVE-2024-38390, CVE-2024-40976, CVE-2024-40934, CVE-2024-40902, CVE-2024-40916, CVE-2024-39298, CVE-2024-38659, CVE-2024-38384, CVE-2024-38635, CVE-2024-39494, CVE-2024-40926, CVE-2024-40956, CVE-2024-40948, CVE-2024-40920, CVE-2024-38624, CVE-2024-39498, CVE-2024-38780, CVE-2024-39503, CVE-2024-40919, CVE-2024-39505, CVE-2024-40988, CVE-2024-36972, CVE-2024-36974, CVE-2024-39495, CVE-2024-40992, CVE-2024-36015, CVE-2024-38618, CVE-2024-39478, CVE-2024-40975, CVE-2024-39507, CVE-2024-39479, CVE-2024-39291, CVE-2024-40925, CVE-2024-39493, CVE-2024-41005, CVE-2024-40932, CVE-2024-39467, CVE-2024-40973, CVE-2024-38634, CVE-2024-34027, CVE-2024-39462, CVE-2024-40949, CVE-2024-40908, CVE-2024-40929, CVE-2024-38662, CVE-2024-39489, CVE-2024-40953, CVE-2024-38306, CVE-2024-40915, CVE-2024-39470, CVE-2024-40969, CVE-2024-31076, CVE-2024-38663, CVE-2024-38629,…
- Record
USN-7005-1- Updated
- 2026-11-02
OSVUSN-7005-2 No score
linux-nvidia-6.8 vulnerabilities
Chenyuan Yang discovered that the CEC driver driver in the Linux kernel contained a use-after-free vulnerability. A local attacker could use this to cause a denial of service (system crash) or possibly execute arbitrary code. (CVE-2024-23848)
It was discovered that the JFS file system contained an out-of-bounds read vulnerability when printing xattr debug information. A local attacker could use this to cause a denial of service (system crash). (CVE-2024-40902)
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;
- MIPS architecture;
- PA-RISC architecture;
- PowerPC architecture;
- RISC-V architecture;
- x86 architecture;
- Block layer subsystem;
- ACPI drivers;
- Drivers core;
- Null block device driver;
- Character device driver;
- Clock framework and drivers;
- CPU frequency scaling framework;
- Hardware crypto device drivers;
- CXL (Compute Express Link) drivers;
- Buffer Sharing and Synchronization framework;
- DMA engine subsystem;
- EFI core;
- FPGA Framework;
- GPU drivers;
- Greybus drivers;
- HID subsystem;
- HW tracing;
- I2C subsystem;
- IIO subsystem;
- InfiniBand drivers;
- Input Device (Mouse) drivers;
- Mailbox framework;
- Media drivers;
- Microchip PCI driver;
- VMware VMCI Driver;
- Network drivers;
- PCI subsystem;
- x86 platform drivers;
- PTP clock framework;
- S/390 drivers;
- SCSI drivers;
- SoundWire subsystem;
- Sonic Silicon Backplane drivers;
- Greybus lights staging drivers;
- Thermal drivers;
- TTY drivers;
- USB subsystem;
- VFIO drivers;
- Framebuffer layer;
- Watchdog drivers;
- 9P distributed file system;
- BTRFS file system;
- File systems infrastructure;
- Ext4 file system;
- F2FS file system;
- JFS file system;
- Network file system server daemon;
- NILFS2 file system;
- NTFS3 file system;
- SMB network file system;
- Tracing file system;
- IOMMU subsystem;
- Tracing infrastructure;
- io_uring subsystem;
- Core kernel;
- BPF subsystem;
- Kernel debugger infrastructure;
- DMA mapping infrastructure;
- IRQ subsystem;
- Memory management;
- 9P file system network protocol;
- Amateur Radio drivers;
- B.A.T.M.A.N. meshing protocol;
- Ethernet bridge;
- Networking core;
- Ethtool driver;
- IPv4 networking;
- IPv6 networking;
- MAC80211 subsystem;
- Multipath TCP;
- Netfilter;
- NET/ROM layer;
- NFC subsystem;
- Network traffic control;
- Sun RPC protocol;
- TIPC protocol;
- TLS protocol;
- Unix domain sockets;
- Wireless networking;
- XFRM subsystem;
- AppArmor security module;
- Integrity Measurement Architecture(IMA) framework;
- Landlock security;
- Linux Security Modules (LSM) Framework;
- SELinux security module;
- Simplified Mandatory Access Control Kernel framework;
- ALSA framework;
- HD-audio driver;
- SOF drivers;
- KVM core; (CVE-2024-39465, CVE-2024-39492, CVE-2024-40976, CVE-2024-40956, CVE-2024-39480, CVE-2024-39467, CVE-2024-39478, CVE-2024-39489, CVE-2024-41003, CVE-2024-39510, CVE-2024-39498, CVE-2024-40994, CVE-2024-40937, CVE-2024-39488, CVE-2024-40990, CVE-2024-40955, CVE-2024-40905, CVE-2024-39496, CVE-2024-36478, CVE-2024-40920, CVE-2024-40954, CVE-2024-32936, CVE-2024-40919, CVE-2024-40947, CVE-2024-40975, CVE-2024-39481, CVE-2024-40983, CVE-2024-39276, CVE-2024-37026, CVE-2024-40980, CVE-2022-48772, CVE-2024-39470, CVE-2024-40951, CVE-2024-40927, CVE-2024-38635, CVE-2024-40974, CVE-2024-39468, CVE-2024-38384, CVE-2024-37354, CVE-2024-40992, CVE-2024-40934, CVE-2024-40925, CVE-2024-40935, CVE-2024-39473, CVE-2024-40910, CVE-2024-40979, CVE-2024-39501, CVE-2024-38628, CVE-2024-39298, CVE-2024-40909, CVE-2024-38629, CVE-2024-41000, CVE-2024-40989, CVE-2024-40924, CVE-2024-40943, CVE-2024-41006, CVE-2024-38621, CVE-2024-39462,…
- Record
USN-7005-2- Updated
- 2026-11-02
OSVUSN-7008-1 No score
linux-lowlatency-hwe-6.8 vulnerabilities
Chenyuan Yang discovered that the CEC driver driver in the Linux kernel contained a use-after-free vulnerability. A local attacker could use this to cause a denial of service (system crash) or possibly execute arbitrary code. (CVE-2024-23848)
It was discovered that the JFS file system contained an out-of-bounds read vulnerability when printing xattr debug information. A local attacker could use this to cause a denial of service (system crash). (CVE-2024-40902)
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;
- MIPS architecture;
- PA-RISC architecture;
- PowerPC architecture;
- RISC-V architecture;
- User-Mode Linux (UML);
- x86 architecture;
- Block layer subsystem;
- ACPI drivers;
- Drivers core;
- Null block device driver;
- Character device driver;
- TPM device driver;
- Clock framework and drivers;
- CPU frequency scaling framework;
- Hardware crypto device drivers;
- CXL (Compute Express Link) drivers;
- Buffer Sharing and Synchronization framework;
- DMA engine subsystem;
- EFI core;
- FPGA Framework;
- GPU drivers;
- Greybus drivers;
- HID subsystem;
- HW tracing;
- I2C subsystem;
- IIO subsystem;
- InfiniBand drivers;
- Input Device (Mouse) drivers;
- Mailbox framework;
- Media drivers;
- Microchip PCI driver;
- VMware VMCI Driver;
- MMC subsystem;
- Network drivers;
- PCI subsystem;
- x86 platform drivers;
- PTP clock framework;
- S/390 drivers;
- SCSI drivers;
- SoundWire subsystem;
- Sonic Silicon Backplane drivers;
- Greybus lights staging drivers;
- Thermal drivers;
- TTY drivers;
- USB subsystem;
- VFIO drivers;
- Framebuffer layer;
- Watchdog drivers;
- 9P distributed file system;
- BTRFS file system;
- File systems infrastructure;
- Ext4 file system;
- F2FS file system;
- JFS file system;
- Network file system server daemon;
- NILFS2 file system;
- NTFS3 file system;
- SMB network file system;
- Tracing file system;
- IOMMU subsystem;
- Tracing infrastructure;
- io_uring subsystem;
- Core kernel;
- BPF subsystem;
- Kernel debugger infrastructure;
- DMA mapping infrastructure;
- IRQ subsystem;
- Memory management;
- 9P file system network protocol;
- Amateur Radio drivers;
- B.A.T.M.A.N. meshing protocol;
- Ethernet bridge;
- Networking core;
- Ethtool driver;
- IPv4 networking;
- IPv6 networking;
- MAC80211 subsystem;
- Multipath TCP;
- Netfilter;
- NET/ROM layer;
- NFC subsystem;
- Network traffic control;
- Sun RPC protocol;
- TIPC protocol;
- TLS protocol;
- Unix domain sockets;
- Wireless networking;
- XFRM subsystem;
- AppArmor security module;
- Integrity Measurement Architecture(IMA) framework;
- Landlock security;
- Linux Security Modules (LSM) Framework;
- SELinux security module;
- Simplified Mandatory Access Control Kernel framework;
- ALSA framework;
- HD-audio driver;
- SOF drivers;
- KVM core; (CVE-2024-38623, CVE-2024-38662, CVE-2024-39484, CVE-2024-42148, CVE-2024-39493, CVE-2024-38637, CVE-2024-40962, CVE-2024-36281, CVE-2024-40922, CVE-2024-40958, CVE-2024-40920, CVE-2024-40986, CVE-2024-40929, CVE-2024-40967, CVE-2024-39296, CVE-2024-40900, CVE-2024-40995, CVE-2024-40974, CVE-2024-40942, CVE-2024-39464, CVE-2024-40916, CVE-2024-40952, CVE-2024-40997, CVE-2024-41004, CVE-2024-40970, CVE-2024-40911, CVE-2024-40972, CVE-2024-36477, CVE-2024-40996, CVE-2024-40988, CVE-2024-38619, CVE-2024-40998, CVE-2024-38627, CVE-2024-36971, CVE-2024-37021, CVE-2024-40989, CVE-2024-40947, CVE-2024-40957, CVE-2024-39508, CVE-2024-41005, CVE-2024-40931, CVE-2024-34777, CVE-2024-38633, CVE-2024-38663, CVE-2024-36288, CVE-2024-40955, CVE-2024-40973, CVE-2024-39483, CVE-2024-38388, CVE-2024-40976, CVE-2024-38622, CVE-2024-40915, CVE-2024-38661, CVE-2024-38306,…
- Record
USN-7008-1- Updated
- 2026-11-02
OSVUSN-7029-1 No score
linux-hwe-6.8
Chenyuan Yang discovered that the CEC driver driver in the Linux kernel contained a use-after-free vulnerability. A local attacker could use this to cause a denial of service (system crash) or possibly execute arbitrary code. (CVE-2024-23848)
It was discovered that the JFS file system contained an out-of-bounds read vulnerability when printing xattr debug information. A local attacker could use this to cause a denial of service (system crash). (CVE-2024-40902)
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;
- MIPS architecture;
- PA-RISC architecture;
- PowerPC architecture;
- RISC-V architecture;
- User-Mode Linux (UML);
- x86 architecture;
- Block layer subsystem;
- ACPI drivers;
- Drivers core;
- Null block device driver;
- Character device driver;
- TPM device driver;
- Clock framework and drivers;
- CPU frequency scaling framework;
- Hardware crypto device drivers;
- CXL (Compute Express Link) drivers;
- Buffer Sharing and Synchronization framework;
- DMA engine subsystem;
- EFI core;
- FPGA Framework;
- GPU drivers;
- Greybus drivers;
- HID subsystem;
- HW tracing;
- I2C subsystem;
- IIO subsystem;
- InfiniBand drivers;
- Input Device (Mouse) drivers;
- Mailbox framework;
- Media drivers;
- Microchip PCI driver;
- VMware VMCI Driver;
- MMC subsystem;
- Network drivers;
- PCI subsystem;
- x86 platform drivers;
- PTP clock framework;
- S/390 drivers;
- SCSI drivers;
- SoundWire subsystem;
- Sonic Silicon Backplane drivers;
- Greybus lights staging drivers;
- Thermal drivers;
- TTY drivers;
- USB subsystem;
- VFIO drivers;
- Framebuffer layer;
- Watchdog drivers;
- 9P distributed file system;
- BTRFS file system;
- File systems infrastructure;
- Ext4 file system;
- F2FS file system;
- JFS file system;
- Network file system server daemon;
- NILFS2 file system;
- NTFS3 file system;
- SMB network file system;
- Tracing file system;
- IOMMU subsystem;
- Tracing infrastructure;
- io_uring subsystem;
- Core kernel;
- BPF subsystem;
- Kernel debugger infrastructure;
- DMA mapping infrastructure;
- IRQ subsystem;
- Memory management;
- 9P file system network protocol;
- Amateur Radio drivers;
- B.A.T.M.A.N. meshing protocol;
- Ethernet bridge;
- Networking core;
- Ethtool driver;
- IPv4 networking;
- IPv6 networking;
- MAC80211 subsystem;
- Multipath TCP;
- Netfilter;
- NET/ROM layer;
- NFC subsystem;
- Network traffic control;
- Sun RPC protocol;
- TIPC protocol;
- TLS protocol;
- Unix domain sockets;
- Wireless networking;
- XFRM subsystem;
- AppArmor security module;
- Integrity Measurement Architecture(IMA) framework;
- Landlock security;
- Linux Security Modules (LSM) Framework;
- SELinux security module;
- Simplified Mandatory Access Control Kernel framework;
- ALSA framework;
- HD-audio driver;
- SOF drivers;
- KVM core; (CVE-2024-39498, CVE-2024-33847, CVE-2024-39510, CVE-2024-39462, CVE-2024-40930, CVE-2024-38634, CVE-2024-40962, CVE-2024-37078, CVE-2024-39371, CVE-2024-40972, CVE-2024-41002, CVE-2024-40920, CVE-2024-40982, CVE-2024-40915, CVE-2024-40942, CVE-2024-42154, CVE-2024-40937, CVE-2024-40967, CVE-2024-40909, CVE-2024-36244, CVE-2024-33619, CVE-2024-39277, CVE-2024-40900, CVE-2024-38661, CVE-2024-40974, CVE-2024-38618, CVE-2024-32936, CVE-2024-40906, CVE-2024-40919, CVE-2024-39470, CVE-2024-38390, CVE-2024-40966, CVE-2024-39467, CVE-2024-40938, CVE-2024-39471, CVE-2024-39485, CVE-2024-39495, CVE-2024-39492, CVE-2024-39475, CVE-2024-40953, CVE-2024-40939, CVE-2024-39493, CVE-2024-38637, CVE-2024-40945, CVE-2024-41006, CVE-2024-39461, CVE-2024-40948, CVE-2024-40916, CVE-2024-40925, CVE-2024-40956, CVE-2024-40970, CVE-2024-40912, CVE-2024-33621, CVE-2024-40989,…
- Record
USN-7029-1- Updated
- 2026-11-02
Affected products
Affected packages
| Package | Affected | Fixed |
|---|---|---|
linux-ltsAlpaquita:23 |
6.1.92-r0 up to 6.1.97-r0 | 6.1.97-r0 |
linux-ltsAlpaquita:25 |
6.6.89-r0 up to 6.12.41-r0 | 6.12.41-r0 |
linux-ltsAlpaquita:stream |
6.6.100-r0 up to 6.12.41-r0 | 6.12.41-r0 |
KernelLinux |
5.17.0 up to 6.1.93, 6.2.0 up to 6.6.33, 6.7.0 up to 6.9.4 | 6.1.936.6.336.9.4 |
linuxDebian:12 |
before 6.1.94-1, plus listed versions 6.1.27-16.1.37-16.1.38-16.1.38-26.1.38-2~bpo11+1 Show 18 moreShow less6.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-16.1.90-16.1.90-1~bpo11+16.1.94-1~bpo11+1 |
6.1.94-1 |
linuxDebian:13 |
before 6.9.7-1 | 6.9.7-1 |
linuxDebian:14 |
before 6.9.7-1 | 6.9.7-1 |
kernelMageia:9 From an advisory covering 320 CVEs |
before 6.6.37-1.mga9 | 6.6.37-1.mga9 |
kmod-xtables-addonsMageia:9 From an advisory covering 320 CVEs |
before 3.24-59.mga9 | 3.24-59.mga9 |
kmod-virtualboxMageia:9 From an advisory covering 320 CVEs |
before 7.0.18-50.mga9 | 7.0.18-50.mga9 |
Show 163 moreShow less
| Package | Affected | Fixed |
|---|---|---|
dwarvesMageia:9 From an advisory covering 320 CVEs |
before 1.27-1.mga9 | 1.27-1.mga9 |
kernel-linusMageia:9 From an advisory covering 320 CVEs |
before 6.6.37-1.mga9 | 6.6.37-1.mga9 |
kernelopenEuler:24.03-LTS From an advisory covering 21 CVEs |
before 6.6.0-31.0.0.39.oe2403 | 6.6.0-31.0.0.39.oe2403 |
kernel-64kbSUSE:Linux Enterprise Module for Basesystem 15 SP6 From an advisory covering 285 CVEs |
before 6.4.0-150600.23.14.1 | 6.4.0-150600.23.14.1 |
kernel-defaultSUSE:Linux Enterprise Module for Basesystem 15 SP6 From an advisory covering 285 CVEs |
before 6.4.0-150600.23.14.2 | 6.4.0-150600.23.14.2 |
kernel-default-baseSUSE:Linux Enterprise Module for Basesystem 15 SP6 From an advisory covering 285 CVEs |
before 6.4.0-150600.23.14.2.150600.12.4.3 | 6.4.0-150600.23.14.2.150600.12.4.3 |
kernel-sourceSUSE:Linux Enterprise Module for Basesystem 15 SP6 From an advisory covering 285 CVEs |
before 6.4.0-150600.23.14.2 | 6.4.0-150600.23.14.2 |
kernel-zfcpdumpSUSE:Linux Enterprise Module for Basesystem 15 SP6 From an advisory covering 285 CVEs |
before 6.4.0-150600.23.14.2 | 6.4.0-150600.23.14.2 |
kernel-docsSUSE:Linux Enterprise Module for Development Tools 15 SP6 From an advisory covering 285 CVEs |
before 6.4.0-150600.23.14.2 | 6.4.0-150600.23.14.2 |
kernel-obs-buildSUSE:Linux Enterprise Module for Development Tools 15 SP6 From an advisory covering 285 CVEs |
before 6.4.0-150600.23.14.2 | 6.4.0-150600.23.14.2 |
kernel-sourceSUSE:Linux Enterprise Module for Development Tools 15 SP6 From an advisory covering 285 CVEs |
before 6.4.0-150600.23.14.2 | 6.4.0-150600.23.14.2 |
kernel-symsSUSE:Linux Enterprise Module for Development Tools 15 SP6 From an advisory covering 285 CVEs |
before 6.4.0-150600.23.14.2 | 6.4.0-150600.23.14.2 |
kernel-defaultSUSE:Linux Enterprise Module for Legacy 15 SP6 From an advisory covering 285 CVEs |
before 6.4.0-150600.23.14.2 | 6.4.0-150600.23.14.2 |
kernel-defaultSUSE:Linux Enterprise Live Patching 15 SP6 From an advisory covering 285 CVEs |
before 6.4.0-150600.23.14.2 | 6.4.0-150600.23.14.2 |
kernel-livepatch-SLE15-SP6_Update_2SUSE:Linux Enterprise Live Patching 15 SP6 From an advisory covering 285 CVEs |
before 1-150600.13.3.2 | 1-150600.13.3.2 |
kernel-defaultSUSE:Linux Enterprise High Availability Extension 15 SP6 From an advisory covering 285 CVEs |
before 6.4.0-150600.23.14.2 | 6.4.0-150600.23.14.2 |
kernel-defaultSUSE:Linux Enterprise Workstation Extension 15 SP6 From an advisory covering 285 CVEs |
before 6.4.0-150600.23.14.2 | 6.4.0-150600.23.14.2 |
dtb-aarch64openSUSE:Leap 15.6 From an advisory covering 285 CVEs |
before 6.4.0-150600.23.14.1 | 6.4.0-150600.23.14.1 |
kernel-64kbopenSUSE:Leap 15.6 From an advisory covering 285 CVEs |
before 6.4.0-150600.23.14.1 | 6.4.0-150600.23.14.1 |
kernel-debugopenSUSE:Leap 15.6 From an advisory covering 285 CVEs |
before 6.4.0-150600.23.14.2 | 6.4.0-150600.23.14.2 |
kernel-defaultopenSUSE:Leap 15.6 From an advisory covering 285 CVEs |
before 6.4.0-150600.23.14.2 | 6.4.0-150600.23.14.2 |
kernel-default-baseopenSUSE:Leap 15.6 From an advisory covering 285 CVEs |
before 6.4.0-150600.23.14.2.150600.12.4.3 | 6.4.0-150600.23.14.2.150600.12.4.3 |
kernel-docsopenSUSE:Leap 15.6 From an advisory covering 285 CVEs |
before 6.4.0-150600.23.14.2 | 6.4.0-150600.23.14.2 |
kernel-kvmsmallopenSUSE:Leap 15.6 From an advisory covering 285 CVEs |
before 6.4.0-150600.23.14.2 | 6.4.0-150600.23.14.2 |
kernel-obs-buildopenSUSE:Leap 15.6 From an advisory covering 285 CVEs |
before 6.4.0-150600.23.14.2 | 6.4.0-150600.23.14.2 |
kernel-obs-qaopenSUSE:Leap 15.6 From an advisory covering 285 CVEs |
before 6.4.0-150600.23.14.2 | 6.4.0-150600.23.14.2 |
kernel-sourceopenSUSE:Leap 15.6 From an advisory covering 285 CVEs |
before 6.4.0-150600.23.14.2 | 6.4.0-150600.23.14.2 |
kernel-symsopenSUSE:Leap 15.6 From an advisory covering 285 CVEs |
before 6.4.0-150600.23.14.2 | 6.4.0-150600.23.14.2 |
kernel-zfcpdumpopenSUSE:Leap 15.6 From an advisory covering 285 CVEs |
before 6.4.0-150600.23.14.2 | 6.4.0-150600.23.14.2 |
kernel-azureSUSE:Linux Enterprise Module for Public Cloud 15 SP6 From an advisory covering 402 CVEs |
before 6.4.0-150600.8.8.2 | 6.4.0-150600.8.8.2 |
kernel-source-azureSUSE:Linux Enterprise Module for Public Cloud 15 SP6 From an advisory covering 402 CVEs |
before 6.4.0-150600.8.8.2 | 6.4.0-150600.8.8.2 |
kernel-syms-azureSUSE:Linux Enterprise Module for Public Cloud 15 SP6 From an advisory covering 402 CVEs |
before 6.4.0-150600.8.8.1 | 6.4.0-150600.8.8.1 |
kernel-azureopenSUSE:Leap 15.6 From an advisory covering 402 CVEs |
before 6.4.0-150600.8.8.2 | 6.4.0-150600.8.8.2 |
kernel-source-azureopenSUSE:Leap 15.6 From an advisory covering 402 CVEs |
before 6.4.0-150600.8.8.2 | 6.4.0-150600.8.8.2 |
kernel-syms-azureopenSUSE:Leap 15.6 From an advisory covering 402 CVEs |
before 6.4.0-150600.8.8.1 | 6.4.0-150600.8.8.1 |
kernel-livepatch-SLE15-SP6-RT_Update_1SUSE:Linux Enterprise Live Patching 15 SP6 From an advisory covering 783 CVEs |
before 1-150600.1.5.1 | 1-150600.1.5.1 |
kernel-rtSUSE:Real Time Module 15 SP6 From an advisory covering 783 CVEs |
before 6.4.0-150600.10.5.1 | 6.4.0-150600.10.5.1 |
kernel-rt_debugSUSE:Real Time Module 15 SP6 From an advisory covering 783 CVEs |
before 6.4.0-150600.10.5.1 | 6.4.0-150600.10.5.1 |
kernel-source-rtSUSE:Real Time Module 15 SP6 From an advisory covering 783 CVEs |
before 6.4.0-150600.10.5.1 | 6.4.0-150600.10.5.1 |
kernel-syms-rtSUSE:Real Time Module 15 SP6 From an advisory covering 783 CVEs |
before 6.4.0-150600.10.5.1 | 6.4.0-150600.10.5.1 |
kernel-rtopenSUSE:Leap 15.6 From an advisory covering 783 CVEs |
before 6.4.0-150600.10.5.1 | 6.4.0-150600.10.5.1 |
kernel-rt_debugopenSUSE:Leap 15.6 From an advisory covering 783 CVEs |
before 6.4.0-150600.10.5.1 | 6.4.0-150600.10.5.1 |
kernel-source-rtopenSUSE:Leap 15.6 From an advisory covering 783 CVEs |
before 6.4.0-150600.10.5.1 | 6.4.0-150600.10.5.1 |
kernel-syms-rtopenSUSE:Leap 15.6 From an advisory covering 783 CVEs |
before 6.4.0-150600.10.5.1 | 6.4.0-150600.10.5.1 |
kernel-defaultSUSE:Linux Micro 6.0 From an advisory covering 848 CVEs |
before 6.4.0-18.1 | 6.4.0-18.1 |
kernel-default-baseSUSE:Linux Micro 6.0 From an advisory covering 848 CVEs |
before 6.4.0-17.1.1.51 | 6.4.0-17.1.1.51 |
kernel-kvmsmallSUSE:Linux Micro 6.0 From an advisory covering 848 CVEs |
before 6.4.0-18.1 | 6.4.0-18.1 |
kernel-sourceSUSE:Linux Micro 6.0 From an advisory covering 848 CVEs |
before 6.4.0-18.1 | 6.4.0-18.1 |
kernel-rtSUSE:Linux Micro 6.0 From an advisory covering 826 CVEs |
before 6.4.0-9.1 | 6.4.0-9.1 |
kernel-source-rtSUSE:Linux Micro 6.0 From an advisory covering 826 CVEs |
before 6.4.0-9.1 | 6.4.0-9.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-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.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.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-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.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-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.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-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-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.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 |
linux-raspi2Ubuntu: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-riscvUbuntu: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 less5.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.11Ubuntu: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 less5.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.8Ubuntu: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 less5.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.19Ubuntu: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.19Ubuntu: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 less5.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.2Ubuntu: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 less6.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.5Ubuntu: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 less6.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-aws-6.8Ubuntu:22.04:LTS |
before 6.8.0-1015.16~22.04.1, plus listed versions 6.8.0-1009.9~22.04.26.8.0-1010.10~22.04.26.8.0-1011.12~22.04.16.8.0-1013.14~22.04.16.8.0-1014.15~22.04.1 |
6.8.0-1015.16~22.04.1 |
linux-azure-5.19Ubuntu: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.2Ubuntu: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 less6.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.5Ubuntu: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 less6.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-6.8Ubuntu:22.04:LTS |
before 6.8.0-1014.16~22.04.1, plus listed versions 6.8.0-1008.8~22.04.16.8.0-1009.9~22.04.16.8.0-1010.10~22.04.16.8.0-1012.14~22.04.16.8.0-1013.15~22.04.1 |
6.8.0-1014.16~22.04.1 |
linux-azure-fde-5.19Ubuntu: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.2Ubuntu: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 less6.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.19Ubuntu: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.2Ubuntu: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 less6.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.5Ubuntu: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 less6.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-gcp-6.8Ubuntu:22.04:LTS |
before 6.8.0-1014.16~22.04.1, plus listed versions 6.8.0-1010.11~22.04.16.8.0-1011.12~22.04.16.8.0-1012.13~22.04.16.8.0-1013.14~22.04.1 |
6.8.0-1014.16~22.04.1 |
linux-hwe-5.19Ubuntu: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 less5.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.2Ubuntu: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 less6.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.5Ubuntu: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 less6.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-hwe-6.8Ubuntu:22.04:LTS |
before 6.8.0-45.45~22.04.1, plus listed versions 6.8.0-38.38~22.04.16.8.0-39.39~22.04.16.8.0-40.40~22.04.3 |
6.8.0-45.45~22.04.1 |
linux-intel-iot-realtimeUbuntu:22.04:LTS |
All versions, plus listed versions 5.15.0-1073.75 |
None known |
linux-lowlatency-hwe-5.19Ubuntu: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 less5.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.2Ubuntu: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 less6.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.5Ubuntu: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 less6.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-lowlatency-hwe-6.8Ubuntu:22.04:LTS |
before 6.8.0-44.44.1~22.04.1, plus listed versions 6.8.0-38.38.1~22.04.26.8.0-40.40.1~22.04.1 |
6.8.0-44.44.1~22.04.1 |
linux-nvidia-6.2Ubuntu: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.5Ubuntu: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 less6.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-nvidia-6.8Ubuntu:22.04:LTS |
before 6.8.0-1013.14~22.04.1, plus listed versions 6.8.0-1008.8~22.04.16.8.0-1009.9~22.04.16.8.0-1010.10~22.04.16.8.0-1011.11~22.04.16.8.0-1012.12~22.04.1 |
6.8.0-1013.14~22.04.1 |
linux-oem-5.17Ubuntu: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 less5.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.0Ubuntu: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 less6.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.1Ubuntu: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 less6.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.5Ubuntu: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 less6.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.5Ubuntu: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 less6.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-oracle-6.8Ubuntu:22.04:LTS |
before 6.8.0-1012.12~22.04.1, plus listed versions 6.8.0-1006.6~22.04.36.8.0-1008.8~22.04.16.8.0-1010.10~22.04.16.8.0-1011.11~22.04.1 |
6.8.0-1012.12~22.04.1 |
linux-realtimeUbuntu:22.04:LTS |
All versions, plus listed versions 5.15.0-1032.35 |
None known |
linux-riscvUbuntu: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 less5.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.19Ubuntu: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.5Ubuntu: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 less6.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-riscv-6.8Ubuntu:22.04:LTS |
before 6.8.0-44.44.1~22.04.1, plus listed versions 6.8.0-38.38.1~22.04.16.8.0-39.39.1~22.04.16.8.0-40.40.1~22.04.16.8.0-41.41.1~22.04.1 |
6.8.0-44.44.1~22.04.1 |
linux-starfive-5.19Ubuntu: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.2Ubuntu: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.5Ubuntu: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 less6.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 |
linuxUbuntu:24.04:LTS |
before 6.8.0-44.44, plus listed versions 6.5.0-9.96.6.0-14.146.8.0-11.116.8.0-20.206.8.0-22.22 Show 8 moreShow less6.8.0-28.286.8.0-31.316.8.0-35.356.8.0-36.366.8.0-38.386.8.0-39.396.8.0-40.406.8.0-41.41 |
6.8.0-44.44 |
linux-awsUbuntu:24.04:LTS |
before 6.8.0-1015.16, plus listed versions 6.5.0-1008.86.6.0-1001.16.8.0-1001.16.8.0-1006.66.8.0-1008.8 Show 6 moreShow less6.8.0-1009.96.8.0-1010.106.8.0-1011.126.8.0-1012.136.8.0-1013.146.8.0-1014.15 |
6.8.0-1015.16 |
linux-azureUbuntu:24.04:LTS |
before 6.8.0-1014.16, plus listed versions 6.5.0-1007.76.6.0-1001.16.8.0-1001.16.8.0-1005.56.8.0-1006.6 Show 6 moreShow less6.8.0-1007.76.8.0-1008.86.8.0-1009.96.8.0-1010.106.8.0-1012.146.8.0-1013.15 |
6.8.0-1014.16 |
linux-gcpUbuntu:24.04:LTS |
before 6.8.0-1014.16, plus listed versions 6.5.0-1007.76.6.0-1001.16.8.0-1002.26.8.0-1005.56.8.0-1006.6 Show 7 moreShow less6.8.0-1007.76.8.0-1008.96.8.0-1009.106.8.0-1010.116.8.0-1011.126.8.0-1012.136.8.0-1013.14 |
6.8.0-1014.16 |
linux-gkeUbuntu:24.04:LTS |
before 6.8.0-1010.13, plus listed versions 6.8.0-1003.56.8.0-1004.76.8.0-1005.86.8.0-1006.96.8.0-1007.106.8.0-1008.116.8.0-1009.12 |
6.8.0-1010.13 |
linux-ibmUbuntu:24.04:LTS |
before 6.8.0-1012.12, plus listed versions 6.5.0-1009.96.8.0-1001.16.8.0-1003.36.8.0-1004.46.8.0-1005.5 Show 6 moreShow less6.8.0-1006.66.8.0-1007.76.8.0-1008.86.8.0-1009.96.8.0-1010.106.8.0-1011.11 |
6.8.0-1012.12 |
linux-lowlatencyUbuntu:24.04:LTS |
before 6.8.0-44.44.1, plus listed versions 6.5.0-9.9.16.6.0-14.14.16.8.0-7.7.16.8.0-25.25.36.8.0-28.28.1 Show 7 moreShow less6.8.0-31.31.16.8.0-35.35.16.8.0-36.36.16.8.0-38.38.16.8.0-39.39.16.8.0-40.40.16.8.0-41.41.1 |
6.8.0-44.44.1 |
linux-nvidiaUbuntu:24.04:LTS |
before 6.8.0-1013.14, plus listed versions 6.8.0-1007.76.8.0-1008.86.8.0-1009.96.8.0-1010.106.8.0-1011.116.8.0-1012.12 |
6.8.0-1013.14 |
linux-nvidia-lowlatencyUbuntu:24.04:LTS |
before 6.8.0-1013.14.1, plus listed versions 6.8.0-1009.9.16.8.0-1011.11.16.8.0-1012.12.1 |
6.8.0-1013.14.1 |
linux-oem-6.8Ubuntu:24.04:LTS |
before 6.8.0-1012.12, 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 4 moreShow less6.8.0-1008.86.8.0-1009.96.8.0-1010.106.8.0-1011.11 |
6.8.0-1012.12 |
linux-oracleUbuntu:24.04:LTS |
before 6.8.0-1012.12, plus listed versions 6.5.0-1010.106.6.0-1001.16.8.0-1001.16.8.0-1004.46.8.0-1005.5 Show 4 moreShow less6.8.0-1006.66.8.0-1008.86.8.0-1010.106.8.0-1011.11 |
6.8.0-1012.12 |
linux-raspiUbuntu:24.04:LTS |
before 6.8.0-1011.12, plus listed versions 6.5.0-1005.76.7.0-1001.16.8.0-1001.16.8.0-1002.26.8.0-1003.3 Show 7 moreShow less6.8.0-1004.46.8.0-1005.56.8.0-1006.66.8.0-1007.76.8.0-1008.86.8.0-1009.106.8.0-1010.11 |
6.8.0-1011.12 |
linux-riscvUbuntu:24.04:LTS |
before 6.8.0-44.44.1, 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 5 moreShow less6.8.0-36.36.16.8.0-38.38.16.8.0-39.39.16.8.0-40.40.16.8.0-41.41.1 |
6.8.0-44.44.1 |
linux-raspi-realtimeUbuntu:Pro:Realtime:24.04:LTS |
before 6.8.0-2010.10, plus listed versions 6.7.0-2001.16.8.0-2001.16.8.0-2002.26.8.0-2004.46.8.0-2005.5 Show 4 moreShow less6.8.0-2006.66.8.0-2007.76.8.0-2008.86.8.0-2009.9 |
6.8.0-2010.10 |
linux-realtimeUbuntu:Pro:Realtime:24.04:LTS |
before 6.8.1-1008.8, plus listed versions 6.8.0-1008.196.8.1-1001.16.8.1-1002.26.8.1-1003.36.8.1-1004.46.8.1-1005.56.8.1-1006.66.8.1-1007.7 |
6.8.1-1008.8 |
linuxUbuntu:24.04:LTS From an advisory covering 220 CVEs |
before 6.8.0-44.44, plus listed versions 6.5.0-9.96.6.0-14.146.8.0-11.116.8.0-20.206.8.0-22.22 Show 8 moreShow less6.8.0-28.286.8.0-31.316.8.0-35.356.8.0-36.366.8.0-38.386.8.0-39.396.8.0-40.406.8.0-41.41 |
6.8.0-44.44 |
linux-awsUbuntu:24.04:LTS From an advisory covering 220 CVEs |
before 6.8.0-1015.16, plus listed versions 6.5.0-1008.86.6.0-1001.16.8.0-1001.16.8.0-1006.66.8.0-1008.8 Show 6 moreShow less6.8.0-1009.96.8.0-1010.106.8.0-1011.126.8.0-1012.136.8.0-1013.146.8.0-1014.15 |
6.8.0-1015.16 |
linux-gcpUbuntu:24.04:LTS From an advisory covering 220 CVEs |
before 6.8.0-1014.16, plus listed versions 6.5.0-1007.76.6.0-1001.16.8.0-1002.26.8.0-1005.56.8.0-1006.6 Show 7 moreShow less6.8.0-1007.76.8.0-1008.96.8.0-1009.106.8.0-1010.116.8.0-1011.126.8.0-1012.136.8.0-1013.14 |
6.8.0-1014.16 |
linux-gkeUbuntu:24.04:LTS From an advisory covering 220 CVEs |
before 6.8.0-1010.13, plus listed versions 6.8.0-1003.56.8.0-1004.76.8.0-1005.86.8.0-1006.96.8.0-1007.106.8.0-1008.116.8.0-1009.12 |
6.8.0-1010.13 |
linux-ibmUbuntu:24.04:LTS From an advisory covering 220 CVEs |
before 6.8.0-1012.12, plus listed versions 6.5.0-1009.96.8.0-1001.16.8.0-1003.36.8.0-1004.46.8.0-1005.5 Show 6 moreShow less6.8.0-1006.66.8.0-1007.76.8.0-1008.86.8.0-1009.96.8.0-1010.106.8.0-1011.11 |
6.8.0-1012.12 |
linux-lowlatencyUbuntu:24.04:LTS From an advisory covering 220 CVEs |
before 6.8.0-44.44.1, plus listed versions 6.5.0-9.9.16.6.0-14.14.16.8.0-7.7.16.8.0-25.25.36.8.0-28.28.1 Show 7 moreShow less6.8.0-31.31.16.8.0-35.35.16.8.0-36.36.16.8.0-38.38.16.8.0-39.39.16.8.0-40.40.16.8.0-41.41.1 |
6.8.0-44.44.1 |
linux-oem-6.8Ubuntu:24.04:LTS From an advisory covering 220 CVEs |
before 6.8.0-1012.12, 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 4 moreShow less6.8.0-1008.86.8.0-1009.96.8.0-1010.106.8.0-1011.11 |
6.8.0-1012.12 |
linux-oracleUbuntu:24.04:LTS From an advisory covering 220 CVEs |
before 6.8.0-1012.12, plus listed versions 6.5.0-1010.106.6.0-1001.16.8.0-1001.16.8.0-1004.46.8.0-1005.5 Show 4 moreShow less6.8.0-1006.66.8.0-1008.86.8.0-1010.106.8.0-1011.11 |
6.8.0-1012.12 |
linux-raspiUbuntu:24.04:LTS From an advisory covering 220 CVEs |
before 6.8.0-1011.12, plus listed versions 6.5.0-1005.76.7.0-1001.16.8.0-1001.16.8.0-1002.26.8.0-1003.3 Show 7 moreShow less6.8.0-1004.46.8.0-1005.56.8.0-1006.66.8.0-1007.76.8.0-1008.86.8.0-1009.106.8.0-1010.11 |
6.8.0-1011.12 |
linux-azureUbuntu:24.04:LTS From an advisory covering 221 CVEs |
before 6.8.0-1014.16, plus listed versions 6.5.0-1007.76.6.0-1001.16.8.0-1001.16.8.0-1005.56.8.0-1006.6 Show 6 moreShow less6.8.0-1007.76.8.0-1008.86.8.0-1009.96.8.0-1010.106.8.0-1012.146.8.0-1013.15 |
6.8.0-1014.16 |
linux-nvidiaUbuntu:24.04:LTS From an advisory covering 219 CVEs |
before 6.8.0-1013.14, plus listed versions 6.8.0-1007.76.8.0-1008.86.8.0-1009.96.8.0-1010.106.8.0-1011.116.8.0-1012.12 |
6.8.0-1013.14 |
linux-nvidia-lowlatencyUbuntu:24.04:LTS From an advisory covering 219 CVEs |
before 6.8.0-1013.14.1, plus listed versions 6.8.0-1009.9.16.8.0-1011.11.16.8.0-1012.12.1 |
6.8.0-1013.14.1 |
linux-nvidia-6.8Ubuntu:22.04:LTS From an advisory covering 219 CVEs |
before 6.8.0-1013.14~22.04.1, plus listed versions 6.8.0-1008.8~22.04.16.8.0-1009.9~22.04.16.8.0-1010.10~22.04.16.8.0-1011.11~22.04.16.8.0-1012.12~22.04.1 |
6.8.0-1013.14~22.04.1 |
linux-lowlatency-hwe-6.8Ubuntu:22.04:LTS From an advisory covering 222 CVEs |
before 6.8.0-44.44.1~22.04.1, plus listed versions 6.8.0-38.38.1~22.04.26.8.0-40.40.1~22.04.1 |
6.8.0-44.44.1~22.04.1 |
linux-hwe-6.8Ubuntu:22.04:LTS From an advisory covering 227 CVEs |
before 6.8.0-45.45~22.04.1, plus listed versions 6.8.0-38.38~22.04.16.8.0-39.39~22.04.16.8.0-40.40~22.04.3 |
6.8.0-45.45~22.04.1 |
History
| Recorded | Changed | Sources |
|---|---|---|
| affected | ||
| facts | ||
| first indexed | CVE List, EUVD, GitHub Advisories, NVD, OSV |
Dates are when Every CVE recorded each change. Upstream dates may differ.
In short
CVE-2024-38636 is a medium vulnerability (CVSS 5.5) in Linux, published June 21, 2024. No source lists public exploit code. EPSS puts the chance of exploitation in the next 30 days at 0.21%, the 11th percentile. Fixed in linux-lts 6.1.97-r0.
References
git.kernel.org/stable/c/1a9225fdd0ec95fcf32936bcea9ceef0cf1512dc
git.kernel.org/stable/c/2b2611a42462c6c685d40b5f3aedcd8d21c27065
git.kernel.org/stable/c/e8b485e39b4d17afa9a2821fc778d5a67abfc03a
git.kernel.org/stable/c/33e62cd7b4c281cd737c62e5d8c4f0e602a8c5c5
nvd.nist.gov/vuln/detail/CVE-2024-38636
github.com/advisories/GHSA-pwgj-c4vj-63r9
Show 194 moreShow less
docs.bell-sw.com/security/cves/CVE-2024-38636
github.com/CVEProject/cvelistV5/tree/main/cves/2024/38xxx/CVE-2024-38636.json
git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
security-tracker.debian.org/tracker/CVE-2024-38636
advisories.mageia.org/MGASA-2024-0263.html
bugs.mageia.org/show_bug.cgi?id=33373
cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.1.37
cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.1.36
cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.1.35
cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.1.34
cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.1.33
cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.1.32
cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.31
cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.30
cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.29
advisories.mageia.org/MGASA-2024-0266.html
bugs.mageia.org/show_bug.cgi?id=33374
openeuler.org/en/security/safety-bulletin/detail.html?id=openEuler-SA-2024-1766
nvd.nist.gov/vuln/detail/CVE-2024-36477
nvd.nist.gov/vuln/detail/CVE-2024-36883
nvd.nist.gov/vuln/detail/CVE-2024-36898
nvd.nist.gov/vuln/detail/CVE-2024-36902
nvd.nist.gov/vuln/detail/CVE-2024-36903
nvd.nist.gov/vuln/detail/CVE-2024-36905
nvd.nist.gov/vuln/detail/CVE-2024-36919
nvd.nist.gov/vuln/detail/CVE-2024-36928
nvd.nist.gov/vuln/detail/CVE-2024-36968
nvd.nist.gov/vuln/detail/CVE-2024-36974
nvd.nist.gov/vuln/detail/CVE-2024-36975
nvd.nist.gov/vuln/detail/CVE-2024-36977
nvd.nist.gov/vuln/detail/CVE-2024-36978
nvd.nist.gov/vuln/detail/CVE-2024-38538
nvd.nist.gov/vuln/detail/CVE-2024-38541
nvd.nist.gov/vuln/detail/CVE-2024-38549
nvd.nist.gov/vuln/detail/CVE-2024-38587
nvd.nist.gov/vuln/detail/CVE-2024-38596
nvd.nist.gov/vuln/detail/CVE-2024-38601
nvd.nist.gov/vuln/detail/CVE-2024-38605
suse.com/support/update/announcement/2024/suse-su-20242571-1
bugzilla.suse.com/1186716
bugzilla.suse.com/1195775
bugzilla.suse.com/1204562
bugzilla.suse.com/1209834
bugzilla.suse.com/1217481
bugzilla.suse.com/1217912
bugzilla.suse.com/1218442
bugzilla.suse.com/1219224
bugzilla.suse.com/1219478
bugzilla.suse.com/1219596
bugzilla.suse.com/1219633
bugzilla.suse.com/1219847
bugzilla.suse.com/1219953
bugzilla.suse.com/1221086
bugzilla.suse.com/1221777
bugzilla.suse.com/1221958
bugzilla.suse.com/1222011
bugzilla.suse.com/1222015
bugzilla.suse.com/1222080
bugzilla.suse.com/1222241
bugzilla.suse.com/1222380
bugzilla.suse.com/1222588
bugzilla.suse.com/1222617
bugzilla.suse.com/1222619
bugzilla.suse.com/1222809
bugzilla.suse.com/1222810
bugzilla.suse.com/1223018
bugzilla.suse.com/1223265
bugzilla.suse.com/1224049
bugzilla.suse.com/1224187
bugzilla.suse.com/1224439
bugzilla.suse.com/1224497
bugzilla.suse.com/1224498
bugzilla.suse.com/1224515
bugzilla.suse.com/1224520
bugzilla.suse.com/1224523
bugzilla.suse.com/1224539
bugzilla.suse.com/1224540
bugzilla.suse.com/1224549
bugzilla.suse.com/1224572
bugzilla.suse.com/1224575
bugzilla.suse.com/1224583
bugzilla.suse.com/1224584
bugzilla.suse.com/1224606
bugzilla.suse.com/1224612
bugzilla.suse.com/1224614
bugzilla.suse.com/1224619
bugzilla.suse.com/1224655
bugzilla.suse.com/1224659
bugzilla.suse.com/1224661
bugzilla.suse.com/1224662
suse.com/security/cve/CVE-2021-47432
suse.com/security/cve/CVE-2022-48772
suse.com/security/cve/CVE-2023-52622
suse.com/security/cve/CVE-2023-52656
suse.com/security/cve/CVE-2023-52672
suse.com/security/cve/CVE-2023-52699
suse.com/security/cve/CVE-2023-52735
suse.com/security/cve/CVE-2023-52749
suse.com/security/cve/CVE-2023-52750
suse.com/security/cve/CVE-2023-52753
suse.com/security/cve/CVE-2023-52754
suse.com/security/cve/CVE-2023-52757
suse.com/security/cve/CVE-2023-52759
suse.com/security/cve/CVE-2023-52762
suse.com/security/cve/CVE-2023-52763
suse.com/security/cve/CVE-2023-52764
suse.com/security/cve/CVE-2023-52765
suse.com/security/cve/CVE-2023-52766
suse.com/security/cve/CVE-2023-52767
suse.com/security/cve/CVE-2023-52768
suse.com/security/cve/CVE-2023-52769
suse.com/security/cve/CVE-2023-52773
suse.com/security/cve/CVE-2023-52774
suse.com/security/cve/CVE-2023-52776
suse.com/security/cve/CVE-2023-52777
suse.com/security/cve/CVE-2023-52780
suse.com/security/cve/CVE-2023-52781
suse.com/security/cve/CVE-2023-52782
suse.com/security/cve/CVE-2023-52783
suse.com/security/cve/CVE-2023-52784
suse.com/security/cve/CVE-2023-52786
suse.com/security/cve/CVE-2023-52787
suse.com/security/cve/CVE-2023-52788
suse.com/security/cve/CVE-2023-52789
suse.com/security/cve/CVE-2023-52791
suse.com/security/cve/CVE-2023-52792
suse.com/security/cve/CVE-2023-52794
suse.com/security/cve/CVE-2023-52795
suse.com/security/cve/CVE-2023-52796
suse.com/security/cve/CVE-2023-52798
suse.com/security/cve/CVE-2023-52799
suse.com/security/cve/CVE-2023-52800
suse.com/security/cve/CVE-2023-52801
suse.com/security/cve/CVE-2023-52803
suse.com/security/cve/CVE-2023-52804
suse.com/security/cve/CVE-2023-52805
suse.com/security/cve/CVE-2023-52806
suse.com/security/cve/CVE-2023-52807
suse.com/security/cve/CVE-2023-52808
suse.com/security/cve/CVE-2023-52809
suse.com/security/cve/CVE-2023-52810
ubuntu.com/security/CVE-2024-38636
cve.org/CVERecord?id=CVE-2024-38636
git.kernel.org/linus/33e62cd7b4c281cd737c62e5d8c4f0e602a8c5c5
ubuntu.com/security/notices/USN-6999-1
ubuntu.com/security/notices/USN-7004-1
ubuntu.com/security/notices/USN-7005-1
ubuntu.com/security/notices/USN-7008-1
ubuntu.com/security/notices/USN-7005-2
ubuntu.com/security/notices/USN-6999-2
ubuntu.com/security/notices/USN-7029-1
ubuntu.com/security/CVE-2022-48772
ubuntu.com/security/CVE-2023-52884
ubuntu.com/security/CVE-2024-23848
ubuntu.com/security/CVE-2024-31076
ubuntu.com/security/CVE-2024-32936
ubuntu.com/security/CVE-2024-33619
ubuntu.com/security/CVE-2024-33621
ubuntu.com/security/CVE-2024-33847
ubuntu.com/security/CVE-2024-34027
ubuntu.com/security/CVE-2024-34030
ubuntu.com/security/CVE-2024-34777
ubuntu.com/security/CVE-2024-35247
ubuntu.com/security/CVE-2024-36015
ubuntu.com/security/CVE-2024-36244
ubuntu.com/security/CVE-2024-36270
ubuntu.com/security/CVE-2024-36281
ubuntu.com/security/CVE-2024-36286
ubuntu.com/security/CVE-2024-36288
ubuntu.com/security/CVE-2024-36477
ubuntu.com/security/CVE-2024-36478
ubuntu.com/security/CVE-2024-36479
ubuntu.com/security/CVE-2024-36481
ubuntu.com/security/CVE-2024-36484
ubuntu.com/security/CVE-2024-36489
ubuntu.com/security/CVE-2024-36971
ubuntu.com/security/CVE-2024-36972
ubuntu.com/security/CVE-2024-36973
ubuntu.com/security/CVE-2024-36974
ubuntu.com/security/CVE-2024-36978
ubuntu.com/security/CVE-2024-37021
ubuntu.com/security/CVE-2024-37026
ubuntu.com/security/CVE-2024-37078
ubuntu.com/security/CVE-2024-37354
ubuntu.com/security/CVE-2024-37356
ubuntu.com/security/CVE-2024-38306
ubuntu.com/security/CVE-2024-38381
ubuntu.com/security/CVE-2024-38384
ubuntu.com/security/CVE-2024-38385
ubuntu.com/security/CVE-2024-38388
ubuntu.com/security/CVE-2024-38390
ubuntu.com/security/CVE-2024-38618
ubuntu.com/security/CVE-2024-38619
ubuntu.com/security/CVE-2024-38621
Left out here: 1 version, 1,982 references and the rest of 13 source descriptions. The JSON record has them.