CVE-2024-26837
net: bridge: switchdev: Skip MDB replays of deferred events on offload
In the Linux kernel, the following vulnerability has been resolved:
net: bridge: switchdev: Skip MDB replays of deferred events on offload
Before this change, generation of the list of MDB events to replay would race against the creation of new group memberships, either from the IGMP/MLD snooping logic or from user configuration.
While new memberships are immediately visible to walkers of br->mdb_list, the notification of their existence to switchdev event subscribers is deferred until a later point in time. So if a replay list was generated during a time that overlapped with such a window, it would also contain a replay of the not-yet-delivered event.
The driver would thus receive two copies of what the bridge internally considered to be one single event. On destruction of the bridge, only a single membership deletion event was therefore sent. As a consequence of this, drivers which reference count memberships (at least DSA), would be left with orphan groups in their hardware database when the bridge was destroyed.
This is only an issue when replaying additions. While deletion events may still be pending on the deferred queue, they will already have been removed from br->mdb_list, so no duplicates can be generated in that scenario.
To a user this meant that old group memberships, from a bridge in which a port was previously attached, could be reanimated (in hardware) when the port joined a new bridge, without the new bridge's knowledge.
For example, on an mv88e6xxx system, create a snooping bridge and immediately add a port to it:
root@infix-06-0b-00:~$ ip link add dev br0 up type bridge mcast_snooping 1 && \
> ip link set dev x3 up master br0
And then destroy the bridge:
root@infix-06-0b-00:~$ ip link del dev br0
root@infix-06-0b-00:~$ mvls atu
ADDRESS FID STATE Q F 0 1 2 3 4 5 6 7 8 9 a
DEV:0 Marvell 88E6393X
33:33:00:00:00:6a 1 static - - 0 . . . . . . . . . .
33:33:ff:87:e4:3f 1 static - - 0 . . . . . . . . . .
ff:ff:ff:ff:ff:ff 1 static - - 0 1 2 3 4 5 6 7 8 9 a
root@infix-06-0b-00:~$
The two IPv6 groups remain in the hardware database because the port (x3) is notified of the host's membership twice: once via the original event and once via a replay. Since only a single delete notification is sent, the count remains at 1 when the bridge is destroyed.
Then add the same port (or another port belonging to the same hardware domain) to a new bridge, this time with snooping disabled:
root@infix-06-0b-00:~$ ip link add dev br1 up type bridge mcast_snooping 0 && \
> ip link set dev x3 up master br1
All multicast, including the two IPv6 groups from br0, should now be flooded, according to the policy of br1. But instead the old memberships are still active in the hardware database, causing the switch to only forward traffic to those groups towards the CPU (port 0).
Eliminate the race in two steps:
- Grab the write-side lock of the MDB while generating the replay list.
This prevents new memberships from showing up while we are generating the replay list. But it leaves the scenario in which a deferred event was already generated, but not delivered, before we grabbed the lock. Therefore:
- Make sure that no deferred version of a replay event is already enqueued to the switchdev deferred queue, before adding it to the replay list, when replaying additions.
Attack profile
How easy it is to exploit
- Attack vector
- Local
- Complexity
- High
- Privileges needed
- Low
- User interaction
- None
What an attacker can affect
- Confidentiality
- None
- Integrity
- None
- Availability
- High
Exploit likelihood
What each source reports
NVD Score used
4.7
In the Linux kernel, the following vulnerability has been resolved:
net: bridge: switchdev: Skip MDB replays of deferred events on offload
Before this change, generation of the list of MDB events to replay would race against the creation of new group memberships, either from the IGMP/MLD snooping logic or from user configuration.
While new memberships are immediately visible to walkers of br->mdb_list, the notification of their existence to switchdev event subscribers is deferred until a later point in time. So if a replay list was generated during a time that overlapped with such a window, it would also contain a replay of the not-yet-delivered event.
The driver would thus receive two copies of what the bridge internally considered to be one single event. On destruction of the bridge, only a single membership deletion event was therefore sent. As a consequence of this, drivers which reference count memberships (at least DSA), would be left with orphan groups in their hardware database when the bridge was destroyed.
This is only an issue when replaying additions. While deletion events may still be pending on the deferred queue, they will already have been removed from br->mdb_list, so no duplicates can be generated in that scenario.
To a user this meant that old group memberships, from a bridge in which a port was previously attached, could be reanimated (in hardware) when the port joined a new bridge, without the new bridge's knowledge.
For example, on an mv88e6xxx system, create a snooping bridge and immediately add a port to it:
root@infix-06-0b-00:~$ ip link add dev br0 up type bridge mcast_snooping 1 && \
> ip link set dev x3 up master br0
And then destroy the bridge:
root@infix-06-0b-00:~$ ip link del dev br0
root@infix-06-0b-00:~$ mvls atu
ADDRESS FID STATE Q F 0 1 2 3 4 5 6 7 8 9 a
DEV:0 Marvell 88E6393X
33:33:00:00:00:6a 1 static - - 0 . . . . . . . . . .
33:33:ff:87:e4:3f 1 static - - 0 . . . . . . . . . .
ff:ff:ff:ff:ff:ff 1 static - - 0 1 2 3 4 5 6 7 8 9 a
root@infix-06-0b-00:~$
The two IPv6 groups remain in the hardware database because the port (x3) is notified of the host's membership twice: once via the original event and once via a replay. Since only a single delete notification is sent, the count remains at 1 when the bridge is destroyed.
Then add the same port (or another port belonging to the same hardware domain) to a new bridge, this time with snooping disabled:
root@infix-06-0b-00:~$ ip link add dev br1 up type bridge mcast_snooping 0 && \
> ip link set dev x3 up master br1
All multicast, including the two IPv6 groups from br0, should now be flooded, according to the policy of br1. But instead the old memberships are still active in the hardware database, causing the switch to only forward traffic to those groups towards the CPU (port 0).
Eliminate the race in two steps:
- Grab the write-side lock of the MDB while generating the replay list.
This prevents new memberships from showing up while we are generating the replay list. But it leaves the scenario in which a deferred event was already generated, but not delivered, before we grabbed the lock. Therefore:
- Make sure that no deferred version of a replay event is already enqueued to the switchdev deferred queue, before adding it to the replay list, when replaying additions.
- Record
CVE-2024-26837- CVSS 3.1
- 4.7 Medium
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H - Weakness
- CWE-362
- Updated
- 2026-11-02
CVE List No score
net: bridge: switchdev: Skip MDB replays of deferred events on offload
In the Linux kernel, the following vulnerability has been resolved:
net: bridge: switchdev: Skip MDB replays of deferred events on offload
Before this change, generation of the list of MDB events to replay would race against the creation of new group memberships, either from the IGMP/MLD snooping logic or from user configuration.
While new memberships are immediately visible to walkers of br->mdb_list, the notification of their existence to switchdev event subscribers is deferred until a later point in time. So if a replay list was generated during a time that overlapped with such a window, it would also contain a replay of the not-yet-delivered event.
The driver would thus receive two copies of what the bridge internally considered to be one single event. On destruction of the bridge, only a single membership deletion event was therefore sent. As a consequence of this, drivers which reference count memberships (at least DSA), would be left with orphan groups in their hardware database when the bridge was destroyed.
This is only an issue when replaying additions. While deletion events may still be pending on the deferred queue, they will already have been removed from br->mdb_list, so no duplicates can be generated in that scenario.
To a user this meant that old group memberships, from a bridge in which a port was previously attached, could be reanimated (in hardware) when the port joined a new bridge, without the new bridge's knowledge.
For example, on an mv88e6xxx system, create a snooping bridge and immediately add a port to it:
root@infix-06-0b-00:~$ ip link add dev br0 up type bridge mcast_snooping 1 && \
> ip link set dev x3 up master br0
And then destroy the bridge:
root@infix-06-0b-00:~$ ip link del dev br0
root@infix-06-0b-00:~$ mvls atu
ADDRESS FID STATE Q F 0 1 2 3 4 5 6 7 8 9 a
DEV:0 Marvell 88E6393X
33:33:00:00:00:6a 1 static - - 0 . . . . . . . . . .
33:33:ff:87:e4:3f 1 static - - 0 . . . . . . . . . .
ff:ff:ff:ff:ff:ff 1 static - - 0 1 2 3 4 5 6 7 8 9 a
root@infix-06-0b-00:~$
The two IPv6 groups remain in the hardware database because the port (x3) is notified of the host's membership twice: once via the original event and once via a replay. Since only a single delete notification is sent, the count remains at 1 when the bridge is destroyed.
Then add the same port (or another port belonging to the same hardware domain) to a new bridge, this time with snooping disabled:
root@infix-06-0b-00:~$ ip link add dev br1 up type bridge mcast_snooping 0 && \
> ip link set dev x3 up master br1
All multicast, including the two IPv6 groups from br0, should now be flooded, according to the policy of br1. But instead the old memberships are still active in the hardware database, causing the switch to only forward traffic to those groups towards the CPU (port 0).
Eliminate the race in two steps:
- Grab the write-side lock of the MDB while generating the replay list.
This prevents new memberships from showing up while we are generating the replay list. But it leaves the scenario in which a deferred event was already generated, but not delivered, before we grabbed the lock. Therefore:
- Make sure that no deferred version of a replay event is already enqueued to the switchdev deferred queue, before adding it to the replay list, when replaying additions.
- Record
CVE-2024-26837- Updated
- 2026-11-02
EUVDEUVD-2024-24099 No score
In the Linux kernel, the following vulnerability has been resolved:
net: bridge: switchdev: Skip MDB replays of deferred events on offload
Before this change, generation of the list of MDB events to replay would race against the creation of new group memberships, either from the IGMP/MLD snooping logic or from user configuration.
While new memberships are immediately visible to walkers of br->mdb_list, the notification of their existence to switchdev event subscribers is deferred until a later point in time. So if a replay list was generated during a time that overlapped with such a window, it would also contain a replay of the not-yet-delivered event.
The driver would thus receive two copies of what the bridge internally considered to be one single event. On destruction of the bridge, only a single membership deletion event was therefore sent. As a consequence of this, drivers which reference count memberships (at least DSA), would be left with orphan groups in their hardware database when the bridge was destroyed.
This is only an issue when replaying additions. While deletion events may still be pending on the deferred queue, they will already have been removed from br->mdb_list, so no duplicates can be generated in that scenario.
To a user this meant that old group memberships, from a bridge in which a port was previously attached, could be reanimated (in hardware) when the port joined a new bridge, without the new bridge's knowledge.
For example, on an mv88e6xxx system, create a snooping bridge and immediately add a port to it:
root@infix-06-0b-00:~$ ip link add dev br0 up type bridge mcast_snooping 1 && \
> ip link set dev x3 up master br0
And then destroy the bridge:
root@infix-06-0b-00:~$ ip link del dev br0
root@infix-06-0b-00:~$ mvls atu
ADDRESS FID STATE Q F 0 1 2 3 4 5 6 7 8 9 a
DEV:0 Marvell 88E6393X
33:33:00:00:00:6a 1 static - - 0 . . . . . . . . . .
33:33:ff:87:e4:3f 1 static - - 0 . . . . . . . . . .
ff:ff:ff:ff:ff:ff 1 static - - 0 1 2 3 4 5 6 7 8 9 a
root@infix-06-0b-00:~$
The two IPv6 groups remain in the hardware database because the port (x3) is notified of the host's membership twice: once via the original event and once via a replay. Since only a single delete notification is sent, the count remains at 1 when the bridge is destroyed.
Then add the same port (or another port belonging to the same hardware domain) to a new bridge, this time with snooping disabled:
root@infix-06-0b-00:~$ ip link add dev br1 up type bridge mcast_snooping 0 && \
> ip link set dev x3 up master br1
All multicast, including the two IPv6 groups from br0, should now be flooded, according to the policy of br1. But instead the old memberships are still active in the hardware database, causing the switch to only forward traffic to those groups towards the CPU (port 0).
Eliminate the race in two steps:
- Grab the write-side lock of the MDB while generating the replay list.
This prevents new memberships from showing up while we are generating the replay list. But it leaves the scenario in which a deferred event was already generated, but not delivered, before we grabbed the lock. Therefore:
- Make sure that no deferred version of a replay event is already enqueued to the switchdev deferred queue, before adding it to the replay list, when replaying additions.
- Record
EUVD-2024-24099- Updated
- 2026-11-02
GitHub AdvisoriesGHSA-8ppx-vmhm-cxj7
4.7
In the Linux kernel, the following vulnerability has been resolved: net: bridge: switchdev: Skip...
In the Linux kernel, the following vulnerability has been resolved:
net: bridge: switchdev: Skip MDB replays of deferred events on offload
Before this change, generation of the list of MDB events to replay would race against the creation of new group memberships, either from the IGMP/MLD snooping logic or from user configuration.
While new memberships are immediately visible to walkers of br->mdb_list, the notification of their existence to switchdev event subscribers is deferred until a later point in time. So if a replay list was generated during a time that overlapped with such a window, it would also contain a replay of the not-yet-delivered event.
The driver would thus receive two copies of what the bridge internally considered to be one single event. On destruction of the bridge, only a single membership deletion event was therefore sent. As a consequence of this, drivers which reference count memberships (at least DSA), would be left with orphan groups in their hardware database when the bridge was destroyed.
This is only an issue when replaying additions. While deletion events may still be pending on the deferred queue, they will already have been removed from br->mdb_list, so no duplicates can be generated in that scenario.
To a user this meant that old group memberships, from a bridge in which a port was previously attached, could be reanimated (in hardware) when the port joined a new bridge, without the new bridge's knowledge.
For example, on an mv88e6xxx system, create a snooping bridge and immediately add a port to it:
root@infix-06-0b-00:~$ ip link add dev br0 up type bridge mcast_snooping 1 && \
> ip link set dev x3 up master br0
And then destroy the bridge:
root@infix-06-0b-00:~$ ip link del dev br0
root@infix-06-0b-00:~$ mvls atu
ADDRESS FID STATE Q F 0 1 2 3 4 5 6 7 8 9 a
DEV:0 Marvell 88E6393X
33:33:00:00:00:6a 1 static - - 0 . . . . . . . . . .
33:33:ff:87:e4:3f 1 static - - 0 . . . . . . . . . .
ff:ff:ff:ff:ff:ff 1 static - - 0 1 2 3 4 5 6 7 8 9 a
root@infix-06-0b-00:~$
The two IPv6 groups remain in the hardware database because the port (x3) is notified of the host's membership twice: once via the original event and once via a replay. Since only a single delete notification is sent, the count remains at 1 when the bridge is destroyed.
Then add the same port (or another port belonging to the same hardware domain) to a new bridge, this time with snooping disabled:
root@infix-06-0b-00:~$ ip link add dev br1 up type bridge mcast_snooping 0 && \
> ip link set dev x3 up master br1
All multicast, including the two IPv6 groups from br0, should now be flooded, according to the policy of br1. But instead the old memberships are still active in the hardware database, causing the switch to only forward traffic to those groups towards the CPU (port 0).
Eliminate the race in two steps:
- Grab the write-side lock of the MDB while generating the replay list.
This prevents new memberships from showing up while we are generating the replay list. But it leaves the scenario in which a deferred event was already generated, but not delivered, before we grabbed the lock. Therefore:
- Make sure that no deferred version of a replay event is already enqueued to the switchdev deferred queue, before adding it to the replay list, when replaying additions.
- Record
GHSA-8ppx-vmhm-cxj7- CVSS 3.1
- 4.7 Medium
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H - Weakness
- CWE-362
- Updated
- 2026-11-02
OSVAZL-59442
4.7
CVE-2024-26837 affecting package kernel 5.15.200.1-1
In the Linux kernel, the following vulnerability has been resolved:
net: bridge: switchdev: Skip MDB replays of deferred events on offload
Before this change, generation of the list of MDB events to replay would race against the creation of new group memberships, either from the IGMP/MLD snooping logic or from user configuration.
While new memberships are immediately visible to walkers of br->mdb_list, the notification of their existence to switchdev event subscribers is deferred until a later point in time. So if a replay list was generated during a time that overlapped with such a window, it would also contain a replay of the not-yet-delivered event.
The driver would thus receive two copies of what the bridge internally considered to be one single event. On destruction of the bridge, only a single membership deletion event was therefore sent. As a consequence of this, drivers which reference count memberships (at least DSA), would be left with orphan groups in their hardware database when the bridge was destroyed.
This is only an issue when replaying additions. While deletion events may still be pending on the deferred queue, they will already have been removed from br->mdb_list, so no duplicates can be generated in that scenario.
To a user this meant that old group memberships, from a bridge in which a port was previously attached, could be reanimated (in hardware) when the port joined a new bridge, without the new bridge's knowledge.
For example, on an mv88e6xxx system, create a snooping bridge and immediately add a port to it:
root@infix-06-0b-00:~$ ip link add dev br0 up type bridge mcast_snooping 1 && \
> ip link set dev x3 up master br0
And then destroy the bridge:
root@infix-06-0b-00:~$ ip link del dev br0
root@infix-06-0b-00:~$ mvls atu
ADDRESS FID STATE Q F 0 1 2 3 4 5 6 7 8 9 a
DEV:0 Marvell 88E6393X
33:33:00:00:00:6a 1 static - - 0 . . . . . . . . . .
33:33:ff:87:e4:3f 1 static - - 0 . . . . . . . . . .
ff:ff:ff:ff:ff:ff 1 static - - 0 1 2 3 4 5 6 7 8 9 a
root@infix-06-0b-00:~$
The two IPv6 groups remain in the hardware database because the port (x3) is notified of the host's membership twice: once via the original event and once via a replay. Since only a single delete notification is sent, the count remains at 1 when the bridge is destroyed.
Then add the same port (or another port belonging to the same hardware domain) to a new bridge, this time with snooping disabled:
root@infix-06-0b-00:~$ ip link add dev br1 up type bridge mcast_snooping 0 && \
> ip link set dev x3 up master br1
All multicast, including the two IPv6 groups from br0, should now be flooded, according to the policy of br1. But instead the old memberships are still active in the hardware database, causing the switch to only forward traffic to those groups towards the CPU (port 0).
Eliminate the race in two steps:
- Grab the write-side lock of the MDB while generating the replay list.
This prevents new memberships from showing up while we are generating the replay list. But it leaves the scenario in which a deferred event was already generated, but not delivered, before we grabbed the lock. Therefore:
- Make sure that no deferred version of a replay event is already enqueued to the switchdev deferred queue, before adding it to the replay list, when replaying additions.
- Record
AZL-59442- CVSS 3.1
- 4.7 Medium
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H - Updated
- 2026-11-02
OSVBELL-CVE-2024-26837
4.7
- Record
BELL-CVE-2024-26837- CVSS 3.1
- 4.7 Medium
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H - Updated
- 2026-11-02
Show 30 moreShow less
OSVDEBIAN-CVE-2024-26837
4.7
In the Linux kernel, the following vulnerability has been resolved: net: bridge: switchdev: Skip MDB replays of deferred events on offload Before this change, generation of the list of MDB events to replay would race against the creation of new group memberships, either from the IGMP/MLD snooping logic or from user configuration. While new memberships are immediately visible to walkers of br->mdb_list, the notification of their existence to switchdev event subscribers is deferred until a later point in time. So if a replay list was generated during a time that overlapped with such a window, it would also contain a replay of the not-yet-delivered event. The driver would thus receive two copies of what the bridge internally considered to be one single event. On destruction of the bridge, only a single membership deletion event was therefore sent. As a consequence of this, drivers which reference count memberships (at least DSA), would be left with orphan groups in their hardware database when the bridge was destroyed. This is only an issue when replaying additions. While deletion events may still be pending on the deferred queue, they will already have been removed from br->mdb_list, so no duplicates can be generated in that scenario. To a user this meant that old group memberships, from a bridge in which a port was previously attached, could be reanimated (in hardware) when the port joined a new bridge, without the new bridge's knowledge. For example, on an mv88e6xxx system, create a snooping bridge and immediately add a port to it: root@infix-06-0b-00:$ ip link add dev br0 up type bridge mcast_snooping 1 && \ > ip link set dev x3 up master br0 And then destroy the bridge: root@infix-06-0b-00:$ ip link del dev br0 root@infix-06-0b-00:$ mvls atu ADDRESS FID STATE Q F 0 1 2 3 4 5 6 7 8 9 a DEV:0 Marvell 88E6393X 33:33:00:00:00:6a 1 static - - 0 . . . . . . . . . . 33:33:ff:87:e4:3f 1 static - - 0 . . . . . . . . . . ff:ff:ff:ff:ff:ff 1 static - - 0 1 2 3 4 5 6 7 8 9 a root@infix-06-0b-00:$ The two IPv6 groups remain in the hardware database because the port (x3) is notified of the host's membership twice: once via the original event and once via a replay. Since only a single delete notification is sent, the count remains at 1 when the bridge is destroyed. Then add the same port (or another port belonging to the same hardware domain) to a new bridge, this time with snooping disabled: root@infix-06-0b-00:~$ ip link add dev br1 up type bridge mcast_snooping 0 && \ > ip link set dev x3 up master br1 All multicast, including the two IPv6 groups from br0, should now be flooded, according to the policy of br1. But instead the old memberships are still active in the hardware database, causing the switch to only forward traffic to those groups towards the CPU (port 0). Eliminate the race in two steps: 1. Grab the write-side lock of the MDB while generating the replay list. This prevents new memberships from showing up while we are generating the replay list. But it leaves the scenario in which a deferred event was already generated, but not delivered, before we grabbed the lock. Therefore: 2. Make sure that no deferred version of a replay event is already enqueued to the switchdev deferred queue, before adding it to the replay list, when replaying additions.
- Record
DEBIAN-CVE-2024-26837- CVSS 3.1
- 4.7 Medium
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H - Updated
- 2026-11-02
OSVRHSA-2024:5101
7.8
Red Hat Security Advisory: kernel security update
- Record
RHSA-2024:5101- 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:5102
7.8
Red Hat Security Advisory: kernel-rt security update
- Record
RHSA-2024:5102- 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:9315
7.8
Red Hat Security Advisory: kernel security update
- Record
RHSA-2024:9315- 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:9546
7.8
Red Hat Security Advisory: kernel security update
- Record
RHSA-2024:9546- CVSS 3.1
- 7.8 High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H - Updated
- 2026-11-02
OSVUBUNTU-CVE-2024-26837
4.7
In the Linux kernel, the following vulnerability has been resolved: net: bridge: switchdev: Skip MDB replays of deferred events on offload Before this change, generation of the list of MDB events to replay would race against the creation of new group memberships, either from the IGMP/MLD snooping logic or from user configuration. While new memberships are immediately visible to walkers of br->mdb_list, the notification of their existence to switchdev event subscribers is deferred until a later point in time. So if a replay list was generated during a time that overlapped with such a window, it would also contain a replay of the not-yet-delivered event. The driver would thus receive two copies of what the bridge internally considered to be one single event. On destruction of the bridge, only a single membership deletion event was therefore sent. As a consequence of this, drivers which reference count memberships (at least DSA), would be left with orphan groups in their hardware database when the bridge was destroyed. This is only an issue when replaying additions. While deletion events may still be pending on the deferred queue, they will already have been removed from br->mdb_list, so no duplicates can be generated in that scenario. To a user this meant that old group memberships, from a bridge in which a port was previously attached, could be reanimated (in hardware) when the port joined a new bridge, without the new bridge's knowledge. For example, on an mv88e6xxx system, create a snooping bridge and immediately add a port to it: root@infix-06-0b-00:$ ip link add dev br0 up type bridge mcast_snooping 1 && \ > ip link set dev x3 up master br0 And then destroy the bridge: root@infix-06-0b-00:$ ip link del dev br0 root@infix-06-0b-00:$ mvls atu ADDRESS FID STATE Q F 0 1 2 3 4 5 6 7 8 9 a DEV:0 Marvell 88E6393X 33:33:00:00:00:6a 1 static - - 0 . . . . . . . . . . 33:33:ff:87:e4:3f 1 static - - 0 . . . . . . . . . . ff:ff:ff:ff:ff:ff 1 static - - 0 1 2 3 4 5 6 7 8 9 a root@infix-06-0b-00:$ The two IPv6 groups remain in the hardware database because the port (x3) is notified of the host's membership twice: once via the original event and once via a replay. Since only a single delete notification is sent, the count remains at 1 when the bridge is destroyed. Then add the same port (or another port belonging to the same hardware domain) to a new bridge, this time with snooping disabled: root@infix-06-0b-00:~$ ip link add dev br1 up type bridge mcast_snooping 0 && \ > ip link set dev x3 up master br1 All multicast, including the two IPv6 groups from br0, should now be flooded, according to the policy of br1. But instead the old memberships are still active in the hardware database, causing the switch to only forward traffic to those groups towards the CPU (port 0). Eliminate the race in two steps: 1. Grab the write-side lock of the MDB while generating the replay list. This prevents new memberships from showing up while we are generating the replay list. But it leaves the scenario in which a deferred event was already generated, but not delivered, before we grabbed the lock. Therefore: 2. Make sure that no deferred version of a replay event is already enqueued to the switchdev deferred queue, before adding it to the replay list, when replaying additions.
- Record
UBUNTU-CVE-2024-26837- CVSS 3.1
- 4.7 Medium
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H - Updated
- 2026-11-11
OSVALSA-2024:5101 No score
Important: kernel security update
The kernel packages contain the Linux kernel, the core of any Linux operating system.
Security Fix(es):
- kernel: powerpc: Fix access beyond end of drmem array (CVE-2023-52451)
- kernel: efivarfs: force RO when remounting if SetVariable is not supported (CVE-2023-52463)
- kernel: tracing: Restructure trace_clock_global() to never block (CVE-2021-46939)
- kernel: ext4: avoid online resizing failures due to oversized flex bg (CVE-2023-52622)
- kernel: net/sched: flower: Fix chain template offload (CVE-2024-26669)
- kernel: stmmac: Clear variable when destroying workqueue (CVE-2024-26802)
- kernel: efi: runtime: Fix potential overflow of soft-reserved region size (CVE-2024-26843)
- kernel: quota: Fix potential NULL pointer dereference (CVE-2024-26878)
- kernel: TIPC message reassembly use-after-free remote code execution vulnerability (CVE-2024-36886)
- kernel: SUNRPC: fix a memleak in gss_import_v2_context (CVE-2023-52653)
- kernel: dmaengine/idxd: hardware erratum allows potential security problem with direct access by untrusted application (CVE-2024-21823)
- kernel: Revert "net/mlx5: Block entering switchdev mode with ns inconsistency" (CVE-2023-52658)
- kernel: ext4: fix corruption during on-line resize (CVE-2024-35807)
- kernel: x86/fpu: Keep xfd_state in sync with MSR_IA32_XFD (CVE-2024-35801)
- kernel: dyndbg: fix old BUG_ON in >control parser (CVE-2024-35947)
- kernel: net/sched: act_skbmod: prevent kernel-infoleak (CVE-2024-35893)
- kernel: x86/mce: Make sure to grab mce_sysfs_mutex in set_bank() (CVE-2024-35876)
- kernel: platform/x86: wmi: Fix opening of char device (CVE-2023-52864)
- kernel: tipc: Change nla_policy for bearer-related names to NLA_NUL_STRING (CVE-2023-52845)
- (CVE-2023-28746)
- (CVE-2023-52847)
- (CVE-2021-47548)
- (CVE-2024-36921)
- (CVE-2024-26921)
- (CVE-2021-47579)
- (CVE-2024-36927)
- (CVE-2024-39276)
- (CVE-2024-33621)
- (CVE-2024-27010)
- (CVE-2024-26960)
- (CVE-2024-38596)
- (CVE-2022-48743)
- (CVE-2024-26733)
- (CVE-2024-26586)
- (CVE-2024-26698)
- (CVE-2023-52619)
Bug Fix(es):
- AlmaLinux8.6 - Spinlock statistics may show negative elapsed time and incorrectly formatted output (JIRA:AlmaLinux-17678)
- [AWS][8.9]There are call traces found when booting debug-kernel for Amazon EC2 r8g.metal-24xl instance (JIRA:AlmaLinux-23841)
- [almalinux8] gfs2: Fix glock shrinker (JIRA:AlmaLinux-32941)
- lan78xx: Microchip LAN7800 never comes up after unplug and replug (JIRA:AlmaLinux-33437)
- [Hyper-V][AlmaLinux-8.10.z] Update hv_netvsc driver to TOT (JIRA:AlmaLinux-39074)
- Use-after-free on proc inode-i_sb triggered by fsnotify (JIRA:AlmaLinux-40167)
- blk-cgroup: Properly propagate the iostat update up the hierarchy [almalinux-8.10.z] (JIRA:AlmaLinux-40939)
- (JIRA:AlmaLinux-31798)
- (JIRA:AlmaLinux-10263)
- (JIRA:AlmaLinux-40901)
- (JIRA:AlmaLinux-43547)
- (JIRA:AlmaLinux-34876)
Enhancement(s):
- [RFE] Add module parameters 'soft_reboot_cmd' and 'soft_active_on_boot' for customizing softdog configuration (JIRA:AlmaLinux-19723)
For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer the CVE page(s) listed in the References section.
- Record
ALSA-2024:5101- Updated
- 2026-11-02
OSVALSA-2024:5102 No score
Important: 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: efivarfs: force RO when remounting if SetVariable is not supported (CVE-2023-52463)
- kernel: tracing: Restructure trace_clock_global() to never block (CVE-2021-46939)
- kernel: ext4: avoid online resizing failures due to oversized flex bg (CVE-2023-52622)
- kernel: net/sched: flower: Fix chain template offload (CVE-2024-26669)
- kernel: stmmac: Clear variable when destroying workqueue (CVE-2024-26802)
- kernel: efi: runtime: Fix potential overflow of soft-reserved region size (CVE-2024-26843)
- kernel: quota: Fix potential NULL pointer dereference (CVE-2024-26878)
- kernel: TIPC message reassembly use-after-free remote code execution vulnerability (CVE-2024-36886)
- kernel: SUNRPC: fix a memleak in gss_import_v2_context (CVE-2023-52653)
- kernel: dmaengine/idxd: hardware erratum allows potential security problem with direct access by untrusted application (CVE-2024-21823)
- kernel: ext4: fix corruption during on-line resize (CVE-2024-35807)
- kernel: x86/fpu: Keep xfd_state in sync with MSR_IA32_XFD (CVE-2024-35801)
- kernel: dyndbg: fix old BUG_ON in >control parser (CVE-2024-35947)
- kernel: net/sched: act_skbmod: prevent kernel-infoleak (CVE-2024-35893)
- kernel: x86/mce: Make sure to grab mce_sysfs_mutex in set_bank() (CVE-2024-35876)
- kernel: platform/x86: wmi: Fix opening of char device (CVE-2023-52864)
- kernel: tipc: Change nla_policy for bearer-related names to NLA_NUL_STRING (CVE-2023-52845)
- kernel: Revert "net/mlx5: Block entering switchdev mode with ns inconsistency" (CVE-2023-52658)
- kernel: crash due to a missing check for leb_size (CVE-2024-25739)
- kernel: tcp: make sure init the accept_queue's spinlocks once (CVE-2024-26614)
- kernel: tcp: add sanity checks to rx zerocopy (CVE-2024-26640)
- kernel: NFSv4.2: fix nfs4_listxattr kernel BUG at mm/usercopy.c:102 (CVE-2024-26870)
- kernel: nfs: fix UAF in direct writes (CVE-2024-26958)
- kernel: SUNRPC: fix some memleaks in gssx_dec_option_array (CVE-2024-27388)
- kernel: wifi: iwlwifi: mvm: don't set the MFP flag for the GTK (CVE-2024-27434)
- kernel: of: Fix double free in of_parse_phandle_with_args_map (CVE-2023-52679)
- kernel: scsi: lpfc: Fix possible memory leak in lpfc_rcv_padisc() (CVE-2024-35930)
- kernel: wifi: iwlwifi: mvm: rfi: fix potential response leaks (CVE-2024-35912)
- kernel: block: prevent division by zero in blk_rq_stat_sum() (CVE-2024-35925)
- kernel: wifi: ath11k: decrease MHI channel buffer length to 8KB (CVE-2024-35938)
- kernel: wifi: cfg80211: check A-MSDU format more carefully (CVE-2024-35937)
- kernel: wifi: rtw89: fix null pointer access when abort scan (CVE-2024-35946)
- kernel: netfilter: nf_tables: honor table dormant flag from netdev release event path (CVE-2024-36005)
- kernel: mm/hugetlb: fix missing hugetlb_lock for resv uncharge (CVE-2024-36000)
- kernel: mlxsw: spectrum_acl_tcam: Fix incorrect list API usage (CVE-2024-36006)
- kernel: net: ieee802154: fix null deref in parse dev addr (CVE-2021-47257)
- kernel: mmc: sdio: fix possible resource leaks in some error paths (CVE-2023-52730)
- kernel: wifi: ath11k: fix gtk offload status event locking (CVE-2023-52777)
- (CVE-2023-52832)
- (CVE-2023-52803)
- (CVE-2023-52756)
- (CVE-2023-52834)
- (CVE-2023-52791)
- (CVE-2023-52764)
- (CVE-2021-47468)
- (CVE-2021-47284)
- (CVE-2024-36025)
- (CVE-2024-36941)
- (CVE-2024-36940)
- (CVE-2024-36904)
- (CVE-2024-36896)
- (CVE-2024-36954)
- (CVE-2024-36950)
- (CVE-2024-38575)
- (CVE-2024-36917)
- (CVE-2024-36016)
- (CVE-2023-52762)
- (CVE-2024-27025)
- (CVE-2021-47548)
- (CVE-2023-52619)
For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer the CVE page(s) listed in the References section.
- Record
ALSA-2024:5102- 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
OSV No score
net: bridge: switchdev: Skip MDB replays of deferred events on offload
In the Linux kernel, the following vulnerability has been resolved:
net: bridge: switchdev: Skip MDB replays of deferred events on offload
Before this change, generation of the list of MDB events to replay would race against the creation of new group memberships, either from the IGMP/MLD snooping logic or from user configuration.
While new memberships are immediately visible to walkers of br->mdb_list, the notification of their existence to switchdev event subscribers is deferred until a later point in time. So if a replay list was generated during a time that overlapped with such a window, it would also contain a replay of the not-yet-delivered event.
The driver would thus receive two copies of what the bridge internally considered to be one single event. On destruction of the bridge, only a single membership deletion event was therefore sent. As a consequence of this, drivers which reference count memberships (at least DSA), would be left with orphan groups in their hardware database when the bridge was destroyed.
This is only an issue when replaying additions. While deletion events may still be pending on the deferred queue, they will already have been removed from br->mdb_list, so no duplicates can be generated in that scenario.
To a user this meant that old group memberships, from a bridge in which a port was previously attached, could be reanimated (in hardware) when the port joined a new bridge, without the new bridge's knowledge.
For example, on an mv88e6xxx system, create a snooping bridge and immediately add a port to it:
root@infix-06-0b-00:~$ ip link add dev br0 up type bridge mcast_snooping 1 && \
> ip link set dev x3 up master br0
And then destroy the bridge:
root@infix-06-0b-00:~$ ip link del dev br0
root@infix-06-0b-00:~$ mvls atu
ADDRESS FID STATE Q F 0 1 2 3 4 5 6 7 8 9 a
DEV:0 Marvell 88E6393X
33:33:00:00:00:6a 1 static - - 0 . . . . . . . . . .
33:33:ff:87:e4:3f 1 static - - 0 . . . . . . . . . .
ff:ff:ff:ff:ff:ff 1 static - - 0 1 2 3 4 5 6 7 8 9 a
root@infix-06-0b-00:~$
The two IPv6 groups remain in the hardware database because the port (x3) is notified of the host's membership twice: once via the original event and once via a replay. Since only a single delete notification is sent, the count remains at 1 when the bridge is destroyed.
Then add the same port (or another port belonging to the same hardware domain) to a new bridge, this time with snooping disabled:
root@infix-06-0b-00:~$ ip link add dev br1 up type bridge mcast_snooping 0 && \
> ip link set dev x3 up master br1
All multicast, including the two IPv6 groups from br0, should now be flooded, according to the policy of br1. But instead the old memberships are still active in the hardware database, causing the switch to only forward traffic to those groups towards the CPU (port 0).
Eliminate the race in two steps:
- Grab the write-side lock of the MDB while generating the replay list.
This prevents new memberships from showing up while we are generating the replay list. But it leaves the scenario in which a deferred event was already generated, but not delivered, before we grabbed the lock. Therefore:
- Make sure that no deferred version of a replay event is already enqueued to the switchdev deferred queue, before adding it to the replay list, when replaying additions.
- Record
CVE-2024-26837- Updated
- 2026-11-02
OSVRLSA-2024:5101 No score
Important: kernel security update
The kernel packages contain the Linux kernel, the core of any Linux operating system.
Security Fix(es):
-
kernel: powerpc: Fix access beyond end of drmem array (CVE-2023-52451)
-
kernel: efivarfs: force RO when remounting if SetVariable is not supported (CVE-2023-52463)
-
kernel: tracing: Restructure trace_clock_global() to never block (CVE-2021-46939)
-
kernel: ext4: avoid online resizing failures due to oversized flex bg (CVE-2023-52622)
-
kernel: net/sched: flower: Fix chain template offload (CVE-2024-26669)
-
kernel: stmmac: Clear variable when destroying workqueue (CVE-2024-26802)
-
kernel: efi: runtime: Fix potential overflow of soft-reserved region size (CVE-2024-26843)
-
kernel: quota: Fix potential NULL pointer dereference (CVE-2024-26878)
-
kernel: TIPC message reassembly use-after-free remote code execution vulnerability (CVE-2024-36886)
-
kernel: SUNRPC: fix a memleak in gss_import_v2_context (CVE-2023-52653)
-
kernel: dmaengine/idxd: hardware erratum allows potential security problem with direct access by untrusted application (CVE-2024-21823)
-
kernel: Revert "net/mlx5: Block entering switchdev mode with ns inconsistency" (CVE-2023-52658)
-
kernel: ext4: fix corruption during on-line resize (CVE-2024-35807)
-
kernel: x86/fpu: Keep xfd_state in sync with MSR_IA32_XFD (CVE-2024-35801)
-
kernel: dyndbg: fix old BUG_ON in >control parser (CVE-2024-35947)
-
kernel: net/sched: act_skbmod: prevent kernel-infoleak (CVE-2024-35893)
-
kernel: x86/mce: Make sure to grab mce_sysfs_mutex in set_bank() (CVE-2024-35876)
-
kernel: platform/x86: wmi: Fix opening of char device (CVE-2023-52864)
-
kernel: tipc: Change nla_policy for bearer-related names to NLA_NUL_STRING (CVE-2023-52845)
-
(CVE-2023-28746)
-
(CVE-2023-52847)
-
(CVE-2021-47548)
-
(CVE-2024-36921)
-
(CVE-2024-26921)
-
(CVE-2021-47579)
-
(CVE-2024-36927)
-
(CVE-2024-39276)
-
(CVE-2024-33621)
-
(CVE-2024-27010)
-
(CVE-2024-26960)
-
(CVE-2024-38596)
-
(CVE-2022-48743)
-
(CVE-2024-26733)
-
(CVE-2024-26586)
-
(CVE-2024-26698)
-
(CVE-2023-52619)
Bug Fix(es):
-
Rocky Linux8.6 - Spinlock statistics may show negative elapsed time and incorrectly formatted output (JIRA:Rocky Linux-17678)
-
[AWS][8.9]There are call traces found when booting debug-kernel for Amazon EC2 r8g.metal-24xl instance (JIRA:Rocky Linux-23841)
-
[rhel8] gfs2: Fix glock shrinker (JIRA:Rocky Linux-32941)
-
lan78xx: Microchip LAN7800 never comes up after unplug and replug (JIRA:Rocky Linux-33437)
-
[Hyper-V][Rocky Linux-8.10.z] Update hv_netvsc driver to TOT (JIRA:Rocky Linux-39074)
-
Use-after-free on proc inode-i_sb triggered by fsnotify (JIRA:Rocky Linux-40167)
-
blk-cgroup: Properly propagate the iostat update up the hierarchy [rhel-8.10.z] (JIRA:Rocky Linux-40939)
-
(JIRA:Rocky Linux-31798)
-
(JIRA:Rocky Linux-10263)
-
(JIRA:Rocky Linux-40901)
-
(JIRA:Rocky Linux-43547)
-
(JIRA:Rocky Linux-34876)
Enhancement(s):
- [RFE] Add module parameters 'soft_reboot_cmd' and 'soft_active_on_boot' for customizing softdog configuration (JIRA:Rocky Linux-19723)
For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer the CVE page(s) listed in the References section.
- Record
RLSA-2024:5101- Updated
- 2026-11-02
OSVRLSA-2024:5102 No score
Important: 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: efivarfs: force RO when remounting if SetVariable is not supported (CVE-2023-52463)
-
kernel: tracing: Restructure trace_clock_global() to never block (CVE-2021-46939)
-
kernel: ext4: avoid online resizing failures due to oversized flex bg (CVE-2023-52622)
-
kernel: net/sched: flower: Fix chain template offload (CVE-2024-26669)
-
kernel: stmmac: Clear variable when destroying workqueue (CVE-2024-26802)
-
kernel: efi: runtime: Fix potential overflow of soft-reserved region size (CVE-2024-26843)
-
kernel: quota: Fix potential NULL pointer dereference (CVE-2024-26878)
-
kernel: TIPC message reassembly use-after-free remote code execution vulnerability (CVE-2024-36886)
-
kernel: SUNRPC: fix a memleak in gss_import_v2_context (CVE-2023-52653)
-
kernel: dmaengine/idxd: hardware erratum allows potential security problem with direct access by untrusted application (CVE-2024-21823)
-
kernel: ext4: fix corruption during on-line resize (CVE-2024-35807)
-
kernel: x86/fpu: Keep xfd_state in sync with MSR_IA32_XFD (CVE-2024-35801)
-
kernel: dyndbg: fix old BUG_ON in >control parser (CVE-2024-35947)
-
kernel: net/sched: act_skbmod: prevent kernel-infoleak (CVE-2024-35893)
-
kernel: x86/mce: Make sure to grab mce_sysfs_mutex in set_bank() (CVE-2024-35876)
-
kernel: platform/x86: wmi: Fix opening of char device (CVE-2023-52864)
-
kernel: tipc: Change nla_policy for bearer-related names to NLA_NUL_STRING (CVE-2023-52845)
-
kernel: Revert "net/mlx5: Block entering switchdev mode with ns inconsistency" (CVE-2023-52658)
-
kernel: crash due to a missing check for leb_size (CVE-2024-25739)
-
kernel: tcp: make sure init the accept_queue's spinlocks once (CVE-2024-26614)
-
kernel: tcp: add sanity checks to rx zerocopy (CVE-2024-26640)
-
kernel: NFSv4.2: fix nfs4_listxattr kernel BUG at mm/usercopy.c:102 (CVE-2024-26870)
-
kernel: nfs: fix UAF in direct writes (CVE-2024-26958)
-
kernel: SUNRPC: fix some memleaks in gssx_dec_option_array (CVE-2024-27388)
-
kernel: wifi: iwlwifi: mvm: don't set the MFP flag for the GTK (CVE-2024-27434)
-
kernel: of: Fix double free in of_parse_phandle_with_args_map (CVE-2023-52679)
-
kernel: scsi: lpfc: Fix possible memory leak in lpfc_rcv_padisc() (CVE-2024-35930)
-
kernel: wifi: iwlwifi: mvm: rfi: fix potential response leaks (CVE-2024-35912)
-
kernel: block: prevent division by zero in blk_rq_stat_sum() (CVE-2024-35925)
-
kernel: wifi: ath11k: decrease MHI channel buffer length to 8KB (CVE-2024-35938)
-
kernel: wifi: cfg80211: check A-MSDU format more carefully (CVE-2024-35937)
-
kernel: wifi: rtw89: fix null pointer access when abort scan (CVE-2024-35946)
-
kernel: netfilter: nf_tables: honor table dormant flag from netdev release event path (CVE-2024-36005)
-
kernel: mm/hugetlb: fix missing hugetlb_lock for resv uncharge (CVE-2024-36000)
-
kernel: mlxsw: spectrum_acl_tcam: Fix incorrect list API usage (CVE-2024-36006)
-
kernel: net: ieee802154: fix null deref in parse dev addr (CVE-2021-47257)
-
kernel: mmc: sdio: fix possible resource leaks in some error paths (CVE-2023-52730)
-
kernel: wifi: ath11k: fix gtk offload status event locking (CVE-2023-52777)
-
(CVE-2023-52832)
-
(CVE-2023-52803)
-
(CVE-2023-52756)
-
(CVE-2023-52834)
-
(CVE-2023-52791)
-
(CVE-2023-52764)
-
(CVE-2021-47468)
-
(CVE-2021-47284)
-
(CVE-2024-36025)
-
(CVE-2024-36941)
-
(CVE-2024-36940)
-
(CVE-2024-36904)
-
(CVE-2024-36896)
-
(CVE-2024-36954)
-
(CVE-2024-36950)
-
(CVE-2024-38575)
-
(CVE-2024-36917)
-
(CVE-2024-36016)
-
(CVE-2023-52762)
-
(CVE-2024-27025)
-
(CVE-2021-47548)
-
(CVE-2023-52619)
For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer the CVE page(s) listed in the References section.
- Record
RLSA-2024:5102- Updated
- 2026-11-02
OSVRXSA-2024:5101 No score
Important: kernel security update
The kernel packages contain the Linux kernel, the core of any Linux operating system.
Security Fix(es):
-
kernel: powerpc: Fix access beyond end of drmem array (CVE-2023-52451)
-
kernel: efivarfs: force RO when remounting if SetVariable is not supported (CVE-2023-52463)
-
kernel: tracing: Restructure trace_clock_global() to never block (CVE-2021-46939)
-
kernel: ext4: avoid online resizing failures due to oversized flex bg (CVE-2023-52622)
-
kernel: net/sched: flower: Fix chain template offload (CVE-2024-26669)
-
kernel: stmmac: Clear variable when destroying workqueue (CVE-2024-26802)
-
kernel: efi: runtime: Fix potential overflow of soft-reserved region size (CVE-2024-26843)
-
kernel: quota: Fix potential NULL pointer dereference (CVE-2024-26878)
-
kernel: TIPC message reassembly use-after-free remote code execution vulnerability (CVE-2024-36886)
-
kernel: SUNRPC: fix a memleak in gss_import_v2_context (CVE-2023-52653)
-
kernel: dmaengine/idxd: hardware erratum allows potential security problem with direct access by untrusted application (CVE-2024-21823)
-
kernel: Revert "net/mlx5: Block entering switchdev mode with ns inconsistency" (CVE-2023-52658)
-
kernel: ext4: fix corruption during on-line resize (CVE-2024-35807)
-
kernel: x86/fpu: Keep xfd_state in sync with MSR_IA32_XFD (CVE-2024-35801)
-
kernel: dyndbg: fix old BUG_ON in >control parser (CVE-2024-35947)
-
kernel: net/sched: act_skbmod: prevent kernel-infoleak (CVE-2024-35893)
-
kernel: x86/mce: Make sure to grab mce_sysfs_mutex in set_bank() (CVE-2024-35876)
-
kernel: platform/x86: wmi: Fix opening of char device (CVE-2023-52864)
-
kernel: tipc: Change nla_policy for bearer-related names to NLA_NUL_STRING (CVE-2023-52845)
-
(CVE-2023-28746)
-
(CVE-2023-52847)
-
(CVE-2021-47548)
-
(CVE-2024-36921)
-
(CVE-2024-26921)
-
(CVE-2021-47579)
-
(CVE-2024-36927)
-
(CVE-2024-39276)
-
(CVE-2024-33621)
-
(CVE-2024-27010)
-
(CVE-2024-26960)
-
(CVE-2024-38596)
-
(CVE-2022-48743)
-
(CVE-2024-26733)
-
(CVE-2024-26586)
-
(CVE-2024-26698)
-
(CVE-2023-52619)
Bug Fix(es):
-
Rocky Linux SIG Cloud8.6 - Spinlock statistics may show negative elapsed time and incorrectly formatted output (JIRA:Rocky Linux SIG Cloud-17678)
-
[AWS][8.9]There are call traces found when booting debug-kernel for Amazon EC2 r8g.metal-24xl instance (JIRA:Rocky Linux SIG Cloud-23841)
-
[rhel8] gfs2: Fix glock shrinker (JIRA:Rocky Linux SIG Cloud-32941)
-
lan78xx: Microchip LAN7800 never comes up after unplug and replug (JIRA:Rocky Linux SIG Cloud-33437)
-
[Hyper-V][Rocky Linux SIG Cloud-8.10.z] Update hv_netvsc driver to TOT (JIRA:Rocky Linux SIG Cloud-39074)
-
Use-after-free on proc inode-i_sb triggered by fsnotify (JIRA:Rocky Linux SIG Cloud-40167)
-
blk-cgroup: Properly propagate the iostat update up the hierarchy [rhel-8.10.z] (JIRA:Rocky Linux SIG Cloud-40939)
-
(JIRA:Rocky Linux SIG Cloud-31798)
-
(JIRA:Rocky Linux SIG Cloud-10263)
-
(JIRA:Rocky Linux SIG Cloud-40901)
-
(JIRA:Rocky Linux SIG Cloud-43547)
-
(JIRA:Rocky Linux SIG Cloud-34876)
Enhancement(s):
- [RFE] Add module parameters 'soft_reboot_cmd' and 'soft_active_on_boot' for customizing softdog configuration (JIRA:Rocky Linux SIG Cloud-19723)
For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer the CVE page(s) listed in the References section.
- Record
RXSA-2024:5101- 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: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:3569-1 No score
Security update for the Linux Kernel
The SUSE Linux Enterprise 15 SP5 kernel was updated to receive various security bugfixes.
The following security bugs were fixed:
- CVE-2022-48901: btrfs: do not start relocation until in progress drops are done (bsc#1229607).
- CVE-2022-48911: kabi: add __nf_queue_get_refs() for kabi compliance. (bsc#1229633).
- CVE-2022-48923: btrfs: prevent copying too big compressed lzo segment (bsc#1229662)
- CVE-2022-48935: Fixed an unregister flowtable hooks on netns exit (bsc#1229619)
- CVE-2023-52610: net/sched: act_ct: fix skb leak and crash on ooo frags (bsc#1221610).
- CVE-2023-52916: media: aspeed: Fix memory overwrite if timing is 1600x900 (bsc#1230269).
- CVE-2024-26640: tcp: add sanity checks to rx zerocopy (bsc#1221650).
- CVE-2024-26759: mm/swap: fix race when skipping swapcache (bsc#1230340).
- CVE-2024-26767: drm/amd/display: fixed integer types and null check locations (bsc#1230339).
- CVE-2024-26804: net: ip_tunnel: prevent perpetual headroom growth (bsc#1222629).
- 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-37353: virtio: fixed a double free in vp_del_vqs() (bsc#1226875).
- CVE-2024-38538: net: bridge: xmit: make sure we have at least eth header len bytes (bsc#1226606).
- CVE-2024-38596: af_unix: Fix data races in unix_release_sock/unix_stream_sendmsg (bsc#1226846).
- CVE-2024-40910: Fix refcount imbalance on inbound connections (bsc#1227832).
- CVE-2024-40973: media: mtk-vcodec: potential null pointer deference in SCP (bsc#1227890).
- CVE-2024-40983: tipc: force a dst refcount before doing decryption (bsc#1227819).
- CVE-2024-41062: Sync sock recv cb and release (bsc#1228576).
- CVE-2024-41082: nvme-fabrics: use reserved tag for reg read/write command (bsc#1228620 CVE-2024-41082).
- CVE-2024-42154: tcp_metrics: validate source addr length (bsc#1228507).
- CVE-2024-42259: Fix Virtual Memory mapping boundaries calculation (bsc#1229156)
- CVE-2024-42265: protect the fetch of ->fd[fd] in do_dup2() from mispredictions (bsc#1229334).
- CVE-2024-42304: ext4: make sure the first directory block is not a hole (bsc#1229364).
- CVE-2024-42305: ext4: check dot and dotdot of dx_root before making dir indexed (bsc#1229363).
- CVE-2024-42306: udf: Avoid using corrupted block bitmap buffer (bsc#1229362).
- CVE-2024-43828: ext4: fix infinite loop when replaying fast_commit (bsc#1229394).
- CVE-2024-43890: tracing: Fix overflow in get_free_elt() (bsc#1229764).
- CVE-2024-43898: ext4: sanity check for NULL pointer after ext4_force_shutdown (bsc#1229753).
- CVE-2024-43912: wifi: nl80211: disallow setting special AP channel widths (bsc#1229830)
- CVE-2024-43914: md/raid5: avoid BUG_ON() while continue reshape after reassembling (bsc#1229790).
- CVE-2024-44935: sctp: Fix null-ptr-deref in reuseport_add_sock() (bsc#1229810).
- CVE-2024-44944: netfilter: ctnetlink: use helper function to calculate expect ID (bsc#1229899).
- CVE-2024-44946: kcm: Serialise kcm_sendmsg() for the same socket (bsc#1230015).
- CVE-2024-44950: serial: sc16is7xx: fix invalid FIFO access with special register set (bsc#1230180).
- CVE-2024-44952: driver core: Fix uevent_show() vs driver detach race (bsc#1230178).
- CVE-2024-44970: net/mlx5e: SHAMPO, Fix invalid WQ linked list unlink (bsc#1230209).
- CVE-2024-44971: net: dsa: bcm_sf2: Fix a possible memory leak in bcm_sf2_mdio_register() (bsc#1230211).
- CVE-2024-44986: ipv6: fix possible UAF in ip6_finish_output2() (bsc#1230230)
- CVE-2024-44987: ipv6: prevent UAF in ip6_send_skb() (bsc#1230185).
- CVE-2024-44988: net: dsa: mv88e6xxx: Fix out-of-bound access (bsc#1230192).
- CVE-2024-44989: bonding: fix xfrm real_dev null pointer dereference (bsc#1230193).
- CVE-2024-44990: bonding: fix null pointer deref in bond_ipsec_offload_ok (bsc#1230194).
- CVE-2024-44998: atm: idt77252: prevent use after free in dequeue_rx() (bsc#1230171).
- CVE-2024-44999: gtp: pull network headers in gtp_dev_xmit()…
- Record
SUSE-SU-2024:3569-1- Updated
- 2026-11-02
OSVSUSE-SU-2024:3587-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-2022-48901: btrfs: do not start relocation until in progress drops are done (bsc#1229607).
- CVE-2022-48911: kabi: add __nf_queue_get_refs() for kabi compliance. (bsc#1229633).
- CVE-2022-48923: btrfs: prevent copying too big compressed lzo segment (bsc#1229662)
- CVE-2022-48935: Fixed an unregister flowtable hooks on netns exit (bsc#1229619)
- CVE-2023-52610: net/sched: act_ct: fix skb leak and crash on ooo frags (bsc#1221610).
- CVE-2023-52916: media: aspeed: Fix memory overwrite if timing is 1600x900 (bsc#1230269).
- CVE-2024-26640: tcp: add sanity checks to rx zerocopy (bsc#1221650).
- CVE-2024-26759: mm/swap: fix race when skipping swapcache (bsc#1230340).
- CVE-2024-26767: drm/amd/display: fixed integer types and null check locations (bsc#1230339).
- CVE-2024-26804: net: ip_tunnel: prevent perpetual headroom growth (bsc#1222629).
- 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-37353: virtio: fixed a double free in vp_del_vqs() (bsc#1226875).
- CVE-2024-38538: net: bridge: xmit: make sure we have at least eth header len bytes (bsc#1226606).
- CVE-2024-38596: af_unix: Fix data races in unix_release_sock/unix_stream_sendmsg (bsc#1226846).
- CVE-2024-40910: Fix refcount imbalance on inbound connections (bsc#1227832).
- CVE-2024-40973: media: mtk-vcodec: potential null pointer deference in SCP (bsc#1227890).
- CVE-2024-40983: tipc: force a dst refcount before doing decryption (bsc#1227819).
- CVE-2024-41062: Sync sock recv cb and release (bsc#1228576).
- CVE-2024-41082: nvme-fabrics: use reserved tag for reg read/write command (bsc#1228620 CVE-2024-41082).
- CVE-2024-42154: tcp_metrics: validate source addr length (bsc#1228507).
- CVE-2024-42259: Fix Virtual Memory mapping boundaries calculation (bsc#1229156)
- CVE-2024-42265: protect the fetch of ->fd[fd] in do_dup2() from mispredictions (bsc#1229334).
- CVE-2024-42304: ext4: make sure the first directory block is not a hole (bsc#1229364).
- CVE-2024-42305: ext4: check dot and dotdot of dx_root before making dir indexed (bsc#1229363).
- CVE-2024-42306: udf: Avoid using corrupted block bitmap buffer (bsc#1229362).
- CVE-2024-43828: ext4: fix infinite loop when replaying fast_commit (bsc#1229394).
- CVE-2024-43890: tracing: Fix overflow in get_free_elt() (bsc#1229764).
- CVE-2024-43898: ext4: sanity check for NULL pointer after ext4_force_shutdown (bsc#1229753).
- CVE-2024-43912: wifi: nl80211: disallow setting special AP channel widths (bsc#1229830)
- CVE-2024-43914: md/raid5: avoid BUG_ON() while continue reshape after reassembling (bsc#1229790).
- CVE-2024-44935: sctp: Fix null-ptr-deref in reuseport_add_sock() (bsc#1229810).
- CVE-2024-44944: netfilter: ctnetlink: use helper function to calculate expect ID (bsc#1229899).
- CVE-2024-44946: kcm: Serialise kcm_sendmsg() for the same socket (bsc#1230015).
- CVE-2024-44950: serial: sc16is7xx: fix invalid FIFO access with special register set (bsc#1230180).
- CVE-2024-44952: driver core: Fix uevent_show() vs driver detach race (bsc#1230178).
- CVE-2024-44970: net/mlx5e: SHAMPO, Fix invalid WQ linked list unlink (bsc#1230209).
- CVE-2024-44971: net: dsa: bcm_sf2: Fix a possible memory leak in bcm_sf2_mdio_register() (bsc#1230211).
- CVE-2024-44986: ipv6: fix possible UAF in ip6_finish_output2() (bsc#1230230)
- CVE-2024-44987: ipv6: prevent UAF in ip6_send_skb() (bsc#1230185).
- CVE-2024-44988: net: dsa: mv88e6xxx: Fix out-of-bound access (bsc#1230192).
- CVE-2024-44989: bonding: fix xfrm real_dev null pointer dereference (bsc#1230193).
- CVE-2024-44990: bonding: fix null pointer deref in bond_ipsec_offload_ok (bsc#1230194).
- CVE-2024-44998: atm: idt77252: prevent use after free in dequeue_rx() (bsc#1230171).
- CVE-2024-44999: gtp: pull network headers in…
- Record
SUSE-SU-2024:3587-1- Updated
- 2026-11-02
OSVSUSE-SU-2024:3592-1 No score
Security update for the Linux Kernel
The SUSE Linux Enterprise 15 SP5 RT kernel was updated to receive various security bugfixes.
The following security bugs were fixed:
- CVE-2022-48901: btrfs: do not start relocation until in progress drops are done (bsc#1229607).
- CVE-2022-48911: kabi: add __nf_queue_get_refs() for kabi compliance. (bsc#1229633).
- CVE-2022-48923: btrfs: prevent copying too big compressed lzo segment (bsc#1229662)
- CVE-2022-48935: Fixed an unregister flowtable hooks on netns exit (bsc#1229619)
- CVE-2023-52610: net/sched: act_ct: fix skb leak and crash on ooo frags (bsc#1221610).
- CVE-2023-52916: media: aspeed: Fix memory overwrite if timing is 1600x900 (bsc#1230269).
- CVE-2024-26640: tcp: add sanity checks to rx zerocopy (bsc#1221650).
- CVE-2024-26759: mm/swap: fix race when skipping swapcache (bsc#1230340).
- CVE-2024-26767: drm/amd/display: fixed integer types and null check locations (bsc#1230339).
- CVE-2024-26804: net: ip_tunnel: prevent perpetual headroom growth (bsc#1222629).
- 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-37353: virtio: fixed a double free in vp_del_vqs() (bsc#1226875).
- CVE-2024-38538: net: bridge: xmit: make sure we have at least eth header len bytes (bsc#1226606).
- CVE-2024-38596: af_unix: Fix data races in unix_release_sock/unix_stream_sendmsg (bsc#1226846).
- CVE-2024-40910: Fix refcount imbalance on inbound connections (bsc#1227832).
- CVE-2024-40973: media: mtk-vcodec: potential null pointer deference in SCP (bsc#1227890).
- CVE-2024-40983: tipc: force a dst refcount before doing decryption (bsc#1227819).
- CVE-2024-41062: Sync sock recv cb and release (bsc#1228576).
- CVE-2024-41082: nvme-fabrics: use reserved tag for reg read/write command (bsc#1228620 CVE-2024-41082).
- CVE-2024-42154: tcp_metrics: validate source addr length (bsc#1228507).
- CVE-2024-42259: Fix Virtual Memory mapping boundaries calculation (bsc#1229156)
- CVE-2024-42265: protect the fetch of ->fd[fd] in do_dup2() from mispredictions (bsc#1229334).
- CVE-2024-42304: ext4: make sure the first directory block is not a hole (bsc#1229364).
- CVE-2024-42305: ext4: check dot and dotdot of dx_root before making dir indexed (bsc#1229363).
- CVE-2024-42306: udf: Avoid using corrupted block bitmap buffer (bsc#1229362).
- CVE-2024-43828: ext4: fix infinite loop when replaying fast_commit (bsc#1229394).
- CVE-2024-43890: tracing: Fix overflow in get_free_elt() (bsc#1229764).
- CVE-2024-43898: ext4: sanity check for NULL pointer after ext4_force_shutdown (bsc#1229753).
- CVE-2024-43912: wifi: nl80211: disallow setting special AP channel widths (bsc#1229830)
- CVE-2024-43914: md/raid5: avoid BUG_ON() while continue reshape after reassembling (bsc#1229790).
- CVE-2024-44935: sctp: Fix null-ptr-deref in reuseport_add_sock() (bsc#1229810).
- CVE-2024-44944: netfilter: ctnetlink: use helper function to calculate expect ID (bsc#1229899).
- CVE-2024-44946: kcm: Serialise kcm_sendmsg() for the same socket (bsc#1230015).
- CVE-2024-44950: serial: sc16is7xx: fix invalid FIFO access with special register set (bsc#1230180).
- CVE-2024-44952: driver core: Fix uevent_show() vs driver detach race (bsc#1230178).
- CVE-2024-44954: ALSA: line6: Fix racy access to midibuf (bsc#1230176).
- CVE-2024-44970: net/mlx5e: SHAMPO, Fix invalid WQ linked list unlink (bsc#1230209).
- CVE-2024-44971: net: dsa: bcm_sf2: Fix a possible memory leak in bcm_sf2_mdio_register() (bsc#1230211).
- CVE-2024-44986: ipv6: fix possible UAF in ip6_finish_output2() (bsc#1230230)
- CVE-2024-44987: ipv6: prevent UAF in ip6_send_skb() (bsc#1230185).
- CVE-2024-44988: net: dsa: mv88e6xxx: Fix out-of-bound access (bsc#1230192).
- CVE-2024-44989: bonding: fix xfrm real_dev null pointer dereference (bsc#1230193).
- CVE-2024-44990: bonding: fix null pointer deref in bond_ipsec_offload_ok (bsc#1230194).
- CVE-2024-44998: atm: idt77252: prevent use after free in dequeue_rx()…
- Record
SUSE-SU-2024:3592-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-7455-1 No score
linux, linux-aws, linux-azure, linux-azure-5.15, linux-azure-fde, linux-azure-fde-5.15, linux-gcp, linux-gke, linux-gkeop, linux-hwe-5.15, linux-ibm, linux-intel-iotg, linux-kvm, linux-lowlatency, linux-lowlatency-hwe-5.15, linux-nvidia, linux-nvidia-tegra, linux-nvidia-tegra-igx, linux-oracle, linux-raspi vulnerabilities
Jann Horn discovered that the watch_queue event notification subsystem in the Linux kernel contained an out-of-bounds write vulnerability. A local attacker could use this to cause a denial of service (system crash) or escalate their privileges. (CVE-2022-0995)
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:
- Network drivers;
- File systems infrastructure;
- NTFS3 file system;
- Ethernet bridge;
- Ethtool driver;
- IPv6 networking;
- Network traffic control;
- VMware vSockets driver; (CVE-2025-21703, CVE-2024-56651, CVE-2024-50248, CVE-2025-21701, CVE-2024-26837, CVE-2024-46826, CVE-2025-21993, CVE-2025-21702, CVE-2024-50256, CVE-2025-21756, CVE-2025-21700)
- Record
USN-7455-1- Updated
- 2026-11-02
OSVUSN-7455-2 No score
linux-aws-fips, linux-fips, linux-gcp-fips vulnerabilities
Jann Horn discovered that the watch_queue event notification subsystem in the Linux kernel contained an out-of-bounds write vulnerability. A local attacker could use this to cause a denial of service (system crash) or escalate their privileges. (CVE-2022-0995)
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:
- Network drivers;
- File systems infrastructure;
- NTFS3 file system;
- Ethernet bridge;
- Ethtool driver;
- IPv6 networking;
- Network traffic control;
- VMware vSockets driver; (CVE-2024-26837, CVE-2025-21993, CVE-2025-21702, CVE-2025-21700, CVE-2025-21701, CVE-2024-50248, CVE-2024-56651, CVE-2024-46826, CVE-2024-50256, CVE-2025-21756, CVE-2025-21703)
- Record
USN-7455-2- Updated
- 2026-11-02
OSVUSN-7455-3 No score
linux-intel-iot-realtime, linux-realtime vulnerabilities
Jann Horn discovered that the watch_queue event notification subsystem in the Linux kernel contained an out-of-bounds write vulnerability. A local attacker could use this to cause a denial of service (system crash) or escalate their privileges. (CVE-2022-0995)
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:
- Network drivers;
- File systems infrastructure;
- NTFS3 file system;
- Ethernet bridge;
- Ethtool driver;
- IPv6 networking;
- Network traffic control;
- VMware vSockets driver; (CVE-2024-56651, CVE-2025-21756, CVE-2024-26837, CVE-2025-21700, CVE-2024-46826, CVE-2024-50256, CVE-2024-50248, CVE-2025-21993, CVE-2025-21702, CVE-2025-21701, CVE-2025-21703)
- Record
USN-7455-3- Updated
- 2026-11-02
OSVUSN-7455-4 No score
linux-oracle-5.15 vulnerabilities
Jann Horn discovered that the watch_queue event notification subsystem in the Linux kernel contained an out-of-bounds write vulnerability. A local attacker could use this to cause a denial of service (system crash) or escalate their privileges. (CVE-2022-0995)
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:
- Network drivers;
- File systems infrastructure;
- NTFS3 file system;
- Ethernet bridge;
- Ethtool driver;
- IPv6 networking;
- Network traffic control;
- VMware vSockets driver; (CVE-2025-21993, CVE-2025-21703, CVE-2024-50248, CVE-2025-21700, CVE-2024-50256, CVE-2025-21701, CVE-2024-56651, CVE-2025-21756, CVE-2024-26837, CVE-2025-21702, CVE-2024-46826)
- Record
USN-7455-4- Updated
- 2026-11-02
OSVUSN-7455-5 No score
linux-aws-5.15 vulnerabilities
Jann Horn discovered that the watch_queue event notification subsystem in the Linux kernel contained an out-of-bounds write vulnerability. A local attacker could use this to cause a denial of service (system crash) or escalate their privileges. (CVE-2022-0995)
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:
- iSCSI Boot Firmware Table Attributes driver;
- Network drivers;
- File systems infrastructure;
- NTFS3 file system;
- Ethernet bridge;
- Ethtool driver;
- IPv6 networking;
- Network traffic control;
- VMware vSockets driver; (CVE-2024-26837, CVE-2025-21993, CVE-2025-21702, CVE-2024-50248, CVE-2024-46826, CVE-2024-50256, CVE-2025-21703, CVE-2025-21700, CVE-2025-21756, CVE-2025-21701, CVE-2024-56651)
- Record
USN-7455-5- Updated
- 2026-11-02
OSVUSN-7459-1 No score
linux-intel-iotg-5.15 vulnerabilities
Jann Horn discovered that the watch_queue event notification subsystem in the Linux kernel contained an out-of-bounds write vulnerability. A local attacker could use this to cause a denial of service (system crash) or escalate their privileges. (CVE-2022-0995)
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;
- PowerPC architecture;
- RISC-V architecture;
- S390 architecture;
- SuperH RISC architecture;
- User-Mode Linux (UML);
- x86 architecture;
- Block layer subsystem;
- Cryptographic API;
- ACPI drivers;
- Drivers core;
- RAM backed block device driver;
- Virtio block driver;
- Data acquisition framework and drivers;
- Hardware crypto device drivers;
- DMA engine subsystem;
- EDAC drivers;
- ARM SCPI message protocol;
- GPIO subsystem;
- GPU drivers;
- HID subsystem;
- Microsoft Hyper-V drivers;
- I3C subsystem;
- IIO ADC drivers;
- IIO subsystem;
- InfiniBand drivers;
- IOMMU subsystem;
- LED subsystem;
- Multiple devices driver;
- Media drivers;
- Multifunction device drivers;
- MMC subsystem;
- MTD block device drivers;
- Network drivers;
- Mellanox network drivers;
- Microsoft Azure Network Adapter (MANA) driver;
- NVME drivers;
- PCI subsystem;
- Pin controllers subsystem;
- x86 platform drivers;
- Power supply drivers;
- Real Time Clock drivers;
- SCSI subsystem;
- SuperH / SH-Mobile drivers;
- i.MX SoC drivers;
- QCOM SoC drivers;
- SPI subsystem;
- Media staging drivers;
- UFS subsystem;
- DesignWare USB3 driver;
- USB Gadget drivers;
- USB Serial drivers;
- USB Type-C Port Controller Manager driver;
- VFIO drivers;
- Framebuffer layer;
- Xen hypervisor drivers;
- AFS file system;
- File systems infrastructure;
- BTRFS file system;
- Ceph distributed file system;
- F2FS file system;
- GFS2 file system;
- JFFS2 file system;
- JFS file system;
- Network file system (NFS) client;
- Network file system (NFS) server daemon;
- NILFS2 file system;
- NTFS3 file system;
- Overlay file system;
- Proc file system;
- Diskquota system;
- SMB network file system;
- UBI file system;
- Timer subsystem;
- VLANs driver;
- LAPB network protocol;
- Network namespace;
- Kernel init infrastructure;
- BPF subsystem;
- Kernel CPU control infrastructure;
- DMA mapping infrastructure;
- KCSAN framework;
- Tracing infrastructure;
- Memory management;
- 9P file system network protocol;
- Bluetooth subsystem;
- Ethernet bridge;
- CAN network layer;
- Networking core;
- DCCP (Datagram Congestion Control Protocol);
- Distributed Switch Architecture;
- Ethtool driver;
- HSR network protocol;
- IEEE802154.4 network protocol;
- IPv4 networking;
- IPv6 networking;
- IEEE 802.15.4 subsystem;
- Multipath TCP;
- Netfilter;
- Netlink;
- NET/ROM layer;
- Packet sockets;
- Network traffic control;
- SCTP protocol;
- SMC sockets;
- Sun RPC protocol;
- TIPC protocol;
- VMware vSockets driver;
- eXpress Data Path;
- SELinux security module;
- ALSA framework;
- USB sound devices; (CVE-2024-57913, CVE-2024-56748, CVE-2024-46871, CVE-2024-57900, CVE-2025-21637, CVE-2025-21756, CVE-2024-53680, CVE-2024-56728, CVE-2024-46826, CVE-2024-57910, CVE-2024-56679, CVE-2024-53215, CVE-2024-56640, CVE-2024-56634, CVE-2024-56594, CVE-2024-56619, CVE-2024-50242, CVE-2024-53150, CVE-2024-49925, CVE-2024-56648, CVE-2024-53121, CVE-2024-36476, CVE-2025-21631, CVE-2024-49996, CVE-2024-56723, CVE-2025-21690, CVE-2024-56769, CVE-2024-56767, CVE-2025-21664, CVE-2024-53155, CVE-2024-48881, CVE-2024-57925, CVE-2024-53197, CVE-2024-53156, CVE-2024-35864, CVE-2024-53122, CVE-2024-50121, CVE-2025-21700, CVE-2022-49034, CVE-2025-21648, CVE-2024-57903, CVE-2024-57902, CVE-2024-53184,…
- Record
USN-7459-1- Updated
- 2026-11-02
OSVUSN-7459-2 No score
linux-gcp-5.15 vulnerabilities
Jann Horn discovered that the watch_queue event notification subsystem in the Linux kernel contained an out-of-bounds write vulnerability. A local attacker could use this to cause a denial of service (system crash) or escalate their privileges. (CVE-2022-0995)
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;
- PowerPC architecture;
- RISC-V architecture;
- S390 architecture;
- SuperH RISC architecture;
- User-Mode Linux (UML);
- x86 architecture;
- Block layer subsystem;
- Cryptographic API;
- ACPI drivers;
- Drivers core;
- RAM backed block device driver;
- Virtio block driver;
- Data acquisition framework and drivers;
- Hardware crypto device drivers;
- DMA engine subsystem;
- EDAC drivers;
- ARM SCPI message protocol;
- iSCSI Boot Firmware Table Attributes driver;
- GPIO subsystem;
- GPU drivers;
- HID subsystem;
- Microsoft Hyper-V drivers;
- I3C subsystem;
- IIO ADC drivers;
- IIO subsystem;
- InfiniBand drivers;
- IOMMU subsystem;
- LED subsystem;
- Multiple devices driver;
- Media drivers;
- Multifunction device drivers;
- MMC subsystem;
- MTD block device drivers;
- Network drivers;
- Mellanox network drivers;
- Microsoft Azure Network Adapter (MANA) driver;
- NVME drivers;
- PCI subsystem;
- Pin controllers subsystem;
- x86 platform drivers;
- Power supply drivers;
- Real Time Clock drivers;
- SCSI subsystem;
- SuperH / SH-Mobile drivers;
- i.MX SoC drivers;
- QCOM SoC drivers;
- SPI subsystem;
- Media staging drivers;
- UFS subsystem;
- DesignWare USB3 driver;
- USB Gadget drivers;
- USB Serial drivers;
- USB Type-C Port Controller Manager driver;
- VFIO drivers;
- Framebuffer layer;
- Xen hypervisor drivers;
- AFS file system;
- File systems infrastructure;
- BTRFS file system;
- Ceph distributed file system;
- F2FS file system;
- GFS2 file system;
- JFFS2 file system;
- JFS file system;
- Network file system (NFS) client;
- Network file system (NFS) server daemon;
- NILFS2 file system;
- NTFS3 file system;
- Overlay file system;
- Proc file system;
- Diskquota system;
- SMB network file system;
- UBI file system;
- Timer subsystem;
- VLANs driver;
- LAPB network protocol;
- Network namespace;
- Kernel init infrastructure;
- BPF subsystem;
- Kernel CPU control infrastructure;
- DMA mapping infrastructure;
- KCSAN framework;
- Tracing infrastructure;
- Memory management;
- 9P file system network protocol;
- Bluetooth subsystem;
- Ethernet bridge;
- CAN network layer;
- Networking core;
- DCCP (Datagram Congestion Control Protocol);
- Distributed Switch Architecture;
- Ethtool driver;
- HSR network protocol;
- IEEE802154.4 network protocol;
- IPv4 networking;
- IPv6 networking;
- IEEE 802.15.4 subsystem;
- Multipath TCP;
- Netfilter;
- Netlink;
- NET/ROM layer;
- Packet sockets;
- Network traffic control;
- SCTP protocol;
- SMC sockets;
- Sun RPC protocol;
- TIPC protocol;
- VMware vSockets driver;
- eXpress Data Path;
- SELinux security module;
- ALSA framework;
- USB sound devices; (CVE-2024-53690, CVE-2024-56642, CVE-2024-56777, CVE-2024-49998, CVE-2024-53181, CVE-2024-53184, CVE-2024-53180, CVE-2024-56615, CVE-2024-56679, CVE-2024-53099, CVE-2025-21993, CVE-2024-53112, CVE-2024-56594, CVE-2024-56606, CVE-2024-56533, CVE-2024-56616, CVE-2024-56631, CVE-2024-46784, CVE-2024-53124, CVE-2024-56623, CVE-2024-57939, CVE-2025-21694, CVE-2025-21653, CVE-2024-56548, CVE-2024-56600, CVE-2024-56578, CVE-2024-53198, CVE-2024-56619, CVE-2024-44938, CVE-2024-56688, CVE-2024-56651, CVE-2024-53215, CVE-2024-53150, CVE-2025-21687, CVE-2025-21646, CVE-2024-49571, CVE-2024-57884, CVE-2025-21700, CVE-2024-57907, CVE-2024-56569,…
- Record
USN-7459-2- Updated
- 2026-11-02
OSVUSN-7460-1 No score
linux-azure-fips vulnerabilities
Jann Horn discovered that the watch_queue event notification subsystem in the Linux kernel contained an out-of-bounds write vulnerability. A local attacker could use this to cause a denial of service (system crash) or escalate their privileges. (CVE-2022-0995)
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:
- Network drivers;
- Microsoft Azure Network Adapter (MANA) driver;
- File systems infrastructure;
- NTFS3 file system;
- Ethernet bridge;
- Ethtool driver;
- IPv6 networking;
- Network traffic control;
- VMware vSockets driver; (CVE-2024-26837, CVE-2024-50248, CVE-2025-21756, CVE-2025-21701, CVE-2024-50256, CVE-2025-21993, CVE-2025-21700, CVE-2025-21702, CVE-2024-56651, CVE-2025-21703, CVE-2024-46826, CVE-2024-42069)
- Record
USN-7460-1- Updated
- 2026-11-02
OSVUSN-7475-1 No score
linux-xilinx-zynqmp vulnerabilities
Jann Horn discovered that the watch_queue event notification subsystem in the Linux kernel contained an out-of-bounds write vulnerability. A local attacker could use this to cause a denial of service (system crash) or escalate their privileges. (CVE-2022-0995)
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:
- iSCSI Boot Firmware Table Attributes driver;
- GPU drivers;
- Network drivers;
- File systems infrastructure;
- NTFS3 file system;
- SMB network file system;
- Network namespace;
- Ethernet bridge;
- Networking core;
- Ethtool driver;
- IPv6 networking;
- Network traffic control;
- VMware vSockets driver; (CVE-2024-50248, CVE-2024-57798, CVE-2025-21702, CVE-2024-56651, CVE-2024-26837, CVE-2025-21703, CVE-2024-46826, CVE-2025-21700, CVE-2024-50256, CVE-2024-35864, CVE-2025-21756, CVE-2025-21993, CVE-2024-26928, CVE-2024-56658, CVE-2025-21701)
- Record
USN-7475-1- Updated
- 2026-11-02
Affected products
Affected packages
| Package | Affected | Fixed |
|---|---|---|
bpftoolAlmaLinux:8 From an advisory covering 160 CVEs |
before 4.18.0-553.16.1.el8_10 | 4.18.0-553.16.1.el8_10 |
kernelAlmaLinux:8 From an advisory covering 160 CVEs |
before 4.18.0-553.16.1.el8_10 | 4.18.0-553.16.1.el8_10 |
kernel-abi-stablelistsAlmaLinux:8 From an advisory covering 160 CVEs |
before 4.18.0-553.16.1.el8_10 | 4.18.0-553.16.1.el8_10 |
kernel-coreAlmaLinux:8 From an advisory covering 160 CVEs |
before 4.18.0-553.16.1.el8_10 | 4.18.0-553.16.1.el8_10 |
kernel-cross-headersAlmaLinux:8 From an advisory covering 160 CVEs |
before 4.18.0-553.16.1.el8_10 | 4.18.0-553.16.1.el8_10 |
kernel-debugAlmaLinux:8 From an advisory covering 160 CVEs |
before 4.18.0-553.16.1.el8_10 | 4.18.0-553.16.1.el8_10 |
kernel-debug-coreAlmaLinux:8 From an advisory covering 160 CVEs |
before 4.18.0-553.16.1.el8_10 | 4.18.0-553.16.1.el8_10 |
kernel-debug-develAlmaLinux:8 From an advisory covering 160 CVEs |
before 4.18.0-553.16.1.el8_10 | 4.18.0-553.16.1.el8_10 |
kernel-debug-modulesAlmaLinux:8 From an advisory covering 160 CVEs |
before 4.18.0-553.16.1.el8_10 | 4.18.0-553.16.1.el8_10 |
kernel-debug-modules-extraAlmaLinux:8 From an advisory covering 160 CVEs |
before 4.18.0-553.16.1.el8_10 | 4.18.0-553.16.1.el8_10 |
Show 290 moreShow less
| Package | Affected | Fixed |
|---|---|---|
kernel-develAlmaLinux:8 From an advisory covering 160 CVEs |
before 4.18.0-553.16.1.el8_10 | 4.18.0-553.16.1.el8_10 |
kernel-docAlmaLinux:8 From an advisory covering 160 CVEs |
before 4.18.0-553.16.1.el8_10 | 4.18.0-553.16.1.el8_10 |
kernel-headersAlmaLinux:8 From an advisory covering 160 CVEs |
before 4.18.0-553.16.1.el8_10 | 4.18.0-553.16.1.el8_10 |
kernel-modulesAlmaLinux:8 From an advisory covering 160 CVEs |
before 4.18.0-553.16.1.el8_10 | 4.18.0-553.16.1.el8_10 |
kernel-modules-extraAlmaLinux:8 From an advisory covering 160 CVEs |
before 4.18.0-553.16.1.el8_10 | 4.18.0-553.16.1.el8_10 |
kernel-toolsAlmaLinux:8 From an advisory covering 160 CVEs |
before 4.18.0-553.16.1.el8_10 | 4.18.0-553.16.1.el8_10 |
kernel-tools-libsAlmaLinux:8 From an advisory covering 160 CVEs |
before 4.18.0-553.16.1.el8_10 | 4.18.0-553.16.1.el8_10 |
kernel-tools-libs-develAlmaLinux:8 From an advisory covering 160 CVEs |
before 4.18.0-553.16.1.el8_10 | 4.18.0-553.16.1.el8_10 |
kernel-zfcpdumpAlmaLinux:8 From an advisory covering 160 CVEs |
before 4.18.0-553.16.1.el8_10 | 4.18.0-553.16.1.el8_10 |
kernel-zfcpdump-coreAlmaLinux:8 From an advisory covering 160 CVEs |
before 4.18.0-553.16.1.el8_10 | 4.18.0-553.16.1.el8_10 |
kernel-zfcpdump-develAlmaLinux:8 From an advisory covering 160 CVEs |
before 4.18.0-553.16.1.el8_10 | 4.18.0-553.16.1.el8_10 |
kernel-zfcpdump-modulesAlmaLinux:8 From an advisory covering 160 CVEs |
before 4.18.0-553.16.1.el8_10 | 4.18.0-553.16.1.el8_10 |
kernel-zfcpdump-modules-extraAlmaLinux:8 From an advisory covering 160 CVEs |
before 4.18.0-553.16.1.el8_10 | 4.18.0-553.16.1.el8_10 |
perfAlmaLinux:8 From an advisory covering 160 CVEs |
before 4.18.0-553.16.1.el8_10 | 4.18.0-553.16.1.el8_10 |
python3-perfAlmaLinux:8 From an advisory covering 160 CVEs |
before 4.18.0-553.16.1.el8_10 | 4.18.0-553.16.1.el8_10 |
kernel-rtAlmaLinux:8 From an advisory covering 149 CVEs |
before 4.18.0-553.16.1.rt7.357.el8_10 | 4.18.0-553.16.1.rt7.357.el8_10 |
kernel-rt-coreAlmaLinux:8 From an advisory covering 149 CVEs |
before 4.18.0-553.16.1.rt7.357.el8_10 | 4.18.0-553.16.1.rt7.357.el8_10 |
kernel-rt-debugAlmaLinux:8 From an advisory covering 149 CVEs |
before 4.18.0-553.16.1.rt7.357.el8_10 | 4.18.0-553.16.1.rt7.357.el8_10 |
kernel-rt-debug-coreAlmaLinux:8 From an advisory covering 149 CVEs |
before 4.18.0-553.16.1.rt7.357.el8_10 | 4.18.0-553.16.1.rt7.357.el8_10 |
kernel-rt-debug-develAlmaLinux:8 From an advisory covering 149 CVEs |
before 4.18.0-553.16.1.rt7.357.el8_10 | 4.18.0-553.16.1.rt7.357.el8_10 |
kernel-rt-debug-kvmAlmaLinux:8 From an advisory covering 149 CVEs |
before 4.18.0-553.16.1.rt7.357.el8_10 | 4.18.0-553.16.1.rt7.357.el8_10 |
kernel-rt-debug-modulesAlmaLinux:8 From an advisory covering 149 CVEs |
before 4.18.0-553.16.1.rt7.357.el8_10 | 4.18.0-553.16.1.rt7.357.el8_10 |
kernel-rt-debug-modules-extraAlmaLinux:8 From an advisory covering 149 CVEs |
before 4.18.0-553.16.1.rt7.357.el8_10 | 4.18.0-553.16.1.rt7.357.el8_10 |
kernel-rt-develAlmaLinux:8 From an advisory covering 149 CVEs |
before 4.18.0-553.16.1.rt7.357.el8_10 | 4.18.0-553.16.1.rt7.357.el8_10 |
kernel-rt-kvmAlmaLinux:8 From an advisory covering 149 CVEs |
before 4.18.0-553.16.1.rt7.357.el8_10 | 4.18.0-553.16.1.rt7.357.el8_10 |
kernel-rt-modulesAlmaLinux:8 From an advisory covering 149 CVEs |
before 4.18.0-553.16.1.rt7.357.el8_10 | 4.18.0-553.16.1.rt7.357.el8_10 |
kernel-rt-modules-extraAlmaLinux:8 From an advisory covering 149 CVEs |
before 4.18.0-553.16.1.rt7.357.el8_10 | 4.18.0-553.16.1.rt7.357.el8_10 |
kernelAzure Linux:2 |
through 5.15.200.1-1 | None known |
linux-ltsAlpaquita:23 |
6.1.74-r0 up to 6.1.81-r0 | 6.1.81-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 |
libbpfTuxCare:AlmaLinux:9.2 From an advisory covering 305 CVEs |
before 2:1.0.0-2.el9_2.tuxcare.11.els8 | 2:1.0.0-2.el9_2.tuxcare.11.els8 |
libbpf-develTuxCare:AlmaLinux:9.2 From an advisory covering 305 CVEs |
before 2:1.0.0-2.el9_2.tuxcare.11.els8 | 2:1.0.0-2.el9_2.tuxcare.11.els8 |
libbpf-staticTuxCare:AlmaLinux:9.2 From an advisory covering 305 CVEs |
before 2:1.0.0-2.el9_2.tuxcare.11.els8 | 2:1.0.0-2.el9_2.tuxcare.11.els8 |
perfTuxCare: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 |
python3-perfTuxCare: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 |
rtlaTuxCare: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.13.0 up to 6.1.80, 6.2.0 up to 6.6.19, 6.7.0 up to 6.7.7 | 6.1.806.6.196.7.7 |
linuxDebian:12 |
before 6.1.82-1, plus listed versions 6.1.27-16.1.37-16.1.38-16.1.38-26.1.38-2~bpo11+1 Show 13 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+1 |
6.1.82-1 |
linuxDebian:13 |
before 6.7.7-1 | 6.7.7-1 |
linuxDebian:14 |
before 6.7.7-1 | 6.7.7-1 |
bpftoolRed Hat:enterprise_linux:8::baseos From an advisory covering 170 CVEs |
before 0:4.18.0-553.16.1.el8_10 | 0:4.18.0-553.16.1.el8_10 |
bpftool-debuginfoRed Hat:enterprise_linux:8::baseos From an advisory covering 170 CVEs |
before 0:4.18.0-553.16.1.el8_10 | 0:4.18.0-553.16.1.el8_10 |
kernelRed Hat:enterprise_linux:8::baseos From an advisory covering 170 CVEs |
before 0:4.18.0-553.16.1.el8_10 | 0:4.18.0-553.16.1.el8_10 |
kernel-abi-stablelistsRed Hat:enterprise_linux:8::baseos From an advisory covering 170 CVEs |
before 0:4.18.0-553.16.1.el8_10 | 0:4.18.0-553.16.1.el8_10 |
kernel-coreRed Hat:enterprise_linux:8::baseos From an advisory covering 170 CVEs |
before 0:4.18.0-553.16.1.el8_10 | 0:4.18.0-553.16.1.el8_10 |
kernel-debugRed Hat:enterprise_linux:8::baseos From an advisory covering 170 CVEs |
before 0:4.18.0-553.16.1.el8_10 | 0:4.18.0-553.16.1.el8_10 |
kernel-debug-coreRed Hat:enterprise_linux:8::baseos From an advisory covering 170 CVEs |
before 0:4.18.0-553.16.1.el8_10 | 0:4.18.0-553.16.1.el8_10 |
kernel-debug-debuginfoRed Hat:enterprise_linux:8::baseos From an advisory covering 170 CVEs |
before 0:4.18.0-553.16.1.el8_10 | 0:4.18.0-553.16.1.el8_10 |
kernel-debug-develRed Hat:enterprise_linux:8::baseos From an advisory covering 170 CVEs |
before 0:4.18.0-553.16.1.el8_10 | 0:4.18.0-553.16.1.el8_10 |
kernel-debug-modulesRed Hat:enterprise_linux:8::baseos From an advisory covering 170 CVEs |
before 0:4.18.0-553.16.1.el8_10 | 0:4.18.0-553.16.1.el8_10 |
kernel-debug-modules-extraRed Hat:enterprise_linux:8::baseos From an advisory covering 170 CVEs |
before 0:4.18.0-553.16.1.el8_10 | 0:4.18.0-553.16.1.el8_10 |
kernel-debuginfoRed Hat:enterprise_linux:8::baseos From an advisory covering 170 CVEs |
before 0:4.18.0-553.16.1.el8_10 | 0:4.18.0-553.16.1.el8_10 |
kernel-debuginfo-common-aarch64Red Hat:enterprise_linux:8::baseos From an advisory covering 170 CVEs |
before 0:4.18.0-553.16.1.el8_10 | 0:4.18.0-553.16.1.el8_10 |
kernel-debuginfo-common-ppc64leRed Hat:enterprise_linux:8::baseos From an advisory covering 170 CVEs |
before 0:4.18.0-553.16.1.el8_10 | 0:4.18.0-553.16.1.el8_10 |
kernel-debuginfo-common-s390xRed Hat:enterprise_linux:8::baseos From an advisory covering 170 CVEs |
before 0:4.18.0-553.16.1.el8_10 | 0:4.18.0-553.16.1.el8_10 |
kernel-debuginfo-common-x86_64Red Hat:enterprise_linux:8::baseos From an advisory covering 170 CVEs |
before 0:4.18.0-553.16.1.el8_10 | 0:4.18.0-553.16.1.el8_10 |
kernel-develRed Hat:enterprise_linux:8::baseos From an advisory covering 170 CVEs |
before 0:4.18.0-553.16.1.el8_10 | 0:4.18.0-553.16.1.el8_10 |
kernel-docRed Hat:enterprise_linux:8::baseos From an advisory covering 170 CVEs |
before 0:4.18.0-553.16.1.el8_10 | 0:4.18.0-553.16.1.el8_10 |
kernel-modulesRed Hat:enterprise_linux:8::baseos From an advisory covering 170 CVEs |
before 0:4.18.0-553.16.1.el8_10 | 0:4.18.0-553.16.1.el8_10 |
kernel-modules-extraRed Hat:enterprise_linux:8::baseos From an advisory covering 170 CVEs |
before 0:4.18.0-553.16.1.el8_10 | 0:4.18.0-553.16.1.el8_10 |
kernel-toolsRed Hat:enterprise_linux:8::baseos From an advisory covering 170 CVEs |
before 0:4.18.0-553.16.1.el8_10 | 0:4.18.0-553.16.1.el8_10 |
kernel-tools-debuginfoRed Hat:enterprise_linux:8::baseos From an advisory covering 170 CVEs |
before 0:4.18.0-553.16.1.el8_10 | 0:4.18.0-553.16.1.el8_10 |
kernel-tools-libsRed Hat:enterprise_linux:8::baseos From an advisory covering 170 CVEs |
before 0:4.18.0-553.16.1.el8_10 | 0:4.18.0-553.16.1.el8_10 |
kernel-zfcpdumpRed Hat:enterprise_linux:8::baseos From an advisory covering 170 CVEs |
before 0:4.18.0-553.16.1.el8_10 | 0:4.18.0-553.16.1.el8_10 |
kernel-zfcpdump-coreRed Hat:enterprise_linux:8::baseos From an advisory covering 170 CVEs |
before 0:4.18.0-553.16.1.el8_10 | 0:4.18.0-553.16.1.el8_10 |
kernel-zfcpdump-debuginfoRed Hat:enterprise_linux:8::baseos From an advisory covering 170 CVEs |
before 0:4.18.0-553.16.1.el8_10 | 0:4.18.0-553.16.1.el8_10 |
kernel-zfcpdump-develRed Hat:enterprise_linux:8::baseos From an advisory covering 170 CVEs |
before 0:4.18.0-553.16.1.el8_10 | 0:4.18.0-553.16.1.el8_10 |
kernel-zfcpdump-modulesRed Hat:enterprise_linux:8::baseos From an advisory covering 170 CVEs |
before 0:4.18.0-553.16.1.el8_10 | 0:4.18.0-553.16.1.el8_10 |
kernel-zfcpdump-modules-extraRed Hat:enterprise_linux:8::baseos From an advisory covering 170 CVEs |
before 0:4.18.0-553.16.1.el8_10 | 0:4.18.0-553.16.1.el8_10 |
perfRed Hat:enterprise_linux:8::baseos From an advisory covering 170 CVEs |
before 0:4.18.0-553.16.1.el8_10 | 0:4.18.0-553.16.1.el8_10 |
perf-debuginfoRed Hat:enterprise_linux:8::baseos From an advisory covering 170 CVEs |
before 0:4.18.0-553.16.1.el8_10 | 0:4.18.0-553.16.1.el8_10 |
python3-perfRed Hat:enterprise_linux:8::baseos From an advisory covering 170 CVEs |
before 0:4.18.0-553.16.1.el8_10 | 0:4.18.0-553.16.1.el8_10 |
python3-perf-debuginfoRed Hat:enterprise_linux:8::baseos From an advisory covering 170 CVEs |
before 0:4.18.0-553.16.1.el8_10 | 0:4.18.0-553.16.1.el8_10 |
bpftool-debuginfoRed Hat:enterprise_linux:8::crb From an advisory covering 170 CVEs |
before 0:4.18.0-553.16.1.el8_10 | 0:4.18.0-553.16.1.el8_10 |
kernel-debug-debuginfoRed Hat:enterprise_linux:8::crb From an advisory covering 170 CVEs |
before 0:4.18.0-553.16.1.el8_10 | 0:4.18.0-553.16.1.el8_10 |
kernel-debuginfoRed Hat:enterprise_linux:8::crb From an advisory covering 170 CVEs |
before 0:4.18.0-553.16.1.el8_10 | 0:4.18.0-553.16.1.el8_10 |
kernel-debuginfo-common-aarch64Red Hat:enterprise_linux:8::crb From an advisory covering 170 CVEs |
before 0:4.18.0-553.16.1.el8_10 | 0:4.18.0-553.16.1.el8_10 |
kernel-debuginfo-common-ppc64leRed Hat:enterprise_linux:8::crb From an advisory covering 170 CVEs |
before 0:4.18.0-553.16.1.el8_10 | 0:4.18.0-553.16.1.el8_10 |
kernel-debuginfo-common-x86_64Red Hat:enterprise_linux:8::crb From an advisory covering 170 CVEs |
before 0:4.18.0-553.16.1.el8_10 | 0:4.18.0-553.16.1.el8_10 |
kernel-tools-debuginfoRed Hat:enterprise_linux:8::crb From an advisory covering 170 CVEs |
before 0:4.18.0-553.16.1.el8_10 | 0:4.18.0-553.16.1.el8_10 |
kernel-tools-libs-develRed Hat:enterprise_linux:8::crb From an advisory covering 170 CVEs |
before 0:4.18.0-553.16.1.el8_10 | 0:4.18.0-553.16.1.el8_10 |
perf-debuginfoRed Hat:enterprise_linux:8::crb From an advisory covering 170 CVEs |
before 0:4.18.0-553.16.1.el8_10 | 0:4.18.0-553.16.1.el8_10 |
python3-perf-debuginfoRed Hat:enterprise_linux:8::crb From an advisory covering 170 CVEs |
before 0:4.18.0-553.16.1.el8_10 | 0:4.18.0-553.16.1.el8_10 |
kernel-rtRed Hat:enterprise_linux:8::nfv From an advisory covering 149 CVEs |
before 0:4.18.0-553.16.1.rt7.357.el8_10 | 0:4.18.0-553.16.1.rt7.357.el8_10 |
kernel-rt-coreRed Hat:enterprise_linux:8::nfv From an advisory covering 149 CVEs |
before 0:4.18.0-553.16.1.rt7.357.el8_10 | 0:4.18.0-553.16.1.rt7.357.el8_10 |
kernel-rt-debugRed Hat:enterprise_linux:8::nfv From an advisory covering 149 CVEs |
before 0:4.18.0-553.16.1.rt7.357.el8_10 | 0:4.18.0-553.16.1.rt7.357.el8_10 |
kernel-rt-debug-coreRed Hat:enterprise_linux:8::nfv From an advisory covering 149 CVEs |
before 0:4.18.0-553.16.1.rt7.357.el8_10 | 0:4.18.0-553.16.1.rt7.357.el8_10 |
kernel-rt-debug-debuginfoRed Hat:enterprise_linux:8::nfv From an advisory covering 149 CVEs |
before 0:4.18.0-553.16.1.rt7.357.el8_10 | 0:4.18.0-553.16.1.rt7.357.el8_10 |
kernel-rt-debug-develRed Hat:enterprise_linux:8::nfv From an advisory covering 149 CVEs |
before 0:4.18.0-553.16.1.rt7.357.el8_10 | 0:4.18.0-553.16.1.rt7.357.el8_10 |
kernel-rt-debug-kvmRed Hat:enterprise_linux:8::nfv From an advisory covering 149 CVEs |
before 0:4.18.0-553.16.1.rt7.357.el8_10 | 0:4.18.0-553.16.1.rt7.357.el8_10 |
kernel-rt-debug-modulesRed Hat:enterprise_linux:8::nfv From an advisory covering 149 CVEs |
before 0:4.18.0-553.16.1.rt7.357.el8_10 | 0:4.18.0-553.16.1.rt7.357.el8_10 |
kernel-rt-debug-modules-extraRed Hat:enterprise_linux:8::nfv From an advisory covering 149 CVEs |
before 0:4.18.0-553.16.1.rt7.357.el8_10 | 0:4.18.0-553.16.1.rt7.357.el8_10 |
kernel-rt-debuginfoRed Hat:enterprise_linux:8::nfv From an advisory covering 149 CVEs |
before 0:4.18.0-553.16.1.rt7.357.el8_10 | 0:4.18.0-553.16.1.rt7.357.el8_10 |
kernel-rt-debuginfo-common-x86_64Red Hat:enterprise_linux:8::nfv From an advisory covering 149 CVEs |
before 0:4.18.0-553.16.1.rt7.357.el8_10 | 0:4.18.0-553.16.1.rt7.357.el8_10 |
kernel-rt-develRed Hat:enterprise_linux:8::nfv From an advisory covering 149 CVEs |
before 0:4.18.0-553.16.1.rt7.357.el8_10 | 0:4.18.0-553.16.1.rt7.357.el8_10 |
kernel-rt-kvmRed Hat:enterprise_linux:8::nfv From an advisory covering 149 CVEs |
before 0:4.18.0-553.16.1.rt7.357.el8_10 | 0:4.18.0-553.16.1.rt7.357.el8_10 |
kernel-rt-modulesRed Hat:enterprise_linux:8::nfv From an advisory covering 149 CVEs |
before 0:4.18.0-553.16.1.rt7.357.el8_10 | 0:4.18.0-553.16.1.rt7.357.el8_10 |
kernelRocky Linux:8 From an advisory covering 160 CVEs |
before 0:4.18.0-553.16.1.el8_10 | 0:4.18.0-553.16.1.el8_10 |
kernel-rtRocky Linux:8 From an advisory covering 149 CVEs |
before 0:4.18.0-553.16.1.rt7.357.el8_10 | 0:4.18.0-553.16.1.rt7.357.el8_10 |
kernelRocky Linux:8 From an advisory covering 160 CVEs |
before 0:4.18.0-553.16.1.el8_10.cloud.0.1 | 0:4.18.0-553.16.1.el8_10.cloud.0.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-64kbSUSE:Linux Enterprise Module for Basesystem 15 SP6 From an advisory covering 394 CVEs |
before 6.4.0-150600.23.22.1 | 6.4.0-150600.23.22.1 |
kernel-defaultSUSE:Linux Enterprise Module for Basesystem 15 SP6 From an advisory covering 394 CVEs |
before 6.4.0-150600.23.22.1 | 6.4.0-150600.23.22.1 |
kernel-default-baseSUSE:Linux Enterprise Module for Basesystem 15 SP6 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-sourceSUSE:Linux Enterprise Module for Basesystem 15 SP6 From an advisory covering 394 CVEs |
before 6.4.0-150600.23.22.1 | 6.4.0-150600.23.22.1 |
kernel-zfcpdumpSUSE:Linux Enterprise Module for Basesystem 15 SP6 From an advisory covering 394 CVEs |
before 6.4.0-150600.23.22.1 | 6.4.0-150600.23.22.1 |
kernel-docsSUSE:Linux Enterprise Module for Development Tools 15 SP6 From an advisory covering 394 CVEs |
before 6.4.0-150600.23.22.1 | 6.4.0-150600.23.22.1 |
kernel-obs-buildSUSE:Linux Enterprise Module for Development Tools 15 SP6 From an advisory covering 394 CVEs |
before 6.4.0-150600.23.22.1 | 6.4.0-150600.23.22.1 |
kernel-sourceSUSE:Linux Enterprise Module for Development Tools 15 SP6 From an advisory covering 394 CVEs |
before 6.4.0-150600.23.22.1 | 6.4.0-150600.23.22.1 |
kernel-symsSUSE:Linux Enterprise Module for Development Tools 15 SP6 From an advisory covering 394 CVEs |
before 6.4.0-150600.23.22.1 | 6.4.0-150600.23.22.1 |
kernel-defaultSUSE:Linux Enterprise Module for Legacy 15 SP6 From an advisory covering 394 CVEs |
before 6.4.0-150600.23.22.1 | 6.4.0-150600.23.22.1 |
kernel-defaultSUSE:Linux Enterprise Live Patching 15 SP6 From an advisory covering 394 CVEs |
before 6.4.0-150600.23.22.1 | 6.4.0-150600.23.22.1 |
kernel-livepatch-SLE15-SP6_Update_4SUSE:Linux Enterprise Live Patching 15 SP6 From an advisory covering 394 CVEs |
before 1-150600.13.3.3 | 1-150600.13.3.3 |
kernel-defaultSUSE:Linux Enterprise High Availability Extension 15 SP6 From an advisory covering 394 CVEs |
before 6.4.0-150600.23.22.1 | 6.4.0-150600.23.22.1 |
kernel-defaultSUSE:Linux Enterprise Workstation Extension 15 SP6 From an advisory covering 394 CVEs |
before 6.4.0-150600.23.22.1 | 6.4.0-150600.23.22.1 |
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 |
kernel-symsopenSUSE: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-zfcpdumpopenSUSE: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-defaultSUSE:Linux Enterprise Micro 5.5 From an advisory covering 130 CVEs |
before 5.14.21-150500.55.83.1 | 5.14.21-150500.55.83.1 |
kernel-default-baseSUSE:Linux Enterprise Micro 5.5 From an advisory covering 130 CVEs |
before 5.14.21-150500.55.83.1.150500.6.37.1 | 5.14.21-150500.55.83.1.150500.6.37.1 |
kernel-64kbSUSE:Linux Enterprise Module for Basesystem 15 SP5 From an advisory covering 130 CVEs |
before 5.14.21-150500.55.83.1 | 5.14.21-150500.55.83.1 |
kernel-defaultSUSE:Linux Enterprise Module for Basesystem 15 SP5 From an advisory covering 130 CVEs |
before 5.14.21-150500.55.83.1 | 5.14.21-150500.55.83.1 |
kernel-default-baseSUSE:Linux Enterprise Module for Basesystem 15 SP5 From an advisory covering 130 CVEs |
before 5.14.21-150500.55.83.1.150500.6.37.1 | 5.14.21-150500.55.83.1.150500.6.37.1 |
kernel-sourceSUSE:Linux Enterprise Module for Basesystem 15 SP5 From an advisory covering 130 CVEs |
before 5.14.21-150500.55.83.1 | 5.14.21-150500.55.83.1 |
kernel-zfcpdumpSUSE:Linux Enterprise Module for Basesystem 15 SP5 From an advisory covering 130 CVEs |
before 5.14.21-150500.55.83.1 | 5.14.21-150500.55.83.1 |
kernel-docsSUSE:Linux Enterprise Module for Development Tools 15 SP5 From an advisory covering 130 CVEs |
before 5.14.21-150500.55.83.1 | 5.14.21-150500.55.83.1 |
kernel-obs-buildSUSE:Linux Enterprise Module for Development Tools 15 SP5 From an advisory covering 130 CVEs |
before 5.14.21-150500.55.83.1 | 5.14.21-150500.55.83.1 |
kernel-sourceSUSE:Linux Enterprise Module for Development Tools 15 SP5 From an advisory covering 130 CVEs |
before 5.14.21-150500.55.83.1 | 5.14.21-150500.55.83.1 |
kernel-symsSUSE:Linux Enterprise Module for Development Tools 15 SP5 From an advisory covering 130 CVEs |
before 5.14.21-150500.55.83.1 | 5.14.21-150500.55.83.1 |
kernel-defaultSUSE:Linux Enterprise Module for Legacy 15 SP5 From an advisory covering 130 CVEs |
before 5.14.21-150500.55.83.1 | 5.14.21-150500.55.83.1 |
kernel-defaultSUSE:Linux Enterprise Live Patching 15 SP5 From an advisory covering 130 CVEs |
before 5.14.21-150500.55.83.1 | 5.14.21-150500.55.83.1 |
kernel-livepatch-SLE15-SP5_Update_20SUSE:Linux Enterprise Live Patching 15 SP5 From an advisory covering 130 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 130 CVEs |
before 5.14.21-150500.55.83.1 | 5.14.21-150500.55.83.1 |
kernel-defaultSUSE:Linux Enterprise Workstation Extension 15 SP5 From an advisory covering 130 CVEs |
before 5.14.21-150500.55.83.1 | 5.14.21-150500.55.83.1 |
kernel-defaultopenSUSE:Leap Micro 5.5 From an advisory covering 130 CVEs |
before 5.14.21-150500.55.83.1 | 5.14.21-150500.55.83.1 |
kernel-default-baseopenSUSE:Leap Micro 5.5 From an advisory covering 130 CVEs |
before 5.14.21-150500.55.83.1.150500.6.37.1 | 5.14.21-150500.55.83.1.150500.6.37.1 |
kernel-azureSUSE:Linux Enterprise Module for Public Cloud 15 SP5 From an advisory covering 132 CVEs |
before 5.14.21-150500.33.69.1 | 5.14.21-150500.33.69.1 |
kernel-source-azureSUSE:Linux Enterprise Module for Public Cloud 15 SP5 From an advisory covering 132 CVEs |
before 5.14.21-150500.33.69.1 | 5.14.21-150500.33.69.1 |
kernel-syms-azureSUSE:Linux Enterprise Module for Public Cloud 15 SP5 From an advisory covering 132 CVEs |
before 5.14.21-150500.33.69.1 | 5.14.21-150500.33.69.1 |
kernel-azureopenSUSE:Leap 15.5 From an advisory covering 132 CVEs |
before 5.14.21-150500.33.69.1 | 5.14.21-150500.33.69.1 |
kernel-source-azureopenSUSE:Leap 15.5 From an advisory covering 132 CVEs |
before 5.14.21-150500.33.69.1 | 5.14.21-150500.33.69.1 |
kernel-syms-azureopenSUSE:Leap 15.5 From an advisory covering 132 CVEs |
before 5.14.21-150500.33.69.1 | 5.14.21-150500.33.69.1 |
kernel-rtSUSE:Linux Enterprise Micro 5.5 From an advisory covering 130 CVEs |
before 5.14.21-150500.13.73.1 | 5.14.21-150500.13.73.1 |
kernel-source-rtSUSE:Linux Enterprise Micro 5.5 From an advisory covering 130 CVEs |
before 5.14.21-150500.13.73.1 | 5.14.21-150500.13.73.1 |
kernel-livepatch-SLE15-SP5-RT_Update_21SUSE:Linux Enterprise Live Patching 15 SP5 From an advisory covering 130 CVEs |
before 1-150500.11.3.1 | 1-150500.11.3.1 |
kernel-rtSUSE:Real Time Module 15 SP5 From an advisory covering 130 CVEs |
before 5.14.21-150500.13.73.1 | 5.14.21-150500.13.73.1 |
kernel-rt_debugSUSE:Real Time Module 15 SP5 From an advisory covering 130 CVEs |
before 5.14.21-150500.13.73.1 | 5.14.21-150500.13.73.1 |
kernel-source-rtSUSE:Real Time Module 15 SP5 From an advisory covering 130 CVEs |
before 5.14.21-150500.13.73.1 | 5.14.21-150500.13.73.1 |
kernel-syms-rtSUSE:Real Time Module 15 SP5 From an advisory covering 130 CVEs |
before 5.14.21-150500.13.73.1 | 5.14.21-150500.13.73.1 |
kernel-rtopenSUSE:Leap Micro 5.5 From an advisory covering 130 CVEs |
before 5.14.21-150500.13.73.1 | 5.14.21-150500.13.73.1 |
kernel-rtopenSUSE:Leap 15.5 From an advisory covering 130 CVEs |
before 5.14.21-150500.13.73.1 | 5.14.21-150500.13.73.1 |
kernel-rt_debugopenSUSE:Leap 15.5 From an advisory covering 130 CVEs |
before 5.14.21-150500.13.73.1 | 5.14.21-150500.13.73.1 |
kernel-source-rtopenSUSE:Leap 15.5 From an advisory covering 130 CVEs |
before 5.14.21-150500.13.73.1 | 5.14.21-150500.13.73.1 |
kernel-syms-rtopenSUSE:Leap 15.5 From an advisory covering 130 CVEs |
before 5.14.21-150500.13.73.1 | 5.14.21-150500.13.73.1 |
kernel-defaultSUSE:Linux Micro 6.0 From an advisory covering 383 CVEs |
before 6.4.0-19.1 | 6.4.0-19.1 |
kernel-default-baseSUSE:Linux Micro 6.0 From an advisory covering 383 CVEs |
before 6.4.0-17.1.1.51 | 6.4.0-17.1.1.51 |
kernel-kvmsmallSUSE:Linux Micro 6.0 From an advisory covering 383 CVEs |
before 6.4.0-19.1 | 6.4.0-19.1 |
kernel-livepatch-MICRO-6-0_Update_2SUSE:Linux Micro 6.0 From an advisory covering 383 CVEs |
before 1-1.1 | 1-1.1 |
kernel-sourceSUSE:Linux Micro 6.0 From an advisory covering 383 CVEs |
before 6.4.0-19.1 | 6.4.0-19.1 |
kernel-livepatch-MICRO-6-0-RT_Update_2SUSE:Linux Micro 6.0 From an advisory covering 383 CVEs |
before 1-1.1 | 1-1.1 |
kernel-rtSUSE:Linux Micro 6.0 From an advisory covering 383 CVEs |
before 6.4.0-10.1 | 6.4.0-10.1 |
kernel-source-rtSUSE:Linux Micro 6.0 From an advisory covering 383 CVEs |
before 6.4.0-10.1 | 6.4.0-10.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-1082.89~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 45 moreShow less5.15.0-1021.25~20.04.15.15.0-1022.26~20.04.15.15.0-1023.27~20.04.15.15.0-1026.30~20.04.25.15.0-1027.31~20.04.15.15.0-1028.32~20.04.15.15.0-1030.34~20.04.15.15.0-1031.35~20.04.15.15.0-1033.37~20.04.15.15.0-1034.38~20.04.15.15.0-1035.39~20.04.15.15.0-1036.40~20.04.15.15.0-1037.41~20.04.15.15.0-1038.43~20.04.15.15.0-1039.44~20.04.15.15.0-1040.45~20.04.15.15.0-1041.46~20.04.15.15.0-1043.48~20.04.15.15.0-1044.49~20.04.15.15.0-1045.50~20.04.15.15.0-1047.52~20.04.15.15.0-1048.53~20.04.15.15.0-1049.54~20.04.15.15.0-1050.55~20.04.15.15.0-1051.56~20.04.15.15.0-1052.57~20.04.15.15.0-1053.58~20.04.15.15.0-1055.60~20.04.15.15.0-1056.61~20.04.15.15.0-1057.63~20.04.15.15.0-1058.64~20.04.15.15.0-1061.67~20.04.15.15.0-1062.68~20.04.15.15.0-1063.69~20.04.15.15.0-1064.70~20.04.15.15.0-1065.71~20.04.15.15.0-1066.72~20.04.15.15.0-1067.73~20.04.15.15.0-1068.74~20.04.15.15.0-1069.75~20.04.15.15.0-1070.76~20.04.15.15.0-1071.77~20.04.15.15.0-1072.78~20.04.15.15.0-1073.79~20.04.15.15.0-1075.82~20.04.1 |
5.15.0-1082.89~20.04.1 |
linux-azure-5.15Ubuntu:20.04:LTS |
before 5.15.0-1087.96~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 45 moreShow less5.15.0-1019.24~20.04.15.15.0-1020.25~20.04.15.15.0-1021.26~20.04.15.15.0-1022.27~20.04.15.15.0-1023.29~20.04.15.15.0-1029.36~20.04.15.15.0-1030.37~20.04.15.15.0-1031.38~20.04.15.15.0-1033.40~20.04.15.15.0-1034.41~20.04.15.15.0-1035.42~20.04.15.15.0-1036.43~20.04.15.15.0-1037.44~20.04.15.15.0-1038.45~20.04.15.15.0-1039.46~20.04.15.15.0-1040.47~20.04.15.15.0-1041.48~20.04.15.15.0-1042.49~20.04.15.15.0-1043.50~20.04.15.15.0-1045.52~20.04.15.15.0-1046.53~20.04.15.15.0-1047.54~20.04.15.15.0-1049.56~20.04.15.15.0-1050.57~20.04.15.15.0-1051.59~20.04.15.15.0-1052.60~20.04.15.15.0-1053.61~20.04.15.15.0-1054.62~20.04.15.15.0-1056.64~20.04.15.15.0-1057.65~20.04.15.15.0-1058.66~20.04.25.15.0-1059.67~20.04.15.15.0-1060.69~20.04.15.15.0-1061.70~20.04.15.15.0-1063.72~20.04.15.15.0-1064.73~20.04.15.15.0-1065.74~20.04.15.15.0-1067.76~20.04.15.15.0-1068.77~20.04.15.15.0-1070.79~20.04.15.15.0-1071.80~20.04.15.15.0-1072.81~20.04.15.15.0-1073.82~20.04.15.15.0-1074.83~20.04.15.15.0-1075.84~20.04.1 |
5.15.0-1087.96~20.04.1 |
linux-gcp-5.15Ubuntu:20.04:LTS |
before 5.15.0-1081.90~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 45 moreShow less5.15.0-1018.24~20.04.15.15.0-1021.28~20.04.15.15.0-1022.29~20.04.15.15.0-1025.32~20.04.25.15.0-1026.33~20.04.15.15.0-1027.34~20.04.15.15.0-1029.36~20.04.15.15.0-1030.37~20.04.15.15.0-1031.38~20.04.15.15.0-1032.40~20.04.15.15.0-1033.41~20.04.15.15.0-1034.42~20.04.15.15.0-1035.43~20.04.15.15.0-1036.44~20.04.15.15.0-1037.45~20.04.15.15.0-1038.46~20.04.15.15.0-1039.47~20.04.15.15.0-1040.48~20.04.15.15.0-1041.49~20.04.15.15.0-1042.50~20.04.15.15.0-1044.52~20.04.15.15.0-1045.53~20.04.25.15.0-1046.54~20.04.15.15.0-1047.55~20.04.15.15.0-1048.56~20.04.15.15.0-1049.57~20.04.15.15.0-1051.59~20.04.15.15.0-1052.60~20.04.15.15.0-1053.61~20.04.15.15.0-1054.62~20.04.15.15.0-1055.63~20.04.15.15.0-1058.66~20.04.15.15.0-1059.67~20.04.15.15.0-1060.68~20.04.15.15.0-1062.70~20.04.15.15.0-1065.73~20.04.15.15.0-1066.74~20.04.15.15.0-1067.75~20.04.15.15.0-1068.76~20.04.15.15.0-1069.77~20.04.15.15.0-1070.78~20.04.15.15.0-1071.79~20.04.15.15.0-1072.80~20.04.15.15.0-1073.81~20.04.15.15.0-1074.83~20.04.1 |
5.15.0-1081.90~20.04.1 |
linux-hwe-5.15Ubuntu:20.04:LTS |
before 5.15.0-138.148~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 45 moreShow less5.15.0-50.56~20.04.15.15.0-52.58~20.04.15.15.0-53.59~20.04.15.15.0-56.62~20.04.15.15.0-57.63~20.04.15.15.0-58.64~20.04.15.15.0-60.66~20.04.15.15.0-67.74~20.04.15.15.0-69.76~20.04.15.15.0-70.77~20.04.15.15.0-71.78~20.04.15.15.0-72.79~20.04.15.15.0-73.80~20.04.15.15.0-75.82~20.04.15.15.0-76.83~20.04.15.15.0-78.85~20.04.15.15.0-79.86~20.04.25.15.0-82.91~20.04.15.15.0-83.92~20.04.15.15.0-84.93~20.04.15.15.0-86.96~20.04.15.15.0-87.97~20.04.15.15.0-88.98~20.04.15.15.0-89.99~20.04.15.15.0-91.101~20.04.15.15.0-92.102~20.04.15.15.0-94.104~20.04.15.15.0-97.107~20.04.15.15.0-100.110~20.04.15.15.0-101.111~20.04.15.15.0-102.112~20.04.15.15.0-105.115~20.04.15.15.0-106.116~20.04.15.15.0-107.117~20.04.15.15.0-113.123~20.04.15.15.0-116.126~20.04.15.15.0-117.127~20.04.15.15.0-118.128~20.04.15.15.0-119.129~20.04.15.15.0-121.131~20.04.15.15.0-122.132~20.04.15.15.0-124.134~20.04.15.15.0-125.135~20.04.15.15.0-126.136~20.04.15.15.0-127.137~20.04.1 |
5.15.0-138.148~20.04.1 |
linux-ibm-5.15Ubuntu:20.04:LTS |
before 5.15.0-1074.77~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 28 moreShow less5.15.0-1038.41~20.04.15.15.0-1040.43~20.04.15.15.0-1041.44~20.04.15.15.0-1042.45~20.04.15.15.0-1043.46~20.04.15.15.0-1044.47~20.04.15.15.0-1045.48~20.04.15.15.0-1046.49~20.04.15.15.0-1047.50~20.04.15.15.0-1048.51~20.04.15.15.0-1049.52~20.04.15.15.0-1050.53~20.04.15.15.0-1053.56~20.04.15.15.0-1054.57~20.04.15.15.0-1055.58~20.04.15.15.0-1057.60~20.04.15.15.0-1058.61~20.04.15.15.0-1059.62~20.04.15.15.0-1060.63~20.04.15.15.0-1061.64~20.04.15.15.0-1062.65~20.04.15.15.0-1063.66~20.04.15.15.0-1064.67~20.04.15.15.0-1065.68~20.04.15.15.0-1066.69~20.04.15.15.0-1067.70~20.04.15.15.0-1068.71~20.04.15.15.0-1069.72~20.04.1 |
5.15.0-1074.77~20.04.1 |
linux-intel-iotg-5.15Ubuntu:20.04:LTS |
before 5.15.0-1077.83~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 38 moreShow less5.15.0-1017.22~20.04.15.15.0-1018.23~20.04.15.15.0-1021.26~20.04.15.15.0-1023.28~20.04.15.15.0-1025.30~20.04.15.15.0-1026.31~20.04.15.15.0-1027.32~20.04.15.15.0-1030.35~20.04.15.15.0-1031.36~20.04.15.15.0-1033.38~20.04.15.15.0-1034.39~20.04.15.15.0-1036.41~20.04.15.15.0-1037.42~20.04.15.15.0-1038.43~20.04.15.15.0-1040.46~20.04.15.15.0-1043.49~20.04.15.15.0-1045.51~20.04.15.15.0-1046.52~20.04.15.15.0-1048.54~20.04.15.15.0-1049.55~20.04.15.15.0-1050.56~20.04.15.15.0-1051.57~20.04.15.15.0-1052.58~20.04.15.15.0-1055.61~20.04.15.15.0-1058.64~20.04.15.15.0-1059.65~20.04.15.15.0-1060.66~20.04.15.15.0-1061.67~20.04.15.15.0-1062.68~20.04.15.15.0-1063.69~20.04.15.15.0-1064.70~20.04.15.15.0-1065.71~20.04.15.15.0-1066.72~20.04.15.15.0-1067.73~20.04.15.15.0-1071.77~20.04.15.15.0-1072.78~20.04.15.15.0-1073.79~20.04.25.15.0-1074.80~20.04.1 |
5.15.0-1077.83~20.04.1 |
linux-lowlatency-hwe-5.15Ubuntu:20.04:LTS |
before 5.15.0-138.148~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 45 moreShow less5.15.0-50.56~20.04.15.15.0-52.58~20.04.15.15.0-53.59~20.04.15.15.0-56.62~20.04.15.15.0-58.64~20.04.15.15.0-60.66~20.04.15.15.0-67.74~20.04.15.15.0-69.76~20.04.15.15.0-70.77~20.04.15.15.0-71.78~20.04.15.15.0-72.79~20.04.15.15.0-73.80~20.04.15.15.0-75.82~20.04.15.15.0-76.83~20.04.15.15.0-78.85~20.04.15.15.0-79.88~20.04.15.15.0-82.91~20.04.15.15.0-83.92~20.04.15.15.0-84.93~20.04.15.15.0-86.95~20.04.15.15.0-87.96~20.04.15.15.0-88.98~20.04.15.15.0-89.99~20.04.15.15.0-91.101~20.04.15.15.0-92.102~20.04.15.15.0-94.104~20.04.15.15.0-97.107~20.04.15.15.0-100.110~20.04.15.15.0-101.111~20.04.15.15.0-102.112~20.04.15.15.0-105.115~20.04.15.15.0-106.116~20.04.15.15.0-107.117~20.04.15.15.0-110.120~20.04.15.15.0-113.123~20.04.15.15.0-116.126~20.04.15.15.0-117.127~20.04.15.15.0-118.128~20.04.15.15.0-119.129~20.04.15.15.0-121.131~20.04.15.15.0-122.132~20.04.15.15.0-124.134~20.04.15.15.0-125.135~20.04.15.15.0-126.136~20.04.15.15.0-127.137~20.04.1 |
5.15.0-138.148~20.04.1 |
linux-oracle-5.15Ubuntu:20.04:LTS |
before 5.15.0-1079.85~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 45 moreShow less5.15.0-1019.24~20.04.15.15.0-1021.27~20.04.15.15.0-1022.28~20.04.15.15.0-1025.31~20.04.25.15.0-1027.33~20.04.15.15.0-1029.35~20.04.15.15.0-1030.36~20.04.15.15.0-1032.38~20.04.15.15.0-1033.39~20.04.15.15.0-1034.40~20.04.15.15.0-1035.41~20.04.15.15.0-1036.42~20.04.15.15.0-1037.43~20.04.15.15.0-1038.44~20.04.15.15.0-1039.45~20.04.15.15.0-1040.46~20.04.15.15.0-1041.47~20.04.15.15.0-1042.48~20.04.15.15.0-1044.50~20.04.15.15.0-1045.51~20.04.15.15.0-1046.52~20.04.15.15.0-1047.53~20.04.15.15.0-1048.54~20.04.15.15.0-1049.55~20.04.15.15.0-1050.56~20.04.15.15.0-1051.57~20.04.15.15.0-1052.58~20.04.15.15.0-1053.59~20.04.15.15.0-1054.60~20.04.15.15.0-1055.61~20.04.15.15.0-1058.64~20.04.15.15.0-1059.65~20.04.15.15.0-1061.67~20.04.15.15.0-1062.68~20.04.15.15.0-1063.69~20.04.15.15.0-1065.71~20.04.15.15.0-1066.72~20.04.15.15.0-1067.73~20.04.15.15.0-1068.74~20.04.15.15.0-1069.75~20.04.15.15.0-1070.76~20.04.15.15.0-1071.77~20.04.15.15.0-1072.78~20.04.15.15.0-1073.79~20.04.15.15.0-1074.80~20.04.1 |
5.15.0-1079.85~20.04.1 |
linux-riscv-5.15Ubuntu:20.04:LTS |
before 5.15.0-1077.81~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 45 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.15.15.0-1066.70~20.04.15.15.0-1067.71~20.04.15.15.0-1068.72~20.04.15.15.0-1069.73~20.04.15.15.0-1070.74~20.04.15.15.0-1071.75~20.04.15.15.0-1072.76~20.04.1 |
5.15.0-1077.81~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-gkeop-5.15Ubuntu:20.04:LTS |
All versions, plus listed versions 5.15.0-1003.5~20.04.25.15.0-1005.7~20.04.15.15.0-1007.10~20.04.15.15.0-1008.12~20.04.15.15.0-1011.15~20.04.2 Show 40 moreShow less5.15.0-1012.16~20.04.15.15.0-1013.17~20.04.15.15.0-1015.19~20.04.15.15.0-1016.21~20.04.15.15.0-1017.22~20.04.15.15.0-1018.23~20.04.15.15.0-1019.24~20.04.15.15.0-1020.25~20.04.15.15.0-1021.26~20.04.15.15.0-1022.27~20.04.15.15.0-1023.28~20.04.15.15.0-1024.29~20.04.15.15.0-1025.30~20.04.15.15.0-1026.31~20.04.15.15.0-1027.32~20.04.15.15.0-1028.33~20.04.15.15.0-1030.35~20.04.15.15.0-1031.37~20.04.15.15.0-1032.38~20.04.15.15.0-1033.39~20.04.15.15.0-1034.40~20.04.15.15.0-1035.41~20.04.15.15.0-1036.42~20.04.15.15.0-1037.43~20.04.15.15.0-1038.44~20.04.15.15.0-1039.45~20.04.15.15.0-1040.46~20.04.15.15.0-1043.50~20.04.15.15.0-1044.51~20.04.15.15.0-1045.52~20.04.15.15.0-1046.53~20.04.15.15.0-1047.54~20.04.15.15.0-1048.55~20.04.15.15.0-1049.56~20.04.15.15.0-1050.57~20.04.15.15.0-1051.58~20.04.15.15.0-1052.59~20.04.15.15.0-1053.60~20.04.15.15.0-1054.61~20.04.15.15.0-1055.62~20.04.1 |
None known |
linux-hwe-5.11Ubuntu:20.04:LTS |
All versions, plus listed versions 5.11.0-22.23~20.04.15.11.0-25.27~20.04.15.11.0-27.29~20.04.15.11.0-34.36~20.04.15.11.0-36.40~20.04.1 Show 7 moreShow less5.11.0-37.41~20.04.25.11.0-38.42~20.04.15.11.0-40.44~20.04.25.11.0-41.45~20.04.15.11.0-43.47~20.04.25.11.0-44.48~20.04.25.11.0-46.51~20.04.1 |
None known |
linux-hwe-5.13Ubuntu:20.04:LTS |
All versions, plus listed versions 5.13.0-21.21~20.04.15.13.0-22.22~20.04.15.13.0-23.23~20.04.25.13.0-25.26~20.04.15.13.0-27.29~20.04.1 Show 11 moreShow less5.13.0-28.31~20.04.15.13.0-30.33~20.04.15.13.0-35.40~20.04.15.13.0-37.42~20.04.15.13.0-39.44~20.04.15.13.0-40.45~20.04.15.13.0-41.46~20.04.15.13.0-44.49~20.04.15.13.0-48.54~20.04.15.13.0-51.58~20.04.15.13.0-52.59~20.04.1 |
None known |
linux-hwe-5.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-nvidia-tegra-5.15Ubuntu:Pro:20.04:LTS |
before 5.15.0-1039.39~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 10 moreShow less5.15.0-1016.16~20.04.15.15.0-1017.17~20.04.15.15.0-1018.18~20.04.15.15.0-1019.19~20.04.15.15.0-1020.20~20.04.15.15.0-1022.22~20.04.15.15.0-1025.25~20.04.15.15.0-1027.27~20.04.15.15.0-1030.30~20.04.15.15.0-1032.32~20.04.1 |
5.15.0-1039.39~20.04.1 |
linux-oem-5.10Ubuntu:20.04:LTS |
All versions, plus listed versions 5.10.0-1008.95.10.0-1011.125.10.0-1013.145.10.0-1014.155.10.0-1016.17 Show 21 moreShow less5.10.0-1017.185.10.0-1019.205.10.0-1021.225.10.0-1022.235.10.0-1023.245.10.0-1025.265.10.0-1026.275.10.0-1029.305.10.0-1032.335.10.0-1033.345.10.0-1034.355.10.0-1038.405.10.0-1044.465.10.0-1045.475.10.0-1049.515.10.0-1050.525.10.0-1051.535.10.0-1052.545.10.0-1053.555.10.0-1055.585.10.0-1057.61 |
None known |
linux-oem-5.13Ubuntu:20.04:LTS |
All versions, plus listed versions 5.13.0-1009.105.13.0-1010.115.13.0-1012.165.13.0-1014.185.13.0-1017.21 Show 7 moreShow less5.13.0-1019.235.13.0-1020.245.13.0-1021.255.13.0-1022.265.13.0-1026.325.13.0-1028.355.13.0-1029.36 |
None known |
linux-oem-5.14Ubuntu:20.04:LTS |
All versions, plus listed versions 5.14.0-1004.45.14.0-1005.55.14.0-1007.75.14.0-1008.85.14.0-1010.10 Show 30 moreShow less5.14.0-1011.115.14.0-1013.135.14.0-1018.195.14.0-1020.225.14.0-1022.245.14.0-1024.265.14.0-1027.305.14.0-1029.325.14.0-1031.345.14.0-1032.355.14.0-1033.365.14.0-1034.375.14.0-1036.405.14.0-1038.425.14.0-1042.475.14.0-1044.495.14.0-1045.515.14.0-1046.535.14.0-1047.545.14.0-1048.555.14.0-1049.565.14.0-1050.575.14.0-1051.585.14.0-1052.595.14.0-1054.615.14.0-1055.625.14.0-1056.635.14.0-1057.645.14.0-1058.665.14.0-1059.67 |
None known |
linux-oem-5.6Ubuntu:20.04:LTS |
All versions, plus listed versions 5.6.0-1007.75.6.0-1008.85.6.0-1010.105.6.0-1011.115.6.0-1013.13 Show 24 moreShow less5.6.0-1017.175.6.0-1018.185.6.0-1020.205.6.0-1021.215.6.0-1023.235.6.0-1026.265.6.0-1027.275.6.0-1028.285.6.0-1031.325.6.0-1032.335.6.0-1033.355.6.0-1034.365.6.0-1035.375.6.0-1036.395.6.0-1039.435.6.0-1042.465.6.0-1047.515.6.0-1048.525.6.0-1050.545.6.0-1052.565.6.0-1053.575.6.0-1054.585.6.0-1055.595.6.0-1056.60 |
None known |
linux-oracle-5.11Ubuntu:20.04:LTS |
All versions, plus listed versions 5.11.0-1008.8~20.04.15.11.0-1013.14~20.04.15.11.0-1016.17~20.04.15.11.0-1017.18~20.04.15.11.0-1019.20~20.04.1 Show 7 moreShow less5.11.0-1020.21~20.04.15.11.0-1021.22~20.04.15.11.0-1022.23~20.04.15.11.0-1023.24~20.04.15.11.0-1025.27~20.04.15.11.0-1027.30~20.04.15.11.0-1028.31~20.04.1 |
None known |
linux-oracle-5.13Ubuntu:20.04:LTS |
All versions, plus listed versions 5.13.0-1011.13~20.04.25.13.0-1015.19~20.04.15.13.0-1016.20~20.04.15.13.0-1018.22~20.04.15.13.0-1021.26~20.04.1 Show 7 moreShow less5.13.0-1025.30~20.04.15.13.0-1027.32~20.04.15.13.0-1028.33~20.04.15.13.0-1030.35~20.04.15.13.0-1033.39~20.04.15.13.0-1034.40~20.04.15.13.0-1036.43~20.04.1 |
None known |
linux-oracle-5.8Ubuntu:20.04:LTS |
All versions, plus listed versions 5.8.0-1031.32~20.04.25.8.0-1033.34~20.04.15.8.0-1034.35~20.04.25.8.0-1037.38~20.04.15.8.0-1038.39~20.04.1 |
None known |
linux-raspi2Ubuntu:20.04:LTS |
All versions, plus listed versions 5.3.0-1007.85.3.0-1014.165.3.0-1015.175.3.0-1017.195.4.0-1004.45.4.0-1006.6 |
None known |
linux-riscvUbuntu:20.04:LTS |
All versions, plus listed versions 5.4.0-24.285.4.0-26.305.4.0-27.315.4.0-28.325.4.0-30.34 Show 7 moreShow less5.4.0-31.355.4.0-33.375.4.0-34.385.4.0-36.415.4.0-37.425.4.0-39.445.4.0-40.45 |
None known |
linux-riscv-5.11Ubuntu:20.04:LTS |
All versions, plus listed versions 5.11.0-1015.16~20.04.15.11.0-1017.18~20.04.15.11.0-1018.19~20.04.25.11.0-1020.21~20.04.15.11.0-1021.22~20.04.1 Show 8 moreShow less5.11.0-1022.23~20.04.15.11.0-1023.24~20.04.15.11.0-1024.25~20.04.15.11.0-1026.28~20.04.15.11.0-1028.31~20.04.15.11.0-1029.32~20.04.15.11.0-1030.345.11.0-1031.35 |
None known |
linux-riscv-5.8Ubuntu:20.04:LTS |
All versions, plus listed versions 5.8.0-14.16~20.04.15.8.0-14.16~20.04.35.8.0-16.18~20.04.15.8.0-17.19~20.04.15.8.0-18.20~20.04.1 Show 5 moreShow less5.8.0-20.22~20.04.15.8.0-22.24~20.04.15.8.0-25.27~20.04.15.8.0-26.28~20.04.15.8.0-29.31~20.04.1 |
None known |
linuxUbuntu:22.04:LTS |
before 5.15.0-138.148, plus listed versions 5.13.0-19.195.15.0-17.175.15.0-18.185.15.0-22.225.15.0-23.23 Show 45 moreShow less5.15.0-25.255.15.0-27.285.15.0-30.315.15.0-33.345.15.0-35.365.15.0-37.395.15.0-39.425.15.0-40.435.15.0-41.445.15.0-43.465.15.0-46.495.15.0-47.515.15.0-48.545.15.0-50.565.15.0-52.585.15.0-53.595.15.0-56.625.15.0-57.635.15.0-58.645.15.0-60.665.15.0-67.745.15.0-69.765.15.0-70.775.15.0-71.785.15.0-72.795.15.0-73.805.15.0-75.825.15.0-76.835.15.0-78.855.15.0-79.865.15.0-82.915.15.0-83.925.15.0-84.935.15.0-86.965.15.0-87.975.15.0-88.985.15.0-89.995.15.0-91.1015.15.0-92.1025.15.0-94.1045.15.0-97.1075.15.0-100.1105.15.0-101.1115.15.0-102.1125.15.0-105.115 |
5.15.0-138.148 |
linux-allwinner-5.19Ubuntu:22.04:LTS |
All versions, plus listed versions 5.19.0-1007.7~22.04.15.19.0-1009.9~22.04.15.19.0-1010.10~22.04.15.19.0-1011.11~22.04.15.19.0-1012.12~22.04.15.19.0-1013.13~22.04.15.19.0-1014.14~22.04.15.19.0-1015.15~22.04.1 |
None known |
linux-awsUbuntu:22.04:LTS |
before 5.15.0-1082.89, plus listed versions 5.13.0-1005.65.15.0-1002.45.15.0-1003.55.15.0-1004.65.15.0-1005.7 Show 45 moreShow less5.15.0-1008.105.15.0-1009.115.15.0-1011.145.15.0-1013.175.15.0-1014.185.15.0-1015.195.15.0-1017.215.15.0-1019.235.15.0-1020.245.15.0-1021.255.15.0-1022.265.15.0-1023.275.15.0-1026.305.15.0-1027.315.15.0-1028.325.15.0-1030.345.15.0-1031.355.15.0-1033.375.15.0-1034.385.15.0-1035.395.15.0-1036.405.15.0-1037.415.15.0-1038.435.15.0-1039.445.15.0-1040.455.15.0-1042.475.15.0-1043.485.15.0-1044.495.15.0-1045.505.15.0-1047.525.15.0-1048.535.15.0-1049.545.15.0-1050.555.15.0-1051.565.15.0-1052.575.15.0-1053.585.15.0-1055.605.15.0-1056.615.15.0-1057.635.15.0-1060.665.15.0-1061.675.15.0-1062.685.15.0-1063.695.15.0-1064.705.15.0-1065.71 |
5.15.0-1082.89 |
History
| Recorded | Changed | Sources |
|---|---|---|
| affected | OSV | |
| 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-26837 is a medium vulnerability (CVSS 4.7) in Linux, published April 17, 2024. No source lists public exploit code. EPSS puts the chance of exploitation in the next 30 days at 0.17%, the 6th percentile. Fixed in linux-lts 6.1.81-r0.
References
git.kernel.org/stable/c/2d5b4b3376fa146a23917b8577064906d643925f
git.kernel.org/stable/c/603be95437e7fd85ba694e75918067fb9e7754db
git.kernel.org/stable/c/e0b4c5b1d760008f1dd18c07c35af0442e54f9c8
git.kernel.org/stable/c/dc489f86257cab5056e747344f17a164f63bff4b
nvd.nist.gov/vuln/detail/CVE-2024-26837
github.com/advisories/GHSA-8ppx-vmhm-cxj7
Show 194 moreShow less
access.redhat.com/errata/RHSA-2024:5101
access.redhat.com/security/cve/CVE-2021-46939
access.redhat.com/security/cve/CVE-2021-47018
access.redhat.com/security/cve/CVE-2021-47257
access.redhat.com/security/cve/CVE-2021-47284
access.redhat.com/security/cve/CVE-2021-47304
access.redhat.com/security/cve/CVE-2021-47373
access.redhat.com/security/cve/CVE-2021-47408
access.redhat.com/security/cve/CVE-2021-47461
access.redhat.com/security/cve/CVE-2021-47468
access.redhat.com/security/cve/CVE-2021-47491
access.redhat.com/security/cve/CVE-2021-47548
access.redhat.com/security/cve/CVE-2021-47579
access.redhat.com/security/cve/CVE-2021-47624
access.redhat.com/security/cve/CVE-2022-48632
access.redhat.com/security/cve/CVE-2022-48743
access.redhat.com/security/cve/CVE-2022-48747
access.redhat.com/security/cve/CVE-2022-48757
bugzilla.redhat.com/2263879
bugzilla.redhat.com/2265645
bugzilla.redhat.com/2265650
bugzilla.redhat.com/2265797
bugzilla.redhat.com/2266341
bugzilla.redhat.com/2266347
bugzilla.redhat.com/2266497
bugzilla.redhat.com/2266594
bugzilla.redhat.com/2267787
bugzilla.redhat.com/2268118
bugzilla.redhat.com/2269070
bugzilla.redhat.com/2269211
bugzilla.redhat.com/2270084
bugzilla.redhat.com/2270100
bugzilla.redhat.com/2270700
bugzilla.redhat.com/2271686
bugzilla.redhat.com/2271688
bugzilla.redhat.com/2272782
errata.almalinux.org/8/ALSA-2024-5101.html
errata.almalinux.org/8/ALSA-2024-5102.html
docs.bell-sw.com/security/cves/CVE-2024-26837
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
github.com/CVEProject/cvelistV5/tree/main/cves/2024/26xxx/CVE-2024-26837.json
git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
security-tracker.debian.org/tracker/CVE-2024-26837
issues.redhat.com/browse/RHEL-36222
security.access.redhat.com/data/csaf/v2/advisories/2024/rhsa-2024_5101.json
cve.org/CVERecord?id=CVE-2021-46939
lore.kernel.org/linux-cve-announce/[email protected]/T
cve.org/CVERecord?id=CVE-2021-47018
git.kernel.org/stable/c/4b9fb2c9039a206d37f215936a4d5bee7b1bf9cd
git.kernel.org/stable/c/9ccba66d4d2aff9a3909aa77d57ea8b7cc166f3c
git.kernel.org/stable/c/a84df7c80bdac598d6ac9268ae578da6928883e8
git.kernel.org/stable/c/abb07dc5e8b61ab7b1dde20dd73aa01a3aeb183f
cve.org/CVERecord?id=CVE-2021-47257
lore.kernel.org/linux-cve-announce/2024052146-CVE-2021-47257-1d1c@gregkh/T
cve.org/CVERecord?id=CVE-2021-47284
lore.kernel.org/linux-cve-announce/2024052154-CVE-2021-47284-c8f5@gregkh/T
cve.org/CVERecord?id=CVE-2021-47304
lore.kernel.org/linux-cve-announce/2024052126-CVE-2021-47304-fc16@gregkh/T
cve.org/CVERecord?id=CVE-2021-47373
cve.org/CVERecord?id=CVE-2021-47408
lore.kernel.org/linux-cve-announce/2024052151-CVE-2021-47408-ad88@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-2021-47468
lore.kernel.org/linux-cve-announce/2024052227-CVE-2021-47468-6c1b@gregkh/T
cve.org/CVERecord?id=CVE-2021-47491
lore.kernel.org/linux-cve-announce/2024052241-CVE-2021-47491-437d@gregkh/T
cve.org/CVERecord?id=CVE-2021-47548
lore.kernel.org/linux-cve-announce/2024052441-CVE-2021-47548-e9c0@gregkh/T
cve.org/CVERecord?id=CVE-2021-47579
lore.kernel.org/linux-cve-announce/2024061915-CVE-2021-47579-4f78@gregkh/T
cve.org/CVERecord?id=CVE-2021-47624
lore.kernel.org/linux-cve-announce/2024071646-CVE-2021-47624-86cd@gregkh/T
cve.org/CVERecord?id=CVE-2022-48632
lore.kernel.org/linux-cve-announce/2024042854-CVE-2022-48632-465f@gregkh/T
cve.org/CVERecord?id=CVE-2022-48743
lore.kernel.org/linux-cve-announce/2024062003-CVE-2022-48743-ee30@gregkh/T
cve.org/CVERecord?id=CVE-2022-48747
lore.kernel.org/linux-cve-announce/2024062004-CVE-2022-48747-c63f@gregkh/T
cve.org/CVERecord?id=CVE-2022-48757
lore.kernel.org/linux-cve-announce/2024062007-CVE-2022-48757-c816@gregkh/T
cve.org/CVERecord?id=CVE-2022-50372
lore.kernel.org/linux-cve-announce/2025091717-CVE-2022-50372-e3b5@gregkh/T
lore.kernel.org/linux-cve-announce/2025100419-CVE-2022-50495-fdee@gregkh/T
intel.com/content/www/us/en/security-center/advisory/intel-sa-00898.html
lore.kernel.org/linux-cve-announce/2024022257-CVE-2023-52451-7bdb@gregkh/T
git.kernel.org/stable/c/28dd788382c43b330480f57cd34cde0840896743
git.kernel.org/stable/c/3426f059eacc33ecc676b0d66539297e1cfafd02
git.kernel.org/stable/c/35fa2394d26e919f63600ce631e6aefc95ec2706
git.kernel.org/stable/c/520e213a0b97b64735a13950e9371e0a5d7a5dc3
git.kernel.org/stable/c/8a27d9d9fc9b5564b8904c3a77a7dea482bfa34e
git.kernel.org/stable/c/8b55b06e737feb2a645b0293ea27e38418876d63
git.kernel.org/stable/c/95084632a65d5c0d682a83b55935560bdcd2a1e3
git.kernel.org/stable/c/b6dcba02ee178282e0d28684d241e0b8462dea6a
git.kernel.org/stable/c/3027e7b15b02d2d37e3f82d6b8404f6d37e3b8cf
download.vusec.net/papers/inspectre_sec24.pdf
intel.com/content/www/us/en/developer/articles/technical/software-security-guidance/technical-documentation/branch-history-injection.html
openwall.com/lists/oss-security/2024/04/09/15
vusec.net/projects/native-bhi
cisa.gov/known-exploited-vulnerabilities-catalog
security.access.redhat.com/data/csaf/v2/advisories/2024/rhsa-2024_5102.json
docs.redhat.com/en/documentation/red_hat_enterprise_linux/9/html/9.5_release_notes/index
issues.redhat.com/browse/RHEL-17714
issues.redhat.com/browse/RHEL-23575
issues.redhat.com/browse/RHEL-26081
issues.redhat.com/browse/RHEL-29437
issues.redhat.com/browse/RHEL-31876
issues.redhat.com/browse/RHEL-32199
issues.redhat.com/browse/RHEL-35853
issues.redhat.com/browse/RHEL-36182
issues.redhat.com/browse/RHEL-36224
issues.redhat.com/browse/RHEL-45158
issues.redhat.com/browse/RHEL-7990
issues.redhat.com/browse/RHEL-9096
issues.redhat.com/browse/RHEL-9148
issues.redhat.com/browse/RHEL-9429
security.access.redhat.com/data/csaf/v2/advisories/2024/rhsa-2024_9315.json
francozappa.github.io/about-bias
kb.cert.org/vuls/id/647177
bugzilla.openanolis.cn/show_bug.cgi?id=7975
patchwork.kernel.org/project/linux-raid/patch/[email protected]
security.access.redhat.com/data/csaf/v2/advisories/2024/rhsa-2024_9546.json
errata.rockylinux.org/RLSA-2024:5101
errata.rockylinux.org/RLSA-2024:5102
errata.rockylinux.org/RXSA-2024:5101
suse.com/support/update/announcement/2024/suse-su-20243194-1
bugzilla.suse.com/1012628
bugzilla.suse.com/1193454
bugzilla.suse.com/1194869
bugzilla.suse.com/1205462
bugzilla.suse.com/1208783
bugzilla.suse.com/1213123
bugzilla.suse.com/1214285
bugzilla.suse.com/1215199
bugzilla.suse.com/1220066
bugzilla.suse.com/1220252
bugzilla.suse.com/1220877
bugzilla.suse.com/1221326
bugzilla.suse.com/1221630
bugzilla.suse.com/1221645
bugzilla.suse.com/1221652
bugzilla.suse.com/1221857
bugzilla.suse.com/1222254
suse.com/security/cve/CVE-2023-52489
suse.com/security/cve/CVE-2023-52581
suse.com/security/cve/CVE-2023-52668
suse.com/security/cve/CVE-2023-52688
suse.com/security/cve/CVE-2023-52735
suse.com/security/cve/CVE-2023-52859
suse.com/security/cve/CVE-2023-52885
suse.com/security/cve/CVE-2023-52886
suse.com/security/cve/CVE-2023-52887
suse.com/security/cve/CVE-2023-52889
suse.com/security/cve/CVE-2024-26590
suse.com/security/cve/CVE-2024-26631
suse.com/security/cve/CVE-2024-26637
suse.com/security/cve/CVE-2024-26668
suse.com/security/cve/CVE-2024-26669
suse.com/security/cve/CVE-2024-26677
suse.com/security/cve/CVE-2024-26682
ubuntu.com/security/CVE-2024-26837
ubuntu.com/security/notices/USN-7455-1
ubuntu.com/security/notices/USN-7455-2
ubuntu.com/security/notices/USN-7455-3
ubuntu.com/security/notices/USN-7459-1
ubuntu.com/security/notices/USN-7460-1
ubuntu.com/security/notices/USN-7455-4
ubuntu.com/security/notices/USN-7459-2
ubuntu.com/security/notices/USN-7455-5
ubuntu.com/security/notices/USN-7475-1
ubuntu.com/security/CVE-2022-0995
ubuntu.com/security/CVE-2024-46826
ubuntu.com/security/CVE-2024-50248
ubuntu.com/security/CVE-2024-50256
ubuntu.com/security/CVE-2024-56651
ubuntu.com/security/CVE-2025-21700
ubuntu.com/security/CVE-2025-21701
Left out here: 392 package rows, 65 versions, 5,241 references and the rest of 11 source descriptions. The JSON record has them.