CVE-2024-41009
bpf: Fix overrunning reservations in ringbuf
In the Linux kernel, the following vulnerability has been resolved:
bpf: Fix overrunning reservations in ringbuf
The BPF ring buffer internally is implemented as a power-of-2 sized circular buffer, with two logical and ever-increasing counters: consumer_pos is the consumer counter to show which logical position the consumer consumed the data, and producer_pos which is the producer counter denoting the amount of data reserved by all producers.
Each time a record is reserved, the producer that "owns" the record will successfully advance producer counter. In user space each time a record is read, the consumer of the data advanced the consumer counter once it finished processing. Both counters are stored in separate pages so that from user space, the producer counter is read-only and the consumer counter is read-write.
One aspect that simplifies and thus speeds up the implementation of both producers and consumers is how the data area is mapped twice contiguously back-to-back in the virtual memory, allowing to not take any special measures for samples that have to wrap around at the end of the circular buffer data area, because the next page after the last data page would be first data page again, and thus the sample will still appear completely contiguous in virtual memory.
Each record has a struct bpf_ringbuf_hdr { u32 len; u32 pg_off; } header for
book-keeping the length and offset, and is inaccessible to the BPF program.
Helpers like bpf_ringbuf_reserve() return (void *)hdr + BPF_RINGBUF_HDR_SZ
for the BPF program to use. Bing-Jhong and Muhammad reported that it is however
possible to make a second allocated memory chunk overlapping with the first
chunk and as a result, the BPF program is now able to edit first chunk's
header.
For example, consider the creation of a BPF_MAP_TYPE_RINGBUF map with size
of 0x4000. Next, the consumer_pos is modified to 0x3000 /before/ a call to
bpf_ringbuf_reserve() is made. This will allocate a chunk A, which is in
[0x0,0x3008], and the BPF program is able to edit [0x8,0x3008]. Now, lets
allocate a chunk B with size 0x3000. This will succeed because consumer_pos
was edited ahead of time to pass the new_prod_pos - cons_pos > rb->mask
check. Chunk B will be in range [0x3008,0x6010], and the BPF program is able
to edit [0x3010,0x6010]. Due to the ring buffer memory layout mentioned
earlier, the ranges [0x0,0x4000] and [0x4000,0x8000] point to the same data
pages. This means that chunk B at [0x4000,0x4008] is chunk A's header.
bpf_ringbuf_submit() / bpf_ringbuf_discard() use the header's pg_off to then
locate the bpf_ringbuf itself via bpf_ringbuf_restore_from_rec(). Once chunk
B modified chunk A's header, then bpf_ringbuf_commit() refers to the wrong
page and could cause a crash.
Fix it by calculating the oldest pending_pos and check whether the range from the oldest outstanding record to the newest would span beyond the ring buffer size. If that is the case, then reject the request. We've tested with the ring buffer benchmark in BPF selftests (./benchs/run_bench_ringbufs.sh) before/after the fix and while it seems a bit slower on some benchmarks, it is still not significantly enough to matter.
Attack profile
How easy it is to exploit
- Attack vector
- Local
- Complexity
- Low
- Privileges needed
- Low
- User interaction
- None
What an attacker can affect
- Confidentiality
- High
- Integrity
- High
- Availability
- High
Exploit likelihood
What each source reports
CVE List Score used
7.8
bpf: Fix overrunning reservations in ringbuf
In the Linux kernel, the following vulnerability has been resolved:
bpf: Fix overrunning reservations in ringbuf
The BPF ring buffer internally is implemented as a power-of-2 sized circular buffer, with two logical and ever-increasing counters: consumer_pos is the consumer counter to show which logical position the consumer consumed the data, and producer_pos which is the producer counter denoting the amount of data reserved by all producers.
Each time a record is reserved, the producer that "owns" the record will successfully advance producer counter. In user space each time a record is read, the consumer of the data advanced the consumer counter once it finished processing. Both counters are stored in separate pages so that from user space, the producer counter is read-only and the consumer counter is read-write.
One aspect that simplifies and thus speeds up the implementation of both producers and consumers is how the data area is mapped twice contiguously back-to-back in the virtual memory, allowing to not take any special measures for samples that have to wrap around at the end of the circular buffer data area, because the next page after the last data page would be first data page again, and thus the sample will still appear completely contiguous in virtual memory.
Each record has a struct bpf_ringbuf_hdr { u32 len; u32 pg_off; } header for
book-keeping the length and offset, and is inaccessible to the BPF program.
Helpers like bpf_ringbuf_reserve() return (void *)hdr + BPF_RINGBUF_HDR_SZ
for the BPF program to use. Bing-Jhong and Muhammad reported that it is however
possible to make a second allocated memory chunk overlapping with the first
chunk and as a result, the BPF program is now able to edit first chunk's
header.
For example, consider the creation of a BPF_MAP_TYPE_RINGBUF map with size
of 0x4000. Next, the consumer_pos is modified to 0x3000 /before/ a call to
bpf_ringbuf_reserve() is made. This will allocate a chunk A, which is in
[0x0,0x3008], and the BPF program is able to edit [0x8,0x3008]. Now, lets
allocate a chunk B with size 0x3000. This will succeed because consumer_pos
was edited ahead of time to pass the new_prod_pos - cons_pos > rb->mask
check. Chunk B will be in range [0x3008,0x6010], and the BPF program is able
to edit [0x3010,0x6010]. Due to the ring buffer memory layout mentioned
earlier, the ranges [0x0,0x4000] and [0x4000,0x8000] point to the same data
pages. This means that chunk B at [0x4000,0x4008] is chunk A's header.
bpf_ringbuf_submit() / bpf_ringbuf_discard() use the header's pg_off to then
locate the bpf_ringbuf itself via bpf_ringbuf_restore_from_rec(). Once chunk
B modified chunk A's header, then bpf_ringbuf_commit() refers to the wrong
page and could cause a crash.
Fix it by calculating the oldest pending_pos and check whether the range from the oldest outstanding record to the newest would span beyond the ring buffer size. If that is the case, then reject the request. We've tested with the ring buffer benchmark in BPF selftests (./benchs/run_bench_ringbufs.sh) before/after the fix and while it seems a bit slower on some benchmarks, it is still not significantly enough to matter.
- Record
CVE-2024-41009- CVSS 3.1
- 7.8 High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H - Updated
- 2026-11-02
EUVDEUVD-2024-39358
7.8
In the Linux kernel, the following vulnerability has been resolved:
bpf: Fix overrunning reservations in ringbuf
The BPF ring buffer internally is implemented as a power-of-2 sized circular buffer, with two logical and ever-increasing counters: consumer_pos is the consumer counter to show which logical position the consumer consumed the data, and producer_pos which is the producer counter denoting the amount of data reserved by all producers.
Each time a record is reserved, the producer that "owns" the record will successfully advance producer counter. In user space each time a record is read, the consumer of the data advanced the consumer counter once it finished processing. Both counters are stored in separate pages so that from user space, the producer counter is read-only and the consumer counter is read-write.
One aspect that simplifies and thus speeds up the implementation of both producers and consumers is how the data area is mapped twice contiguously back-to-back in the virtual memory, allowing to not take any special measures for samples that have to wrap around at the end of the circular buffer data area, because the next page after the last data page would be first data page again, and thus the sample will still appear completely contiguous in virtual memory.
Each record has a struct bpf_ringbuf_hdr { u32 len; u32 pg_off; } header for
book-keeping the length and offset, and is inaccessible to the BPF program.
Helpers like bpf_ringbuf_reserve() return (void *)hdr + BPF_RINGBUF_HDR_SZ
for the BPF program to use. Bing-Jhong and Muhammad reported that it is however
possible to make a second allocated memory chunk overlapping with the first
chunk and as a result, the BPF program is now able to edit first chunk's
header.
For example, consider the creation of a BPF_MAP_TYPE_RINGBUF map with size
of 0x4000. Next, the consumer_pos is modified to 0x3000 /before/ a call to
bpf_ringbuf_reserve() is made. This will allocate a chunk A, which is in
[0x0,0x3008], and the BPF program is able to edit [0x8,0x3008]. Now, lets
allocate a chunk B with size 0x3000. This will succeed because consumer_pos
was edited ahead of time to pass the new_prod_pos - cons_pos > rb->mask
check. Chunk B will be in range [0x3008,0x6010], and the BPF program is able
to edit [0x3010,0x6010]. Due to the ring buffer memory layout mentioned
earlier, the ranges [0x0,0x4000] and [0x4000,0x8000] point to the same data
pages. This means that chunk B at [0x4000,0x4008] is chunk A's header.
bpf_ringbuf_submit() / bpf_ringbuf_discard() use the header's pg_off to then
locate the bpf_ringbuf itself via bpf_ringbuf_restore_from_rec(). Once chunk
B modified chunk A's header, then bpf_ringbuf_commit() refers to the wrong
page and could cause a crash.
Fix it by calculating the oldest pending_pos and check whether the range from the oldest outstanding record to the newest would span beyond the ring buffer size. If that is the case, then reject the request. We've tested with the ring buffer benchmark in BPF selftests (./benchs/run_bench_ringbufs.sh) before/after the fix and while it seems a bit slower on some benchmarks, it is still not significantly enough to matter.
- Record
EUVD-2024-39358- CVSS 3.1
- 7.8 High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H - Updated
- 2026-11-02
GitHub AdvisoriesGHSA-qvfw-rqcg-jh9g
5.5
In the Linux kernel, the following vulnerability has been resolved: bpf: Fix overrunning...
In the Linux kernel, the following vulnerability has been resolved:
bpf: Fix overrunning reservations in ringbuf
The BPF ring buffer internally is implemented as a power-of-2 sized circular buffer, with two logical and ever-increasing counters: consumer_pos is the consumer counter to show which logical position the consumer consumed the data, and producer_pos which is the producer counter denoting the amount of data reserved by all producers.
Each time a record is reserved, the producer that "owns" the record will successfully advance producer counter. In user space each time a record is read, the consumer of the data advanced the consumer counter once it finished processing. Both counters are stored in separate pages so that from user space, the producer counter is read-only and the consumer counter is read-write.
One aspect that simplifies and thus speeds up the implementation of both producers and consumers is how the data area is mapped twice contiguously back-to-back in the virtual memory, allowing to not take any special measures for samples that have to wrap around at the end of the circular buffer data area, because the next page after the last data page would be first data page again, and thus the sample will still appear completely contiguous in virtual memory.
Each record has a struct bpf_ringbuf_hdr { u32 len; u32 pg_off; } header for
book-keeping the length and offset, and is inaccessible to the BPF program.
Helpers like bpf_ringbuf_reserve() return (void *)hdr + BPF_RINGBUF_HDR_SZ
for the BPF program to use. Bing-Jhong and Muhammad reported that it is however
possible to make a second allocated memory chunk overlapping with the first
chunk and as a result, the BPF program is now able to edit first chunk's
header.
For example, consider the creation of a BPF_MAP_TYPE_RINGBUF map with size
of 0x4000. Next, the consumer_pos is modified to 0x3000 /before/ a call to
bpf_ringbuf_reserve() is made. This will allocate a chunk A, which is in
[0x0,0x3008], and the BPF program is able to edit [0x8,0x3008]. Now, lets
allocate a chunk B with size 0x3000. This will succeed because consumer_pos
was edited ahead of time to pass the new_prod_pos - cons_pos > rb->mask
check. Chunk B will be in range [0x3008,0x6010], and the BPF program is able
to edit [0x3010,0x6010]. Due to the ring buffer memory layout mentioned
earlier, the ranges [0x0,0x4000] and [0x4000,0x8000] point to the same data
pages. This means that chunk B at [0x4000,0x4008] is chunk A's header.
bpf_ringbuf_submit() / bpf_ringbuf_discard() use the header's pg_off to then
locate the bpf_ringbuf itself via bpf_ringbuf_restore_from_rec(). Once chunk
B modified chunk A's header, then bpf_ringbuf_commit() refers to the wrong
page and could cause a crash.
Fix it by calculating the oldest pending_pos and check whether the range from the oldest outstanding record to the newest would span beyond the ring buffer size. If that is the case, then reject the request. We've tested with the ring buffer benchmark in BPF selftests (./benchs/run_bench_ringbufs.sh) before/after the fix and while it seems a bit slower on some benchmarks, it is still not significantly enough to matter.
- Record
GHSA-qvfw-rqcg-jh9g- 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 - Weakness
- CWE-770
- Updated
- 2026-11-02
NVD
7.8
In the Linux kernel, the following vulnerability has been resolved:
bpf: Fix overrunning reservations in ringbuf
The BPF ring buffer internally is implemented as a power-of-2 sized circular buffer, with two logical and ever-increasing counters: consumer_pos is the consumer counter to show which logical position the consumer consumed the data, and producer_pos which is the producer counter denoting the amount of data reserved by all producers.
Each time a record is reserved, the producer that "owns" the record will successfully advance producer counter. In user space each time a record is read, the consumer of the data advanced the consumer counter once it finished processing. Both counters are stored in separate pages so that from user space, the producer counter is read-only and the consumer counter is read-write.
One aspect that simplifies and thus speeds up the implementation of both producers and consumers is how the data area is mapped twice contiguously back-to-back in the virtual memory, allowing to not take any special measures for samples that have to wrap around at the end of the circular buffer data area, because the next page after the last data page would be first data page again, and thus the sample will still appear completely contiguous in virtual memory.
Each record has a struct bpf_ringbuf_hdr { u32 len; u32 pg_off; } header for
book-keeping the length and offset, and is inaccessible to the BPF program.
Helpers like bpf_ringbuf_reserve() return (void *)hdr + BPF_RINGBUF_HDR_SZ
for the BPF program to use. Bing-Jhong and Muhammad reported that it is however
possible to make a second allocated memory chunk overlapping with the first
chunk and as a result, the BPF program is now able to edit first chunk's
header.
For example, consider the creation of a BPF_MAP_TYPE_RINGBUF map with size
of 0x4000. Next, the consumer_pos is modified to 0x3000 /before/ a call to
bpf_ringbuf_reserve() is made. This will allocate a chunk A, which is in
[0x0,0x3008], and the BPF program is able to edit [0x8,0x3008]. Now, lets
allocate a chunk B with size 0x3000. This will succeed because consumer_pos
was edited ahead of time to pass the new_prod_pos - cons_pos > rb->mask
check. Chunk B will be in range [0x3008,0x6010], and the BPF program is able
to edit [0x3010,0x6010]. Due to the ring buffer memory layout mentioned
earlier, the ranges [0x0,0x4000] and [0x4000,0x8000] point to the same data
pages. This means that chunk B at [0x4000,0x4008] is chunk A's header.
bpf_ringbuf_submit() / bpf_ringbuf_discard() use the header's pg_off to then
locate the bpf_ringbuf itself via bpf_ringbuf_restore_from_rec(). Once chunk
B modified chunk A's header, then bpf_ringbuf_commit() refers to the wrong
page and could cause a crash.
Fix it by calculating the oldest pending_pos and check whether the range from the oldest outstanding record to the newest would span beyond the ring buffer size. If that is the case, then reject the request. We've tested with the ring buffer benchmark in BPF selftests (./benchs/run_bench_ringbufs.sh) before/after the fix and while it seems a bit slower on some benchmarks, it is still not significantly enough to matter.
- Record
CVE-2024-41009- CVSS 3.1
- 7.8 High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H - 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 - Weakness
- CWE-770
- Updated
- 2026-11-02
OSVAZL-43396
5.5
CVE-2024-41009 affecting package kernel for versions less than 6.6.43.1-7
In the Linux kernel, the following vulnerability has been resolved:
bpf: Fix overrunning reservations in ringbuf
The BPF ring buffer internally is implemented as a power-of-2 sized circular buffer, with two logical and ever-increasing counters: consumer_pos is the consumer counter to show which logical position the consumer consumed the data, and producer_pos which is the producer counter denoting the amount of data reserved by all producers.
Each time a record is reserved, the producer that "owns" the record will successfully advance producer counter. In user space each time a record is read, the consumer of the data advanced the consumer counter once it finished processing. Both counters are stored in separate pages so that from user space, the producer counter is read-only and the consumer counter is read-write.
One aspect that simplifies and thus speeds up the implementation of both producers and consumers is how the data area is mapped twice contiguously back-to-back in the virtual memory, allowing to not take any special measures for samples that have to wrap around at the end of the circular buffer data area, because the next page after the last data page would be first data page again, and thus the sample will still appear completely contiguous in virtual memory.
Each record has a struct bpf_ringbuf_hdr { u32 len; u32 pg_off; } header for
book-keeping the length and offset, and is inaccessible to the BPF program.
Helpers like bpf_ringbuf_reserve() return (void *)hdr + BPF_RINGBUF_HDR_SZ
for the BPF program to use. Bing-Jhong and Muhammad reported that it is however
possible to make a second allocated memory chunk overlapping with the first
chunk and as a result, the BPF program is now able to edit first chunk's
header.
For example, consider the creation of a BPF_MAP_TYPE_RINGBUF map with size
of 0x4000. Next, the consumer_pos is modified to 0x3000 /before/ a call to
bpf_ringbuf_reserve() is made. This will allocate a chunk A, which is in
[0x0,0x3008], and the BPF program is able to edit [0x8,0x3008]. Now, lets
allocate a chunk B with size 0x3000. This will succeed because consumer_pos
was edited ahead of time to pass the new_prod_pos - cons_pos > rb->mask
check. Chunk B will be in range [0x3008,0x6010], and the BPF program is able
to edit [0x3010,0x6010]. Due to the ring buffer memory layout mentioned
earlier, the ranges [0x0,0x4000] and [0x4000,0x8000] point to the same data
pages. This means that chunk B at [0x4000,0x4008] is chunk A's header.
bpf_ringbuf_submit() / bpf_ringbuf_discard() use the header's pg_off to then
locate the bpf_ringbuf itself via bpf_ringbuf_restore_from_rec(). Once chunk
B modified chunk A's header, then bpf_ringbuf_commit() refers to the wrong
page and could cause a crash.
Fix it by calculating the oldest pending_pos and check whether the range from the oldest outstanding record to the newest would span beyond the ring buffer size. If that is the case, then reject the request. We've tested with the ring buffer benchmark in BPF selftests (./benchs/run_bench_ringbufs.sh) before/after the fix and while it seems a bit slower on some benchmarks, it is still not significantly enough to matter.
- Record
AZL-43396- 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
OSVAZL-43409
5.5
CVE-2024-41009 affecting package kernel for versions less than 5.15.164.1-1
In the Linux kernel, the following vulnerability has been resolved:
bpf: Fix overrunning reservations in ringbuf
The BPF ring buffer internally is implemented as a power-of-2 sized circular buffer, with two logical and ever-increasing counters: consumer_pos is the consumer counter to show which logical position the consumer consumed the data, and producer_pos which is the producer counter denoting the amount of data reserved by all producers.
Each time a record is reserved, the producer that "owns" the record will successfully advance producer counter. In user space each time a record is read, the consumer of the data advanced the consumer counter once it finished processing. Both counters are stored in separate pages so that from user space, the producer counter is read-only and the consumer counter is read-write.
One aspect that simplifies and thus speeds up the implementation of both producers and consumers is how the data area is mapped twice contiguously back-to-back in the virtual memory, allowing to not take any special measures for samples that have to wrap around at the end of the circular buffer data area, because the next page after the last data page would be first data page again, and thus the sample will still appear completely contiguous in virtual memory.
Each record has a struct bpf_ringbuf_hdr { u32 len; u32 pg_off; } header for
book-keeping the length and offset, and is inaccessible to the BPF program.
Helpers like bpf_ringbuf_reserve() return (void *)hdr + BPF_RINGBUF_HDR_SZ
for the BPF program to use. Bing-Jhong and Muhammad reported that it is however
possible to make a second allocated memory chunk overlapping with the first
chunk and as a result, the BPF program is now able to edit first chunk's
header.
For example, consider the creation of a BPF_MAP_TYPE_RINGBUF map with size
of 0x4000. Next, the consumer_pos is modified to 0x3000 /before/ a call to
bpf_ringbuf_reserve() is made. This will allocate a chunk A, which is in
[0x0,0x3008], and the BPF program is able to edit [0x8,0x3008]. Now, lets
allocate a chunk B with size 0x3000. This will succeed because consumer_pos
was edited ahead of time to pass the new_prod_pos - cons_pos > rb->mask
check. Chunk B will be in range [0x3008,0x6010], and the BPF program is able
to edit [0x3010,0x6010]. Due to the ring buffer memory layout mentioned
earlier, the ranges [0x0,0x4000] and [0x4000,0x8000] point to the same data
pages. This means that chunk B at [0x4000,0x4008] is chunk A's header.
bpf_ringbuf_submit() / bpf_ringbuf_discard() use the header's pg_off to then
locate the bpf_ringbuf itself via bpf_ringbuf_restore_from_rec(). Once chunk
B modified chunk A's header, then bpf_ringbuf_commit() refers to the wrong
page and could cause a crash.
Fix it by calculating the oldest pending_pos and check whether the range from the oldest outstanding record to the newest would span beyond the ring buffer size. If that is the case, then reject the request. We've tested with the ring buffer benchmark in BPF selftests (./benchs/run_bench_ringbufs.sh) before/after the fix and while it seems a bit slower on some benchmarks, it is still not significantly enough to matter.
- Record
AZL-43409- 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 46 moreShow less
OSVBELL-CVE-2024-41009
5.5
- Record
BELL-CVE-2024-41009- 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
7.8
bpf: Fix overrunning reservations in ringbuf
In the Linux kernel, the following vulnerability has been resolved:
bpf: Fix overrunning reservations in ringbuf
The BPF ring buffer internally is implemented as a power-of-2 sized circular buffer, with two logical and ever-increasing counters: consumer_pos is the consumer counter to show which logical position the consumer consumed the data, and producer_pos which is the producer counter denoting the amount of data reserved by all producers.
Each time a record is reserved, the producer that "owns" the record will successfully advance producer counter. In user space each time a record is read, the consumer of the data advanced the consumer counter once it finished processing. Both counters are stored in separate pages so that from user space, the producer counter is read-only and the consumer counter is read-write.
One aspect that simplifies and thus speeds up the implementation of both producers and consumers is how the data area is mapped twice contiguously back-to-back in the virtual memory, allowing to not take any special measures for samples that have to wrap around at the end of the circular buffer data area, because the next page after the last data page would be first data page again, and thus the sample will still appear completely contiguous in virtual memory.
Each record has a struct bpf_ringbuf_hdr { u32 len; u32 pg_off; } header for
book-keeping the length and offset, and is inaccessible to the BPF program.
Helpers like bpf_ringbuf_reserve() return (void *)hdr + BPF_RINGBUF_HDR_SZ
for the BPF program to use. Bing-Jhong and Muhammad reported that it is however
possible to make a second allocated memory chunk overlapping with the first
chunk and as a result, the BPF program is now able to edit first chunk's
header.
For example, consider the creation of a BPF_MAP_TYPE_RINGBUF map with size
of 0x4000. Next, the consumer_pos is modified to 0x3000 /before/ a call to
bpf_ringbuf_reserve() is made. This will allocate a chunk A, which is in
[0x0,0x3008], and the BPF program is able to edit [0x8,0x3008]. Now, lets
allocate a chunk B with size 0x3000. This will succeed because consumer_pos
was edited ahead of time to pass the new_prod_pos - cons_pos > rb->mask
check. Chunk B will be in range [0x3008,0x6010], and the BPF program is able
to edit [0x3010,0x6010]. Due to the ring buffer memory layout mentioned
earlier, the ranges [0x0,0x4000] and [0x4000,0x8000] point to the same data
pages. This means that chunk B at [0x4000,0x4008] is chunk A's header.
bpf_ringbuf_submit() / bpf_ringbuf_discard() use the header's pg_off to then
locate the bpf_ringbuf itself via bpf_ringbuf_restore_from_rec(). Once chunk
B modified chunk A's header, then bpf_ringbuf_commit() refers to the wrong
page and could cause a crash.
Fix it by calculating the oldest pending_pos and check whether the range from the oldest outstanding record to the newest would span beyond the ring buffer size. If that is the case, then reject the request. We've tested with the ring buffer benchmark in BPF selftests (./benchs/run_bench_ringbufs.sh) before/after the fix and while it seems a bit slower on some benchmarks, it is still not significantly enough to matter.
- Record
CVE-2024-41009- CVSS 3.1
- 7.8 High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H - Updated
- 2026-11-02
OSVDEBIAN-CVE-2024-41009
5.5
In the Linux kernel, the following vulnerability has been resolved: bpf: Fix overrunning reservations in ringbuf The BPF ring buffer internally is implemented as a power-of-2 sized circular buffer, with two logical and ever-increasing counters: consumer_pos is the consumer counter to show which logical position the consumer consumed the data, and producer_pos which is the producer counter denoting the amount of data reserved by all producers. Each time a record is reserved, the producer that "owns" the record will successfully advance producer counter. In user space each time a record is read, the consumer of the data advanced the consumer counter once it finished processing. Both counters are stored in separate pages so that from user space, the producer counter is read-only and the consumer counter is read-write. One aspect that simplifies and thus speeds up the implementation of both producers and consumers is how the data area is mapped twice contiguously back-to-back in the virtual memory, allowing to not take any special measures for samples that have to wrap around at the end of the circular buffer data area, because the next page after the last data page would be first data page again, and thus the sample will still appear completely contiguous in virtual memory. Each record has a struct bpf_ringbuf_hdr { u32 len; u32 pg_off; } header for book-keeping the length and offset, and is inaccessible to the BPF program. Helpers like bpf_ringbuf_reserve() return (void *)hdr + BPF_RINGBUF_HDR_SZ for the BPF program to use. Bing-Jhong and Muhammad reported that it is however possible to make a second allocated memory chunk overlapping with the first chunk and as a result, the BPF program is now able to edit first chunk's header. For example, consider the creation of a BPF_MAP_TYPE_RINGBUF map with size of 0x4000. Next, the consumer_pos is modified to 0x3000 /before/ a call to bpf_ringbuf_reserve() is made. This will allocate a chunk A, which is in [0x0,0x3008], and the BPF program is able to edit [0x8,0x3008]. Now, lets allocate a chunk B with size 0x3000. This will succeed because consumer_pos was edited ahead of time to pass the new_prod_pos - cons_pos > rb->mask check. Chunk B will be in range [0x3008,0x6010], and the BPF program is able to edit [0x3010,0x6010]. Due to the ring buffer memory layout mentioned earlier, the ranges [0x0,0x4000] and [0x4000,0x8000] point to the same data pages. This means that chunk B at [0x4000,0x4008] is chunk A's header. bpf_ringbuf_submit() / bpf_ringbuf_discard() use the header's pg_off to then locate the bpf_ringbuf itself via bpf_ringbuf_restore_from_rec(). Once chunk B modified chunk A's header, then bpf_ringbuf_commit() refers to the wrong page and could cause a crash. Fix it by calculating the oldest pending_pos and check whether the range from the oldest outstanding record to the newest would span beyond the ring buffer size. If that is the case, then reject the request. We've tested with the ring buffer benchmark in BPF selftests (./benchs/run_bench_ringbufs.sh) before/after the fix and while it seems a bit slower on some benchmarks, it is still not significantly enough to matter.
- Record
DEBIAN-CVE-2024-41009- 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
OSVOESA-2024-1894
9.8
kernel security update
The Linux Kernel, the operating system core itself.
Security Fix(es):
In the Linux kernel, the following vulnerability has been resolved:
lib/generic-radix-tree.c: Don't overflow in peek()
When we started spreading new inode numbers throughout most of the 64 bit inode space, that triggered some corner case bugs, in particular some integer overflows related to the radix tree code. Oops.(CVE-2021-47432)
In the Linux kernel, the following vulnerability has been resolved:
scsi: ufs: Fix a deadlock in the error handler
The following deadlock has been observed on a test setup:
-
All tags allocated
-
The SCSI error handler calls ufshcd_eh_host_reset_handler()
-
ufshcd_eh_host_reset_handler() queues work that calls ufshcd_err_handler()
-
ufshcd_err_handler() locks up as follows:
Workqueue: ufs_eh_wq_0 ufshcd_err_handler.cfi_jt Call trace: __switch_to+0x298/0x5d8 __schedule+0x6cc/0xa94 schedule+0x12c/0x298 blk_mq_get_tag+0x210/0x480 __blk_mq_alloc_request+0x1c8/0x284 blk_get_request+0x74/0x134 ufshcd_exec_dev_cmd+0x68/0x640 ufshcd_verify_dev_init+0x68/0x35c ufshcd_probe_hba+0x12c/0x1cb8 ufshcd_host_reset_and_restore+0x88/0x254 ufshcd_reset_and_restore+0xd0/0x354 ufshcd_err_handler+0x408/0xc58 process_one_work+0x24c/0x66c worker_thread+0x3e8/0xa4c kthread+0x150/0x1b4 ret_from_fork+0x10/0x30
Fix this lockup by making ufshcd_exec_dev_cmd() allocate a reserved request.(CVE-2021-47622)
In the Linux kernel, the following vulnerability has been resolved:
net: dsa: seville: register the mdiobus under devres
As explained in commits: 74b6d7d13307 ("net: dsa: realtek: register the MDIO bus under devres") 5135e96a3dd2 ("net: dsa: don't allocate the slave_mii_bus using devres")
mdiobus_free() will panic when called from devm_mdiobus_free() <- devres_release_all() <- __device_release_driver(), and that mdiobus was not previously unregistered.
The Seville VSC9959 switch is a platform device, so the initial set of constraints that I thought would cause this (I2C or SPI buses which call ->remove on ->shutdown) do not apply. But there is one more which applies here.
If the DSA master itself is on a bus that calls ->remove from ->shutdown (like dpaa2-eth, which is on the fsl-mc bus), there is a device link between the switch and the DSA master, and device_links_unbind_consumers() will unbind the seville switch driver on shutdown.
So the same treatment must be applied to all DSA switch drivers, which is: either use devres for both the mdiobus allocation and registration, or don't use devres at all.
The seville driver has a code structure that could accommodate both the mdiobus_unregister and mdiobus_free calls, but it has an external dependency upon mscc_miim_setup() from mdio-mscc-miim.c, which calls devm_mdiobus_alloc_size() on its behalf. So rather than restructuring that, and exporting yet one more symbol mscc_miim_teardown(), let's work with devres and replace of_mdiobus_register with the devres variant. When we use all-devres, we can ensure that devres doesn't free a still-registered bus (it either runs both callbacks, or none).(CVE-2022-48814)
In the Linux kernel, the following vulnerability has been resolved:
SUNRPC: lock against ->sock changing during sysfs read
->sock can be set to NULL asynchronously unless ->recv_mutex is held. So it is important to hold that mutex. Otherwise a sysfs read can trigger an oops. Commit 17f09d3f619a ("SUNRPC: Check if the xprt is connected before handling sysfs reads") appears to attempt to fix this problem, but it only narrows the race window.(CVE-2022-48816)
In the Linux kernel, the following vulnerability has been resolved:
Bluetooth: hci_core: Fix leaking sent_cmd skb
sent_cmd memory is not freed before freeing hci_dev causing it to leak it contents.(CVE-2022-48844)
In the Linux kernel, the following vulnerability has been…
- Record
OESA-2024-1894- CVSS 3.1
- 9.8 Critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H - Updated
- 2026-11-02
OSVOESA-2024-1896
7.8
kernel security update
The Linux Kernel, the operating system core itself.
Security Fix(es):
In the Linux kernel, the following vulnerability has been resolved:
lib/generic-radix-tree.c: Don't overflow in peek()
When we started spreading new inode numbers throughout most of the 64 bit inode space, that triggered some corner case bugs, in particular some integer overflows related to the radix tree code. Oops.(CVE-2021-47432)
In the Linux kernel, the following vulnerability has been resolved:
scsi: ufs: Fix a deadlock in the error handler
The following deadlock has been observed on a test setup:
-
All tags allocated
-
The SCSI error handler calls ufshcd_eh_host_reset_handler()
-
ufshcd_eh_host_reset_handler() queues work that calls ufshcd_err_handler()
-
ufshcd_err_handler() locks up as follows:
Workqueue: ufs_eh_wq_0 ufshcd_err_handler.cfi_jt Call trace: __switch_to+0x298/0x5d8 __schedule+0x6cc/0xa94 schedule+0x12c/0x298 blk_mq_get_tag+0x210/0x480 __blk_mq_alloc_request+0x1c8/0x284 blk_get_request+0x74/0x134 ufshcd_exec_dev_cmd+0x68/0x640 ufshcd_verify_dev_init+0x68/0x35c ufshcd_probe_hba+0x12c/0x1cb8 ufshcd_host_reset_and_restore+0x88/0x254 ufshcd_reset_and_restore+0xd0/0x354 ufshcd_err_handler+0x408/0xc58 process_one_work+0x24c/0x66c worker_thread+0x3e8/0xa4c kthread+0x150/0x1b4 ret_from_fork+0x10/0x30
Fix this lockup by making ufshcd_exec_dev_cmd() allocate a reserved request.(CVE-2021-47622)
In the Linux kernel, the following vulnerability has been resolved:
net: dsa: seville: register the mdiobus under devres
As explained in commits: 74b6d7d13307 ("net: dsa: realtek: register the MDIO bus under devres") 5135e96a3dd2 ("net: dsa: don't allocate the slave_mii_bus using devres")
mdiobus_free() will panic when called from devm_mdiobus_free() <- devres_release_all() <- __device_release_driver(), and that mdiobus was not previously unregistered.
The Seville VSC9959 switch is a platform device, so the initial set of constraints that I thought would cause this (I2C or SPI buses which call ->remove on ->shutdown) do not apply. But there is one more which applies here.
If the DSA master itself is on a bus that calls ->remove from ->shutdown (like dpaa2-eth, which is on the fsl-mc bus), there is a device link between the switch and the DSA master, and device_links_unbind_consumers() will unbind the seville switch driver on shutdown.
So the same treatment must be applied to all DSA switch drivers, which is: either use devres for both the mdiobus allocation and registration, or don't use devres at all.
The seville driver has a code structure that could accommodate both the mdiobus_unregister and mdiobus_free calls, but it has an external dependency upon mscc_miim_setup() from mdio-mscc-miim.c, which calls devm_mdiobus_alloc_size() on its behalf. So rather than restructuring that, and exporting yet one more symbol mscc_miim_teardown(), let's work with devres and replace of_mdiobus_register with the devres variant. When we use all-devres, we can ensure that devres doesn't free a still-registered bus (it either runs both callbacks, or none).(CVE-2022-48814)
In the Linux kernel, the following vulnerability has been resolved:
SUNRPC: lock against ->sock changing during sysfs read
->sock can be set to NULL asynchronously unless ->recv_mutex is held. So it is important to hold that mutex. Otherwise a sysfs read can trigger an oops. Commit 17f09d3f619a ("SUNRPC: Check if the xprt is connected before handling sysfs reads") appears to attempt to fix this problem, but it only narrows the race window.(CVE-2022-48816)
In the Linux kernel, the following vulnerability has been resolved:
Bluetooth: hci_core: Fix leaking sent_cmd skb
sent_cmd memory is not freed before freeing hci_dev causing it to leak it contents.(CVE-2022-48844)
In the Linux kernel, the following vulnerability has been…
- Record
OESA-2024-1896- CVSS 3.1
- 7.8 High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H - Updated
- 2026-11-02
OSVOESA-2024-1897
9.8
kernel security update
The Linux Kernel, the operating system core itself.
Security Fix(es):
In the Linux kernel, the following vulnerability has been resolved:
PCI: of_property: Return error for int_map allocation failure
Return -ENOMEM from of_pci_prop_intr_map() if kcalloc() fails to prevent a NULL pointer dereference in this case.
In the Linux kernel, the following vulnerability has been resolved:
drm/arm/malidp: fix a possible null pointer dereference
In malidp_mw_connector_reset, new memory is allocated with kzalloc, but no check is performed. In order to prevent null pointer dereferencing, ensure that mw_state is checked before calling __drm_atomic_helper_connector_reset.(CVE-2024-36014)
In the Linux kernel, the following vulnerability has been resolved:
tty: n_gsm: fix possible out-of-bounds in gsm0_receive()
Assuming the following:
- side A configures the n_gsm in basic option mode
- side B sends the header of a basic option mode frame with data length 1
- side A switches to advanced option mode
- side B sends 2 data bytes which exceeds gsm->len Reason: gsm->len is not used in advanced option mode.
- side A switches to basic option mode
- side B keeps sending until gsm0_receive() writes past gsm->buf Reason: Neither gsm->state nor gsm->len have been reset after reconfiguration.
Fix this by changing gsm->count to gsm->len comparison from equal to less than. Also add upper limit checks against the constant MAX_MRU in gsm0_receive() and gsm1_receive() to harden against memory corruption of gsm->len and gsm->mru.
All other checks remain as we still need to limit the data according to the user configuration and actual payload size.(CVE-2024-36016)
In the Linux kernel, the following vulnerability has been resolved:
keys: Fix overwrite of key expiration on instantiation
The expiry time of a key is unconditionally overwritten during instantiation, defaulting to turn it permanent. This causes a problem for DNS resolution as the expiration set by user-space is overwritten to TIME64_MAX, disabling further DNS updates. Fix this by restoring the condition that key_set_expiry is only called when the pre-parser sets a specific expiry.(CVE-2024-36031)
In the Linux kernel, the following vulnerability has been resolved:
mm/userfaultfd: reset ptes when close() for wr-protected ones
Userfaultfd unregister includes a step to remove wr-protect bits from all the relevant pgtable entries, but that only covered an explicit UFFDIO_UNREGISTER ioctl, not a close() on the userfaultfd itself. Cover that too. This fixes a WARN trace.
The only user visible side effect is the user can observe leftover wr-protect bits even if the user close()ed on an userfaultfd when releasing the last reference of it. However hopefully that should be harmless, and nothing bad should happen even if so.
This change is now more important after the recent page-table-check patch we merged in mm-unstable (446dd9ad37d0 ("mm/page_table_check: support userfault wr-protect entries")), as we'll do sanity check on uffd-wp bits without vma context. So it's better if we can 100% guarantee no uffd-wp bit leftovers, to make sure each report will be valid.(CVE-2024-36881)
In the Linux kernel, the following vulnerability has been resolved:
nfs: Handle error of rpc_proc_register() in nfs_net_init().
syzkaller reported a warning [0] triggered while destroying immature netns.
rpc_proc_register() was called in init_nfs_fs(), but its error has been ignored since at least the initial commit 1da177e4c3f4 ("Linux-2.6.12-rc2").
Recently, commit d47151b79e32 ("nfs: expose /proc/net/sunrpc/nfs in net namespaces") converted the procfs to per-netns and made the problem more visible.
Even when rpc_proc_register() fails, nfs_net_init() could succeed, and thus nfs_net_exit() will be called while destroying the netns.
Then,…
- Record
OESA-2024-1897- CVSS 3.1
- 9.8 Critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H - Updated
- 2026-11-02
OSVRHSA-2024:10262
7.0
Red Hat Security Advisory: kernel security update
- Record
RHSA-2024:10262- CVSS 3.1
- 7.0 High
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H - Updated
- 2026-11-02
OSVRHSA-2024:10274
6.7
Red Hat Security Advisory: kernel security update
- Record
RHSA-2024:10274- CVSS 3.1
- 6.7 Medium
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H - Updated
- 2026-11-02
OSVRHSA-2024:10771
7.8
Red Hat Security Advisory: kernel security update
- Record
RHSA-2024:10771- CVSS 3.1
- 7.8 High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H - Updated
- 2026-11-02
OSVRHSA-2024:10772
7.0
Red Hat Security Advisory: kernel security update
- Record
RHSA-2024:10772- CVSS 3.1
- 7.0 High
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H - Updated
- 2026-11-02
OSVRHSA-2024:10773
7.0
Red Hat Security Advisory: kernel-rt security update
- Record
RHSA-2024:10773- CVSS 3.1
- 7.0 High
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H - Updated
- 2026-11-02
OSVRHSA-2024:6753
7.8
Red Hat Security Advisory: kernel security update
- Record
RHSA-2024:6753- CVSS 3.1
- 7.8 High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H - Updated
- 2026-11-02
OSVRHSA-2024:8856
7.3
Red Hat Security Advisory: kernel security update
- Record
RHSA-2024:8856- CVSS 3.1
- 7.3 High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:H - Updated
- 2026-11-02
OSVRHSA-2024:8870
7.3
Red Hat Security Advisory: kernel-rt security update
- Record
RHSA-2024:8870- CVSS 3.1
- 7.3 High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:H - Updated
- 2026-11-02
OSVUBUNTU-CVE-2024-41009
7.3
In the Linux kernel, the following vulnerability has been resolved: bpf: Fix overrunning reservations in ringbuf The BPF ring buffer internally is implemented as a power-of-2 sized circular buffer, with two logical and ever-increasing counters: consumer_pos is the consumer counter to show which logical position the consumer consumed the data, and producer_pos which is the producer counter denoting the amount of data reserved by all producers. Each time a record is reserved, the producer that "owns" the record will successfully advance producer counter. In user space each time a record is read, the consumer of the data advanced the consumer counter once it finished processing. Both counters are stored in separate pages so that from user space, the producer counter is read-only and the consumer counter is read-write. One aspect that simplifies and thus speeds up the implementation of both producers and consumers is how the data area is mapped twice contiguously back-to-back in the virtual memory, allowing to not take any special measures for samples that have to wrap around at the end of the circular buffer data area, because the next page after the last data page would be first data page again, and thus the sample will still appear completely contiguous in virtual memory. Each record has a struct bpf_ringbuf_hdr { u32 len; u32 pg_off; } header for book-keeping the length and offset, and is inaccessible to the BPF program. Helpers like bpf_ringbuf_reserve() return (void *)hdr + BPF_RINGBUF_HDR_SZ for the BPF program to use. Bing-Jhong and Muhammad reported that it is however possible to make a second allocated memory chunk overlapping with the first chunk and as a result, the BPF program is now able to edit first chunk's header. For example, consider the creation of a BPF_MAP_TYPE_RINGBUF map with size of 0x4000. Next, the consumer_pos is modified to 0x3000 /before/ a call to bpf_ringbuf_reserve() is made. This will allocate a chunk A, which is in [0x0,0x3008], and the BPF program is able to edit [0x8,0x3008]. Now, lets allocate a chunk B with size 0x3000. This will succeed because consumer_pos was edited ahead of time to pass the new_prod_pos - cons_pos > rb->mask check. Chunk B will be in range [0x3008,0x6010], and the BPF program is able to edit [0x3010,0x6010]. Due to the ring buffer memory layout mentioned earlier, the ranges [0x0,0x4000] and [0x4000,0x8000] point to the same data pages. This means that chunk B at [0x4000,0x4008] is chunk A's header. bpf_ringbuf_submit() / bpf_ringbuf_discard() use the header's pg_off to then locate the bpf_ringbuf itself via bpf_ringbuf_restore_from_rec(). Once chunk B modified chunk A's header, then bpf_ringbuf_commit() refers to the wrong page and could cause a crash. Fix it by calculating the oldest pending_pos and check whether the range from the oldest outstanding record to the newest would span beyond the ring buffer size. If that is the case, then reject the request. We've tested with the ring buffer benchmark in BPF selftests (./benchs/run_bench_ringbufs.sh) before/after the fix and while it seems a bit slower on some benchmarks, it is still not significantly enough to matter.
- Record
UBUNTU-CVE-2024-41009- CVSS 4.0
- 7.3 High
CVSS:4.0/AV:L/AC:H/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N - 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 - CVSS 3.1
- 7.8 High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H - Updated
- 2026-11-02
OSVALSA-2024:10274 No score
Moderate: kernel security update
The kernel packages contain the Linux kernel, the core of any Linux operating system.
Security Fix(es):
- kernel: bpf: Fix overrunning reservations in ringbuf (CVE-2024-41009)
- kernel: USB: serial: mos7840: fix crash on resume (CVE-2024-42244)
- kernel: cxl/port: Fix use-after-free, permit out-of-order decoder shutdown (CVE-2024-50226)
For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.
- Record
ALSA-2024:10274- Updated
- 2026-11-02
OSVALSA-2024:8856 No score
Moderate: kernel security update
The kernel packages contain the Linux kernel, the core of any Linux operating system.
Security Fix(es):
- kernel: net/bluetooth: race condition in conn_info_{min,max}_age_set() (CVE-2024-24857)
- kernel: dmaengine: fix NULL pointer in channel unregistration function (CVE-2023-52492)
- kernel: netfilter: nf_conntrack_h323: Add protection for bmp length out of range (CVE-2024-26851)
- kernel: netfilter: nft_set_pipapo: do not free live element (CVE-2024-26924)
- kernel: netfilter: nft_set_pipapo: walk over current view on netlink dump (CVE-2024-27017)
- kernel: KVM: Always flush async #PF workqueue when vCPU is being destroyed (CVE-2024-26976)
- kernel: nouveau: lock the client object tree. (CVE-2024-27062)
- kernel: netfilter: bridge: replace physindev with physinif in nf_bridge_info (CVE-2024-35839)
- kernel: netfilter: nf_tables: Fix potential data-race in __nft_flowtable_type_get() (CVE-2024-35898)
- kernel: dma-direct: Leak pages on dma_set_decrypted() failure (CVE-2024-35939)
- kernel: net/mlx5e: Fix netif state handling (CVE-2024-38608)
- kernel: r8169: Fix possible ring buffer corruption on fragmented Tx packets. (CVE-2024-38586)
- kernel: of: module: add buffer overflow check in of_modalias() (CVE-2024-38541)
- kernel: bnxt_re: avoid shift undefined behavior in bnxt_qplib_alloc_init_hwq (CVE-2024-38540)
- kernel: netfilter: ipset: Fix race between namespace cleanup and gc in the list:set type (CVE-2024-39503)
- kernel: drm/i915/dpt: Make DPT object unshrinkable (CVE-2024-40924)
- kernel: ipv6: prevent possible NULL deref in fib6_nh_init() (CVE-2024-40961)
- kernel: tipc: force a dst refcount before doing decryption (CVE-2024-40983)
- kernel: ACPICA: Revert "ACPICA: avoid Info: mapping multiple BARs. Your kernel is fine." (CVE-2024-40984)
- kernel: xprtrdma: fix pointer derefs in error cases of rpcrdma_ep_create (CVE-2022-48773)
- kernel: bpf: Fix overrunning reservations in ringbuf (CVE-2024-41009)
- kernel: netfilter: nf_tables: prefer nft_chain_validate (CVE-2024-41042)
- kernel: ibmvnic: Add tx check to prevent skb leak (CVE-2024-41066)
- kernel: drm/i915/gt: Fix potential UAF by revoke of fence registers (CVE-2024-41092)
- kernel: drm/amdgpu: avoid using null object of framebuffer (CVE-2024-41093)
- kernel: netfilter: nf_tables: fully validate NFT_DATA_VALUE on store to data registers (CVE-2024-42070)
- kernel: gfs2: Fix NULL pointer dereference in gfs2_log_flush (CVE-2024-42079)
- kernel: USB: serial: mos7840: fix crash on resume (CVE-2024-42244)
- kernel: tipc: Return non-zero value from tipc_udp_addr2str() on error (CVE-2024-42284)
- kernel: kobject_uevent: Fix OOB access within zap_modalias_env() (CVE-2024-42292)
- kernel: dev/parport: fix the array out-of-bounds risk (CVE-2024-42301)
- kernel: block: initialize integrity buffer to zero before writing it to media (CVE-2024-43854)
- kernel: mlxsw: spectrum_acl_erp: Fix object nesting warning (CVE-2024-43880)
- kernel: gso: do not skip outer ip header in case of ipip and net_failover (CVE-2022-48936)
- kernel: padata: Fix possible divide-by-0 panic in padata_mt_helper() (CVE-2024-43889)
- kernel: memcg: protect concurrent access to mem_cgroup_idr (CVE-2024-43892)
- kernel: sctp: Fix null-ptr-deref in reuseport_add_sock(). (CVE-2024-44935)
- kernel: bonding: fix xfrm real_dev null pointer dereference (CVE-2024-44989)
- kernel: bonding: fix null pointer deref in bond_ipsec_offload_ok (CVE-2024-44990)
- kernel: netfilter: flowtable: initialise extack before use (CVE-2024-45018)
- kernel: ELF: fix kernel.randomize_va_space double read (CVE-2024-46826)
- kernel: lib/generic-radix-tree.c: Fix rare race in __genradix_ptr_alloc() (CVE-2024-47668)
For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.
- Record
ALSA-2024:8856- Updated
- 2026-11-02
OSVALSA-2024:8870 No score
Moderate: kernel-rt security update
The kernel-rt packages provide the Real Time Linux Kernel, which enables fine-tuning for systems with extremely high determinism requirements.
Security Fix(es):
- kernel: net/bluetooth: race condition in conn_info_{min,max}_age_set() (CVE-2024-24857)
- kernel: dmaengine: fix NULL pointer in channel unregistration function (CVE-2023-52492)
- kernel: netfilter: nf_conntrack_h323: Add protection for bmp length out of range (CVE-2024-26851)
- kernel: netfilter: nft_set_pipapo: do not free live element (CVE-2024-26924)
- kernel: netfilter: nft_set_pipapo: walk over current view on netlink dump (CVE-2024-27017)
- kernel: KVM: Always flush async #PF workqueue when vCPU is being destroyed (CVE-2024-26976)
- kernel: nouveau: lock the client object tree. (CVE-2024-27062)
- kernel: netfilter: bridge: replace physindev with physinif in nf_bridge_info (CVE-2024-35839)
- kernel: netfilter: nf_tables: Fix potential data-race in __nft_flowtable_type_get() (CVE-2024-35898)
- kernel: dma-direct: Leak pages on dma_set_decrypted() failure (CVE-2024-35939)
- kernel: net/mlx5e: Fix netif state handling (CVE-2024-38608)
- kernel: r8169: Fix possible ring buffer corruption on fragmented Tx packets. (CVE-2024-38586)
- kernel: of: module: add buffer overflow check in of_modalias() (CVE-2024-38541)
- kernel: bnxt_re: avoid shift undefined behavior in bnxt_qplib_alloc_init_hwq (CVE-2024-38540)
- kernel: netfilter: ipset: Fix race between namespace cleanup and gc in the list:set type (CVE-2024-39503)
- kernel: drm/i915/dpt: Make DPT object unshrinkable (CVE-2024-40924)
- kernel: ipv6: prevent possible NULL deref in fib6_nh_init() (CVE-2024-40961)
- kernel: tipc: force a dst refcount before doing decryption (CVE-2024-40983)
- kernel: ACPICA: Revert "ACPICA: avoid Info: mapping multiple BARs. Your kernel is fine." (CVE-2024-40984)
- kernel: xprtrdma: fix pointer derefs in error cases of rpcrdma_ep_create (CVE-2022-48773)
- kernel: bpf: Fix overrunning reservations in ringbuf (CVE-2024-41009)
- kernel: netfilter: nf_tables: prefer nft_chain_validate (CVE-2024-41042)
- kernel: ibmvnic: Add tx check to prevent skb leak (CVE-2024-41066)
- kernel: drm/i915/gt: Fix potential UAF by revoke of fence registers (CVE-2024-41092)
- kernel: drm/amdgpu: avoid using null object of framebuffer (CVE-2024-41093)
- kernel: netfilter: nf_tables: fully validate NFT_DATA_VALUE on store to data registers (CVE-2024-42070)
- kernel: gfs2: Fix NULL pointer dereference in gfs2_log_flush (CVE-2024-42079)
- kernel: USB: serial: mos7840: fix crash on resume (CVE-2024-42244)
- kernel: tipc: Return non-zero value from tipc_udp_addr2str() on error (CVE-2024-42284)
- kernel: kobject_uevent: Fix OOB access within zap_modalias_env() (CVE-2024-42292)
- kernel: dev/parport: fix the array out-of-bounds risk (CVE-2024-42301)
- kernel: block: initialize integrity buffer to zero before writing it to media (CVE-2024-43854)
- kernel: mlxsw: spectrum_acl_erp: Fix object nesting warning (CVE-2024-43880)
- kernel: gso: do not skip outer ip header in case of ipip and net_failover (CVE-2022-48936)
- kernel: padata: Fix possible divide-by-0 panic in padata_mt_helper() (CVE-2024-43889)
- kernel: memcg: protect concurrent access to mem_cgroup_idr (CVE-2024-43892)
- kernel: sctp: Fix null-ptr-deref in reuseport_add_sock(). (CVE-2024-44935)
- kernel: bonding: fix xfrm real_dev null pointer dereference (CVE-2024-44989)
- kernel: bonding: fix null pointer deref in bond_ipsec_offload_ok (CVE-2024-44990)
- kernel: netfilter: flowtable: initialise extack before use (CVE-2024-45018)
- kernel: ELF: fix kernel.randomize_va_space double read (CVE-2024-46826)
- kernel: lib/generic-radix-tree.c: Fix rare race in __genradix_ptr_alloc() (CVE-2024-47668)
For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the…
- Record
ALSA-2024:8870- Updated
- 2026-11-02
OSVCLSA-2026-1783791447 No score
kernel: Fix of 307 CVEs
- gpiolib: cdev: Set lineevent_state::irq after IRQ register successfully {CVE-2022-48660}
- ipv4: check for NULL idev in ip_route_use_hint() {CVE-2024-36008}
- KEYS: trusted: Do not use WARN when encode fails {CVE-2024-36975}
- Fix userfaultfd_api to return EINVAL as expected {CVE-2024-41027}
- xhci: Fix null pointer dereference when host dies {CVE-2023-52898}
- sctp: sysctl: auth_enable: avoid using current->nsproxy {CVE-2025-21638}
- blk-mq: fix IO hang from sbitmap wakeup race {CVE-2024-26671}
- net: openvswitch: fix flow memory leak in ovs_flow_cmd_new {CVE-2023-52977}
- gpiolib: fix memory leak in gpiochip_setup_dev() {CVE-2022-48975}
- HID: betop: check shape of output reports {CVE-2023-53015}
- mm/swapfile: add cond_resched() in get_swap_pages() {CVE-2023-52932}
- HV: hv_balloon: fix memory leak with using debugfs_lookup() {CVE-2023-52937}
- drm/i915: Fix a memory leak with reused mmap_offset {CVE-2023-53002}
- ptdma: pt_core_execute_cmd() should use spinlock {CVE-2023-53013}
- RDMA/core: Fix ib block iterator counter overflow {CVE-2023-53026}
- Bluetooth: hci_conn: Fix memory leaks {CVE-2023-53018}
- scsi: target: pscsi: Fix bio_put() for error case {CVE-2024-26760}
- sctp: Prevent TOCTOU out-of-bounds write {CVE-2025-40331}
- pnfs/flexfiles: Fix memory leak in nfs4_ff_alloc_deviceid_node() {CVE-2026-23038}
- cpufreq: intel_pstate: Fix object lifecycle issue in update_qos_request() {CVE-2025-40194}
- ALSA: hda/cs8409: Fix possible NULL dereference {CVE-2024-50160}
- nbd: don't allow reconnect after disconnect {CVE-2025-21731}
- openvswitch: fix lockup on tx to unregistering netdev with carrier {CVE-2025-21681}
- ext4: detect invalid INLINE_DATA + EXTENTS flag combination {CVE-2025-40167}
- ext4: xattr: fix null pointer deref in ext4_raw_inode() {CVE-2025-68820}
- net: fix memory leak in skb_segment_list for GRO packets {CVE-2026-22979}
- wifi: brcmfmac: fix crash while sending Action Frames in standalone AP Mode {CVE-2025-40321}
- ipvs: fix ipv4 null-ptr-deref in route error path {CVE-2025-68813}
- ASoC: Intel: bytcr_rt5651: Fix invalid quirk input mapping {CVE-2025-40121}
- i40e: Fix macvlan leak by synchronizing access to mac_filter_hash {CVE-2024-50041}
- net/mlx5e: Fix NULL deref in mlx5e_tir_builder_alloc() {CVE-2024-50000}
- bpf: Fix reference count leak in bpf_prog_test_run_xdp() {CVE-2026-22994}
- xsk: check IFF_UP earlier in Tx path {CVE-2023-53240}
- firmware: cs_dsp: Prevent buffer overrun when processing V2 alg headers {CVE-2024-41038}
- virtgpu: don't reset on shutdown {CVE-2025-38064}
- xen/netfront: fix crash when removing device {CVE-2022-48969}
- mptcp: do not fallback when OoO is present {CVE-2024-50185}
- can: j1939: add missing calls in NETDEV_UNREGISTER notification handler {CVE-2025-39925}
- netfilter: nf_tables: remove redundant chain validation on register store {CVE-2025-71160}
- xfs: fix use-after-free in xattr node block inactivation {CVE-2026-43053}
- ext4: fix racy may inline data check in dio write {CVE-2023-52786}
- drm/amdgpu/fence: Fix oops due to non-matching drm_sched init/fini {CVE-2023-52738}
- macsec: fix UAF bug for real_dev {CVE-2022-49390}
- drm/i915/gem: Fix Virtual Memory mapping boundaries calculation {CVE-2024-42259}
- mm/shmem: disable PMD-sized page cache if needed {CVE-2024-42241}
- driver: iio: add missing checks on iio_info's callback access {CVE-2024-46715}
- udmabuf: fix memory leak on last export_udmabuf() error path {CVE-2024-56712}
- ALSA: control: Avoid WARN() for symlink errors {CVE-2024-56657}
- mm/mempolicy: fix migrate_to_node() assuming there is at least one VMA in a MM {CVE-2024-56611}
- eth: bnxt: always recalculate features after XDP clearing, fix null-deref {CVE-2025-21682}
- net: annotate data-races around sk->sk_{data_ready,write_space} {CVE-2026-23302}
- udmabuf: change folios array from kmalloc to kvmalloc {CVE-2024-56544}
- RDMA/mlx5: Move events notifier registration to be after device registration {CVE-2024-53224}
- dlm: fix possible lkb_resource…
- Record
CLSA-2026-1783791447- Updated
- 2026-11-02
OSVRLSA-2024:8856 No score
Moderate: kernel security update
The kernel packages contain the Linux kernel, the core of any Linux operating system.
Security Fix(es):
-
kernel: net/bluetooth: race condition in conn_info_{min,max}_age_set() (CVE-2024-24857)
-
kernel: dmaengine: fix NULL pointer in channel unregistration function (CVE-2023-52492)
-
kernel: netfilter: nf_conntrack_h323: Add protection for bmp length out of range (CVE-2024-26851)
-
kernel: netfilter: nft_set_pipapo: do not free live element (CVE-2024-26924)
-
kernel: netfilter: nft_set_pipapo: walk over current view on netlink dump (CVE-2024-27017)
-
kernel: KVM: Always flush async #PF workqueue when vCPU is being destroyed (CVE-2024-26976)
-
kernel: nouveau: lock the client object tree. (CVE-2024-27062)
-
kernel: netfilter: bridge: replace physindev with physinif in nf_bridge_info (CVE-2024-35839)
-
kernel: netfilter: nf_tables: Fix potential data-race in __nft_flowtable_type_get() (CVE-2024-35898)
-
kernel: dma-direct: Leak pages on dma_set_decrypted() failure (CVE-2024-35939)
-
kernel: net/mlx5e: Fix netif state handling (CVE-2024-38608)
-
kernel: r8169: Fix possible ring buffer corruption on fragmented Tx packets. (CVE-2024-38586)
-
kernel: of: module: add buffer overflow check in of_modalias() (CVE-2024-38541)
-
kernel: bnxt_re: avoid shift undefined behavior in bnxt_qplib_alloc_init_hwq (CVE-2024-38540)
-
kernel: netfilter: ipset: Fix race between namespace cleanup and gc in the list:set type (CVE-2024-39503)
-
kernel: drm/i915/dpt: Make DPT object unshrinkable (CVE-2024-40924)
-
kernel: ipv6: prevent possible NULL deref in fib6_nh_init() (CVE-2024-40961)
-
kernel: tipc: force a dst refcount before doing decryption (CVE-2024-40983)
-
kernel: ACPICA: Revert "ACPICA: avoid Info: mapping multiple BARs. Your kernel is fine." (CVE-2024-40984)
-
kernel: xprtrdma: fix pointer derefs in error cases of rpcrdma_ep_create (CVE-2022-48773)
-
kernel: bpf: Fix overrunning reservations in ringbuf (CVE-2024-41009)
-
kernel: netfilter: nf_tables: prefer nft_chain_validate (CVE-2024-41042)
-
kernel: ibmvnic: Add tx check to prevent skb leak (CVE-2024-41066)
-
kernel: drm/i915/gt: Fix potential UAF by revoke of fence registers (CVE-2024-41092)
-
kernel: drm/amdgpu: avoid using null object of framebuffer (CVE-2024-41093)
-
kernel: netfilter: nf_tables: fully validate NFT_DATA_VALUE on store to data registers (CVE-2024-42070)
-
kernel: gfs2: Fix NULL pointer dereference in gfs2_log_flush (CVE-2024-42079)
-
kernel: USB: serial: mos7840: fix crash on resume (CVE-2024-42244)
-
kernel: tipc: Return non-zero value from tipc_udp_addr2str() on error (CVE-2024-42284)
-
kernel: kobject_uevent: Fix OOB access within zap_modalias_env() (CVE-2024-42292)
-
kernel: dev/parport: fix the array out-of-bounds risk (CVE-2024-42301)
-
kernel: block: initialize integrity buffer to zero before writing it to media (CVE-2024-43854)
-
kernel: mlxsw: spectrum_acl_erp: Fix object nesting warning (CVE-2024-43880)
-
kernel: gso: do not skip outer ip header in case of ipip and net_failover (CVE-2022-48936)
-
kernel: padata: Fix possible divide-by-0 panic in padata_mt_helper() (CVE-2024-43889)
-
kernel: memcg: protect concurrent access to mem_cgroup_idr (CVE-2024-43892)
-
kernel: sctp: Fix null-ptr-deref in reuseport_add_sock(). (CVE-2024-44935)
-
kernel: bonding: fix xfrm real_dev null pointer dereference (CVE-2024-44989)
-
kernel: bonding: fix null pointer deref in bond_ipsec_offload_ok (CVE-2024-44990)
-
kernel: netfilter: flowtable: initialise extack before use (CVE-2024-45018)
-
kernel: ELF: fix kernel.randomize_va_space double read (CVE-2024-46826)
-
kernel: lib/generic-radix-tree.c: Fix rare race in __genradix_ptr_alloc() (CVE-2024-47668)
For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.
- Record
RLSA-2024:8856- Updated
- 2026-11-02
OSVRLSA-2024:8870 No score
Moderate: kernel-rt security update
The kernel-rt packages provide the Real Time Linux Kernel, which enables fine-tuning for systems with extremely high determinism requirements.
Security Fix(es):
-
kernel: net/bluetooth: race condition in conn_info_{min,max}_age_set() (CVE-2024-24857)
-
kernel: dmaengine: fix NULL pointer in channel unregistration function (CVE-2023-52492)
-
kernel: netfilter: nf_conntrack_h323: Add protection for bmp length out of range (CVE-2024-26851)
-
kernel: netfilter: nft_set_pipapo: do not free live element (CVE-2024-26924)
-
kernel: netfilter: nft_set_pipapo: walk over current view on netlink dump (CVE-2024-27017)
-
kernel: KVM: Always flush async #PF workqueue when vCPU is being destroyed (CVE-2024-26976)
-
kernel: nouveau: lock the client object tree. (CVE-2024-27062)
-
kernel: netfilter: bridge: replace physindev with physinif in nf_bridge_info (CVE-2024-35839)
-
kernel: netfilter: nf_tables: Fix potential data-race in __nft_flowtable_type_get() (CVE-2024-35898)
-
kernel: dma-direct: Leak pages on dma_set_decrypted() failure (CVE-2024-35939)
-
kernel: net/mlx5e: Fix netif state handling (CVE-2024-38608)
-
kernel: r8169: Fix possible ring buffer corruption on fragmented Tx packets. (CVE-2024-38586)
-
kernel: of: module: add buffer overflow check in of_modalias() (CVE-2024-38541)
-
kernel: bnxt_re: avoid shift undefined behavior in bnxt_qplib_alloc_init_hwq (CVE-2024-38540)
-
kernel: netfilter: ipset: Fix race between namespace cleanup and gc in the list:set type (CVE-2024-39503)
-
kernel: drm/i915/dpt: Make DPT object unshrinkable (CVE-2024-40924)
-
kernel: ipv6: prevent possible NULL deref in fib6_nh_init() (CVE-2024-40961)
-
kernel: tipc: force a dst refcount before doing decryption (CVE-2024-40983)
-
kernel: ACPICA: Revert "ACPICA: avoid Info: mapping multiple BARs. Your kernel is fine." (CVE-2024-40984)
-
kernel: xprtrdma: fix pointer derefs in error cases of rpcrdma_ep_create (CVE-2022-48773)
-
kernel: bpf: Fix overrunning reservations in ringbuf (CVE-2024-41009)
-
kernel: netfilter: nf_tables: prefer nft_chain_validate (CVE-2024-41042)
-
kernel: ibmvnic: Add tx check to prevent skb leak (CVE-2024-41066)
-
kernel: drm/i915/gt: Fix potential UAF by revoke of fence registers (CVE-2024-41092)
-
kernel: drm/amdgpu: avoid using null object of framebuffer (CVE-2024-41093)
-
kernel: netfilter: nf_tables: fully validate NFT_DATA_VALUE on store to data registers (CVE-2024-42070)
-
kernel: gfs2: Fix NULL pointer dereference in gfs2_log_flush (CVE-2024-42079)
-
kernel: USB: serial: mos7840: fix crash on resume (CVE-2024-42244)
-
kernel: tipc: Return non-zero value from tipc_udp_addr2str() on error (CVE-2024-42284)
-
kernel: kobject_uevent: Fix OOB access within zap_modalias_env() (CVE-2024-42292)
-
kernel: dev/parport: fix the array out-of-bounds risk (CVE-2024-42301)
-
kernel: block: initialize integrity buffer to zero before writing it to media (CVE-2024-43854)
-
kernel: mlxsw: spectrum_acl_erp: Fix object nesting warning (CVE-2024-43880)
-
kernel: gso: do not skip outer ip header in case of ipip and net_failover (CVE-2022-48936)
-
kernel: padata: Fix possible divide-by-0 panic in padata_mt_helper() (CVE-2024-43889)
-
kernel: memcg: protect concurrent access to mem_cgroup_idr (CVE-2024-43892)
-
kernel: sctp: Fix null-ptr-deref in reuseport_add_sock(). (CVE-2024-44935)
-
kernel: bonding: fix xfrm real_dev null pointer dereference (CVE-2024-44989)
-
kernel: bonding: fix null pointer deref in bond_ipsec_offload_ok (CVE-2024-44990)
-
kernel: netfilter: flowtable: initialise extack before use (CVE-2024-45018)
-
kernel: ELF: fix kernel.randomize_va_space double read (CVE-2024-46826)
-
kernel: lib/generic-radix-tree.c: Fix rare race in __genradix_ptr_alloc() (CVE-2024-47668)
For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.
- Record
RLSA-2024:8870- Updated
- 2026-11-02
OSVSUSE-SU-2024:2894-1 No score
Security update for the Linux Kernel
The SUSE Linux Enterprise 15 SP5 RT kernel was updated to receive various security bugfixes.
The following security bugs were fixed:
- CVE-2021-47086: phonet/pep: refuse to enable an unbound pipe (bsc#1220952).
- CVE-2021-47103: net: sock: preserve kabi for sock (bsc#1221010).
- CVE-2021-47186: tipc: check for null after calling kmemdup (bsc#1222702).
- CVE-2021-47546: Kabi fix for ipv6: fix memory leak in fib6_rule_suppress (bsc#1225504).
- CVE-2021-47547: net: tulip: de4x5: fix the problem that the array 'lp->phy' may be out of bound (bsc#1225505).
- CVE-2021-47588: sit: do not call ipip6_dev_free() from sit_init_net() (bsc#1226568).
- CVE-2021-47590: mptcp: fix deadlock in __mptcp_push_pending() (bsc#1226565).
- CVE-2021-47591: mptcp: remove tcp ulp setsockopt support (bsc#1226570).
- CVE-2021-47593: mptcp: clear 'kern' flag from fallback sockets (bsc#1226551).
- CVE-2021-47598: sch_cake: do not call cake_destroy() from cake_init() (bsc#1226574).
- CVE-2021-47599: btrfs: use latest_dev in btrfs_show_devname (bsc#1226571)
- CVE-2021-47606: net: netlink: af_netlink: Prevent empty skb by adding a check on len (bsc#1226555).
- CVE-2021-47623: powerpc/fixmap: Fix VM debug warning on unmap (bsc#1227919).
- CVE-2022-48785: ipv6: mcast: use rcu-safe version of ipv6_get_lladdr() (bsc#1227927)
- CVE-2022-48810: ipmr,ip6mr: acquire RTNL before calling ip[6]mr_free_table() on failure path (bsc#1227936).
- CVE-2022-48850: net-sysfs: add check for netdevice being present to speed_show (bsc#1228071)
- CVE-2022-48855: sctp: fix kernel-infoleak for SCTP sockets (bsc#1228003).
- CVE-2023-52435: net: prevent mss overflow in skb_segment() (bsc#1220138).
- CVE-2023-52573: net: rds: Fix possible NULL-pointer dereference (bsc#1220869)
- CVE-2023-52580: net/core: Fix ETH_P_1588 flow dissector (bsc#1220876).
- CVE-2023-52751: smb: client: fix use-after-free in smb2_query_info_compound() (bsc#1225489).
- CVE-2023-52775: net/smc: avoid data corruption caused by decline (bsc#1225088).
- CVE-2023-52812: drm/amd: check num of link levels when update pcie param (bsc#1225564).
- CVE-2023-52857: drm/mediatek: Fix coverity issue with unintentional integer overflow (bsc#1225581).
- CVE-2023-52863: hwmon: (axi-fan-control) Fix possible NULL pointer dereference (bsc#1225586).
- CVE-2024-26585: Fixed race between tx work scheduling and socket close (bsc#1220187).
- CVE-2024-26615: net/smc: fix illegal rmb_desc access in SMC-D connection dump (bsc#1220942).
- CVE-2024-26633: ip6_tunnel: fix NEXTHDR_FRAGMENT handling in ip6_tnl_parse_tlv_enc_lim() (bsc#1221647).
- CVE-2024-26635: llc: Drop support for ETH_P_TR_802_2 (bsc#1221656).
- CVE-2024-26636: llc: make llc_ui_sendmsg() more robust against bonding changes (bsc#1221659).
- CVE-2024-26641: ip6_tunnel: make sure to pull inner header in __ip6_tnl_rcv() (bsc#1221654).
- CVE-2024-26661: drm/amd/display: Add NULL test for 'timing generator' in (bsc#1222323)
- CVE-2024-26663: tipc: Check the bearer type before calling tipc_udp_nl_bearer_add() (bsc#1222326).
- CVE-2024-26665: tunnels: fix out of bounds access when building IPv6 PMTU error (bsc#1222328).
- CVE-2024-26802: stmmac: Clear variable when destroying workqueue (bsc#1222799).
- CVE-2024-26863: hsr: Fix uninit-value access in hsr_get_node() (bsc#1223021).
- CVE-2024-26961: mac802154: fix llsec key resources release in mac802154_llsec_key_del (bsc#1223652).
- CVE-2024-27015: netfilter: flowtable: incorrect pppoe tuple (bsc#1223806).
- CVE-2024-27019: netfilter: nf_tables: Fix potential data-race in __nft_obj_type_get() (bsc#1223813)
- CVE-2024-27020: netfilter: nf_tables: Fix potential data-race in __nft_expr_type_get() (bsc#1223815)
- CVE-2024-27025: nbd: null check for nla_nest_start (bsc#1223778)
- CVE-2024-27065: netfilter: nf_tables: do not compare internal table flags on updates (bsc#1223836).
- CVE-2024-27402: phonet/pep: fix racy skb_queue_empty() use (bsc#1224414).
- CVE-2024-27437: vfio/pci: Disable auto-enable of exclusive INTx IRQ…
- Record
SUSE-SU-2024:2894-1- Updated
- 2026-11-02
OSVSUSE-SU-2024:2939-1 No score
Security update for the Linux Kernel
The SUSE Linux Enterprise 15 SP5 kernel was updated to receive various security bugfixes.
The following security bugs were fixed:
- CVE-2021-47086: phonet/pep: refuse to enable an unbound pipe (bsc#1220952).
- CVE-2021-47089: kfence: fix memory leak when cat kfence objects (bsc#1220958).
- CVE-2021-47103: net: sock: preserve kabi for sock (bsc#1221010).
- CVE-2021-47186: tipc: check for null after calling kmemdup (bsc#1222702).
- CVE-2021-47432: lib/generic-radix-tree.c: Do not overflow in peek() (bsc#1225391).
- CVE-2021-47515: seg6: fix the iif in the IPv6 socket control block (bsc#1225426).
- CVE-2021-47538: rxrpc: Fix rxrpc_local leak in rxrpc_lookup_peer() (bsc#1225448).
- CVE-2021-47539: rxrpc: Fix rxrpc_peer leak in rxrpc_look_up_bundle() (bsc#1225452).
- CVE-2021-47546: ipv6: fix memory leak in fib6_rule_suppress (bsc#1225504).
- CVE-2021-47547: net: tulip: de4x5: fix the problem that the array 'lp->phy' may be out of bound (bsc#1225505).
- CVE-2021-47555: net: vlan: fix underflow for the real_dev refcnt (bsc#1225467).
- CVE-2021-47566: Fix clearing user buffer by properly using clear_user() (bsc#1225514).
- CVE-2021-47571: staging: rtl8192e: Fix use after free in _rtl92e_pci_disconnect() (bsc#1225518).
- CVE-2021-47572: net: nexthop: fix null pointer dereference when IPv6 is not enabled (bsc#1225389).
- CVE-2021-47588: sit: do not call ipip6_dev_free() from sit_init_net() (bsc#1226568).
- CVE-2021-47590: mptcp: fix deadlock in __mptcp_push_pending() (bsc#1226565).
- CVE-2021-47591: mptcp: remove tcp ulp setsockopt support (bsc#1226570).
- CVE-2021-47593: mptcp: clear 'kern' flag from fallback sockets (bsc#1226551).
- CVE-2021-47598: sch_cake: do not call cake_destroy() from cake_init() (bsc#1226574).
- CVE-2021-47599: btrfs: use latest_dev in btrfs_show_devname (bsc#1226571).
- CVE-2021-47606: net: netlink: af_netlink: Prevent empty skb by adding a check on len. (bsc#1226555).
- CVE-2021-47623: powerpc/fixmap: Fix VM debug warning on unmap (bsc#1227919).
- CVE-2022-48716: ASoC: codecs: wcd938x: fix incorrect used of portid (bsc#1226678).
- CVE-2022-48785: ipv6: mcast: use rcu-safe version of ipv6_get_lladdr() (bsc#1227927)
- CVE-2022-48810: ipmr,ip6mr: acquire RTNL before calling ip[6]mr_free_table() on failure path (bsc#1227936).
- CVE-2022-48850: net-sysfs: add check for netdevice being present to speed_show (bsc#1228071).
- CVE-2022-48855: sctp: fix kernel-infoleak for SCTP sockets (bsc#1228003).
- CVE-2023-24023: Bluetooth: Add more enc key size check (bsc#1218148).
- CVE-2023-52435: net: prevent mss overflow in skb_segment() (bsc#1220138).
- CVE-2023-52573: net: rds: Fix possible NULL-pointer dereference (bsc#1220869).
- CVE-2023-52580: net/core: Fix ETH_P_1588 flow dissector (bsc#1220876).
- CVE-2023-52622: ext4: avoid online resizing failures due to oversized flex bg (bsc#1222080).
- CVE-2023-52658: Revert 'net/mlx5: Block entering switchdev mode with ns inconsistency' (bsc#1224719).
- CVE-2023-52667: net/mlx5e: fix a potential double-free in fs_any_create_groups (bsc#1224603).
- CVE-2023-52670: rpmsg: virtio: Free driver_override when rpmsg_remove() (bsc#1224696).
- CVE-2023-52672: pipe: wakeup wr_wait after setting max_usage (bsc#1224614).
- CVE-2023-52675: powerpc/imc-pmu: Add a null pointer check in update_events_in_group() (bsc#1224504).
- CVE-2023-52735: bpf, sockmap: Don't let sock_map_{close,destroy,unhash} call itself (bsc#1225475).
- CVE-2023-52737: btrfs: lock the inode in shared mode before starting fiemap (bsc#1225484).
- CVE-2023-52751: smb: client: fix use-after-free in smb2_query_info_compound() (bsc#1225489).
- CVE-2023-52752: smb: client: fix use-after-free bug in cifs_debug_data_proc_show() (bsc#1225487).
- CVE-2023-52762: virtio-blk: fix implicit overflow on virtio_max_dma_size (bsc#1225573).
- CVE-2023-52775: net/smc: avoid data corruption caused by decline (bsc#1225088).
- CVE-2023-52784: bonding: stop the device in bond_setup_by_slave() (bsc#1224946).
- CVE-2023-52787: blk-mq: make…
- Record
SUSE-SU-2024:2939-1- Updated
- 2026-11-02
OSVSUSE-SU-2024:2947-1 No score
Security update for the Linux Kernel
The SUSE Linux Enterprise 15 SP5 Azure kernel was updated to receive various security bugfixes.
The following security bugs were fixed:
- CVE-2021-47086: phonet/pep: refuse to enable an unbound pipe (bsc#1220952).
- CVE-2021-47103: net: sock: preserve kabi for sock (bsc#1221010).
- CVE-2021-47186: ipc: check for null after calling kmemdup (bsc#1222702).
- CVE-2021-47546: Kabi fix for ipv6: fix memory leak in fib6_rule_suppress (bsc#1225504).
- CVE-2021-47547: net: tulip: de4x5: fix the problem that the array 'lp->phy' may be out of bound (bsc#1225505).
- CVE-2021-47588: sit: do not call ipip6_dev_free() from sit_init_net() (bsc#1226568).
- CVE-2021-47590: mptcp: fix deadlock in __mptcp_push_pending() (bsc#1226565).
- CVE-2021-47591: mptcp: remove tcp ulp setsockopt support (bsc#1226570).
- CVE-2021-47593: mptcp: clear 'kern' flag from fallback sockets (bsc#1226551).
- CVE-2021-47598: sch_cake: do not call cake_destroy() from cake_init() (bsc#1226574).
- CVE-2021-47599: btrfs: use latest_dev in btrfs_show_devname (bsc#1226571)
- CVE-2021-47606: net: netlink: af_netlink: Prevent empty skb by adding a check on len (bsc#1226555).
- CVE-2021-47623: powerpc/fixmap: Fix VM debug warning on unmap (bsc#1227919).
- CVE-2022-48785: ipv6: mcast: use rcu-safe version of ipv6_get_lladdr() (bsc#1227927)
- CVE-2022-48810: ipmr,ip6mr: acquire RTNL before calling ip[6]mr_free_table() on failure path (bsc#1227936).
- CVE-2022-48850: net-sysfs: add check for netdevice being present to speed_show (bsc#1228071)
- CVE-2022-48855: sctp: fix kernel-infoleak for SCTP sockets (bsc#1228003).
- CVE-2023-52435: net: prevent mss overflow in skb_segment() (bsc#1220138).
- CVE-2023-52573: net: rds: Fix possible NULL-pointer dereference (bsc#1220869)
- CVE-2023-52580: net/core: Fix ETH_P_1588 flow dissector (bsc#1220876).
- CVE-2023-52751: smb: client: fix use-after-free in smb2_query_info_compound() (bsc#1225489).
- CVE-2023-52775: net/smc: avoid data corruption caused by decline (bsc#1225088).
- CVE-2023-52812: drm/amd: check num of link levels when update pcie param (bsc#1225564).
- CVE-2023-52857: drm/mediatek: Fix coverity issue with unintentional integer overflow (bsc#1225581).
- CVE-2023-52863: hwmon: (axi-fan-control) Fix possible NULL pointer dereference (bsc#1225586).
- CVE-2024-26585: Fixed race between tx work scheduling and socket close (bsc#1220187).
- CVE-2024-26615: net/smc: fix illegal rmb_desc access in SMC-D connection dump (bsc#1220942).
- CVE-2024-26633: ip6_tunnel: fix NEXTHDR_FRAGMENT handling in ip6_tnl_parse_tlv_enc_lim() (bsc#1221647).
- CVE-2024-26635: llc: Drop support for ETH_P_TR_802_2 (bsc#1221656).
- CVE-2024-26636: llc: make llc_ui_sendmsg() more robust against bonding changes (bsc#1221659).
- CVE-2024-26641: ip6_tunnel: make sure to pull inner header in __ip6_tnl_rcv() (bsc#1221654).
- CVE-2024-26661: drm/amd/display: Add NULL test for 'timing generator' in (bsc#1222323)
- CVE-2024-26663: tipc: Check the bearer type before calling tipc_udp_nl_bearer_add() (bsc#1222326).
- CVE-2024-26665: tunnels: fix out of bounds access when building IPv6 PMTU error (bsc#1222328).
- CVE-2024-26802: stmmac: Clear variable when destroying workqueue (bsc#1222799).
- CVE-2024-26863: hsr: Fix uninit-value access in hsr_get_node() (bsc#1223021).
- CVE-2024-26961: mac802154: fix llsec key resources release in mac802154_llsec_key_del (bsc#1223652).
- CVE-2024-27015: netfilter: flowtable: incorrect pppoe tuple (bsc#1223806).
- CVE-2024-27019: netfilter: nf_tables: Fix potential data-race in __nft_obj_type_get() (bsc#1223813)
- CVE-2024-27020: netfilter: nf_tables: Fix potential data-race in __nft_expr_type_get() (bsc#1223815)
- CVE-2024-27025: nbd: null check for nla_nest_start (bsc#1223778)
- CVE-2024-27065: netfilter: nf_tables: do not compare internal table flags on updates (bsc#1223836).
- CVE-2024-27402: phonet/pep: fix racy skb_queue_empty() use (bsc#1224414).
- CVE-2024-27437: vfio/pci: Disable auto-enable of exclusive INTx IRQ…
- Record
SUSE-SU-2024:2947-1- Updated
- 2026-11-02
OSVSUSE-SU-2024:3190-1 No score
Security update for the Linux Kernel
The SUSE Linux Enterprise 15 SP5 Azure kernel was updated to receive various security bugfixes.
The following security bugs were fixed:
- CVE-2024-44947: Initialize beyond-EOF page contents before setting uptodate (bsc#1229454).
- CVE-2024-36936: Touch soft lockup during memory accept (bsc#1225773).
- CVE-2022-48706: Do proper cleanup if IFCVF init fails (bsc#1225524).
- CVE-2024-43883: Do not drop references before new references are gained (bsc#1229707).
- CVE-2024-41062: Sync sock recv cb and release (bsc#1228576).
- CVE-2024-43861: Fix memory leak for not ip packets (bsc#1229500).
- CVE-2023-52489: Fix race in accessing memory_section->usage (bsc#1221326).
- CVE-2024-43893: Check uartclk for zero to avoid divide by zero (bsc#1229759).
- CVE-2024-43821: Fix a possible null pointer dereference (bsc#1229315).
- CVE-2024-43900: Avoid use-after-free in load_firmware_cb() (bsc#1229756).
- CVE-2024-44938: Fix shift-out-of-bounds in dbDiscardAG (bsc#1229792).
- CVE-2024-44939: fix null ptr deref in dtInsertEntry (bsc#1229820).
- CVE-2024-41087: Fix double free on error (CVE-2024-41087,bsc#1228466).
- CVE-2024-42277: Avoid NULL deref in sprd_iommu_hw_en (bsc#1229409).
- CVE-2024-43902: Add null checker before passing variables (bsc#1229767).
- CVE-2024-43904: Add null checks for 'stream' and 'plane' before dereferencing (bsc#1229768)
- CVE-2024-43880: Put back removed metod in struct objagg_ops (bsc#1229481).
- CVE-2024-43884: Add error handling to pair_device() (bsc#1229739)
- CVE-2024-43899: Fix null pointer deref in dcn20_resource.c (bsc#1229754).
- CVE-2022-48920: Get rid of warning on transaction commit when using flushoncommit (bsc#1229658).
- CVE-2023-52906: Fix warning during failed attribute validation (bsc#1229527).
- CVE-2024-43882: Fixed ToCToU between perm check and set-uid/gid usage. (bsc#1229503)
- CVE-2024-43866: Always drain health in shutdown callback (bsc#1229495).
- CVE-2024-26812: Struct virqfd kABI workaround (bsc#1222808).
- CVE-2022-48912: Fix use-after-free in __nf_register_net_hook() (bsc#1229641)
- CVE-2024-27010: Fix mirred deadlock on device recursion (bsc#1223720).
- CVE-2022-48906: Correctly set DATA_FIN timeout when number of retransmits is large (bsc#1229605)
- CVE-2024-42155: Wipe copies of protected- and secure-keys (bsc#1228733).
- CVE-2024-42156: Wipe copies of clear-key structures on failure (bsc#1228722).
- CVE-2023-52899: Add exception protection processing for vd in axi_chan_handle_err function (bsc#1229569).
- CVE-2024-42158: Use kfree_sensitive() to fix Coccinelle warnings (bsc#1228720).
- CVE-2024-26631: Fix data-race in ipv6_mc_down / mld_ifc_work (bsc#1221630).
- CVE-2024-43873: Always initialize seqpacket_allow (bsc#1229488)
- CVE-2024-40905: Fix possible race in __fib6_drop_pcpu_from() (bsc#1227761)
- CVE-2024-39489: Fix memleak in seg6_hmac_init_algo (bsc#1227623)
- CVE-2021-47106: Fix use-after-free in nft_set_catchall_destroy() (bsc#1220962)
- CVE-2021-47517: Fix panic when interrupt coaleceing is set via ethtool (bsc#1225428).
- CVE-2024-36489: Fix missing memory barrier in tls_init (bsc#1226874)
- CVE-2024-41020: Fix fcntl/close race recovery compat path (bsc#1228427).
- CVE-2024-27079: Fix NULL domain on device release (bsc#1223742).
- CVE-2024-35897: Discard table flag update with pending basechain deletion (bsc#1224510).
- CVE-2024-27403: Restore const specifier in flow_offload_route_init() (bsc#1224415).
- CVE-2024-27011: Fix memleak in map from abort path (bsc#1223803).
- CVE-2024-43819: Reject memory region operations for ucontrol VMs (bsc#1229290 git-fixes).
- CVE-2024-26668: Reject configurations that cause integer overflow (bsc#1222335).
- CVE-2024-26835: Set dormant flag on hook register failure (bsc#1222967).
- CVE-2024-26808: Handle NETDEV_UNREGISTER for inet/ingress basechain (bsc#1222634).
- CVE-2024-27016: Validate pppoe header (bsc#1223807).
- CVE-2024-35945: Prevent nullptr exceptions on ISR (bsc#1224639).
- CVE-2023-52581: Fix memleak when more than 255…
- Record
SUSE-SU-2024:3190-1- Updated
- 2026-11-02
OSVSUSE-SU-2024:3194-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-41062: Sync sock recv cb and release (bsc#1228576).
- CVE-2023-52489: Fix race in accessing memory_section->usage (bsc#1221326).
- CVE-2024-43821: Fix a possible null pointer dereference (bsc#1229315).
- CVE-2024-43911: Fix NULL dereference at band check in starting tx ba session (bsc#1229827).
- CVE-2024-42277: Avoid NULL deref in sprd_iommu_hw_en (bsc#1229409).
- CVE-2024-43880: Put back removed metod in struct objagg_ops (bsc#1229481).
- CVE-2024-43899: Fix null pointer deref in dcn20_resource.c (bsc#1229754).
- CVE-2024-43882: Fixed ToCToU between perm check and set-uid/gid usage. (bsc#1229503)
- CVE-2024-43866: Always drain health in shutdown callback (bsc#1229495).
- CVE-2024-26812: Struct virqfd kABI workaround (bsc#1222808).
- CVE-2024-27010: Fix mirred deadlock on device recursion (bsc#1223720).
- CVE-2024-36270: Fix reference in patches.suse/netfilter-tproxy-bail-out-if-IP-has-been-disabled-on.patch (bsc#1226798)
- CVE-2024-36881: Reset ptes when close() for wr-protected ones (bsc#1225718).
- CVE-2024-42316: Fix div-by-zero in vmpressure_calc_level() (bsc#1229353).
- CVE-2024-43855: Fix deadlock between mddev_suspend and flush bio (bsc#1229342,).
- CVE-2024-43864: Fix CT entry update leaks of modify header context (bsc#1229496)
- CVE-2024-26631: Fix data-race in ipv6_mc_down / mld_ifc_work (bsc#1221630).
- CVE-2024-42109: Unconditionally flush pending work before notifier (bsc#1228505)
- CVE-2024-41084: Avoid null pointer dereference in region lookup (bsc#1228472)
- CVE-2024-40905: Fix possible race in __fib6_drop_pcpu_from() (bsc#1227761)
- CVE-2024-39489: Fix memleak in seg6_hmac_init_algo (bsc#1227623)
- CVE-2024-36489: Fix missing memory barrier in tls_init (bsc#1226874)
- CVE-2024-27079: Add kABI workaround patch (bsc#1223742).
- CVE-2024-41020: Fix fcntl/close race recovery compat path (bsc#1228427).
- CVE-2024-35897: Discard table flag update with pending basechain deletion (bsc#1224510).
- CVE-2024-27403: Restore const specifier in flow_offload_route_init() (bsc#1224415).
- CVE-2024-27011: Fix memleak in map from abort path (bsc#1223803).
- CVE-2024-26668: Reject configurations that cause integer overflow (bsc#1222335).
- CVE-2024-26835: Set dormant flag on hook register failure (bsc#1222967).
- CVE-2024-26808: Handle NETDEV_UNREGISTER for inet/ingress basechain (bsc#1222634).
- CVE-2024-26809: Release elements in clone only from destroy path (bsc#1222633).
- CVE-2023-52581: Fix memleak when more than 255 elements expired (bsc#1220877).
- CVE-2024-43837: Fix updating attached freplace prog in prog_array map (bsc#1229297).
- CVE-2024-35939: Fixed leak pages on dma_set_decrypted() failure (bsc#1224535).
- CVE-2024-42291: Add a per-VF limit on number of FDIR filters (bsc#1229374).
- CVE-2024-42268: Fix missing lock on sync reset reload (bsc#1229391).
- CVE-2024-43834: Fix invalid wait context of page_pool_destroy() (bsc#1229314)
- CVE-2024-27433: Fix an error handling path in clk_mt8135_apmixed_probe() (bsc#1224711).
- CVE-2024-36286: Acquire rcu_read_lock() in instance_destroy_rcu() (bsc#1226801)
- CVE-2024-26851: Add protection for bmp length out of range (bsc#1223074)
- CVE-2024-40920: Fix suspicious rcu usage in br_mst_set_state (bsc#1227781).
- CVE-2024-40921: Pass vlan group directly to br_mst_vlan_set_state (bsc#1227784).
- CVE-2024-36979: Fix vlan use-after-free (bsc#1226604).
- CVE-2024-26590: Fix inconsistent per-file compression format (bsc#1220252,).
- CVE-2023-52859: Fix use-after-free when register pmu fails (bsc#1225582).
- CVE-2024-42270: Fix null-ptr-deref in iptable_nat_table_init() (bsc#1229404)
- CVE-2024-42269: Fix potential null-ptr-deref in ip6table_nat_table_init() (bsc#1229402)
- CVE-2024-42284: Return non-zero value from tipc_udp_addr2str() on error (bsc#1229382)
- CVE-2024-42283: Initialize all fields in dumped nexthops (bsc#1229383) -…
- Record
SUSE-SU-2024:3194-1- Updated
- 2026-11-02
OSVSUSE-SU-2024:3195-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-2024-41062: Sync sock recv cb and release (bsc#1228576).
- CVE-2023-52489: Fix race in accessing memory_section->usage (bsc#1221326).
- CVE-2024-43821: Fix a possible null pointer dereference (bsc#1229315).
- CVE-2024-43911: Fix NULL dereference at band check in starting tx ba session (bsc#1229827).
- CVE-2024-42277: Avoid NULL deref in sprd_iommu_hw_en (bsc#1229409).
- CVE-2024-43880: Put back removed metod in struct objagg_ops (bsc#1229481).
- CVE-2024-43899: Fix null pointer deref in dcn20_resource.c (bsc#1229754).
- CVE-2024-43882: Fixed ToCToU between perm check and set-uid/gid usage. (bsc#1229503)
- CVE-2024-43866: Always drain health in shutdown callback (bsc#1229495).
- CVE-2024-26812: Struct virqfd kABI workaround (bsc#1222808).
- CVE-2024-27010: Fix mirred deadlock on device recursion (bsc#1223720).
- CVE-2024-36881: Fix reset ptes when close() for wr-protected (bsc#1225718).
- CVE-2024-42316: Fix div-by-zero in vmpressure_calc_level() (bsc#1229353).
- CVE-2024-43855: Fix deadlock between mddev_suspend and flush bio (bsc#1229342).
- CVE-2024-43864: Fix CT entry update leaks of modify header context (bsc#1229496).
- CVE-2024-26631: Fix data-race in ipv6_mc_down / mld_ifc_work (bsc#1221630).
- CVE-2024-42109: Unconditionally flush pending work before notifier (bsc#1228505).
- CVE-2024-41084: Avoid null pointer dereference in region lookup (bsc#1228472).
- CVE-2024-40905: Fix possible race in __fib6_drop_pcpu_from() (bsc#1227761)
- CVE-2024-39489: Fix memleak in seg6_hmac_init_algo (bsc#1227623)
- CVE-2024-36489: Fix missing memory barrier in tls_init (bsc#1226874)
- CVE-2024-27079: Fix NULL domain on device release (bsc#1223742).
- CVE-2024-41020: Fix fcntl/close race recovery compat path (bsc#1228427).
- CVE-2024-35897: Discard table flag update with pending basechain deletion (bsc#1224510).
- CVE-2024-27403: Restore const specifier in flow_offload_route_init() (bsc#1224415).
- CVE-2024-27011: Fix memleak in map from abort path (bsc#1223803).
- CVE-2024-26668: Reject configurations that cause integer overflow (bsc#1222335).
- CVE-2024-26835: Set dormant flag on hook register failure (bsc#1222967).
- CVE-2024-26808: Handle NETDEV_UNREGISTER for inet/ingress basechain (bsc#1222634).
- CVE-2024-26809: Release elements in clone only from destroy path (bsc#1222633).
- CVE-2023-52581: Fix memleak when more than 255 elements expired (bsc#1220877).
- CVE-2024-43837: Fix updating attached freplace prog in prog_array map (bsc#1229297).
- CVE-2024-35939: Fixed leak pages on dma_set_decrypted() failure (bsc#1224535).
- CVE-2024-42291: Add a per-VF limit on number of FDIR filters (bsc#1229374).
- CVE-2024-42268: Fix missing lock on sync reset reload (bsc#1229391).
- CVE-2024-43834: Fix invalid wait context of page_pool_destroy() (bsc#1229314)
- CVE-2024-27433: Fix an error handling path in clk_mt8135_apmixed_probe() (bsc#1224711).
- CVE-2024-36286: Acquire rcu_read_lock() in instance_destroy_rcu() (bsc#1226801)
- CVE-2024-26851: Add protection for bmp length out of range (bsc#1223074)
- CVE-2024-40920: Fix suspicious rcu usage in br_mst_set_state (bsc#1227781).
- CVE-2024-40921: Pass vlan group directly to br_mst_vlan_set_state (bsc#1227784).
- CVE-2024-36979: Fix vlan use-after-free (bsc#1226604).
- CVE-2024-26590: Fix inconsistent per-file compression format (bsc#1220252).
- CVE-2023-52859: Fix use-after-free when register pmu fails (bsc#1225582).
- CVE-2024-42270: Fix null-ptr-deref in iptable_nat_table_init() (bsc#1229404).
- CVE-2024-42269: Fix potential null-ptr-deref in ip6table_nat_table_init() (bsc#1229402).
- CVE-2024-42284: Return non-zero value from tipc_udp_addr2str() on error (bsc#1229382)
- CVE-2024-42283: Initialize all fields in dumped nexthops (bsc#1229383)
- CVE-2024-42312: Always initialize i_uid/i_gid (bsc#1229357)
- CVE-2024-43854: Initialize integrity buffer to zero…
- Record
SUSE-SU-2024:3195-1- Updated
- 2026-11-02
OSVSUSE-SU-2024:3209-1 No score
Security update for the Linux Kernel
The SUSE Linux Enterprise 15 SP5 RT kernel was updated to receive various security bugfixes.
The following security bugs were fixed:
- CVE-2024-44947: Initialize beyond-EOF page contents before setting uptodate (bsc#1229454).
- CVE-2024-36936: Touch soft lockup during memory accept (bsc#1225773).
- CVE-2022-48706: Do proper cleanup if IFCVF init fails (bsc#1225524).
- CVE-2024-43883: Do not drop references before new references are gained (bsc#1229707).
- CVE-2024-41062: Sync sock recv cb and release (bsc#1228576).
- CVE-2024-43861: Fix memory leak for not ip packets (bsc#1229500).
- CVE-2023-52489: Fix race in accessing memory_section->usage (bsc#1221326).
- CVE-2024-43893: Check uartclk for zero to avoid divide by zero (bsc#1229759).
- CVE-2024-43821: Fix a possible null pointer dereference (bsc#1229315).
- CVE-2024-43900: Avoid use-after-free in load_firmware_cb() (bsc#1229756).
- CVE-2024-44938: Fix shift-out-of-bounds in dbDiscardAG (bsc#1229792).
- CVE-2024-44939: Fix null ptr deref in dtInsertEntry (bsc#1229820).
- CVE-2024-41087: Fix double free on error (bsc#1228466).
- CVE-2024-42277: Avoid NULL deref in sprd_iommu_hw_en (bsc#1229409).
- CVE-2024-43902: Add null checker before passing variables (bsc#1229767).
- CVE-2024-43904: Add null checks for 'stream' and 'plane' before dereferencing (bsc#1229768)
- CVE-2024-43880: Put back removed metod in struct objagg_ops (bsc#1229481).
- CVE-2024-43884: Add error handling to pair_device() (bsc#1229739)
- CVE-2024-43899: Fix null pointer deref in dcn20_resource.c (bsc#1229754).
- CVE-2022-48920: Get rid of warning on transaction commit when using flushoncommit (bsc#1229658).
- CVE-2023-52906: Fix warning during failed attribute validation (bsc#1229527).
- CVE-2024-43882: Fixed ToCToU between perm check and set-uid/gid usage. (bsc#1229503)
- CVE-2024-43866: Always drain health in shutdown callback (bsc#1229495).
- CVE-2024-26812: struct virqfd kABI workaround (bsc#1222808).
- CVE-2022-48912: Fix use-after-free in __nf_register_net_hook() (bsc#1229641)
- CVE-2024-27010: Fix mirred deadlock on device recursion (bsc#1223720).
- CVE-2022-48906: Correctly set DATA_FIN timeout when number of retransmits is large (bsc#1229605)
- CVE-2024-42155: Wipe copies of protected- and secure-keys (bsc#1228733).
- CVE-2024-42156: Wipe copies of clear-key structures on failure (bsc#1228722).
- CVE-2023-52899: Add exception protection processing for vd in axi_chan_handle_err function (bsc#1229569).
- CVE-2024-42158: Use kfree_sensitive() to fix Coccinelle warnings (bsc#1228720).
- CVE-2024-26631: Fix data-race in ipv6_mc_down / mld_ifc_work (bsc#1221630).
- CVE-2024-43873: Always initialize seqpacket_allow (bsc#1229488)
- CVE-2024-40905: Fix possible race in __fib6_drop_pcpu_from() (bsc#1227761)
- CVE-2024-39489: Fix memleak in seg6_hmac_init_algo (bsc#1227623)
- CVE-2021-47106: Fix use-after-free in nft_set_catchall_destroy() (bsc#1220962)
- CVE-2021-47517: Fix panic when interrupt coaleceing is set via ethtool (bsc#1225428).
- CVE-2024-36489: Fix missing memory barrier in tls_init (bsc#1226874)
- CVE-2024-41020: Fix fcntl/close race recovery compat path (bsc#1228427).
- CVE-2024-27079: Fix NULL domain on device release (bsc#1223742).
- CVE-2024-35897: Discard table flag update with pending basechain deletion (bsc#1224510).
- CVE-2024-27403: Restore const specifier in flow_offload_route_init() (bsc#1224415).
- CVE-2024-27011: Fix memleak in map from abort path (bsc#1223803).
- CVE-2024-43819: Reject memory region operations for ucontrol VMs (bsc#1229290).
- CVE-2024-26668: Reject configurations that cause integer overflow (bsc#1222335).
- CVE-2024-26835: Set dormant flag on hook register failure (bsc#1222967).
- CVE-2024-26808: Handle NETDEV_UNREGISTER for inet/ingress basechain (bsc#1222634).
- CVE-2024-27016: Validate pppoe header (bsc#1223807).
- CVE-2024-35945: Prevent nullptr exceptions on ISR (bsc#1224639).
- CVE-2023-52581: Fix memleak when more than 255 elements expired (bsc#1220877).…
- Record
SUSE-SU-2024:3209-1- Updated
- 2026-11-02
OSVSUSE-SU-2024:3225-1 No score
Security update for the Linux Kernel
The SUSE Linux Enterprise 15 SP3 RT kernel was updated to receive various security bugfixes.
The following security bugs were fixed:
- CVE-2024-44947: Initialize beyond-EOF page contents before setting uptodate (bsc#1229454).
- CVE-2022-48919: Fix double free race when mount fails in cifs_get_root() (bsc#1229657).
- CVE-2023-52854: Fix refcnt handling in padata_free_shell() (bsc#1225584).
- CVE-2024-43883: Do not drop references before new references are gained (bsc#1229707).
- CVE-2024-41062: bluetooth/l2cap: sync sock recv cb and release (bsc#1228576).
- CVE-2024-43861: Fix memory leak for not ip packets (bsc#1229500).
- CVE-2024-41087: Fix double free on error (CVE-2024-41087,bsc#1228466).
- CVE-2024-43882: Fixed ToCToU between perm check and set-uid/gid usage. (bsc#1229503)
- CVE-2022-48912: Fix use-after-free in __nf_register_net_hook() (bsc#1229641)
- CVE-2022-48872: Fix use-after-free race condition for maps (bsc#1229510).
- CVE-2022-48873: Do not remove map on creater_process and device_release (bsc#1229512).
- CVE-2024-42271: Fixed a use after free in iucv_sock_close(). (bsc#1229400)
- CVE-2024-42232: Fixed a race between delayed_work() and ceph_monc_stop(). (bsc#1228959)
- CVE-2024-40910: Fix refcount imbalance on inbound connections (bsc#1227832).
- CVE-2024-41009: bpf: Fix overrunning reservations in ringbuf (bsc#1228020).
The following non-security bugs were fixed:
- Bluetooth: L2CAP: Fix deadlock (git-fixes).
- sched/psi: use kernfs polling functions for PSI trigger polling (bsc#1209799 bsc#1225109).
- Record
SUSE-SU-2024:3225-1- Updated
- 2026-11-02
OSVSUSE-SU-2024:3227-1 No score
Security update for the Linux Kernel
The SUSE Linux Enterprise 15 SP4 RT kernel was updated to receive various security bugfixes.
The following security bugs were fixed:
- CVE-2024-41062: bluetooth/l2cap: sync sock recv cb and release (bsc#1228576).
- CVE-2024-44947: Initialize beyond-EOF page contents before setting uptodate (bsc#1229454).
- CVE-2024-43883: Do not drop references before new references are gained (bsc#1229707).
- CVE-2024-43861: Fix memory leak for not ip packets (bsc#1229500).
- CVE-2023-52489: mm/sparsemem: fix race in accessing memory_section->usage (bsc#1221326).
- CVE-2024-44938: Fix shift-out-of-bounds in dbDiscardAG (bsc#1229792).
- CVE-2024-41087: Fix double free on error (CVE-2024-41087,bsc#1228466).
- CVE-2024-43882: Fixed ToCToU between perm check and set-uid/gid usage. (bsc#1229503)
- CVE-2022-48935: Fixed an unregister flowtable hooks on netns exit (bsc#1229619)
- CVE-2022-48912: Fix use-after-free in __nf_register_net_hook() (bsc#1229641)
- CVE-2024-42271: Fixed a use after free in iucv_sock_close(). (bsc#1229400)
- CVE-2024-42232: Fixed a race between delayed_work() and ceph_monc_stop(). (bsc#1228959)
- CVE-2024-40910: Fix refcount imbalance on inbound connections (bsc#1227832).
- CVE-2024-41009: bpf: Fix overrunning reservations in ringbuf (bsc#1228020).
The following non-security bugs were fixed:
- Bluetooth: L2CAP: Fix deadlock (git-fixes).
- mm, kmsan: fix infinite recursion due to RCU critical section (git-fixes).
- mm: prevent derefencing NULL ptr in pfn_section_valid() (git-fixes).
- nvme_core: scan namespaces asynchronously (bsc#1224105).
- Record
SUSE-SU-2024:3227-1- Updated
- 2026-11-02
OSVSUSE-SU-2024:3249-1 No score
Security update for the Linux Kernel
The SUSE Linux Enterprise 15 SP3 kernel was updated to receive various security bugfixes.
The following security bugs were fixed:
- CVE-2024-44947: Initialize beyond-EOF page contents before setting uptodate (bsc#1229454).
- CVE-2022-48919: Fix double free race when mount fails in cifs_get_root() (bsc#1229657).
- CVE-2023-52854: Fix refcnt handling in padata_free_shell() (bsc#1225584).
- CVE-2024-43883: Do not drop references before new references are gained (bsc#1229707).
- CVE-2024-41062: Sync sock recv cb and release (bsc#1228576).
- CVE-2024-43861: Fix memory leak for not ip packets (bsc#1229500).
- CVE-2024-43882: Fixed ToCToU between perm check and set-uid/gid usage. (bsc#1229503)
- CVE-2022-48912: Fix use-after-free in __nf_register_net_hook() (bsc#1229641)
- CVE-2022-48872: Fix use-after-free race condition for maps (bsc#1229510).
- CVE-2022-48873: Do not remove map on creater_process and device_release (bsc#1229512).
- CVE-2024-42271: Fixed a use after free in iucv_sock_close(). (bsc#1229400)
- CVE-2024-42232: Fixed a race between delayed_work() and ceph_monc_stop(). (bsc#1228959)
- CVE-2024-40910: Fix refcount imbalance on inbound connections (bsc#1227832).
- CVE-2022-48686: Fixed UAF when detecting digest errors (bsc#1223948).
- CVE-2024-41009: bpf: Fix overrunning reservations in ringbuf (bsc#1228020).
- CVE-2022-48791: Fix use-after-free for aborted TMF sas_task (bsc#1228002)
The following non-security bugs were fixed:
- Bluetooth: L2CAP: Fix deadlock (git-fixes).
- powerpc: Remove support for PowerPC 601 (Remove unused and malformed assembly causing build error).
- sched/psi: use kernfs polling functions for PSI trigger polling (bsc#1209799 bsc#1225109).
- scsi: pm80xx: Fix TMF task completion race condition (bsc#1228002).
- Record
SUSE-SU-2024:3249-1- Updated
- 2026-11-02
OSVSUSE-SU-2024:3383-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-43911: wifi: mac80211: fix NULL dereference at band check in starting tx ba session (bsc#1229827).
- CVE-2024-43899: drm/amd/display: Fix null pointer deref in dcn20_resource.c (bsc#1229754).
- CVE-2024-43882: Fixed ToCToU between perm check and set-uid/gid usage. (bsc#1229503)
- CVE-2024-43880: kabi: lib: objagg: Put back removed metod in struct objagg_ops (bsc#1229481).
- CVE-2024-43866: net/mlx5: Always drain health in shutdown callback (bsc#1229495).
- CVE-2024-43864: net/mlx5e: Fix CT entry update leaks of modify header context (bsc#1229496).
- CVE-2024-43855: md: fix deadlock between mddev_suspend and flush bio (bsc#1229342).
- CVE-2024-43854: block: initialize integrity buffer to zero before writing it to media (bsc#1229345)
- CVE-2024-43850: soc: qcom: icc-bwmon: Fix refcount imbalance seen during bwmon_remove (bsc#1229316).
- CVE-2024-43839: bna: adjust 'name' buf size of bna_tcb and bna_ccb structures (bsc#1229301).
- CVE-2024-43837: bpf: Fix updating attached freplace prog in prog_array map (bsc#1229297).
- CVE-2024-43834: xdp: fix invalid wait context of page_pool_destroy() (bsc#1229314)
- CVE-2024-43831: media: mediatek: vcodec: Handle invalid decoder vsi (bsc#1229309).
- CVE-2024-43821: scsi: lpfc: Fix a possible null pointer dereference (bsc#1229315).
- CVE-2024-42322: ipvs: properly dereference pe in ip_vs_add_service (bsc#1229347)
- CVE-2024-42318: landlock: Do not lose track of restrictions on cred_transfer (bsc#1229351).
- CVE-2024-42316: mm/mglru: fix div-by-zero in vmpressure_calc_level() (bsc#1229353).
- CVE-2024-42312: sysctl: always initialize i_uid/i_gid (bsc#1229357)
- CVE-2024-42308: Update DRM patch reference (bsc#1229411)
- CVE-2024-42301: dev/parport: fix the array out-of-bounds risk (bsc#1229407).
- CVE-2024-42295: nilfs2: handle inconsistent state in nilfs_btnode_create_block() (bsc#1229370).
- CVE-2024-42291: ice: Add a per-VF limit on number of FDIR filters (bsc#1229374).
- CVE-2024-42290: irqchip/imx-irqsteer: Handle runtime power management correctly (bsc#1229379).
- CVE-2024-42284: tipc: Return non-zero value from tipc_udp_addr2str() on error (bsc#1229382)
- CVE-2024-42283: net: nexthop: Initialize all fields in dumped nexthops (bsc#1229383)
- CVE-2024-42281: bpf: Fix a segment issue when downgrading gso_size (bsc#1229386).
- CVE-2024-42277: iommu: sprd: Avoid NULL deref in sprd_iommu_hw_en (bsc#1229409).
- CVE-2024-42270: netfilter: iptables: Fix null-ptr-deref in iptable_nat_table_init() (bsc#1229404).
- CVE-2024-42269: netfilter: iptables: Fix potential null-ptr-deref in ip6table_nat_table_init() (bsc#1229402).
- CVE-2024-42268: net/mlx5: Fix missing lock on sync reset reload (bsc#1229391).
- CVE-2024-42247: wireguard: allowedips: avoid unaligned 64-bit memory accesses (bsc#1228988).
- CVE-2024-42246: net, sunrpc: Remap EPERM in case of connection failure in xs_tcp_setup_socket (bsc#1228989).
- CVE-2024-42245: Revert 'sched/fair: Make sure to try to detach at least one movable task' (bsc#1228978).
- CVE-2024-42241: mm/shmem: disable PMD-sized page cache if needed (bsc#1228986).
- CVE-2024-42224: net: dsa: mv88e6xxx: Correct check for empty list (bsc#1228723).
- CVE-2024-42162: gve: Account for stopped queues when reading NIC stats (bsc#1228706).
- CVE-2024-42161: bpf: avoid uninitialized value in BPF_CORE_READ_BITFIELD (bsc#1228756).
- CVE-2024-42159: scsi: mpi3mr: fix sanitise num_phys (bsc#1228754).
- CVE-2024-42158: s390/pkey: Use kfree_sensitive() to fix Coccinelle warnings (bsc#1228720).
- CVE-2024-42157: s390/pkey: Wipe sensitive data on failure (bsc#1228727).
- CVE-2024-42156: s390/pkey: Wipe copies of clear-key structures on failure (bsc#1228722).
- CVE-2024-42155: s390/pkey: Wipe copies of protected- and secure-keys (bsc#1228733).
- CVE-2024-42148: bnx2x: Fix multiple UBSAN array-index-out-of-bounds (bsc#1228487).
- CVE-2024-42145:…
- Record
SUSE-SU-2024:3383-1- Updated
- 2026-11-02
OSVSUSE-SU-2024:3408-1 No score
Security update for the Linux Kernel
The SUSE Linux Enterprise 15 SP4 kernel was updated to receive various security bugfixes.
The following security bugs were fixed:
- CVE-2024-41062: Sync sock recv cb and release (bsc#1228576).
- CVE-2024-44947: Initialize beyond-EOF page contents before setting uptodate (bsc#1229454).
- CVE-2024-43883: Do not drop references before new references are gained (bsc#1229707).
- CVE-2024-43861: Fix memory leak for not ip packets (bsc#1229500).
- CVE-2023-52489: Fix race in accessing memory_section->usage (bsc#1221326).
- CVE-2024-44938: Fix shift-out-of-bounds in dbDiscardAG (bsc#1229792).
- CVE-2024-41087: Fix double free on error (CVE-2024-41087,bsc#1228466).
- CVE-2024-43882: Fixed ToCToU between perm check and set-uid/gid usage. (bsc#1229503)
- CVE-2022-48935: Fixed an unregister flowtable hooks on netns exit (bsc#1229619)
- CVE-2022-48912: Fix use-after-free in __nf_register_net_hook() (bsc#1229641)
- CVE-2024-42271: Fixed a use after free in iucv_sock_close(). (bsc#1229400)
- CVE-2024-42232: Fixed a race between delayed_work() and ceph_monc_stop(). (bsc#1228959)
- CVE-2024-40910: Fix refcount imbalance on inbound connections (bsc#1227832).
- CVE-2024-41009: Fix overrunning reservations in ringbuf (bsc#1228020).
- CVE-2024-45003: Don't evict inode under the inode lru traversing context (bsc#1230245).
The following non-security bugs were fixed:
- Bluetooth: L2CAP: Fix deadlock (git-fixes).
- mm, kmsan: fix infinite recursion due to RCU critical section (git-fixes).
- mm: prevent derefencing NULL ptr in pfn_section_valid() (git-fixes).
- Revert 'mm: prevent derefencing NULL ptr in pfn_section_valid()' (bsc#1230413).
- Revert 'mm, kmsan: fix infinite recursion due to RCU critical section' (bsc#1230413).
- Revert 'mm/sparsemem: fix race in accessing memory_section->usage' (bsc#1230413).
- nvme_core: scan namespaces asynchronously (bsc#1224105).
- Record
SUSE-SU-2024:3408-1- Updated
- 2026-11-02
OSVSUSE-SU-2024:3483-1 No score
Security update for the Linux Kernel
The SUSE Linux Enterprise 15 SP5 kernel was updated to receive various security bugfixes.
The following security bugs were fixed:
- CVE-2024-44947: Initialize beyond-EOF page contents before setting uptodate (bsc#1229454).
- CVE-2024-36936: Touch soft lockup during memory accept (bsc#1225773).
- CVE-2022-48706: Do proper cleanup if IFCVF init fails (bsc#1225524).
- CVE-2024-43883: Do not drop references before new references are gained (bsc#1229707).
- CVE-2024-41062: Sync sock recv cb and release (bsc#1228576).
- CVE-2024-43861: Fix memory leak for not ip packets (bsc#1229500).
- CVE-2024-36270: Fix reference in patches.suse/netfilter-tproxy-bail-out-if-IP-has-been-disabled-on.patch (bsc#1226798)
- CVE-2023-52489: Fix race in accessing memory_section->usage (bsc#1221326).
- CVE-2024-43893: Check uartclk for zero to avoid divide by zero (bsc#1229759).
- CVE-2024-43821: Fix a possible null pointer dereference (bsc#1229315).
- CVE-2024-43900: Avoid use-after-free in load_firmware_cb() (bsc#1229756).
- CVE-2024-44938: Fix shift-out-of-bounds in dbDiscardAG (bsc#1229792).
- CVE-2024-44939: Fix null ptr deref in dtInsertEntry (bsc#1229820).
- CVE-2024-41087: Fix double free on error (CVE-2024-41087,bsc#1228466).
- CVE-2024-42277: Avoid NULL deref in sprd_iommu_hw_en (bsc#1229409).
- CVE-2024-43902: Add null checker before passing variables (bsc#1229767).
- CVE-2024-43904: Add null checks for 'stream' and 'plane' before dereferencing (bsc#1229768)
- CVE-2024-43880: Put back removed metod in struct objagg_ops (bsc#1229481).
- CVE-2024-43884: Add error handling to pair_device() (bsc#1229739)
- CVE-2024-43899: Fix null pointer deref in dcn20_resource.c (bsc#1229754).
- CVE-2022-48920: Get rid of warning on transaction commit when using flushoncommit (bsc#1229658).
- CVE-2023-52906: Fix warning during failed attribute validation (bsc#1229527).
- CVE-2024-43882: Fixed ToCToU between perm check and set-uid/gid usage. (bsc#1229503)
- CVE-2024-43866: Always drain health in shutdown callback (bsc#1229495).
- CVE-2024-26812: Struct virqfd kABI workaround (bsc#1222808).
- CVE-2022-48912: Fix use-after-free in __nf_register_net_hook() (bsc#1229641)
- CVE-2024-27010: Fix mirred deadlock on device recursion (bsc#1223720).
- CVE-2022-48906: Correctly set DATA_FIN timeout when number of retransmits is large (bsc#1229605)
- CVE-2024-42155: Wipe copies of protected- and secure-keys (bsc#1228733).
- CVE-2024-42156: Wipe copies of clear-key structures on failure (bsc#1228722).
- CVE-2023-52899: Add exception protection processing for vd in axi_chan_handle_err function (bsc#1229569).
- CVE-2024-42158: Use kfree_sensitive() to fix Coccinelle warnings (bsc#1228720).
- CVE-2024-26631: Fix data-race in ipv6_mc_down / mld_ifc_work (bsc#1221630).
- CVE-2024-43873: Always initialize seqpacket_allow (bsc#1229488)
- CVE-2024-40905: Fix possible race in __fib6_drop_pcpu_from() (bsc#1227761)
- CVE-2024-39489: Fix memleak in seg6_hmac_init_algo (bsc#1227623)
- CVE-2021-47106: Fix use-after-free in nft_set_catchall_destroy() (bsc#1220962)
- CVE-2021-47517: Fix panic when interrupt coaleceing is set via ethtool (bsc#1225428).
- CVE-2024-36489: Fix missing memory barrier in tls_init (bsc#1226874)
- CVE-2024-41020: Fix fcntl/close race recovery compat path (bsc#1228427).
- CVE-2024-27079: Fix NULL domain on device release (bsc#1223742).
- CVE-2024-35897: Discard table flag update with pending basechain deletion (bsc#1224510).
- CVE-2024-27403: Restore const specifier in flow_offload_route_init() (bsc#1224415).
- CVE-2024-27011: Fix memleak in map from abort path (bsc#1223803).
- CVE-2024-43819: Reject memory region operations for ucontrol VMs (bsc#1229290 git-fixes).
- CVE-2024-26668: Reject configurations that cause integer overflow (bsc#1222335).
- CVE-2024-26835: Set dormant flag on hook register failure (bsc#1222967).
- CVE-2024-26808: Handle NETDEV_UNREGISTER for inet/ingress basechain (bsc#1222634).
- CVE-2024-27016: Validate pppoe header (bsc#1223807). -…
- Record
SUSE-SU-2024:3483-1- Updated
- 2026-11-02
OSVSUSE-SU-2025:20044-1 No score
Security update for the Linux Kernel
The SUSE Linux Enterprise Micro 6.0 kernel was updated to receive various security bugfixes.
This release includes the first live patch.
The following security bugs were fixed:
- CVE-2023-52489: mm/sparsemem: fix race in accessing memory_section->usage (bsc#1221326).
- CVE-2023-52581: netfilter: nf_tables: fix memleak when more than 255 elements expired (bsc#1220877).
- CVE-2023-52859: perf: hisi: Fix use-after-free when register pmu fails (bsc#1225582).
- CVE-2023-52889: apparmor: Fix null pointer deref when receiving skb during sock creation (bsc#1229287,).
- CVE-2024-26590: erofs: fix inconsistent per-file compression format (bsc#1220252).
- CVE-2024-26631: ipv6: mcast: fix data-race in ipv6_mc_down / mld_ifc_work (bsc#1221630).
- CVE-2024-26668: netfilter: nft_limit: reject configurations that cause integer overflow (bsc#1222335).
- CVE-2024-26669: kABI fix for net/sched: flower: Fix chain template offload (bsc#1222350).
- CVE-2024-26677: blacklist.conf: Add e7870cf13d20 ("rxrpc: Fix delayed ACKs to not set the reference serial number") (bsc#1222387)
- CVE-2024-26735: ipv6: sr: fix possible use-after-free and null-ptr-deref (bsc#1222372).
- CVE-2024-26808: netfilter: nft_chain_filter: handle NETDEV_UNREGISTER for inet/ingress basechain (bsc#1222634).
- CVE-2024-26809: netfilter: nft_set_pipapo: release elements in clone only from destroy path (bsc#1222633).
- CVE-2024-26812: kABI: vfio: struct virqfd kABI workaround (bsc#1222808).
- CVE-2024-26835: netfilter: nf_tables: set dormant flag on hook register failure (bsc#1222967).
- CVE-2024-26837: net: bridge: switchdev: Skip MDB replays of deferred events on offload (bsc#1222973).
- CVE-2024-26851: netfilter: nf_conntrack_h323: Add protection for bmp length out of range (bsc#1223074)
- CVE-2024-27010: net/sched: Fix mirred deadlock on device recursion (bsc#1223720).
- CVE-2024-27011: netfilter: nf_tables: fix memleak in map from abort path (bsc#1223803).
- CVE-2024-27024: net/rds: fix WARNING in rds_conn_connect_if_down (bsc#1223777).
- CVE-2024-27079: iommu/vt-d: Fix NULL domain on device release (bsc#1223742).
- CVE-2024-27403: kabi: restore const specifier in flow_offload_route_init() (bsc#1224415).
- CVE-2024-27433: clk: mediatek: mt7622-apmixedsys: Fix an error handling path in clk_mt8135_apmixed_probe() (bsc#1224711).
- CVE-2024-27437: vfio/pci: Disable auto-enable of exclusive INTx IRQ (bsc#1222625).
- CVE-2024-35897: netfilter: nf_tables: discard table flag update with pending basechain deletion (bsc#1224510).
- CVE-2024-35939: Fixed leak pages on dma_set_decrypted() failure (bsc#1224535).
- CVE-2024-35949: btrfs: make sure that WRITTEN is set on all metadata blocks (bsc#1224700).
- CVE-2024-36286: netfilter: nfnetlink_queue: acquire rcu_read_lock() in instance_destroy_rcu() (bsc#1226801)
- CVE-2024-36489: tls: fix missing memory barrier in tls_init (bsc#1226874)
- CVE-2024-36881: mm/userfaultfd: reset ptes when close() for wr-protected ones (bsc#1225718).
- CVE-2024-36929: net: core: reject skb_copy(_expand) for fraglist GSO skbs (bsc#1225814).
- CVE-2024-36933: net: nsh: Use correct mac_offset to unwind gso skb in nsh_gso_segment() (bsc#1225832).
- CVE-2024-36979: net: bridge: mst: fix vlan use-after-free syzbot reported a suspicious rcu usage[1] in bridge's mst code. (bsc#1226604).
- CVE-2024-38662: selftests/bpf: Cover verifier checks for mutating sockmap/sockhash (bsc#1226885).
- CVE-2024-39489: ipv6: sr: fix memleak in seg6_hmac_init_algo (bsc#1227623)
- CVE-2024-39506: liquidio: adjust a NULL pointer handling path in lio_vf_rep_copy_packet (bsc#1227729).
- CVE-2024-40905: ipv6: fix possible race in __fib6_drop_pcpu_from() (bsc#1227761)
- CVE-2024-40909: bpf: Fix a potential use-after-free in bpf_link_free() (bsc#1227798).
- CVE-2024-40920: net: bridge: mst: fix suspicious rcu usage in br_mst_set_state (bsc#1227781).
- CVE-2024-40921: net: bridge: mst: pass vlan group directly to br_mst_vlan_set_state (bsc#1227784).
- CVE-2024-40938: landlock: fix d_parent…
- Record
SUSE-SU-2025:20044-1- Updated
- 2026-11-02
OSVSUSE-SU-2025:20047-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-2023-52489: mm/sparsemem: fix race in accessing memory_section->usage (bsc#1221326).
- CVE-2023-52581: netfilter: nf_tables: fix memleak when more than 255 elements expired (bsc#1220877).
- CVE-2023-52859: perf: hisi: Fix use-after-free when register pmu fails (bsc#1225582).
- CVE-2023-52889: apparmor: Fix null pointer deref when receiving skb during sock creation (bsc#1229287).
- CVE-2024-26590: erofs: fix inconsistent per-file compression format (bsc#1220252).
- CVE-2024-26631: ipv6: mcast: fix data-race in ipv6_mc_down / mld_ifc_work (bsc#1221630).
- CVE-2024-26668: netfilter: nft_limit: reject configurations that cause integer overflow (bsc#1222335).
- CVE-2024-26669: kABI fix for net/sched: flower: Fix chain template offload (bsc#1222350).
- CVE-2024-26677: Blacklist e7870cf13d20 (" Fix delayed ACKs to not set the reference serial number") (bsc#1222387)
- CVE-2024-26735: ipv6: sr: fix possible use-after-free and null-ptr-deref (bsc#1222372).
- CVE-2024-26808: netfilter: nft_chain_filter: handle NETDEV_UNREGISTER for inet/ingress basechain (bsc#1222634).
- CVE-2024-26809: netfilter: nft_set_pipapo: release elements in clone only from destroy path (bsc#1222633).
- CVE-2024-26812: kABI: vfio: struct virqfd kABI workaround (bsc#1222808).
- CVE-2024-26835: netfilter: nf_tables: set dormant flag on hook register failure (bsc#1222967).
- CVE-2024-26837: net: bridge: switchdev: race between creation of new group memberships and generation of the list of MDB events to replay (bsc#1222973).
- CVE-2024-26851: netfilter: nf_conntrack_h323: Add protection for bmp length out of range (bsc#1223074)
- CVE-2024-27010: net/sched: Fix mirred deadlock on device recursion (bsc#1223720).
- CVE-2024-27011: netfilter: nf_tables: fix memleak in map from abort path (bsc#1223803).
- CVE-2024-27024: net/rds: fix WARNING in rds_conn_connect_if_down (bsc#1223777).
- CVE-2024-27079: iommu/vt-d: Fix NULL domain on device release (bsc#1223742).
- CVE-2024-27403: kabi: restore const specifier in flow_offload_route_init() (bsc#1224415).
- CVE-2024-27433: clk: mediatek: mt7622-apmixedsys: Fix an error handling path in clk_mt8135_apmixed_probe() (bsc#1224711).
- CVE-2024-27437: vfio/pci: Disable auto-enable of exclusive INTx IRQ (bsc#1222625).
- CVE-2024-35897: netfilter: nf_tables: discard table flag update with pending basechain deletion (bsc#1224510).
- CVE-2024-35939: Fixed leak pages on dma_set_decrypted() failure (bsc#1224535).
- CVE-2024-35949: btrfs: make sure that WRITTEN is set on all metadata blocks (bsc#1224700).
- CVE-2024-36286: netfilter: nfnetlink_queue: acquire rcu_read_lock() in instance_destroy_rcu() (bsc#1226801)
- CVE-2024-36489: tls: fix missing memory barrier in tls_init (bsc#1226874)
- CVE-2024-36881: mm/userfaultfd: Fix reset ptes when close() for wr-protected (bsc#1225718).
- CVE-2024-36929: net: core: reject skb_copy(_expand) for fraglist GSO skbs (bsc#1225814).
- CVE-2024-36933: net: nsh: Use correct mac_offset to unwind gso skb in nsh_gso_segment() (bsc#1225832).
- CVE-2024-36979: net: bridge: mst: fix vlan use-after-free (bsc#1226604).
- CVE-2024-38662: selftests/bpf: Cover verifier checks for mutating sockmap/sockhash (bsc#1226885).
- CVE-2024-39489: ipv6: sr: fix memleak in seg6_hmac_init_algo (bsc#1227623)
- CVE-2024-39506: liquidio: adjust a NULL pointer handling path in lio_vf_rep_copy_packet (bsc#1227729).
- CVE-2024-40905: ipv6: fix possible race in __fib6_drop_pcpu_from() (bsc#1227761)
- CVE-2024-40909: bpf: Fix a potential use-after-free in bpf_link_free() (bsc#1227798).
- CVE-2024-40920: net: bridge: mst: fix suspicious rcu usage in br_mst_set_state (bsc#1227781).
- CVE-2024-40921: net: bridge: mst: pass vlan group directly to br_mst_vlan_set_state (bsc#1227784).
- CVE-2024-40938: landlock: fix d_parent walk (bsc#1227840).
- CVE-2024-40939: net: wwan: iosm: Fix tainted…
- Record
SUSE-SU-2025:20047-1- Updated
- 2026-11-02
OSVUSN-7020-1 No score
linux, linux-aws, linux-gcp, linux-gke, linux-ibm, linux-lowlatency, linux-lowlatency-hwe-6.8, linux-nvidia, linux-nvidia-6.8, linux-nvidia-lowlatency, linux-oem-6.8, linux-oracle vulnerabilities
Several security issues were discovered in the Linux kernel. An attacker could possibly use these to compromise the system. This update corrects flaws in the following subsystems:
- GPU drivers;
- Network drivers;
- SCSI drivers;
- F2FS file system;
- BPF subsystem;
- IPv4 networking; (CVE-2024-42160, CVE-2024-42159, CVE-2024-42154, CVE-2024-41009, CVE-2024-42228, CVE-2024-42224)
- Record
USN-7020-1- Updated
- 2026-11-02
OSVUSN-7020-2 No score
linux-azure vulnerabilities
Several security issues were discovered in the Linux kernel. An attacker could possibly use these to compromise the system. This update corrects flaws in the following subsystems:
- GPU drivers;
- Network drivers;
- SCSI drivers;
- F2FS file system;
- BPF subsystem;
- IPv4 networking; (CVE-2024-42160, CVE-2024-42159, CVE-2024-42154, CVE-2024-41009, CVE-2024-42228, CVE-2024-42224)
- Record
USN-7020-2- Updated
- 2026-11-02
OSVUSN-7020-3 No score
linux-raspi vulnerabilities
Several security issues were discovered in the Linux kernel. An attacker could possibly use these to compromise the system. This update corrects flaws in the following subsystems:
- GPU drivers;
- Network drivers;
- SCSI drivers;
- F2FS file system;
- BPF subsystem;
- IPv4 networking; (CVE-2024-42160, CVE-2024-42159, CVE-2024-42224, CVE-2024-41009, CVE-2024-42154, CVE-2024-42228)
- Record
USN-7020-3- Updated
- 2026-11-02
OSVUSN-7020-4 No score
linux-aws-6.8, linux-oracle-6.8 vulnerabilities
Several security issues were discovered in the Linux kernel. An attacker could possibly use these to compromise the system. This update corrects flaws in the following subsystems:
- GPU drivers;
- Network drivers;
- SCSI drivers;
- F2FS file system;
- BPF subsystem;
- IPv4 networking; (CVE-2024-42228, CVE-2024-42154, CVE-2024-42160, CVE-2024-42159, CVE-2024-41009, CVE-2024-42224)
- Record
USN-7020-4- Updated
- 2026-11-02
OSVUSN-7021-1 No score
linux, linux-aws, linux-aws-5.15, linux-azure, linux-azure-5.15, linux-gcp, linux-gcp-5.15, linux-gke, linux-gkeop, linux-gkeop-5.15, linux-hwe-5.15, linux-ibm, linux-intel-iotg, linux-intel-iotg-5.15, linux-kvm, linux-nvidia, linux-oracle, linux-raspi vulnerabilities
Several security issues were discovered in the Linux kernel. An attacker could possibly use these to compromise the system. This update corrects flaws in the following subsystems:
- GPU drivers;
- BTRFS file system;
- F2FS file system;
- GFS2 file system;
- BPF subsystem;
- Netfilter;
- RxRPC session sockets;
- Integrity Measurement Architecture(IMA) framework; (CVE-2024-39496, CVE-2024-41009, CVE-2024-26677, CVE-2024-42160, CVE-2024-27012, CVE-2024-42228, CVE-2024-39494, CVE-2024-38570)
- Record
USN-7021-1- Updated
- 2026-11-02
OSVUSN-7021-2 No score
linux-ibm-5.15, linux-oracle-5.15, linux-xilinx-zynqmp vulnerabilities
Several security issues were discovered in the Linux kernel. An attacker could possibly use these to compromise the system. This update corrects flaws in the following subsystems:
- GPU drivers;
- BTRFS file system;
- F2FS file system;
- GFS2 file system;
- BPF subsystem;
- Netfilter;
- RxRPC session sockets;
- Integrity Measurement Architecture(IMA) framework; (CVE-2024-27012, CVE-2024-39496, CVE-2024-26677, CVE-2024-42228, CVE-2024-38570, CVE-2024-39494, CVE-2024-42160, CVE-2024-41009)
- Record
USN-7021-2- Updated
- 2026-11-02
OSVUSN-7021-3 No score
linux-lowlatency, linux-lowlatency-hwe-5.15 vulnerabilities
Several security issues were discovered in the Linux kernel. An attacker could possibly use these to compromise the system. This update corrects flaws in the following subsystems:
- GPU drivers;
- BTRFS file system;
- F2FS file system;
- GFS2 file system;
- BPF subsystem;
- Netfilter;
- RxRPC session sockets;
- Integrity Measurement Architecture(IMA) framework; (CVE-2024-39494, CVE-2024-38570, CVE-2024-27012, CVE-2024-39496, CVE-2024-42160, CVE-2024-41009, CVE-2024-42228, CVE-2024-26677)
- Record
USN-7021-3- Updated
- 2026-11-02
OSVUSN-7021-4 No score
linux-azure-fde-5.15 vulnerabilities
Several security issues were discovered in the Linux kernel. An attacker could possibly use these to compromise the system. This update corrects flaws in the following subsystems:
- GPU drivers;
- BTRFS file system;
- F2FS file system;
- GFS2 file system;
- BPF subsystem;
- Netfilter;
- RxRPC session sockets;
- Integrity Measurement Architecture(IMA) framework; (CVE-2024-41009, CVE-2024-26677, CVE-2024-42160, CVE-2024-39494, CVE-2024-39496, CVE-2024-38570, CVE-2024-27012, CVE-2024-42228)
- Record
USN-7021-4- Updated
- 2026-11-02
OSVUSN-7021-5 No score
linux-azure-fde vulnerabilities
Several security issues were discovered in the Linux kernel. An attacker could possibly use these to compromise the system. This update corrects flaws in the following subsystems:
- GPU drivers;
- BTRFS file system;
- F2FS file system;
- GFS2 file system;
- BPF subsystem;
- Netfilter;
- RxRPC session sockets;
- Integrity Measurement Architecture(IMA) framework; (CVE-2024-27012, CVE-2024-38570, CVE-2024-42228, CVE-2024-41009, CVE-2024-39494, CVE-2024-42160, CVE-2024-39496, CVE-2024-26677)
- Record
USN-7021-5- 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 |
|---|---|---|
bpftoolAlmaLinux:9 From an advisory covering 3 CVEs |
before 7.4.0-503.15.1.el9_5 | 7.4.0-503.15.1.el9_5 |
kernelAlmaLinux:9 From an advisory covering 3 CVEs |
before 5.14.0-503.15.1.el9_5 | 5.14.0-503.15.1.el9_5 |
kernel-64kAlmaLinux:9 From an advisory covering 3 CVEs |
before 5.14.0-503.15.1.el9_5 | 5.14.0-503.15.1.el9_5 |
kernel-64k-coreAlmaLinux:9 From an advisory covering 3 CVEs |
before 5.14.0-503.15.1.el9_5 | 5.14.0-503.15.1.el9_5 |
kernel-64k-debugAlmaLinux:9 From an advisory covering 3 CVEs |
before 5.14.0-503.15.1.el9_5 | 5.14.0-503.15.1.el9_5 |
kernel-64k-debug-coreAlmaLinux:9 From an advisory covering 3 CVEs |
before 5.14.0-503.15.1.el9_5 | 5.14.0-503.15.1.el9_5 |
kernel-64k-debug-develAlmaLinux:9 From an advisory covering 3 CVEs |
before 5.14.0-503.15.1.el9_5 | 5.14.0-503.15.1.el9_5 |
kernel-64k-debug-devel-matchedAlmaLinux:9 From an advisory covering 3 CVEs |
before 5.14.0-503.15.1.el9_5 | 5.14.0-503.15.1.el9_5 |
kernel-64k-debug-modulesAlmaLinux:9 From an advisory covering 3 CVEs |
before 5.14.0-503.15.1.el9_5 | 5.14.0-503.15.1.el9_5 |
kernel-64k-debug-modules-coreAlmaLinux:9 From an advisory covering 3 CVEs |
before 5.14.0-503.15.1.el9_5 | 5.14.0-503.15.1.el9_5 |
Show 290 moreShow less
| Package | Affected | Fixed |
|---|---|---|
kernel-64k-debug-modules-extraAlmaLinux:9 From an advisory covering 3 CVEs |
before 5.14.0-503.15.1.el9_5 | 5.14.0-503.15.1.el9_5 |
kernel-64k-develAlmaLinux:9 From an advisory covering 3 CVEs |
before 5.14.0-503.15.1.el9_5 | 5.14.0-503.15.1.el9_5 |
kernel-64k-devel-matchedAlmaLinux:9 From an advisory covering 3 CVEs |
before 5.14.0-503.15.1.el9_5 | 5.14.0-503.15.1.el9_5 |
kernel-64k-modulesAlmaLinux:9 From an advisory covering 3 CVEs |
before 5.14.0-503.15.1.el9_5 | 5.14.0-503.15.1.el9_5 |
kernel-64k-modules-coreAlmaLinux:9 From an advisory covering 3 CVEs |
before 5.14.0-503.15.1.el9_5 | 5.14.0-503.15.1.el9_5 |
kernel-64k-modules-extraAlmaLinux:9 From an advisory covering 3 CVEs |
before 5.14.0-503.15.1.el9_5 | 5.14.0-503.15.1.el9_5 |
kernel-abi-stablelistsAlmaLinux:9 From an advisory covering 3 CVEs |
before 5.14.0-503.15.1.el9_5 | 5.14.0-503.15.1.el9_5 |
kernel-coreAlmaLinux:9 From an advisory covering 3 CVEs |
before 5.14.0-503.15.1.el9_5 | 5.14.0-503.15.1.el9_5 |
kernel-cross-headersAlmaLinux:9 From an advisory covering 3 CVEs |
before 5.14.0-503.15.1.el9_5 | 5.14.0-503.15.1.el9_5 |
kernel-debugAlmaLinux:9 From an advisory covering 3 CVEs |
before 5.14.0-503.15.1.el9_5 | 5.14.0-503.15.1.el9_5 |
kernel-debug-coreAlmaLinux:9 From an advisory covering 3 CVEs |
before 5.14.0-503.15.1.el9_5 | 5.14.0-503.15.1.el9_5 |
kernel-debug-develAlmaLinux:9 From an advisory covering 3 CVEs |
before 5.14.0-503.15.1.el9_5 | 5.14.0-503.15.1.el9_5 |
kernel-debug-devel-matchedAlmaLinux:9 From an advisory covering 3 CVEs |
before 5.14.0-503.15.1.el9_5 | 5.14.0-503.15.1.el9_5 |
kernel-debug-modulesAlmaLinux:9 From an advisory covering 3 CVEs |
before 5.14.0-503.15.1.el9_5 | 5.14.0-503.15.1.el9_5 |
kernel-debug-modules-coreAlmaLinux:9 From an advisory covering 3 CVEs |
before 5.14.0-503.15.1.el9_5 | 5.14.0-503.15.1.el9_5 |
kernel-debug-modules-extraAlmaLinux:9 From an advisory covering 3 CVEs |
before 5.14.0-503.15.1.el9_5 | 5.14.0-503.15.1.el9_5 |
kernel-debug-uki-virtAlmaLinux:9 From an advisory covering 3 CVEs |
before 5.14.0-503.15.1.el9_5 | 5.14.0-503.15.1.el9_5 |
kernel-develAlmaLinux:9 From an advisory covering 3 CVEs |
before 5.14.0-503.15.1.el9_5 | 5.14.0-503.15.1.el9_5 |
kernel-devel-matchedAlmaLinux:9 From an advisory covering 3 CVEs |
before 5.14.0-503.15.1.el9_5 | 5.14.0-503.15.1.el9_5 |
kernel-docAlmaLinux:9 From an advisory covering 3 CVEs |
before 5.14.0-503.15.1.el9_5 | 5.14.0-503.15.1.el9_5 |
kernel-headersAlmaLinux:9 From an advisory covering 3 CVEs |
before 5.14.0-503.15.1.el9_5 | 5.14.0-503.15.1.el9_5 |
kernel-modulesAlmaLinux:9 From an advisory covering 3 CVEs |
before 5.14.0-503.15.1.el9_5 | 5.14.0-503.15.1.el9_5 |
kernel-modules-coreAlmaLinux:9 From an advisory covering 3 CVEs |
before 5.14.0-503.15.1.el9_5 | 5.14.0-503.15.1.el9_5 |
kernel-modules-extraAlmaLinux:9 From an advisory covering 3 CVEs |
before 5.14.0-503.15.1.el9_5 | 5.14.0-503.15.1.el9_5 |
kernel-rtAlmaLinux:9 From an advisory covering 3 CVEs |
before 5.14.0-503.15.1.el9_5 | 5.14.0-503.15.1.el9_5 |
kernel-rt-coreAlmaLinux:9 From an advisory covering 3 CVEs |
before 5.14.0-503.15.1.el9_5 | 5.14.0-503.15.1.el9_5 |
kernel-rt-debugAlmaLinux:9 From an advisory covering 3 CVEs |
before 5.14.0-503.15.1.el9_5 | 5.14.0-503.15.1.el9_5 |
kernel-rt-debug-coreAlmaLinux:9 From an advisory covering 3 CVEs |
before 5.14.0-503.15.1.el9_5 | 5.14.0-503.15.1.el9_5 |
kernel-rt-debug-develAlmaLinux:9 From an advisory covering 3 CVEs |
before 5.14.0-503.15.1.el9_5 | 5.14.0-503.15.1.el9_5 |
kernel-rt-debug-modulesAlmaLinux:9 From an advisory covering 3 CVEs |
before 5.14.0-503.15.1.el9_5 | 5.14.0-503.15.1.el9_5 |
kernel-rt-debug-modules-coreAlmaLinux:9 From an advisory covering 3 CVEs |
before 5.14.0-503.15.1.el9_5 | 5.14.0-503.15.1.el9_5 |
kernel-rt-debug-modules-extraAlmaLinux:9 From an advisory covering 3 CVEs |
before 5.14.0-503.15.1.el9_5 | 5.14.0-503.15.1.el9_5 |
kernel-rt-develAlmaLinux:9 From an advisory covering 3 CVEs |
before 5.14.0-503.15.1.el9_5 | 5.14.0-503.15.1.el9_5 |
kernel-rt-modulesAlmaLinux:9 From an advisory covering 3 CVEs |
before 5.14.0-503.15.1.el9_5 | 5.14.0-503.15.1.el9_5 |
kernel-rt-modules-coreAlmaLinux:9 From an advisory covering 3 CVEs |
before 5.14.0-503.15.1.el9_5 | 5.14.0-503.15.1.el9_5 |
kernel-rt-modules-extraAlmaLinux:9 From an advisory covering 3 CVEs |
before 5.14.0-503.15.1.el9_5 | 5.14.0-503.15.1.el9_5 |
kernel-toolsAlmaLinux:9 From an advisory covering 3 CVEs |
before 5.14.0-503.15.1.el9_5 | 5.14.0-503.15.1.el9_5 |
kernel-tools-libsAlmaLinux:9 From an advisory covering 3 CVEs |
before 5.14.0-503.15.1.el9_5 | 5.14.0-503.15.1.el9_5 |
kernelAzure Linux:3 |
before 6.6.43.1-7 | 6.6.43.1-7 |
kernelAzure Linux:2 |
before 5.15.164.1-1 | 5.15.164.1-1 |
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 |
bpftoolTuxCare:AlmaLinux:9.2 From an advisory covering 305 CVEs |
before 7.0.0-284.1101.el9_2.tuxcare.11.els8 | 7.0.0-284.1101.el9_2.tuxcare.11.els8 |
kernelTuxCare:AlmaLinux:9.2 From an advisory covering 305 CVEs |
before 5.14.0-284.1101.el9_2.tuxcare.11.els8 | 5.14.0-284.1101.el9_2.tuxcare.11.els8 |
kernel-64kTuxCare:AlmaLinux:9.2 From an advisory covering 305 CVEs |
before 5.14.0-284.1101.el9_2.tuxcare.11.els8 | 5.14.0-284.1101.el9_2.tuxcare.11.els8 |
kernel-64k-coreTuxCare:AlmaLinux:9.2 From an advisory covering 305 CVEs |
before 5.14.0-284.1101.el9_2.tuxcare.11.els8 | 5.14.0-284.1101.el9_2.tuxcare.11.els8 |
kernel-64k-debugTuxCare:AlmaLinux:9.2 From an advisory covering 305 CVEs |
before 5.14.0-284.1101.el9_2.tuxcare.11.els8 | 5.14.0-284.1101.el9_2.tuxcare.11.els8 |
kernel-64k-debug-coreTuxCare:AlmaLinux:9.2 From an advisory covering 305 CVEs |
before 5.14.0-284.1101.el9_2.tuxcare.11.els8 | 5.14.0-284.1101.el9_2.tuxcare.11.els8 |
kernel-64k-debug-develTuxCare:AlmaLinux:9.2 From an advisory covering 305 CVEs |
before 5.14.0-284.1101.el9_2.tuxcare.11.els8 | 5.14.0-284.1101.el9_2.tuxcare.11.els8 |
kernel-64k-debug-devel-matchedTuxCare:AlmaLinux:9.2 From an advisory covering 305 CVEs |
before 5.14.0-284.1101.el9_2.tuxcare.11.els8 | 5.14.0-284.1101.el9_2.tuxcare.11.els8 |
kernel-64k-debug-modulesTuxCare:AlmaLinux:9.2 From an advisory covering 305 CVEs |
before 5.14.0-284.1101.el9_2.tuxcare.11.els8 | 5.14.0-284.1101.el9_2.tuxcare.11.els8 |
kernel-64k-debug-modules-coreTuxCare:AlmaLinux:9.2 From an advisory covering 305 CVEs |
before 5.14.0-284.1101.el9_2.tuxcare.11.els8 | 5.14.0-284.1101.el9_2.tuxcare.11.els8 |
kernel-64k-debug-modules-extraTuxCare:AlmaLinux:9.2 From an advisory covering 305 CVEs |
before 5.14.0-284.1101.el9_2.tuxcare.11.els8 | 5.14.0-284.1101.el9_2.tuxcare.11.els8 |
kernel-64k-debug-modules-internalTuxCare:AlmaLinux:9.2 From an advisory covering 305 CVEs |
before 5.14.0-284.1101.el9_2.tuxcare.11.els8 | 5.14.0-284.1101.el9_2.tuxcare.11.els8 |
kernel-64k-debug-modules-partnerTuxCare:AlmaLinux:9.2 From an advisory covering 305 CVEs |
before 5.14.0-284.1101.el9_2.tuxcare.11.els8 | 5.14.0-284.1101.el9_2.tuxcare.11.els8 |
kernel-64k-develTuxCare:AlmaLinux:9.2 From an advisory covering 305 CVEs |
before 5.14.0-284.1101.el9_2.tuxcare.11.els8 | 5.14.0-284.1101.el9_2.tuxcare.11.els8 |
kernel-64k-devel-matchedTuxCare:AlmaLinux:9.2 From an advisory covering 305 CVEs |
before 5.14.0-284.1101.el9_2.tuxcare.11.els8 | 5.14.0-284.1101.el9_2.tuxcare.11.els8 |
kernel-64k-modulesTuxCare:AlmaLinux:9.2 From an advisory covering 305 CVEs |
before 5.14.0-284.1101.el9_2.tuxcare.11.els8 | 5.14.0-284.1101.el9_2.tuxcare.11.els8 |
kernel-64k-modules-coreTuxCare:AlmaLinux:9.2 From an advisory covering 305 CVEs |
before 5.14.0-284.1101.el9_2.tuxcare.11.els8 | 5.14.0-284.1101.el9_2.tuxcare.11.els8 |
kernel-64k-modules-extraTuxCare:AlmaLinux:9.2 From an advisory covering 305 CVEs |
before 5.14.0-284.1101.el9_2.tuxcare.11.els8 | 5.14.0-284.1101.el9_2.tuxcare.11.els8 |
kernel-64k-modules-internalTuxCare:AlmaLinux:9.2 From an advisory covering 305 CVEs |
before 5.14.0-284.1101.el9_2.tuxcare.11.els8 | 5.14.0-284.1101.el9_2.tuxcare.11.els8 |
kernel-64k-modules-partnerTuxCare:AlmaLinux:9.2 From an advisory covering 305 CVEs |
before 5.14.0-284.1101.el9_2.tuxcare.11.els8 | 5.14.0-284.1101.el9_2.tuxcare.11.els8 |
kernel-abi-stablelistsTuxCare:AlmaLinux:9.2 From an advisory covering 305 CVEs |
before 5.14.0-284.1101.el9_2.tuxcare.11.els8 | 5.14.0-284.1101.el9_2.tuxcare.11.els8 |
kernel-coreTuxCare:AlmaLinux:9.2 From an advisory covering 305 CVEs |
before 5.14.0-284.1101.el9_2.tuxcare.11.els8 | 5.14.0-284.1101.el9_2.tuxcare.11.els8 |
kernel-cross-headersTuxCare:AlmaLinux:9.2 From an advisory covering 305 CVEs |
before 5.14.0-284.1101.el9_2.tuxcare.11.els8 | 5.14.0-284.1101.el9_2.tuxcare.11.els8 |
kernel-debugTuxCare:AlmaLinux:9.2 From an advisory covering 305 CVEs |
before 5.14.0-284.1101.el9_2.tuxcare.11.els8 | 5.14.0-284.1101.el9_2.tuxcare.11.els8 |
kernel-debug-coreTuxCare:AlmaLinux:9.2 From an advisory covering 305 CVEs |
before 5.14.0-284.1101.el9_2.tuxcare.11.els8 | 5.14.0-284.1101.el9_2.tuxcare.11.els8 |
kernel-debug-develTuxCare:AlmaLinux:9.2 From an advisory covering 305 CVEs |
before 5.14.0-284.1101.el9_2.tuxcare.11.els8 | 5.14.0-284.1101.el9_2.tuxcare.11.els8 |
kernel-debug-devel-matchedTuxCare:AlmaLinux:9.2 From an advisory covering 305 CVEs |
before 5.14.0-284.1101.el9_2.tuxcare.11.els8 | 5.14.0-284.1101.el9_2.tuxcare.11.els8 |
kernel-debug-modulesTuxCare:AlmaLinux:9.2 From an advisory covering 305 CVEs |
before 5.14.0-284.1101.el9_2.tuxcare.11.els8 | 5.14.0-284.1101.el9_2.tuxcare.11.els8 |
kernel-debug-modules-coreTuxCare:AlmaLinux:9.2 From an advisory covering 305 CVEs |
before 5.14.0-284.1101.el9_2.tuxcare.11.els8 | 5.14.0-284.1101.el9_2.tuxcare.11.els8 |
kernel-debug-modules-extraTuxCare:AlmaLinux:9.2 From an advisory covering 305 CVEs |
before 5.14.0-284.1101.el9_2.tuxcare.11.els8 | 5.14.0-284.1101.el9_2.tuxcare.11.els8 |
kernel-debug-modules-internalTuxCare:AlmaLinux:9.2 From an advisory covering 305 CVEs |
before 5.14.0-284.1101.el9_2.tuxcare.11.els8 | 5.14.0-284.1101.el9_2.tuxcare.11.els8 |
kernel-debug-modules-partnerTuxCare:AlmaLinux:9.2 From an advisory covering 305 CVEs |
before 5.14.0-284.1101.el9_2.tuxcare.11.els8 | 5.14.0-284.1101.el9_2.tuxcare.11.els8 |
kernel-debug-uki-virtTuxCare:AlmaLinux:9.2 From an advisory covering 305 CVEs |
before 5.14.0-284.1101.el9_2.tuxcare.11.els8 | 5.14.0-284.1101.el9_2.tuxcare.11.els8 |
kernel-develTuxCare:AlmaLinux:9.2 From an advisory covering 305 CVEs |
before 5.14.0-284.1101.el9_2.tuxcare.11.els8 | 5.14.0-284.1101.el9_2.tuxcare.11.els8 |
kernel-devel-matchedTuxCare:AlmaLinux:9.2 From an advisory covering 305 CVEs |
before 5.14.0-284.1101.el9_2.tuxcare.11.els8 | 5.14.0-284.1101.el9_2.tuxcare.11.els8 |
kernel-docTuxCare:AlmaLinux:9.2 From an advisory covering 305 CVEs |
before 5.14.0-284.1101.el9_2.tuxcare.11.els8 | 5.14.0-284.1101.el9_2.tuxcare.11.els8 |
kernel-headersTuxCare:AlmaLinux:9.2 From an advisory covering 305 CVEs |
before 5.14.0-284.1101.el9_2.tuxcare.11.els8 | 5.14.0-284.1101.el9_2.tuxcare.11.els8 |
kernel-ipaclones-internalTuxCare:AlmaLinux:9.2 From an advisory covering 305 CVEs |
before 5.14.0-284.1101.el9_2.tuxcare.11.els8 | 5.14.0-284.1101.el9_2.tuxcare.11.els8 |
kernel-modulesTuxCare:AlmaLinux:9.2 From an advisory covering 305 CVEs |
before 5.14.0-284.1101.el9_2.tuxcare.11.els8 | 5.14.0-284.1101.el9_2.tuxcare.11.els8 |
kernel-modules-coreTuxCare:AlmaLinux:9.2 From an advisory covering 305 CVEs |
before 5.14.0-284.1101.el9_2.tuxcare.11.els8 | 5.14.0-284.1101.el9_2.tuxcare.11.els8 |
kernel-modules-extraTuxCare:AlmaLinux:9.2 From an advisory covering 305 CVEs |
before 5.14.0-284.1101.el9_2.tuxcare.11.els8 | 5.14.0-284.1101.el9_2.tuxcare.11.els8 |
kernel-modules-internalTuxCare:AlmaLinux:9.2 From an advisory covering 305 CVEs |
before 5.14.0-284.1101.el9_2.tuxcare.11.els8 | 5.14.0-284.1101.el9_2.tuxcare.11.els8 |
kernel-modules-partnerTuxCare:AlmaLinux:9.2 From an advisory covering 305 CVEs |
before 5.14.0-284.1101.el9_2.tuxcare.11.els8 | 5.14.0-284.1101.el9_2.tuxcare.11.els8 |
kernel-selftests-internalTuxCare:AlmaLinux:9.2 From an advisory covering 305 CVEs |
before 5.14.0-284.1101.el9_2.tuxcare.11.els8 | 5.14.0-284.1101.el9_2.tuxcare.11.els8 |
kernel-toolsTuxCare:AlmaLinux:9.2 From an advisory covering 305 CVEs |
before 5.14.0-284.1101.el9_2.tuxcare.11.els8 | 5.14.0-284.1101.el9_2.tuxcare.11.els8 |
kernel-tools-libsTuxCare:AlmaLinux:9.2 From an advisory covering 305 CVEs |
before 5.14.0-284.1101.el9_2.tuxcare.11.els8 | 5.14.0-284.1101.el9_2.tuxcare.11.els8 |
kernel-tools-libs-develTuxCare:AlmaLinux:9.2 From an advisory covering 305 CVEs |
before 5.14.0-284.1101.el9_2.tuxcare.11.els8 | 5.14.0-284.1101.el9_2.tuxcare.11.els8 |
kernel-uki-virtTuxCare:AlmaLinux:9.2 From an advisory covering 305 CVEs |
before 5.14.0-284.1101.el9_2.tuxcare.11.els8 | 5.14.0-284.1101.el9_2.tuxcare.11.els8 |
KernelLinux |
5.8.0 up to 5.10.223, 5.11.0 up to 5.15.164, 5.16.0 up to 6.1.97, 6.2.0 up to 6.6.37, 6.7.0 up to 6.9.8 | 5.10.2235.15.1646.1.976.6.376.9.8 |
linuxDebian:12 |
before 6.1.98-1, plus listed versions 6.1.27-16.1.37-16.1.38-16.1.38-26.1.38-2~bpo11+1 Show 19 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-16.1.94-1~bpo11+1 |
6.1.98-1 |
linuxDebian:13 |
before 6.9.8-1 | 6.9.8-1 |
linuxDebian:14 |
before 6.9.8-1 | 6.9.8-1 |
linux-6.1Debian:11 From an advisory covering 838 CVEs |
before 6.1.119-1~deb11u1, plus listed versions 6.1.106-3~deb11u16.1.106-3~deb11u26.1.106-3~deb11u36.1.112-1~deb11u1 |
6.1.119-1~deb11u1 |
linuxDebian:11 From an advisory covering 60 CVEs |
before 5.10.223-1, plus listed versions 5.10.103-15.10.103-1~bpo10+15.10.106-15.10.113-15.10.120-1 Show 37 moreShow less5.10.120-1~bpo10+15.10.127-15.10.127-25.10.127-2~bpo10+15.10.136-15.10.140-15.10.148-15.10.149-15.10.149-25.10.158-15.10.158-25.10.162-15.10.178-15.10.178-25.10.178-35.10.179-15.10.179-25.10.179-35.10.179-45.10.179-55.10.191-15.10.197-15.10.205-15.10.205-25.10.209-15.10.209-25.10.216-15.10.218-15.10.221-15.10.46-45.10.46-55.10.70-15.10.70-1~bpo10+15.10.84-15.10.92-15.10.92-1~bpo10+15.10.92-2 |
5.10.223-1 |
kernelopenEuler:22.03-LTS-SP3 From an advisory covering 36 CVEs |
before 5.10.0-220.0.0.123.oe2203sp3 | 5.10.0-220.0.0.123.oe2203sp3 |
kernelopenEuler:22.03-LTS-SP1 From an advisory covering 35 CVEs |
before 5.10.0-136.86.0.167.oe2203sp1 | 5.10.0-136.86.0.167.oe2203sp1 |
kernelopenEuler:24.03-LTS From an advisory covering 42 CVEs |
before 6.6.0-35.0.0.43.oe2403 | 6.6.0-35.0.0.43.oe2403 |
bpftoolRed Hat:rhel_eus:8.8::baseos From an advisory covering 22 CVEs |
before 0:4.18.0-477.81.1.el8_8 | 0:4.18.0-477.81.1.el8_8 |
bpftool-debuginfoRed Hat:rhel_eus:8.8::baseos From an advisory covering 22 CVEs |
before 0:4.18.0-477.81.1.el8_8 | 0:4.18.0-477.81.1.el8_8 |
kernelRed Hat:rhel_eus:8.8::baseos From an advisory covering 22 CVEs |
before 0:4.18.0-477.81.1.el8_8 | 0:4.18.0-477.81.1.el8_8 |
kernel-abi-stablelistsRed Hat:rhel_eus:8.8::baseos From an advisory covering 22 CVEs |
before 0:4.18.0-477.81.1.el8_8 | 0:4.18.0-477.81.1.el8_8 |
kernel-coreRed Hat:rhel_eus:8.8::baseos From an advisory covering 22 CVEs |
before 0:4.18.0-477.81.1.el8_8 | 0:4.18.0-477.81.1.el8_8 |
kernel-debugRed Hat:rhel_eus:8.8::baseos From an advisory covering 22 CVEs |
before 0:4.18.0-477.81.1.el8_8 | 0:4.18.0-477.81.1.el8_8 |
kernel-debug-coreRed Hat:rhel_eus:8.8::baseos From an advisory covering 22 CVEs |
before 0:4.18.0-477.81.1.el8_8 | 0:4.18.0-477.81.1.el8_8 |
kernel-debug-debuginfoRed Hat:rhel_eus:8.8::baseos From an advisory covering 22 CVEs |
before 0:4.18.0-477.81.1.el8_8 | 0:4.18.0-477.81.1.el8_8 |
kernel-debug-develRed Hat:rhel_eus:8.8::baseos From an advisory covering 22 CVEs |
before 0:4.18.0-477.81.1.el8_8 | 0:4.18.0-477.81.1.el8_8 |
kernel-debug-modulesRed Hat:rhel_eus:8.8::baseos From an advisory covering 22 CVEs |
before 0:4.18.0-477.81.1.el8_8 | 0:4.18.0-477.81.1.el8_8 |
kernel-debug-modules-extraRed Hat:rhel_eus:8.8::baseos From an advisory covering 22 CVEs |
before 0:4.18.0-477.81.1.el8_8 | 0:4.18.0-477.81.1.el8_8 |
kernel-debuginfoRed Hat:rhel_eus:8.8::baseos From an advisory covering 22 CVEs |
before 0:4.18.0-477.81.1.el8_8 | 0:4.18.0-477.81.1.el8_8 |
kernel-debuginfo-common-aarch64Red Hat:rhel_eus:8.8::baseos From an advisory covering 22 CVEs |
before 0:4.18.0-477.81.1.el8_8 | 0:4.18.0-477.81.1.el8_8 |
kernel-debuginfo-common-ppc64leRed Hat:rhel_eus:8.8::baseos From an advisory covering 22 CVEs |
before 0:4.18.0-477.81.1.el8_8 | 0:4.18.0-477.81.1.el8_8 |
kernel-debuginfo-common-s390xRed Hat:rhel_eus:8.8::baseos From an advisory covering 22 CVEs |
before 0:4.18.0-477.81.1.el8_8 | 0:4.18.0-477.81.1.el8_8 |
kernel-debuginfo-common-x86_64Red Hat:rhel_eus:8.8::baseos From an advisory covering 22 CVEs |
before 0:4.18.0-477.81.1.el8_8 | 0:4.18.0-477.81.1.el8_8 |
kernel-develRed Hat:rhel_eus:8.8::baseos From an advisory covering 22 CVEs |
before 0:4.18.0-477.81.1.el8_8 | 0:4.18.0-477.81.1.el8_8 |
kernel-docRed Hat:rhel_eus:8.8::baseos From an advisory covering 22 CVEs |
before 0:4.18.0-477.81.1.el8_8 | 0:4.18.0-477.81.1.el8_8 |
kernel-modulesRed Hat:rhel_eus:8.8::baseos From an advisory covering 22 CVEs |
before 0:4.18.0-477.81.1.el8_8 | 0:4.18.0-477.81.1.el8_8 |
kernel-modules-extraRed Hat:rhel_eus:8.8::baseos From an advisory covering 22 CVEs |
before 0:4.18.0-477.81.1.el8_8 | 0:4.18.0-477.81.1.el8_8 |
kernel-toolsRed Hat:rhel_eus:8.8::baseos From an advisory covering 22 CVEs |
before 0:4.18.0-477.81.1.el8_8 | 0:4.18.0-477.81.1.el8_8 |
kernel-tools-debuginfoRed Hat:rhel_eus:8.8::baseos From an advisory covering 22 CVEs |
before 0:4.18.0-477.81.1.el8_8 | 0:4.18.0-477.81.1.el8_8 |
kernel-tools-libsRed Hat:rhel_eus:8.8::baseos From an advisory covering 22 CVEs |
before 0:4.18.0-477.81.1.el8_8 | 0:4.18.0-477.81.1.el8_8 |
kernel-zfcpdumpRed Hat:rhel_eus:8.8::baseos From an advisory covering 22 CVEs |
before 0:4.18.0-477.81.1.el8_8 | 0:4.18.0-477.81.1.el8_8 |
kernel-zfcpdump-coreRed Hat:rhel_eus:8.8::baseos From an advisory covering 22 CVEs |
before 0:4.18.0-477.81.1.el8_8 | 0:4.18.0-477.81.1.el8_8 |
kernel-zfcpdump-debuginfoRed Hat:rhel_eus:8.8::baseos From an advisory covering 22 CVEs |
before 0:4.18.0-477.81.1.el8_8 | 0:4.18.0-477.81.1.el8_8 |
kernel-zfcpdump-develRed Hat:rhel_eus:8.8::baseos From an advisory covering 22 CVEs |
before 0:4.18.0-477.81.1.el8_8 | 0:4.18.0-477.81.1.el8_8 |
kernel-zfcpdump-modulesRed Hat:rhel_eus:8.8::baseos From an advisory covering 22 CVEs |
before 0:4.18.0-477.81.1.el8_8 | 0:4.18.0-477.81.1.el8_8 |
kernel-zfcpdump-modules-extraRed Hat:rhel_eus:8.8::baseos From an advisory covering 22 CVEs |
before 0:4.18.0-477.81.1.el8_8 | 0:4.18.0-477.81.1.el8_8 |
perfRed Hat:rhel_eus:8.8::baseos From an advisory covering 22 CVEs |
before 0:4.18.0-477.81.1.el8_8 | 0:4.18.0-477.81.1.el8_8 |
perf-debuginfoRed Hat:rhel_eus:8.8::baseos From an advisory covering 22 CVEs |
before 0:4.18.0-477.81.1.el8_8 | 0:4.18.0-477.81.1.el8_8 |
python3-perfRed Hat:rhel_eus:8.8::baseos From an advisory covering 22 CVEs |
before 0:4.18.0-477.81.1.el8_8 | 0:4.18.0-477.81.1.el8_8 |
python3-perf-debuginfoRed Hat:rhel_eus:8.8::baseos From an advisory covering 22 CVEs |
before 0:4.18.0-477.81.1.el8_8 | 0:4.18.0-477.81.1.el8_8 |
bpftool-debuginfoRed Hat:rhel_eus:8.8::crb From an advisory covering 22 CVEs |
before 0:4.18.0-477.81.1.el8_8 | 0:4.18.0-477.81.1.el8_8 |
kernel-debug-debuginfoRed Hat:rhel_eus:8.8::crb From an advisory covering 22 CVEs |
before 0:4.18.0-477.81.1.el8_8 | 0:4.18.0-477.81.1.el8_8 |
kernel-debuginfoRed Hat:rhel_eus:8.8::crb From an advisory covering 22 CVEs |
before 0:4.18.0-477.81.1.el8_8 | 0:4.18.0-477.81.1.el8_8 |
kernel-debuginfo-common-aarch64Red Hat:rhel_eus:8.8::crb From an advisory covering 22 CVEs |
before 0:4.18.0-477.81.1.el8_8 | 0:4.18.0-477.81.1.el8_8 |
kernel-debuginfo-common-ppc64leRed Hat:rhel_eus:8.8::crb From an advisory covering 22 CVEs |
before 0:4.18.0-477.81.1.el8_8 | 0:4.18.0-477.81.1.el8_8 |
kernel-debuginfo-common-x86_64Red Hat:rhel_eus:8.8::crb From an advisory covering 22 CVEs |
before 0:4.18.0-477.81.1.el8_8 | 0:4.18.0-477.81.1.el8_8 |
kernel-tools-debuginfoRed Hat:rhel_eus:8.8::crb From an advisory covering 22 CVEs |
before 0:4.18.0-477.81.1.el8_8 | 0:4.18.0-477.81.1.el8_8 |
kernel-tools-libs-develRed Hat:rhel_eus:8.8::crb From an advisory covering 22 CVEs |
before 0:4.18.0-477.81.1.el8_8 | 0:4.18.0-477.81.1.el8_8 |
perf-debuginfoRed Hat:rhel_eus:8.8::crb From an advisory covering 22 CVEs |
before 0:4.18.0-477.81.1.el8_8 | 0:4.18.0-477.81.1.el8_8 |
python3-perf-debuginfoRed Hat:rhel_eus:8.8::crb From an advisory covering 22 CVEs |
before 0:4.18.0-477.81.1.el8_8 | 0:4.18.0-477.81.1.el8_8 |
bpftool-debuginfoRed Hat:enterprise_linux:9::appstream From an advisory covering 4 CVEs |
before 0:7.4.0-503.15.1.el9_5 | 0:7.4.0-503.15.1.el9_5 |
kernel-64k-debug-debuginfoRed Hat:enterprise_linux:9::appstream From an advisory covering 4 CVEs |
before 0:5.14.0-503.15.1.el9_5 | 0:5.14.0-503.15.1.el9_5 |
kernel-64k-debug-develRed Hat:enterprise_linux:9::appstream From an advisory covering 4 CVEs |
before 0:5.14.0-503.15.1.el9_5 | 0:5.14.0-503.15.1.el9_5 |
kernel-64k-debug-devel-matchedRed Hat:enterprise_linux:9::appstream From an advisory covering 4 CVEs |
before 0:5.14.0-503.15.1.el9_5 | 0:5.14.0-503.15.1.el9_5 |
kernelRocky Linux:8 From an advisory covering 42 CVEs |
before 0:4.18.0-553.27.1.el8_10 | 0:4.18.0-553.27.1.el8_10 |
kernel-rtRocky Linux:8 From an advisory covering 42 CVEs |
before 0:4.18.0-553.27.1.rt7.368.el8_10 | 0:4.18.0-553.27.1.rt7.368.el8_10 |
kernel-rtSUSE:Linux Enterprise Micro 5.5 From an advisory covering 310 CVEs |
before 5.14.21-150500.13.64.1 | 5.14.21-150500.13.64.1 |
kernel-source-rtSUSE:Linux Enterprise Micro 5.5 From an advisory covering 310 CVEs |
before 5.14.21-150500.13.64.1 | 5.14.21-150500.13.64.1 |
kernel-livepatch-SLE15-SP5-RT_Update_18SUSE:Linux Enterprise Live Patching 15 SP5 From an advisory covering 310 CVEs |
before 1-150500.11.3.1 | 1-150500.11.3.1 |
kernel-rtSUSE:Real Time Module 15 SP5 From an advisory covering 310 CVEs |
before 5.14.21-150500.13.64.1 | 5.14.21-150500.13.64.1 |
kernel-rt_debugSUSE:Real Time Module 15 SP5 From an advisory covering 310 CVEs |
before 5.14.21-150500.13.64.1 | 5.14.21-150500.13.64.1 |
kernel-source-rtSUSE:Real Time Module 15 SP5 From an advisory covering 310 CVEs |
before 5.14.21-150500.13.64.1 | 5.14.21-150500.13.64.1 |
kernel-syms-rtSUSE:Real Time Module 15 SP5 From an advisory covering 310 CVEs |
before 5.14.21-150500.13.64.1 | 5.14.21-150500.13.64.1 |
kernel-rtopenSUSE:Leap Micro 5.5 From an advisory covering 310 CVEs |
before 5.14.21-150500.13.64.1 | 5.14.21-150500.13.64.1 |
kernel-rtopenSUSE:Leap 15.5 From an advisory covering 310 CVEs |
before 5.14.21-150500.13.64.1 | 5.14.21-150500.13.64.1 |
kernel-rt_debugopenSUSE:Leap 15.5 From an advisory covering 310 CVEs |
before 5.14.21-150500.13.64.1 | 5.14.21-150500.13.64.1 |
kernel-source-rtopenSUSE:Leap 15.5 From an advisory covering 310 CVEs |
before 5.14.21-150500.13.64.1 | 5.14.21-150500.13.64.1 |
kernel-syms-rtopenSUSE:Leap 15.5 From an advisory covering 310 CVEs |
before 5.14.21-150500.13.64.1 | 5.14.21-150500.13.64.1 |
kernel-defaultSUSE:Linux Enterprise Micro 5.5 From an advisory covering 531 CVEs |
before 5.14.21-150500.55.73.1 | 5.14.21-150500.55.73.1 |
kernel-default-baseSUSE:Linux Enterprise Micro 5.5 From an advisory covering 531 CVEs |
before 5.14.21-150500.55.73.1.150500.6.33.8 | 5.14.21-150500.55.73.1.150500.6.33.8 |
kernel-64kbSUSE:Linux Enterprise Module for Basesystem 15 SP5 From an advisory covering 531 CVEs |
before 5.14.21-150500.55.73.1 | 5.14.21-150500.55.73.1 |
kernel-defaultSUSE:Linux Enterprise Module for Basesystem 15 SP5 From an advisory covering 531 CVEs |
before 5.14.21-150500.55.73.1 | 5.14.21-150500.55.73.1 |
kernel-default-baseSUSE:Linux Enterprise Module for Basesystem 15 SP5 From an advisory covering 531 CVEs |
before 5.14.21-150500.55.73.1.150500.6.33.8 | 5.14.21-150500.55.73.1.150500.6.33.8 |
kernel-sourceSUSE:Linux Enterprise Module for Basesystem 15 SP5 From an advisory covering 531 CVEs |
before 5.14.21-150500.55.73.1 | 5.14.21-150500.55.73.1 |
kernel-zfcpdumpSUSE:Linux Enterprise Module for Basesystem 15 SP5 From an advisory covering 531 CVEs |
before 5.14.21-150500.55.73.1 | 5.14.21-150500.55.73.1 |
kernel-docsSUSE:Linux Enterprise Module for Development Tools 15 SP5 From an advisory covering 531 CVEs |
before 5.14.21-150500.55.73.2 | 5.14.21-150500.55.73.2 |
kernel-obs-buildSUSE:Linux Enterprise Module for Development Tools 15 SP5 From an advisory covering 531 CVEs |
before 5.14.21-150500.55.73.1 | 5.14.21-150500.55.73.1 |
kernel-sourceSUSE:Linux Enterprise Module for Development Tools 15 SP5 From an advisory covering 531 CVEs |
before 5.14.21-150500.55.73.1 | 5.14.21-150500.55.73.1 |
kernel-symsSUSE:Linux Enterprise Module for Development Tools 15 SP5 From an advisory covering 531 CVEs |
before 5.14.21-150500.55.73.1 | 5.14.21-150500.55.73.1 |
kernel-defaultSUSE:Linux Enterprise Module for Legacy 15 SP5 From an advisory covering 531 CVEs |
before 5.14.21-150500.55.73.1 | 5.14.21-150500.55.73.1 |
kernel-defaultSUSE:Linux Enterprise Live Patching 15 SP5 From an advisory covering 531 CVEs |
before 5.14.21-150500.55.73.1 | 5.14.21-150500.55.73.1 |
kernel-livepatch-SLE15-SP5_Update_17SUSE:Linux Enterprise Live Patching 15 SP5 From an advisory covering 531 CVEs |
before 1-150500.11.3.1 | 1-150500.11.3.1 |
kernel-defaultSUSE:Linux Enterprise High Availability Extension 15 SP5 From an advisory covering 531 CVEs |
before 5.14.21-150500.55.73.1 | 5.14.21-150500.55.73.1 |
kernel-defaultSUSE:Linux Enterprise Workstation Extension 15 SP5 From an advisory covering 531 CVEs |
before 5.14.21-150500.55.73.1 | 5.14.21-150500.55.73.1 |
kernel-defaultopenSUSE:Leap Micro 5.5 From an advisory covering 531 CVEs |
before 5.14.21-150500.55.73.1 | 5.14.21-150500.55.73.1 |
kernel-default-baseopenSUSE:Leap Micro 5.5 From an advisory covering 531 CVEs |
before 5.14.21-150500.55.73.1.150500.6.33.8 | 5.14.21-150500.55.73.1.150500.6.33.8 |
dtb-aarch64openSUSE:Leap 15.5 From an advisory covering 531 CVEs |
before 5.14.21-150500.55.73.1 | 5.14.21-150500.55.73.1 |
kernel-64kbopenSUSE:Leap 15.5 From an advisory covering 531 CVEs |
before 5.14.21-150500.55.73.1 | 5.14.21-150500.55.73.1 |
kernel-debugopenSUSE:Leap 15.5 From an advisory covering 531 CVEs |
before 5.14.21-150500.55.73.1 | 5.14.21-150500.55.73.1 |
kernel-defaultopenSUSE:Leap 15.5 From an advisory covering 531 CVEs |
before 5.14.21-150500.55.73.1 | 5.14.21-150500.55.73.1 |
kernel-default-baseopenSUSE:Leap 15.5 From an advisory covering 531 CVEs |
before 5.14.21-150500.55.73.1.150500.6.33.8 | 5.14.21-150500.55.73.1.150500.6.33.8 |
kernel-docsopenSUSE:Leap 15.5 From an advisory covering 531 CVEs |
before 5.14.21-150500.55.73.2 | 5.14.21-150500.55.73.2 |
kernel-kvmsmallopenSUSE:Leap 15.5 From an advisory covering 531 CVEs |
before 5.14.21-150500.55.73.1 | 5.14.21-150500.55.73.1 |
kernel-obs-buildopenSUSE:Leap 15.5 From an advisory covering 531 CVEs |
before 5.14.21-150500.55.73.1 | 5.14.21-150500.55.73.1 |
kernel-obs-qaopenSUSE:Leap 15.5 From an advisory covering 531 CVEs |
before 5.14.21-150500.55.73.1 | 5.14.21-150500.55.73.1 |
kernel-sourceopenSUSE:Leap 15.5 From an advisory covering 531 CVEs |
before 5.14.21-150500.55.73.1 | 5.14.21-150500.55.73.1 |
kernel-symsopenSUSE:Leap 15.5 From an advisory covering 531 CVEs |
before 5.14.21-150500.55.73.1 | 5.14.21-150500.55.73.1 |
kernel-zfcpdumpopenSUSE:Leap 15.5 From an advisory covering 531 CVEs |
before 5.14.21-150500.55.73.1 | 5.14.21-150500.55.73.1 |
kernel-azureSUSE:Linux Enterprise Module for Public Cloud 15 SP5 From an advisory covering 310 CVEs |
before 5.14.21-150500.33.63.1 | 5.14.21-150500.33.63.1 |
kernel-source-azureSUSE:Linux Enterprise Module for Public Cloud 15 SP5 From an advisory covering 310 CVEs |
before 5.14.21-150500.33.63.1 | 5.14.21-150500.33.63.1 |
kernel-syms-azureSUSE:Linux Enterprise Module for Public Cloud 15 SP5 From an advisory covering 310 CVEs |
before 5.14.21-150500.33.63.1 | 5.14.21-150500.33.63.1 |
kernel-azureopenSUSE:Leap 15.5 From an advisory covering 310 CVEs |
before 5.14.21-150500.33.63.1 | 5.14.21-150500.33.63.1 |
kernel-source-azureopenSUSE:Leap 15.5 From an advisory covering 310 CVEs |
before 5.14.21-150500.33.63.1 | 5.14.21-150500.33.63.1 |
kernel-syms-azureopenSUSE:Leap 15.5 From an advisory covering 310 CVEs |
before 5.14.21-150500.33.63.1 | 5.14.21-150500.33.63.1 |
kernel-azureSUSE:Linux Enterprise Module for Public Cloud 15 SP5 From an advisory covering 292 CVEs |
before 5.14.21-150500.33.66.1 | 5.14.21-150500.33.66.1 |
kernel-source-azureSUSE:Linux Enterprise Module for Public Cloud 15 SP5 From an advisory covering 292 CVEs |
before 5.14.21-150500.33.66.1 | 5.14.21-150500.33.66.1 |
kernel-syms-azureSUSE:Linux Enterprise Module for Public Cloud 15 SP5 From an advisory covering 292 CVEs |
before 5.14.21-150500.33.66.1 | 5.14.21-150500.33.66.1 |
kernel-azureopenSUSE:Leap 15.5 From an advisory covering 292 CVEs |
before 5.14.21-150500.33.66.1 | 5.14.21-150500.33.66.1 |
kernel-source-azureopenSUSE:Leap 15.5 From an advisory covering 292 CVEs |
before 5.14.21-150500.33.66.1 | 5.14.21-150500.33.66.1 |
kernel-syms-azureopenSUSE:Leap 15.5 From an advisory covering 292 CVEs |
before 5.14.21-150500.33.66.1 | 5.14.21-150500.33.66.1 |
kernel-azureSUSE:Linux Enterprise Module for Public Cloud 15 SP6 From an advisory covering 394 CVEs |
before 6.4.0-150600.8.11.1 | 6.4.0-150600.8.11.1 |
kernel-source-azureSUSE:Linux Enterprise Module for Public Cloud 15 SP6 From an advisory covering 394 CVEs |
before 6.4.0-150600.8.11.1 | 6.4.0-150600.8.11.1 |
kernel-syms-azureSUSE:Linux Enterprise Module for Public Cloud 15 SP6 From an advisory covering 394 CVEs |
before 6.4.0-150600.8.11.1 | 6.4.0-150600.8.11.1 |
kernel-azureopenSUSE:Leap 15.6 From an advisory covering 394 CVEs |
before 6.4.0-150600.8.11.1 | 6.4.0-150600.8.11.1 |
kernel-source-azureopenSUSE:Leap 15.6 From an advisory covering 394 CVEs |
before 6.4.0-150600.8.11.1 | 6.4.0-150600.8.11.1 |
kernel-syms-azureopenSUSE:Leap 15.6 From an advisory covering 394 CVEs |
before 6.4.0-150600.8.11.1 | 6.4.0-150600.8.11.1 |
kernel-livepatch-SLE15-SP6-RT_Update_2SUSE:Linux Enterprise Live Patching 15 SP6 From an advisory covering 393 CVEs |
before 1-150600.1.3.2 | 1-150600.1.3.2 |
kernel-rtSUSE:Real Time Module 15 SP6 From an advisory covering 393 CVEs |
before 6.4.0-150600.10.8.3 | 6.4.0-150600.10.8.3 |
kernel-rt_debugSUSE:Real Time Module 15 SP6 From an advisory covering 393 CVEs |
before 6.4.0-150600.10.8.3 | 6.4.0-150600.10.8.3 |
kernel-source-rtSUSE:Real Time Module 15 SP6 From an advisory covering 393 CVEs |
before 6.4.0-150600.10.8.3 | 6.4.0-150600.10.8.3 |
kernel-syms-rtSUSE:Real Time Module 15 SP6 From an advisory covering 393 CVEs |
before 6.4.0-150600.10.8.1 | 6.4.0-150600.10.8.1 |
kernel-rtopenSUSE:Leap 15.6 From an advisory covering 393 CVEs |
before 6.4.0-150600.10.8.3 | 6.4.0-150600.10.8.3 |
kernel-rt_debugopenSUSE:Leap 15.6 From an advisory covering 393 CVEs |
before 6.4.0-150600.10.8.3 | 6.4.0-150600.10.8.3 |
kernel-source-rtopenSUSE:Leap 15.6 From an advisory covering 393 CVEs |
before 6.4.0-150600.10.8.3 | 6.4.0-150600.10.8.3 |
kernel-syms-rtopenSUSE:Leap 15.6 From an advisory covering 393 CVEs |
before 6.4.0-150600.10.8.1 | 6.4.0-150600.10.8.1 |
kernel-rtSUSE:Linux Enterprise Micro 5.5 From an advisory covering 292 CVEs |
before 5.14.21-150500.13.67.3 | 5.14.21-150500.13.67.3 |
kernel-source-rtSUSE:Linux Enterprise Micro 5.5 From an advisory covering 292 CVEs |
before 5.14.21-150500.13.67.3 | 5.14.21-150500.13.67.3 |
kernel-livepatch-SLE15-SP5-RT_Update_19SUSE:Linux Enterprise Live Patching 15 SP5 From an advisory covering 292 CVEs |
before 1-150500.11.3.2 | 1-150500.11.3.2 |
kernel-rtSUSE:Real Time Module 15 SP5 From an advisory covering 292 CVEs |
before 5.14.21-150500.13.67.3 | 5.14.21-150500.13.67.3 |
kernel-rt_debugSUSE:Real Time Module 15 SP5 From an advisory covering 292 CVEs |
before 5.14.21-150500.13.67.3 | 5.14.21-150500.13.67.3 |
kernel-source-rtSUSE:Real Time Module 15 SP5 From an advisory covering 292 CVEs |
before 5.14.21-150500.13.67.3 | 5.14.21-150500.13.67.3 |
kernel-syms-rtSUSE:Real Time Module 15 SP5 From an advisory covering 292 CVEs |
before 5.14.21-150500.13.67.1 | 5.14.21-150500.13.67.1 |
kernel-rtopenSUSE:Leap Micro 5.5 From an advisory covering 292 CVEs |
before 5.14.21-150500.13.67.3 | 5.14.21-150500.13.67.3 |
kernel-rtopenSUSE:Leap 15.5 From an advisory covering 292 CVEs |
before 5.14.21-150500.13.67.3 | 5.14.21-150500.13.67.3 |
kernel-rt_debugopenSUSE:Leap 15.5 From an advisory covering 292 CVEs |
before 5.14.21-150500.13.67.3 | 5.14.21-150500.13.67.3 |
kernel-source-rtopenSUSE:Leap 15.5 From an advisory covering 292 CVEs |
before 5.14.21-150500.13.67.3 | 5.14.21-150500.13.67.3 |
kernel-syms-rtopenSUSE:Leap 15.5 From an advisory covering 292 CVEs |
before 5.14.21-150500.13.67.1 | 5.14.21-150500.13.67.1 |
kernel-rtSUSE:Linux Enterprise Micro 5.1 From an advisory covering 51 CVEs |
before 5.3.18-150300.181.2 | 5.3.18-150300.181.2 |
kernel-source-rtSUSE:Linux Enterprise Micro 5.1 From an advisory covering 51 CVEs |
before 5.3.18-150300.181.2 | 5.3.18-150300.181.2 |
kernel-rtSUSE:Linux Enterprise Micro 5.2 From an advisory covering 51 CVEs |
before 5.3.18-150300.181.2 | 5.3.18-150300.181.2 |
dtb-aarch64openSUSE:Leap 15.6 From an advisory covering 394 CVEs |
before 6.4.0-150600.23.22.1 | 6.4.0-150600.23.22.1 |
kernel-64kbopenSUSE:Leap 15.6 From an advisory covering 394 CVEs |
before 6.4.0-150600.23.22.1 | 6.4.0-150600.23.22.1 |
kernel-debugopenSUSE:Leap 15.6 From an advisory covering 394 CVEs |
before 6.4.0-150600.23.22.1 | 6.4.0-150600.23.22.1 |
kernel-defaultopenSUSE:Leap 15.6 From an advisory covering 394 CVEs |
before 6.4.0-150600.23.22.1 | 6.4.0-150600.23.22.1 |
kernel-default-baseopenSUSE:Leap 15.6 From an advisory covering 394 CVEs |
before 6.4.0-150600.23.22.1.150600.12.8.3 | 6.4.0-150600.23.22.1.150600.12.8.3 |
kernel-docsopenSUSE:Leap 15.6 From an advisory covering 394 CVEs |
before 6.4.0-150600.23.22.1 | 6.4.0-150600.23.22.1 |
kernel-kvmsmallopenSUSE:Leap 15.6 From an advisory covering 394 CVEs |
before 6.4.0-150600.23.22.1 | 6.4.0-150600.23.22.1 |
kernel-obs-buildopenSUSE:Leap 15.6 From an advisory covering 394 CVEs |
before 6.4.0-150600.23.22.1 | 6.4.0-150600.23.22.1 |
kernel-obs-qaopenSUSE:Leap 15.6 From an advisory covering 394 CVEs |
before 6.4.0-150600.23.22.1 | 6.4.0-150600.23.22.1 |
kernel-sourceopenSUSE:Leap 15.6 From an advisory covering 394 CVEs |
before 6.4.0-150600.23.22.1 | 6.4.0-150600.23.22.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.15Ubuntu:20.04:LTS |
before 5.15.0-1070.76~20.04.1, plus listed versions 5.15.0-1014.18~20.04.15.15.0-1015.19~20.04.15.15.0-1017.21~20.04.15.15.0-1019.23~20.04.15.15.0-1020.24~20.04.1 Show 40 moreShow less5.15.0-1021.25~20.04.15.15.0-1022.26~20.04.15.15.0-1023.27~20.04.15.15.0-1026.30~20.04.25.15.0-1027.31~20.04.15.15.0-1028.32~20.04.15.15.0-1030.34~20.04.15.15.0-1031.35~20.04.15.15.0-1033.37~20.04.15.15.0-1034.38~20.04.15.15.0-1035.39~20.04.15.15.0-1036.40~20.04.15.15.0-1037.41~20.04.15.15.0-1038.43~20.04.15.15.0-1039.44~20.04.15.15.0-1040.45~20.04.15.15.0-1041.46~20.04.15.15.0-1043.48~20.04.15.15.0-1044.49~20.04.15.15.0-1045.50~20.04.15.15.0-1047.52~20.04.15.15.0-1048.53~20.04.15.15.0-1049.54~20.04.15.15.0-1050.55~20.04.15.15.0-1051.56~20.04.15.15.0-1052.57~20.04.15.15.0-1053.58~20.04.15.15.0-1055.60~20.04.15.15.0-1056.61~20.04.15.15.0-1057.63~20.04.15.15.0-1058.64~20.04.15.15.0-1061.67~20.04.15.15.0-1062.68~20.04.15.15.0-1063.69~20.04.15.15.0-1064.70~20.04.15.15.0-1065.71~20.04.15.15.0-1066.72~20.04.15.15.0-1067.73~20.04.15.15.0-1068.74~20.04.15.15.0-1069.75~20.04.1 |
5.15.0-1070.76~20.04.1 |
linux-azure-5.15Ubuntu:20.04:LTS |
before 5.15.0-1073.82~20.04.1, plus listed versions 5.15.0-1007.8~20.04.15.15.0-1008.9~20.04.15.15.0-1013.16~20.04.15.15.0-1014.17~20.04.15.15.0-1017.20~20.04.1 Show 42 moreShow less5.15.0-1019.24~20.04.15.15.0-1020.25~20.04.15.15.0-1021.26~20.04.15.15.0-1022.27~20.04.15.15.0-1023.29~20.04.15.15.0-1029.36~20.04.15.15.0-1030.37~20.04.15.15.0-1031.38~20.04.15.15.0-1033.40~20.04.15.15.0-1034.41~20.04.15.15.0-1035.42~20.04.15.15.0-1036.43~20.04.15.15.0-1037.44~20.04.15.15.0-1038.45~20.04.15.15.0-1039.46~20.04.15.15.0-1040.47~20.04.15.15.0-1041.48~20.04.15.15.0-1042.49~20.04.15.15.0-1043.50~20.04.15.15.0-1045.52~20.04.15.15.0-1046.53~20.04.15.15.0-1047.54~20.04.15.15.0-1049.56~20.04.15.15.0-1050.57~20.04.15.15.0-1051.59~20.04.15.15.0-1052.60~20.04.15.15.0-1053.61~20.04.15.15.0-1054.62~20.04.15.15.0-1056.64~20.04.15.15.0-1057.65~20.04.15.15.0-1058.66~20.04.25.15.0-1059.67~20.04.15.15.0-1060.69~20.04.15.15.0-1061.70~20.04.15.15.0-1063.72~20.04.15.15.0-1064.73~20.04.15.15.0-1065.74~20.04.15.15.0-1067.76~20.04.15.15.0-1068.77~20.04.15.15.0-1070.79~20.04.15.15.0-1071.80~20.04.15.15.0-1072.81~20.04.1 |
5.15.0-1073.82~20.04.1 |
linux-gcp-5.15Ubuntu:20.04:LTS |
before 5.15.0-1069.77~20.04.1, plus listed versions 5.15.0-1006.9~20.04.15.15.0-1012.17~20.04.15.15.0-1013.18~20.04.15.15.0-1016.21~20.04.15.15.0-1017.23~20.04.2 Show 39 moreShow less5.15.0-1018.24~20.04.15.15.0-1021.28~20.04.15.15.0-1022.29~20.04.15.15.0-1025.32~20.04.25.15.0-1026.33~20.04.15.15.0-1027.34~20.04.15.15.0-1029.36~20.04.15.15.0-1030.37~20.04.15.15.0-1031.38~20.04.15.15.0-1032.40~20.04.15.15.0-1033.41~20.04.15.15.0-1034.42~20.04.15.15.0-1035.43~20.04.15.15.0-1036.44~20.04.15.15.0-1037.45~20.04.15.15.0-1038.46~20.04.15.15.0-1039.47~20.04.15.15.0-1040.48~20.04.15.15.0-1041.49~20.04.15.15.0-1042.50~20.04.15.15.0-1044.52~20.04.15.15.0-1045.53~20.04.25.15.0-1046.54~20.04.15.15.0-1047.55~20.04.15.15.0-1048.56~20.04.15.15.0-1049.57~20.04.15.15.0-1051.59~20.04.15.15.0-1052.60~20.04.15.15.0-1053.61~20.04.15.15.0-1054.62~20.04.15.15.0-1055.63~20.04.15.15.0-1058.66~20.04.15.15.0-1059.67~20.04.15.15.0-1060.68~20.04.15.15.0-1062.70~20.04.15.15.0-1065.73~20.04.15.15.0-1066.74~20.04.15.15.0-1067.75~20.04.15.15.0-1068.76~20.04.1 |
5.15.0-1069.77~20.04.1 |
linux-gkeop-5.15Ubuntu:20.04:LTS |
before 5.15.0-1053.60~20.04.1, plus listed versions 5.15.0-1003.5~20.04.25.15.0-1005.7~20.04.15.15.0-1007.10~20.04.15.15.0-1008.12~20.04.15.15.0-1011.15~20.04.2 Show 37 moreShow less5.15.0-1012.16~20.04.15.15.0-1013.17~20.04.15.15.0-1015.19~20.04.15.15.0-1016.21~20.04.15.15.0-1017.22~20.04.15.15.0-1018.23~20.04.15.15.0-1019.24~20.04.15.15.0-1020.25~20.04.15.15.0-1021.26~20.04.15.15.0-1022.27~20.04.15.15.0-1023.28~20.04.15.15.0-1024.29~20.04.15.15.0-1025.30~20.04.15.15.0-1026.31~20.04.15.15.0-1027.32~20.04.15.15.0-1028.33~20.04.15.15.0-1030.35~20.04.15.15.0-1031.37~20.04.15.15.0-1032.38~20.04.15.15.0-1033.39~20.04.15.15.0-1034.40~20.04.15.15.0-1035.41~20.04.15.15.0-1036.42~20.04.15.15.0-1037.43~20.04.15.15.0-1038.44~20.04.15.15.0-1039.45~20.04.15.15.0-1040.46~20.04.15.15.0-1043.50~20.04.15.15.0-1044.51~20.04.15.15.0-1045.52~20.04.15.15.0-1046.53~20.04.15.15.0-1047.54~20.04.15.15.0-1048.55~20.04.15.15.0-1049.56~20.04.15.15.0-1050.57~20.04.15.15.0-1051.58~20.04.15.15.0-1052.59~20.04.1 |
5.15.0-1053.60~20.04.1 |
linux-hwe-5.15Ubuntu:20.04:LTS |
before 5.15.0-122.132~20.04.1, plus listed versions 5.15.0-33.34~20.04.15.15.0-41.44~20.04.15.15.0-43.46~20.04.15.15.0-46.49~20.04.15.15.0-48.54~20.04.1 Show 40 moreShow less5.15.0-50.56~20.04.15.15.0-52.58~20.04.15.15.0-53.59~20.04.15.15.0-56.62~20.04.15.15.0-57.63~20.04.15.15.0-58.64~20.04.15.15.0-60.66~20.04.15.15.0-67.74~20.04.15.15.0-69.76~20.04.15.15.0-70.77~20.04.15.15.0-71.78~20.04.15.15.0-72.79~20.04.15.15.0-73.80~20.04.15.15.0-75.82~20.04.15.15.0-76.83~20.04.15.15.0-78.85~20.04.15.15.0-79.86~20.04.25.15.0-82.91~20.04.15.15.0-83.92~20.04.15.15.0-84.93~20.04.15.15.0-86.96~20.04.15.15.0-87.97~20.04.15.15.0-88.98~20.04.15.15.0-89.99~20.04.15.15.0-91.101~20.04.15.15.0-92.102~20.04.15.15.0-94.104~20.04.15.15.0-97.107~20.04.15.15.0-100.110~20.04.15.15.0-101.111~20.04.15.15.0-102.112~20.04.15.15.0-105.115~20.04.15.15.0-106.116~20.04.15.15.0-107.117~20.04.15.15.0-113.123~20.04.15.15.0-116.126~20.04.15.15.0-117.127~20.04.15.15.0-118.128~20.04.15.15.0-119.129~20.04.15.15.0-121.131~20.04.1 |
5.15.0-122.132~20.04.1 |
linux-ibm-5.15Ubuntu:20.04:LTS |
before 5.15.0-1063.66~20.04.1, plus listed versions 5.15.0-1033.36~20.04.15.15.0-1034.37~20.04.15.15.0-1035.38~20.04.15.15.0-1036.39~20.04.15.15.0-1037.40~20.04.1 Show 21 moreShow less5.15.0-1038.41~20.04.15.15.0-1040.43~20.04.15.15.0-1041.44~20.04.15.15.0-1042.45~20.04.15.15.0-1043.46~20.04.15.15.0-1044.47~20.04.15.15.0-1045.48~20.04.15.15.0-1046.49~20.04.15.15.0-1047.50~20.04.15.15.0-1048.51~20.04.15.15.0-1049.52~20.04.15.15.0-1050.53~20.04.15.15.0-1053.56~20.04.15.15.0-1054.57~20.04.15.15.0-1055.58~20.04.15.15.0-1057.60~20.04.15.15.0-1058.61~20.04.15.15.0-1059.62~20.04.15.15.0-1060.63~20.04.15.15.0-1061.64~20.04.15.15.0-1062.65~20.04.1 |
5.15.0-1063.66~20.04.1 |
linux-intel-iotg-5.15Ubuntu:20.04:LTS |
before 5.15.0-1065.71~20.04.1, plus listed versions 5.15.0-1003.5~20.04.15.15.0-1008.11~20.04.15.15.0-1010.14~20.04.15.15.0-1015.20~20.04.25.15.0-1016.21~20.04.1 Show 31 moreShow less5.15.0-1017.22~20.04.15.15.0-1018.23~20.04.15.15.0-1021.26~20.04.15.15.0-1023.28~20.04.15.15.0-1025.30~20.04.15.15.0-1026.31~20.04.15.15.0-1027.32~20.04.15.15.0-1030.35~20.04.15.15.0-1031.36~20.04.15.15.0-1033.38~20.04.15.15.0-1034.39~20.04.15.15.0-1036.41~20.04.15.15.0-1037.42~20.04.15.15.0-1038.43~20.04.15.15.0-1040.46~20.04.15.15.0-1043.49~20.04.15.15.0-1045.51~20.04.15.15.0-1046.52~20.04.15.15.0-1048.54~20.04.15.15.0-1049.55~20.04.15.15.0-1050.56~20.04.15.15.0-1051.57~20.04.15.15.0-1052.58~20.04.15.15.0-1055.61~20.04.15.15.0-1058.64~20.04.15.15.0-1059.65~20.04.15.15.0-1060.66~20.04.15.15.0-1061.67~20.04.15.15.0-1062.68~20.04.15.15.0-1063.69~20.04.15.15.0-1064.70~20.04.1 |
5.15.0-1065.71~20.04.1 |
linux-lowlatency-hwe-5.15Ubuntu:20.04:LTS |
before 5.15.0-122.132~20.04.1, plus listed versions 5.15.0-33.34~20.04.15.15.0-42.45~20.04.15.15.0-43.46~20.04.15.15.0-46.49~20.04.15.15.0-48.54~20.04.1 Show 40 moreShow less5.15.0-50.56~20.04.15.15.0-52.58~20.04.15.15.0-53.59~20.04.15.15.0-56.62~20.04.15.15.0-58.64~20.04.15.15.0-60.66~20.04.15.15.0-67.74~20.04.15.15.0-69.76~20.04.15.15.0-70.77~20.04.15.15.0-71.78~20.04.15.15.0-72.79~20.04.15.15.0-73.80~20.04.15.15.0-75.82~20.04.15.15.0-76.83~20.04.15.15.0-78.85~20.04.15.15.0-79.88~20.04.15.15.0-82.91~20.04.15.15.0-83.92~20.04.15.15.0-84.93~20.04.15.15.0-86.95~20.04.15.15.0-87.96~20.04.15.15.0-88.98~20.04.15.15.0-89.99~20.04.15.15.0-91.101~20.04.15.15.0-92.102~20.04.15.15.0-94.104~20.04.15.15.0-97.107~20.04.15.15.0-100.110~20.04.15.15.0-101.111~20.04.15.15.0-102.112~20.04.15.15.0-105.115~20.04.15.15.0-106.116~20.04.15.15.0-107.117~20.04.15.15.0-110.120~20.04.15.15.0-113.123~20.04.15.15.0-116.126~20.04.15.15.0-117.127~20.04.15.15.0-118.128~20.04.15.15.0-119.129~20.04.15.15.0-121.131~20.04.1 |
5.15.0-122.132~20.04.1 |
linux-nvidia-tegra-5.15Ubuntu:20.04:LTS |
before 5.15.0-1030.30~20.04.1, plus listed versions 5.15.0-1009.9~20.04.15.15.0-1010.10~20.04.15.15.0-1012.12~20.04.15.15.0-1014.14~20.04.15.15.0-1015.15~20.04.1 Show 8 moreShow less5.15.0-1016.16~20.04.15.15.0-1017.17~20.04.15.15.0-1018.18~20.04.15.15.0-1019.19~20.04.15.15.0-1020.20~20.04.15.15.0-1022.22~20.04.15.15.0-1025.25~20.04.15.15.0-1027.27~20.04.1 |
5.15.0-1030.30~20.04.1 |
linux-oracle-5.15Ubuntu:20.04:LTS |
before 5.15.0-1068.74~20.04.1, plus listed versions 5.15.0-1007.9~20.04.15.15.0-1013.17~20.04.15.15.0-1016.20~20.04.15.15.0-1017.22~20.04.15.15.0-1018.23~20.04.1 Show 38 moreShow less5.15.0-1019.24~20.04.15.15.0-1021.27~20.04.15.15.0-1022.28~20.04.15.15.0-1025.31~20.04.25.15.0-1027.33~20.04.15.15.0-1029.35~20.04.15.15.0-1030.36~20.04.15.15.0-1032.38~20.04.15.15.0-1033.39~20.04.15.15.0-1034.40~20.04.15.15.0-1035.41~20.04.15.15.0-1036.42~20.04.15.15.0-1037.43~20.04.15.15.0-1038.44~20.04.15.15.0-1039.45~20.04.15.15.0-1040.46~20.04.15.15.0-1041.47~20.04.15.15.0-1042.48~20.04.15.15.0-1044.50~20.04.15.15.0-1045.51~20.04.15.15.0-1046.52~20.04.15.15.0-1047.53~20.04.15.15.0-1048.54~20.04.15.15.0-1049.55~20.04.15.15.0-1050.56~20.04.15.15.0-1051.57~20.04.15.15.0-1052.58~20.04.15.15.0-1053.59~20.04.15.15.0-1054.60~20.04.15.15.0-1055.61~20.04.15.15.0-1058.64~20.04.15.15.0-1059.65~20.04.15.15.0-1061.67~20.04.15.15.0-1062.68~20.04.15.15.0-1063.69~20.04.15.15.0-1065.71~20.04.15.15.0-1066.72~20.04.15.15.0-1067.73~20.04.1 |
5.15.0-1068.74~20.04.1 |
linux-riscv-5.15Ubuntu:20.04:LTS |
before 5.15.0-1066.70~20.04.1, plus listed versions 5.15.0-1015.17~20.04.15.15.0-1017.19~20.04.15.15.0-1018.21~20.04.15.15.0-1019.22~20.04.15.15.0-1022.26~20.04.1 Show 38 moreShow less5.15.0-1023.27~20.04.15.15.0-1026.30~20.04.25.15.0-1027.31~20.04.15.15.0-1028.32~20.04.15.15.0-1029.33~20.04.15.15.0-1030.34~20.04.15.15.0-1031.35~20.04.15.15.0-1032.36~20.04.15.15.0-1033.37~20.04.15.15.0-1034.38~20.04.15.15.0-1035.39~20.04.15.15.0-1036.40~20.04.25.15.0-1037.41~20.04.25.15.0-1038.42~20.04.25.15.0-1039.43~20.04.25.15.0-1040.44~20.04.35.15.0-1041.45~20.04.15.15.0-1043.47~20.04.15.15.0-1044.48~20.04.15.15.0-1045.49~20.04.15.15.0-1046.50~20.04.15.15.0-1047.51~20.04.15.15.0-1048.52~20.04.15.15.0-1049.53~20.04.25.15.0-1050.54~20.04.15.15.0-1051.55~20.04.15.15.0-1052.56~20.04.15.15.0-1053.57~20.04.15.15.0-1056.60~20.04.15.15.0-1057.61~20.04.15.15.0-1058.62~20.04.15.15.0-1059.63~20.04.15.15.0-1060.64~20.04.15.15.0-1061.65~20.04.15.15.0-1062.66~20.04.15.15.0-1063.67~20.04.15.15.0-1064.68~20.04.15.15.0-1065.69~20.04.1 |
5.15.0-1066.70~20.04.1 |
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 |
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-41009 is a high vulnerability (CVSS 7.8) in Linux, published July 17, 2024. No source lists public exploit code. EPSS puts the chance of exploitation in the next 30 days at 0.27%, the 19th percentile. Fixed in kernel 6.6.43.1-7.
References
git.kernel.org/stable/c/be35504b959f2749bab280f4671e8df96dcf836f
git.kernel.org/stable/c/0f98f40eb1ed52af8b81f61901b6c0289ff59de4
git.kernel.org/stable/c/d1b9df0435bc61e0b44f578846516df8ef476686
git.kernel.org/stable/c/511804ab701c0503b72eac08217eabfd366ba069
git.kernel.org/stable/c/47416c852f2a04d348ea66ee451cbdcf8119f225
git.kernel.org/stable/c/cfa1a2329a691ffd991fcf7248a57d752e712881
Show 194 moreShow less
lists.debian.org/debian-lts-announce/2025/01/msg00001.html
nvd.nist.gov/vuln/detail/CVE-2024-41009
github.com/advisories/GHSA-qvfw-rqcg-jh9g
access.redhat.com/errata/RHSA-2024:10274
access.redhat.com/security/cve/CVE-2024-41009
access.redhat.com/security/cve/CVE-2024-42244
access.redhat.com/security/cve/CVE-2024-50226
bugzilla.redhat.com/2298412
bugzilla.redhat.com/2324876
errata.almalinux.org/9/ALSA-2024-10274.html
access.redhat.com/errata/RHSA-2024:8856
access.redhat.com/security/cve/CVE-2022-48773
access.redhat.com/security/cve/CVE-2022-48936
access.redhat.com/security/cve/CVE-2023-52492
access.redhat.com/security/cve/CVE-2024-24857
access.redhat.com/security/cve/CVE-2024-26851
access.redhat.com/security/cve/CVE-2024-26924
access.redhat.com/security/cve/CVE-2024-26976
access.redhat.com/security/cve/CVE-2024-27017
access.redhat.com/security/cve/CVE-2024-27062
access.redhat.com/security/cve/CVE-2024-35839
access.redhat.com/security/cve/CVE-2024-35898
access.redhat.com/security/cve/CVE-2024-35939
access.redhat.com/security/cve/CVE-2024-38540
access.redhat.com/security/cve/CVE-2024-38541
access.redhat.com/security/cve/CVE-2024-38586
bugzilla.redhat.com/2266247
bugzilla.redhat.com/2269183
bugzilla.redhat.com/2275750
bugzilla.redhat.com/2277168
bugzilla.redhat.com/2278262
bugzilla.redhat.com/2278350
bugzilla.redhat.com/2278387
bugzilla.redhat.com/2281284
bugzilla.redhat.com/2281669
bugzilla.redhat.com/2281817
bugzilla.redhat.com/2293356
bugzilla.redhat.com/2293402
bugzilla.redhat.com/2293458
bugzilla.redhat.com/2293459
bugzilla.redhat.com/2297475
bugzilla.redhat.com/2297508
bugzilla.redhat.com/2297545
bugzilla.redhat.com/2297567
errata.almalinux.org/8/ALSA-2024-8856.html
redhat.com/security/data/cve/CVE-2022-50341.html
redhat.com/security/data/cve/CVE-2023-53621.html
redhat.com/security/data/cve/CVE-2024-46679.html
errata.almalinux.org/8/ALSA-2024-8870.html
docs.bell-sw.com/security/cves/CVE-2024-41009
errata.tuxcare.com/els_os/almalinux9.2esu/CLSA-2026-1783791447.html
nvd.nist.gov/vuln/detail/CVE-2021-4454
nvd.nist.gov/vuln/detail/CVE-2021-47416
nvd.nist.gov/vuln/detail/CVE-2022-1462
nvd.nist.gov/vuln/detail/CVE-2022-48660
nvd.nist.gov/vuln/detail/CVE-2022-48961
nvd.nist.gov/vuln/detail/CVE-2022-48971
nvd.nist.gov/vuln/detail/CVE-2022-48975
nvd.nist.gov/vuln/detail/CVE-2022-49269
nvd.nist.gov/vuln/detail/CVE-2022-49390
nvd.nist.gov/vuln/detail/CVE-2022-49441
nvd.nist.gov/vuln/detail/CVE-2022-49443
nvd.nist.gov/vuln/detail/CVE-2022-49728
nvd.nist.gov/vuln/detail/CVE-2022-49749
nvd.nist.gov/vuln/detail/CVE-2022-49764
nvd.nist.gov/vuln/detail/CVE-2022-49766
nvd.nist.gov/vuln/detail/CVE-2022-49796
nvd.nist.gov/vuln/detail/CVE-2022-49797
nvd.nist.gov/vuln/detail/CVE-2022-49824
nvd.nist.gov/vuln/detail/CVE-2022-49825
github.com/CVEProject/cvelistV5/tree/main/cves/2024/41xxx/CVE-2024-41009.json
git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
security-tracker.debian.org/tracker/CVE-2024-41009
openeuler.org/zh/security/security-bulletins/detail?id=openEuler-SA-2024-1894
openeuler.org/zh/security/security-bulletins/detail?id=openEuler-SA-2024-1896
openeuler.org/zh/security/security-bulletins/detail?id=openEuler-SA-2024-1897
security.access.redhat.com/data/csaf/v2/advisories/2024/rhsa-2024_10262.json
cve.org/CVERecord?id=CVE-2021-4204
openwall.com/lists/oss-security/2022/01/11/4
cve.org/CVERecord?id=CVE-2021-47393
lore.kernel.org/linux-cve-announce/2024052147-CVE-2021-47393-ea1c@gregkh/T
cve.org/CVERecord?id=CVE-2021-47461
lore.kernel.org/linux-cve-announce/2024052225-CVE-2021-47461-a472@gregkh/T
cve.org/CVERecord?id=CVE-2022-0500
git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit?id=20b2aff4bc15bda809f994761d5719827d66c0b4
git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit?id=216e3cd2f28dbbf1fe86848e0e29e6693b9f0a20
git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit?id=34d3a78c681e8e7844b43d1a2f4671a04249c821
git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit?id=3c4807322660d4290ac9062c034aed6b87243861
git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit?id=48946bd6a5d695c50b34546864b79c1f910a33c1
git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit?id=c25b2ae136039ffa820c26138ed4a5e5f3ab3841
git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit?id=cf9f2f8d62eca810afbd1ee6cc0800202b000e57
cve.org/CVERecord?id=CVE-2022-23222
openwall.com/lists/oss-security/2022/01/13/1
cve.org/CVERecord?id=CVE-2022-48686
lore.kernel.org/linux-cve-announce/2024050342-CVE-2022-48686-5e8e@gregkh/T
cve.org/CVERecord?id=CVE-2022-48773
lore.kernel.org/linux-cve-announce/2024071628-CVE-2022-48773-9563@gregkh/T
cve.org/CVERecord?id=CVE-2022-48929
lore.kernel.org/linux-cve-announce/2024082222-CVE-2022-48929-857d@gregkh/T
cve.org/CVERecord?id=CVE-2023-0597
lore.kernel.org/lkml/Yz%[email protected]
cve.org/CVERecord?id=CVE-2023-52489
lore.kernel.org/linux-cve-announce/[email protected]/T
cve.org/CVERecord?id=CVE-2024-26671
lore.kernel.org/linux-cve-announce/2024040219-CVE-2024-26671-2543@gregkh/T
cve.org/CVERecord?id=CVE-2024-26961
lore.kernel.org/linux-cve-announce/2024050129-CVE-2024-26961-408d@gregkh/T
cve.org/CVERecord?id=CVE-2024-31076
lore.kernel.org/linux-cve-announce/2024062134-CVE-2024-31076-786e@gregkh/T
cve.org/CVERecord?id=CVE-2024-35823
lore.kernel.org/linux-cve-announce/2024051745-CVE-2024-35823-1e69@gregkh/T
cve.org/CVERecord?id=CVE-2024-36889
lore.kernel.org/linux-cve-announce/2024053033-CVE-2024-36889-222d@gregkh/T
cve.org/CVERecord?id=CVE-2024-36920
lore.kernel.org/linux-cve-announce/2024053039-CVE-2024-36920-b4a7@gregkh/T
cve.org/CVERecord?id=CVE-2024-38564
lore.kernel.org/linux-cve-announce/2024061955-CVE-2024-38564-b069@gregkh/T
cve.org/CVERecord?id=CVE-2024-40988
lore.kernel.org/linux-cve-announce/2024071249-CVE-2024-40988-490e@gregkh/T
cve.org/CVERecord?id=CVE-2024-41009
lore.kernel.org/linux-cve-announce/2024071715-CVE-2024-41009-cac5@gregkh/T
cve.org/CVERecord?id=CVE-2024-41014
lore.kernel.org/linux-cve-announce/2024072910-CVE-2024-41014-9186@gregkh/T
lore.kernel.org/linux-cve-announce/2024072917-CVE-2024-41023-32a0@gregkh/T
lore.kernel.org/linux-cve-announce/2024092744-CVE-2024-46858-dab6@gregkh/T
security.access.redhat.com/data/csaf/v2/advisories/2024/rhsa-2024_10274.json
lore.kernel.org/linux-cve-announce/2024080741-CVE-2024-42244-2346@gregkh/T
security.access.redhat.com/data/csaf/v2/advisories/2024/rhsa-2024_10771.json
security.access.redhat.com/data/csaf/v2/advisories/2024/rhsa-2024_10772.json
security.access.redhat.com/data/csaf/v2/advisories/2024/rhsa-2024_10773.json
security.access.redhat.com/data/csaf/v2/advisories/2024/rhsa-2024_6753.json
security.access.redhat.com/data/csaf/v2/advisories/2024/rhsa-2024_8856.json
security.access.redhat.com/data/csaf/v2/advisories/2024/rhsa-2024_8870.json
errata.rockylinux.org/RLSA-2024:8856
errata.rockylinux.org/RLSA-2024:8870
suse.com/support/update/announcement/2024/suse-su-20242894-1
bugzilla.suse.com/1082555
bugzilla.suse.com/1193454
bugzilla.suse.com/1193554
bugzilla.suse.com/1193787
bugzilla.suse.com/1194324
bugzilla.suse.com/1194869
bugzilla.suse.com/1195357
bugzilla.suse.com/1195668
bugzilla.suse.com/1195927
bugzilla.suse.com/1195957
bugzilla.suse.com/1196018
bugzilla.suse.com/1196823
bugzilla.suse.com/1197146
bugzilla.suse.com/1197246
bugzilla.suse.com/1197762
bugzilla.suse.com/1202346
bugzilla.suse.com/1202686
bugzilla.suse.com/1208783
bugzilla.suse.com/1209636
suse.com/security/cve/CVE-2021-47086
suse.com/security/cve/CVE-2021-47103
suse.com/security/cve/CVE-2021-47186
suse.com/security/cve/CVE-2021-47402
suse.com/security/cve/CVE-2021-47546
suse.com/security/cve/CVE-2021-47547
suse.com/security/cve/CVE-2021-47588
suse.com/security/cve/CVE-2021-47590
suse.com/security/cve/CVE-2021-47591
suse.com/security/cve/CVE-2021-47593
suse.com/security/cve/CVE-2021-47598
suse.com/security/cve/CVE-2021-47599
suse.com/security/cve/CVE-2021-47606
suse.com/security/cve/CVE-2021-47622
suse.com/security/cve/CVE-2021-47623
suse.com/security/cve/CVE-2021-47624
suse.com/security/cve/CVE-2022-48713
suse.com/security/cve/CVE-2022-48730
suse.com/security/cve/CVE-2022-48732
ubuntu.com/security/CVE-2024-41009
git.kernel.org/linus/cfa1a2329a691ffd991fcf7248a57d752e712881
ubuntu.com/security/notices/USN-7020-1
ubuntu.com/security/notices/USN-7021-1
ubuntu.com/security/notices/USN-7020-2
ubuntu.com/security/notices/USN-7029-1
ubuntu.com/security/notices/USN-7021-2
ubuntu.com/security/notices/USN-7020-3
ubuntu.com/security/notices/USN-7021-3
ubuntu.com/security/notices/USN-7021-4
ubuntu.com/security/notices/USN-7020-4
ubuntu.com/security/notices/USN-7021-5
ubuntu.com/security/notices/USN-7156-1
ubuntu.com/security/CVE-2024-42154
ubuntu.com/security/CVE-2024-42159
ubuntu.com/security/CVE-2024-42160
ubuntu.com/security/CVE-2024-42224
ubuntu.com/security/CVE-2024-42228
ubuntu.com/security/CVE-2024-26677
ubuntu.com/security/CVE-2024-27012
Left out here: 885 package rows, 1 version, 3,775 references and the rest of 17 source descriptions. The JSON record has them. Left out on purpose, here and in the API, to keep responses small: 1 source record.