CVE-2024-40927
xhci: Handle TD clearing for multiple streams case
In the Linux kernel, the following vulnerability has been resolved:
xhci: Handle TD clearing for multiple streams case
When multiple streams are in use, multiple TDs might be in flight when an endpoint is stopped. We need to issue a Set TR Dequeue Pointer for each, to ensure everything is reset properly and the caches cleared. Change the logic so that any N>1 TDs found active for different streams are deferred until after the first one is processed, calling xhci_invalidate_cancelled_tds() again from xhci_handle_cmd_set_deq() to queue another command until we are done with all of them. Also change the error/"should never happen" paths to ensure we at least clear any affected TDs, even if we can't issue a command to clear the hardware cache, and complain loudly with an xhci_warn() if this ever happens.
This problem case dates back to commit e9df17eb1408 ("USB: xhci: Correct assumptions about number of rings per endpoint.") early on in the XHCI driver's life, when stream support was first added. It was then identified but not fixed nor made into a warning in commit 674f8438c121 ("xhci: split handling halted endpoints into two steps"), which added a FIXME comment for the problem case (without materially changing the behavior as far as I can tell, though the new logic made the problem more obvious).
Then later, in commit 94f339147fc3 ("xhci: Fix failure to give back some cached cancelled URBs."), it was acknowledged again.
[Mathias: commit 94f339147fc3 ("xhci: Fix failure to give back some cached cancelled URBs.") was a targeted regression fix to the previously mentioned patch. Users reported issues with usb stuck after unmounting/disconnecting UAS devices. This rolled back the TD clearing of multiple streams to its original state.]
Apparently the commit author was aware of the problem (yet still chose to submit it): It was still mentioned as a FIXME, an xhci_dbg() was added to log the problem condition, and the remaining issue was mentioned in the commit description. The choice of making the log type xhci_dbg() for what is, at this point, a completely unhandled and known broken condition is puzzling and unfortunate, as it guarantees that no actual users would see the log in production, thereby making it nigh undebuggable (indeed, even if you turn on DEBUG, the message doesn't really hint at there being a problem at all).
It took me months of random xHC crashes to finally find a reliable repro and be able to do a deep dive debug session, which could all have been avoided had this unhandled, broken condition been actually reported with a warning, as it should have been as a bug intentionally left in unfixed (never mind that it shouldn't have been left in at all).
Another fix to solve clearing the caches of all stream rings with cancelled TDs is needed, but not as urgent.
3 years after that statement and 14 years after the original bug was introduced, I think it's finally time to fix it. And maybe next time let's not leave bugs unfixed (that are actually worse than the original bug), and let's actually get people to review kernel commits please.
Fixes xHC crashes and IOMMU faults with UAS devices when handling
errors/faults. Easiest repro is to use hdparm to mark an early sector
(e.g. 1024) on a disk as bad, then cat /dev/sdX > /dev/null in a loop.
At least in the case of JMicron controllers, the read errors end up
having to cancel two TDs (for two queued requests to different streams)
and the one that didn't get cleared properly ends up faulting the xHC
entirely when it tries to access DMA pages that have since been unmapped,
referred to by the stale TDs. This normally happens quickly (after two
or three loops). After this fix, I left the cat in a loop running
overnight and experienced no xHC failures, with all read errors
recovered properly. Repro'd and tested on an Apple M1 Mac Mini
(dwc3 host).
On systems without an IOMMU, this bug would instead silently corrupt freed memory, making this a ---truncated---
Attack profile
How easy it is to exploit
- Attack vector
- Local
- Complexity
- Low
- Privileges needed
- Low
- User interaction
- None
What an attacker can affect
- Confidentiality
- High
- Integrity
- High
- Availability
- High
Exploit likelihood
What each source reports
NVD Score used
7.8
In the Linux kernel, the following vulnerability has been resolved:
xhci: Handle TD clearing for multiple streams case
When multiple streams are in use, multiple TDs might be in flight when an endpoint is stopped. We need to issue a Set TR Dequeue Pointer for each, to ensure everything is reset properly and the caches cleared. Change the logic so that any N>1 TDs found active for different streams are deferred until after the first one is processed, calling xhci_invalidate_cancelled_tds() again from xhci_handle_cmd_set_deq() to queue another command until we are done with all of them. Also change the error/"should never happen" paths to ensure we at least clear any affected TDs, even if we can't issue a command to clear the hardware cache, and complain loudly with an xhci_warn() if this ever happens.
This problem case dates back to commit e9df17eb1408 ("USB: xhci: Correct assumptions about number of rings per endpoint.") early on in the XHCI driver's life, when stream support was first added. It was then identified but not fixed nor made into a warning in commit 674f8438c121 ("xhci: split handling halted endpoints into two steps"), which added a FIXME comment for the problem case (without materially changing the behavior as far as I can tell, though the new logic made the problem more obvious).
Then later, in commit 94f339147fc3 ("xhci: Fix failure to give back some cached cancelled URBs."), it was acknowledged again.
[Mathias: commit 94f339147fc3 ("xhci: Fix failure to give back some cached cancelled URBs.") was a targeted regression fix to the previously mentioned patch. Users reported issues with usb stuck after unmounting/disconnecting UAS devices. This rolled back the TD clearing of multiple streams to its original state.]
Apparently the commit author was aware of the problem (yet still chose to submit it): It was still mentioned as a FIXME, an xhci_dbg() was added to log the problem condition, and the remaining issue was mentioned in the commit description. The choice of making the log type xhci_dbg() for what is, at this point, a completely unhandled and known broken condition is puzzling and unfortunate, as it guarantees that no actual users would see the log in production, thereby making it nigh undebuggable (indeed, even if you turn on DEBUG, the message doesn't really hint at there being a problem at all).
It took me months of random xHC crashes to finally find a reliable repro and be able to do a deep dive debug session, which could all have been avoided had this unhandled, broken condition been actually reported with a warning, as it should have been as a bug intentionally left in unfixed (never mind that it shouldn't have been left in at all).
Another fix to solve clearing the caches of all stream rings with cancelled TDs is needed, but not as urgent.
3 years after that statement and 14 years after the original bug was introduced, I think it's finally time to fix it. And maybe next time let's not leave bugs unfixed (that are actually worse than the original bug), and let's actually get people to review kernel commits please.
Fixes xHC crashes and IOMMU faults with UAS devices when handling
errors/faults. Easiest repro is to use hdparm to mark an early sector
(e.g. 1024) on a disk as bad, then cat /dev/sdX > /dev/null in a loop.
At least in the case of JMicron controllers, the read errors end up
having to cancel two TDs (for two queued requests to different streams)
and the one that didn't get cleared properly ends up faulting the xHC
entirely when it tries to access DMA pages that have since been unmapped,
referred to by the stale TDs. This normally happens quickly (after two
or three loops). After this fix, I left the cat in a loop running
overnight and experienced no xHC failures, with all read errors
recovered properly. Repro'd and tested on an Apple M1 Mac Mini
(dwc3 host).
On systems without an IOMMU, this bug would instead silently corrupt freed memory, making this a ---truncated---
- Record
CVE-2024-40927- CVSS 3.1
- 7.8 High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H - Weakness
- CWE-416
- Updated
- 2026-11-02
CVE List No score
xhci: Handle TD clearing for multiple streams case
In the Linux kernel, the following vulnerability has been resolved:
xhci: Handle TD clearing for multiple streams case
When multiple streams are in use, multiple TDs might be in flight when an endpoint is stopped. We need to issue a Set TR Dequeue Pointer for each, to ensure everything is reset properly and the caches cleared. Change the logic so that any N>1 TDs found active for different streams are deferred until after the first one is processed, calling xhci_invalidate_cancelled_tds() again from xhci_handle_cmd_set_deq() to queue another command until we are done with all of them. Also change the error/"should never happen" paths to ensure we at least clear any affected TDs, even if we can't issue a command to clear the hardware cache, and complain loudly with an xhci_warn() if this ever happens.
This problem case dates back to commit e9df17eb1408 ("USB: xhci: Correct assumptions about number of rings per endpoint.") early on in the XHCI driver's life, when stream support was first added. It was then identified but not fixed nor made into a warning in commit 674f8438c121 ("xhci: split handling halted endpoints into two steps"), which added a FIXME comment for the problem case (without materially changing the behavior as far as I can tell, though the new logic made the problem more obvious).
Then later, in commit 94f339147fc3 ("xhci: Fix failure to give back some cached cancelled URBs."), it was acknowledged again.
[Mathias: commit 94f339147fc3 ("xhci: Fix failure to give back some cached cancelled URBs.") was a targeted regression fix to the previously mentioned patch. Users reported issues with usb stuck after unmounting/disconnecting UAS devices. This rolled back the TD clearing of multiple streams to its original state.]
Apparently the commit author was aware of the problem (yet still chose to submit it): It was still mentioned as a FIXME, an xhci_dbg() was added to log the problem condition, and the remaining issue was mentioned in the commit description. The choice of making the log type xhci_dbg() for what is, at this point, a completely unhandled and known broken condition is puzzling and unfortunate, as it guarantees that no actual users would see the log in production, thereby making it nigh undebuggable (indeed, even if you turn on DEBUG, the message doesn't really hint at there being a problem at all).
It took me months of random xHC crashes to finally find a reliable repro and be able to do a deep dive debug session, which could all have been avoided had this unhandled, broken condition been actually reported with a warning, as it should have been as a bug intentionally left in unfixed (never mind that it shouldn't have been left in at all).
Another fix to solve clearing the caches of all stream rings with cancelled TDs is needed, but not as urgent.
3 years after that statement and 14 years after the original bug was introduced, I think it's finally time to fix it. And maybe next time let's not leave bugs unfixed (that are actually worse than the original bug), and let's actually get people to review kernel commits please.
Fixes xHC crashes and IOMMU faults with UAS devices when handling
errors/faults. Easiest repro is to use hdparm to mark an early sector
(e.g. 1024) on a disk as bad, then cat /dev/sdX > /dev/null in a loop.
At least in the case of JMicron controllers, the read errors end up
having to cancel two TDs (for two queued requests to different streams)
and the one that didn't get cleared properly ends up faulting the xHC
entirely when it tries to access DMA pages that have since been unmapped,
referred to by the stale TDs. This normally happens quickly (after two
or three loops). After this fix, I left the cat in a loop running
overnight and experienced no xHC failures, with all read errors
recovered properly. Repro'd and tested on an Apple M1 Mac Mini
(dwc3 host).
On systems without an IOMMU, this bug would instead silently corrupt freed memory, making this a ---truncated---
- Record
CVE-2024-40927- Updated
- 2026-11-02
EUVDEUVD-2024-38738 No score
In the Linux kernel, the following vulnerability has been resolved:
xhci: Handle TD clearing for multiple streams case
When multiple streams are in use, multiple TDs might be in flight when an endpoint is stopped. We need to issue a Set TR Dequeue Pointer for each, to ensure everything is reset properly and the caches cleared. Change the logic so that any N>1 TDs found active for different streams are deferred until after the first one is processed, calling xhci_invalidate_cancelled_tds() again from xhci_handle_cmd_set_deq() to queue another command until we are done with all of them. Also change the error/"should never happen" paths to ensure we at least clear any affected TDs, even if we can't issue a command to clear the hardware cache, and complain loudly with an xhci_warn() if this ever happens.
This problem case dates back to commit e9df17eb1408 ("USB: xhci: Correct assumptions about number of rings per endpoint.") early on in the XHCI driver's life, when stream support was first added. It was then identified but not fixed nor made into a warning in commit 674f8438c121 ("xhci: split handling halted endpoints into two steps"), which added a FIXME comment for the problem case (without materially changing the behavior as far as I can tell, though the new logic made the problem more obvious).
Then later, in commit 94f339147fc3 ("xhci: Fix failure to give back some cached cancelled URBs."), it was acknowledged again.
[Mathias: commit 94f339147fc3 ("xhci: Fix failure to give back some cached cancelled URBs.") was a targeted regression fix to the previously mentioned patch. Users reported issues with usb stuck after unmounting/disconnecting UAS devices. This rolled back the TD clearing of multiple streams to its original state.]
Apparently the commit author was aware of the problem (yet still chose to submit it): It was still mentioned as a FIXME, an xhci_dbg() was added to log the problem condition, and the remaining issue was mentioned in the commit description. The choice of making the log type xhci_dbg() for what is, at this point, a completely unhandled and known broken condition is puzzling and unfortunate, as it guarantees that no actual users would see the log in production, thereby making it nigh undebuggable (indeed, even if you turn on DEBUG, the message doesn't really hint at there being a problem at all).
It took me months of random xHC crashes to finally find a reliable repro and be able to do a deep dive debug session, which could all have been avoided had this unhandled, broken condition been actually reported with a warning, as it should have been as a bug intentionally left in unfixed (never mind that it shouldn't have been left in at all).
Another fix to solve clearing the caches of all stream rings with cancelled TDs is needed, but not as urgent.
3 years after that statement and 14 years after the original bug was introduced, I think it's finally time to fix it. And maybe next time let's not leave bugs unfixed (that are actually worse than the original bug), and let's actually get people to review kernel commits please.
Fixes xHC crashes and IOMMU faults with UAS devices when handling
errors/faults. Easiest repro is to use hdparm to mark an early sector
(e.g. 1024) on a disk as bad, then cat /dev/sdX > /dev/null in a loop.
At least in the case of JMicron controllers, the read errors end up
having to cancel two TDs (for two queued requests to different streams)
and the one that didn't get cleared properly ends up faulting the xHC
entirely when it tries to access DMA pages that have since been unmapped,
referred to by the stale TDs. This normally happens quickly (after two
or three loops). After this fix, I left the cat in a loop running
overnight and experienced no xHC failures, with all read errors
recovered properly. Repro'd and tested on an Apple M1 Mac Mini
(dwc3 host).
On systems without an IOMMU, this bug would instead silently corrupt freed memory, making this a ---truncated---
- Record
EUVD-2024-38738- Updated
- 2026-11-02
GitHub AdvisoriesGHSA-38vr-8qrj-3x4h
7.8
In the Linux kernel, the following vulnerability has been resolved: xhci: Handle TD clearing for...
In the Linux kernel, the following vulnerability has been resolved:
xhci: Handle TD clearing for multiple streams case
When multiple streams are in use, multiple TDs might be in flight when an endpoint is stopped. We need to issue a Set TR Dequeue Pointer for each, to ensure everything is reset properly and the caches cleared. Change the logic so that any N>1 TDs found active for different streams are deferred until after the first one is processed, calling xhci_invalidate_cancelled_tds() again from xhci_handle_cmd_set_deq() to queue another command until we are done with all of them. Also change the error/"should never happen" paths to ensure we at least clear any affected TDs, even if we can't issue a command to clear the hardware cache, and complain loudly with an xhci_warn() if this ever happens.
This problem case dates back to commit e9df17eb1408 ("USB: xhci: Correct assumptions about number of rings per endpoint.") early on in the XHCI driver's life, when stream support was first added. It was then identified but not fixed nor made into a warning in commit 674f8438c121 ("xhci: split handling halted endpoints into two steps"), which added a FIXME comment for the problem case (without materially changing the behavior as far as I can tell, though the new logic made the problem more obvious).
Then later, in commit 94f339147fc3 ("xhci: Fix failure to give back some cached cancelled URBs."), it was acknowledged again.
[Mathias: commit 94f339147fc3 ("xhci: Fix failure to give back some cached cancelled URBs.") was a targeted regression fix to the previously mentioned patch. Users reported issues with usb stuck after unmounting/disconnecting UAS devices. This rolled back the TD clearing of multiple streams to its original state.]
Apparently the commit author was aware of the problem (yet still chose to submit it): It was still mentioned as a FIXME, an xhci_dbg() was added to log the problem condition, and the remaining issue was mentioned in the commit description. The choice of making the log type xhci_dbg() for what is, at this point, a completely unhandled and known broken condition is puzzling and unfortunate, as it guarantees that no actual users would see the log in production, thereby making it nigh undebuggable (indeed, even if you turn on DEBUG, the message doesn't really hint at there being a problem at all).
It took me months of random xHC crashes to finally find a reliable repro and be able to do a deep dive debug session, which could all have been avoided had this unhandled, broken condition been actually reported with a warning, as it should have been as a bug intentionally left in unfixed (never mind that it shouldn't have been left in at all).
Another fix to solve clearing the caches of all stream rings with cancelled TDs is needed, but not as urgent.
3 years after that statement and 14 years after the original bug was introduced, I think it's finally time to fix it. And maybe next time let's not leave bugs unfixed (that are actually worse than the original bug), and let's actually get people to review kernel commits please.
Fixes xHC crashes and IOMMU faults with UAS devices when handling
errors/faults. Easiest repro is to use hdparm to mark an early sector
(e.g. 1024) on a disk as bad, then cat /dev/sdX > /dev/null in a loop.
At least in the case of JMicron controllers, the read errors end up
having to cancel two TDs (for two queued requests to different streams)
and the one that didn't get cleared properly ends up faulting the xHC
entirely when it tries to access DMA pages that have since been unmapped,
referred to by the stale TDs. This normally happens quickly (after two
or three loops). After this fix, I left the cat in a loop running
overnight and experienced no xHC failures, with all read errors
recovered properly. Repro'd and tested on an Apple M1 Mac Mini
(dwc3 host).
On systems without an IOMMU, this bug would instead silently corrupt freed memory, making this a ---truncated---
- Record
GHSA-38vr-8qrj-3x4h- CVSS 3.1
- 7.8 High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H - Weakness
- CWE-416
- Updated
- 2026-11-02
OSVBELL-CVE-2024-40927
7.8
- Record
BELL-CVE-2024-40927- CVSS 3.1
- 7.8 High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H - Updated
- 2026-11-02
OSVDEBIAN-CVE-2024-40927
7.8
In the Linux kernel, the following vulnerability has been resolved: xhci: Handle TD clearing for multiple streams case When multiple streams are in use, multiple TDs might be in flight when an endpoint is stopped. We need to issue a Set TR Dequeue Pointer for each, to ensure everything is reset properly and the caches cleared. Change the logic so that any N>1 TDs found active for different streams are deferred until after the first one is processed, calling xhci_invalidate_cancelled_tds() again from xhci_handle_cmd_set_deq() to queue another command until we are done with all of them. Also change the error/"should never happen" paths to ensure we at least clear any affected TDs, even if we can't issue a command to clear the hardware cache, and complain loudly with an xhci_warn() if this ever happens. This problem case dates back to commit e9df17eb1408 ("USB: xhci: Correct assumptions about number of rings per endpoint.") early on in the XHCI driver's life, when stream support was first added. It was then identified but not fixed nor made into a warning in commit 674f8438c121 ("xhci: split handling halted endpoints into two steps"), which added a FIXME comment for the problem case (without materially changing the behavior as far as I can tell, though the new logic made the problem more obvious). Then later, in commit 94f339147fc3 ("xhci: Fix failure to give back some cached cancelled URBs."), it was acknowledged again. [Mathias: commit 94f339147fc3 ("xhci: Fix failure to give back some cached cancelled URBs.") was a targeted regression fix to the previously mentioned patch. Users reported issues with usb stuck after unmounting/disconnecting UAS devices. This rolled back the TD clearing of multiple streams to its original state.] Apparently the commit author was aware of the problem (yet still chose to submit it): It was still mentioned as a FIXME, an xhci_dbg() was added to log the problem condition, and the remaining issue was mentioned in the commit description. The choice of making the log type xhci_dbg() for what is, at this point, a completely unhandled and known broken condition is puzzling and unfortunate, as it guarantees that no actual users would see the log in production, thereby making it nigh undebuggable (indeed, even if you turn on DEBUG, the message doesn't really hint at there being a problem at all). It took me months of random xHC crashes to finally find a reliable repro and be able to do a deep dive debug session, which could all have been avoided had this unhandled, broken condition been actually reported with a warning, as it should have been as a bug intentionally left in unfixed (never mind that it shouldn't have been left in at all). > Another fix to solve clearing the caches of all stream rings with > cancelled TDs is needed, but not as urgent. 3 years after that statement and 14 years after the original bug was introduced, I think it's finally time to fix it. And maybe next time let's not leave bugs unfixed (that are actually worse than the original bug), and let's actually get people to review kernel commits please. Fixes xHC crashes and IOMMU faults with UAS devices when handling errors/faults. Easiest repro is to use hdparm to mark an early sector (e.g. 1024) on a disk as bad, then cat /dev/sdX > /dev/null in a loop. At least in the case of JMicron controllers, the read errors end up having to cancel two TDs (for two queued requests to different streams) and the one that didn't get cleared properly ends up faulting the xHC entirely when it tries to access DMA pages that have since been unmapped, referred to by the stale TDs. This normally happens quickly (after two or three loops). After this fix, I left the cat in a loop running overnight and experienced no xHC failures, with all read errors recovered properly. Repro'd and tested on an Apple M1 Mac Mini (dwc3 host). On systems without an IOMMU, this bug would instead silently corrupt freed memory, making this a ---truncated---
- Record
DEBIAN-CVE-2024-40927- CVSS 3.1
- 7.8 High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H - Updated
- 2026-11-02
Show 40 moreShow less
OSVOESA-2024-2534
7.8
kernel security update
The Linux Kernel, the operating system core itself.
Security Fix(es):
In the Linux kernel, the following vulnerability has been resolved: xhci: Handle TD clearing for multiple streams case When multiple streams are in use, multiple TDs might be in flight when an endpoint is stopped. We need to issue a Set TR Dequeue Pointer for each, to ensure everything is reset properly and the caches cleared. Change the logic so that any N>1 TDs found active for different streams are deferred until after the first one is processed, calling xhci_invalidate_cancelled_tds() again from xhci_handle_cmd_set_deq() to queue another command until we are done with all of them. Also change the error/"should never happen" paths to ensure we at least clear any affected TDs, even if we can't issue a command to clear the hardware cache, and complain loudly with an xhci_warn() if this ever happens. This problem case dates back to commit e9df17eb1408 ("USB: xhci: Correct assumptions about number of rings per endpoint.") early on in the XHCI driver's life, when stream support was first added. It was then identified but not fixed nor made into a warning in commit 674f8438c121 ("xhci: split handling halted endpoints into two steps"), which added a FIXME comment for the problem case (without materially changing the behavior as far as I can tell, though the new logic made the problem more obvious). Then later, in commit 94f339147fc3 ("xhci: Fix failure to give back some cached cancelled URBs."), it was acknowledged again. [Mathias: commit 94f339147fc3 ("xhci: Fix failure to give back some cached cancelled URBs.") was a targeted regression fix to the previously mentioned patch. Users reported issues with usb stuck after unmounting/disconnecting UAS devices. This rolled back the TD clearing of multiple streams to its original state.] Apparently the commit author was aware of the problem (yet still chose to submit it): It was still mentioned as a FIXME, an xhci_dbg() was added to log the problem condition, and the remaining issue was mentioned in the commit description. The choice of making the log type xhci_dbg() for what is, at this point, a completely unhandled and known broken condition is puzzling and unfortunate, as it guarantees that no actual users would see the log in production, thereby making it nigh undebuggable (indeed, even if you turn on DEBUG, the message doesn't really hint at there being a problem at all). It took me months of random xHC crashes to finally find a reliable repro and be able to do a deep dive debug session, which could all have been avoided had this unhandled, broken condition been actually reported with a warning, as it should have been as a bug intentionally left in unfixed (never mind that it shouldn't have been left in at all). > Another fix to solve clearing the caches of all stream rings with > cancelled TDs is needed, but not as urgent. 3 years after that statement and 14 years after the original bug was introduced, I think it's finally time to fix it. And maybe next time let's not leave bugs unfixed (that are actually worse than the original bug), and let's actually get people to review kernel commits please. Fixes xHC crashes and IOMMU faults with UAS devices when handling errors/faults. Easiest repro is to use hdparm to mark an early sector (e.g. 1024) on a disk as bad, then cat /dev/sdX > /dev/null in a loop. At least in the case of JMicron controllers, the read errors end up having to cancel two TDs (for two queued requests to different streams) and the one that didn't get cleared properly ends up faulting the xHC entirely when it tries to access DMA pages that have since been unmapped, referred to by the stale TDs. This normally happens quickly (after two or three loops). After this fix, I left the cat in a loop running overnight and experienced no xHC failures, with all read errors recovered…
- Record
OESA-2024-2534- CVSS 3.1
- 7.8 High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H - Updated
- 2026-11-02
OSVOESA-2024-2537
7.8
kernel security update
The Linux Kernel, the operating system core itself.
Security Fix(es):
In the Linux kernel, the following vulnerability has been resolved: xhci: Handle TD clearing for multiple streams case When multiple streams are in use, multiple TDs might be in flight when an endpoint is stopped. We need to issue a Set TR Dequeue Pointer for each, to ensure everything is reset properly and the caches cleared. Change the logic so that any N>1 TDs found active for different streams are deferred until after the first one is processed, calling xhci_invalidate_cancelled_tds() again from xhci_handle_cmd_set_deq() to queue another command until we are done with all of them. Also change the error/"should never happen" paths to ensure we at least clear any affected TDs, even if we can't issue a command to clear the hardware cache, and complain loudly with an xhci_warn() if this ever happens. This problem case dates back to commit e9df17eb1408 ("USB: xhci: Correct assumptions about number of rings per endpoint.") early on in the XHCI driver's life, when stream support was first added. It was then identified but not fixed nor made into a warning in commit 674f8438c121 ("xhci: split handling halted endpoints into two steps"), which added a FIXME comment for the problem case (without materially changing the behavior as far as I can tell, though the new logic made the problem more obvious). Then later, in commit 94f339147fc3 ("xhci: Fix failure to give back some cached cancelled URBs."), it was acknowledged again. [Mathias: commit 94f339147fc3 ("xhci: Fix failure to give back some cached cancelled URBs.") was a targeted regression fix to the previously mentioned patch. Users reported issues with usb stuck after unmounting/disconnecting UAS devices. This rolled back the TD clearing of multiple streams to its original state.] Apparently the commit author was aware of the problem (yet still chose to submit it): It was still mentioned as a FIXME, an xhci_dbg() was added to log the problem condition, and the remaining issue was mentioned in the commit description. The choice of making the log type xhci_dbg() for what is, at this point, a completely unhandled and known broken condition is puzzling and unfortunate, as it guarantees that no actual users would see the log in production, thereby making it nigh undebuggable (indeed, even if you turn on DEBUG, the message doesn't really hint at there being a problem at all). It took me months of random xHC crashes to finally find a reliable repro and be able to do a deep dive debug session, which could all have been avoided had this unhandled, broken condition been actually reported with a warning, as it should have been as a bug intentionally left in unfixed (never mind that it shouldn't have been left in at all). > Another fix to solve clearing the caches of all stream rings with > cancelled TDs is needed, but not as urgent. 3 years after that statement and 14 years after the original bug was introduced, I think it's finally time to fix it. And maybe next time let's not leave bugs unfixed (that are actually worse than the original bug), and let's actually get people to review kernel commits please. Fixes xHC crashes and IOMMU faults with UAS devices when handling errors/faults. Easiest repro is to use hdparm to mark an early sector (e.g. 1024) on a disk as bad, then cat /dev/sdX > /dev/null in a loop. At least in the case of JMicron controllers, the read errors end up having to cancel two TDs (for two queued requests to different streams) and the one that didn't get cleared properly ends up faulting the xHC entirely when it tries to access DMA pages that have since been unmapped, referred to by the stale TDs. This normally happens quickly (after two or three loops). After this fix, I left the cat in a loop running overnight and experienced no xHC failures, with all read errors recovered…
- Record
OESA-2024-2537- CVSS 3.1
- 7.8 High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H - Updated
- 2026-11-02
OSVOESA-2024-2571
7.8
kernel security update
The Linux Kernel, the operating system core itself.
Security Fix(es):
In the Linux kernel, the following vulnerability has been resolved:
dmaengine: idxd: Let probe fail when workqueue cannot be enabled
The workqueue is enabled when the appropriate driver is loaded and disabled when the driver is removed. When the driver is removed it assumes that the workqueue was enabled successfully and proceeds to free allocations made during workqueue enabling.
Failure during workqueue enabling does not prevent the driver from being loaded. This is because the error path within drv_enable_wq() returns success unless a second failure is encountered during the error path. By returning success it is possible to load the driver even if the workqueue cannot be enabled and allocations that do not exist are attempted to be freed during driver remove.
Some examples of problematic flows: (a)
idxd_dmaengine_drv_probe() -> drv_enable_wq() -> idxd_wq_request_irq(): In above flow, if idxd_wq_request_irq() fails then idxd_wq_unmap_portal() is called on error exit path, but drv_enable_wq() returns 0 because idxd_wq_disable() succeeds. The driver is thus loaded successfully.
idxd_dmaengine_drv_remove()->drv_disable_wq()->idxd_wq_unmap_portal() Above flow on driver unload triggers the WARN in devm_iounmap() because the device resource has already been removed during error path of drv_enable_wq().
(b)
idxd_dmaengine_drv_probe() -> drv_enable_wq() -> idxd_wq_request_irq(): In above flow, if idxd_wq_request_irq() fails then idxd_wq_init_percpu_ref() is never called to initialize the percpu counter, yet the driver loads successfully because drv_enable_wq() returns 0.
idxd_dmaengine_drv_remove()->__idxd_wq_quiesce()->percpu_ref_kill(): Above flow on driver unload triggers a BUG when attempting to drop the initial ref of the uninitialized percpu ref: BUG: kernel NULL pointer dereference, address: 0000000000000010
Fix the drv_enable_wq() error path by returning the original error that indicates failure of workqueue enabling. This ensures that the probe fails when an error is encountered and the driver remove paths are only attempted when the workqueue was enabled successfully.(CVE-2022-48868)
In the Linux kernel, the following vulnerability has been resolved: xhci: Handle TD clearing for multiple streams case When multiple streams are in use, multiple TDs might be in flight when an endpoint is stopped. We need to issue a Set TR Dequeue Pointer for each, to ensure everything is reset properly and the caches cleared. Change the logic so that any N>1 TDs found active for different streams are deferred until after the first one is processed, calling xhci_invalidate_cancelled_tds() again from xhci_handle_cmd_set_deq() to queue another command until we are done with all of them. Also change the error/"should never happen" paths to ensure we at least clear any affected TDs, even if we can't issue a command to clear the hardware cache, and complain loudly with an xhci_warn() if this ever happens. This problem case dates back to commit e9df17eb1408 ("USB: xhci: Correct assumptions about number of rings per endpoint.") early on in the XHCI driver's life, when stream support was first added. It was then identified but not fixed nor made into a warning in commit 674f8438c121 ("xhci: split handling halted endpoints into two steps"), which added a FIXME comment for the problem case (without materially changing the behavior as far as I can tell, though the new logic made the problem more obvious). Then later, in commit 94f339147fc3 ("xhci: Fix failure to give back some cached cancelled URBs."), it was acknowledged again. [Mathias: commit 94f339147fc3 ("xhci: Fix failure to give back some cached cancelled URBs.") was a targeted regression fix to the previously mentioned patch. Users reported issues with usb stuck after…
- Record
OESA-2024-2571- 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: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:6567
7.1
Red Hat Security Advisory: kernel security update
- Record
RHSA-2024:6567- CVSS 3.1
- 7.1 High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H - Updated
- 2026-11-02
OSVROOT-OS-DEBIAN-11-CVE-2024-40927
7.8
CVE-2024-40927 in linux - Patched by Root
Root has patched CVE-2024-40927 in the linux package for Root:Debian:11. Multiple fixed versions available.
- Record
ROOT-OS-DEBIAN-11-CVE-2024-40927- 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-40927
7.0
In the Linux kernel, the following vulnerability has been resolved: xhci: Handle TD clearing for multiple streams case When multiple streams are in use, multiple TDs might be in flight when an endpoint is stopped. We need to issue a Set TR Dequeue Pointer for each, to ensure everything is reset properly and the caches cleared. Change the logic so that any N>1 TDs found active for different streams are deferred until after the first one is processed, calling xhci_invalidate_cancelled_tds() again from xhci_handle_cmd_set_deq() to queue another command until we are done with all of them. Also change the error/"should never happen" paths to ensure we at least clear any affected TDs, even if we can't issue a command to clear the hardware cache, and complain loudly with an xhci_warn() if this ever happens. This problem case dates back to commit e9df17eb1408 ("USB: xhci: Correct assumptions about number of rings per endpoint.") early on in the XHCI driver's life, when stream support was first added. It was then identified but not fixed nor made into a warning in commit 674f8438c121 ("xhci: split handling halted endpoints into two steps"), which added a FIXME comment for the problem case (without materially changing the behavior as far as I can tell, though the new logic made the problem more obvious). Then later, in commit 94f339147fc3 ("xhci: Fix failure to give back some cached cancelled URBs."), it was acknowledged again. [Mathias: commit 94f339147fc3 ("xhci: Fix failure to give back some cached cancelled URBs.") was a targeted regression fix to the previously mentioned patch. Users reported issues with usb stuck after unmounting/disconnecting UAS devices. This rolled back the TD clearing of multiple streams to its original state.] Apparently the commit author was aware of the problem (yet still chose to submit it): It was still mentioned as a FIXME, an xhci_dbg() was added to log the problem condition, and the remaining issue was mentioned in the commit description. The choice of making the log type xhci_dbg() for what is, at this point, a completely unhandled and known broken condition is puzzling and unfortunate, as it guarantees that no actual users would see the log in production, thereby making it nigh undebuggable (indeed, even if you turn on DEBUG, the message doesn't really hint at there being a problem at all). It took me months of random xHC crashes to finally find a reliable repro and be able to do a deep dive debug session, which could all have been avoided had this unhandled, broken condition been actually reported with a warning, as it should have been as a bug intentionally left in unfixed (never mind that it shouldn't have been left in at all). > Another fix to solve clearing the caches of all stream rings with > cancelled TDs is needed, but not as urgent. 3 years after that statement and 14 years after the original bug was introduced, I think it's finally time to fix it. And maybe next time let's not leave bugs unfixed (that are actually worse than the original bug), and let's actually get people to review kernel commits please. Fixes xHC crashes and IOMMU faults with UAS devices when handling errors/faults. Easiest repro is to use hdparm to mark an early sector (e.g. 1024) on a disk as bad, then cat /dev/sdX > /dev/null in a loop. At least in the case of JMicron controllers, the read errors end up having to cancel two TDs (for two queued requests to different streams) and the one that didn't get cleared properly ends up faulting the xHC entirely when it tries to access DMA pages that have since been unmapped, referred to by the stale TDs. This normally happens quickly (after two or three loops). After this fix, I left the cat in a loop running overnight and experienced no xHC failures, with all read errors recovered properly. Repro'd and tested on an Apple M1 Mac Mini (dwc3 host). On systems without an IOMMU, this bug would instead silently corrupt freed memory, making this a ---truncated---
- Record
UBUNTU-CVE-2024-40927- CVSS 4.0
- 7.0 High
CVSS:4.0/AV:P/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N - CVSS 3.1
- 7.8 High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H - Updated
- 2026-11-02
OSVALSA-2024: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
OSVALSA-2024:6567 No score
Moderate: kernel security update
The kernel packages contain the Linux kernel, the core of any Linux operating system.
Security Fix(es):
- kernel: efivarfs: force RO when remounting if SetVariable is not supported (CVE-2023-52463)
- kernel: nfsd: fix RELEASE_LOCKOWNER (CVE-2024-26629)
- kernel: mm: cachestat: fix folio read-after-free in cache walk (CVE-2024-26630)
- kernel: mm/writeback: fix possible divide-by-zero in wb_dirty_limits(), again (CVE-2024-26720)
- kernel: Bluetooth: af_bluetooth: Fix deadlock (CVE-2024-26886)
- kernel: kprobes/x86: Use copy_from_kernel_nofault() to read from unsafe address (CVE-2024-26946)
- kernel: KVM: SVM: Flush pages under kvm->lock to fix UAF in svm_register_enc_region() (CVE-2024-35791)
- kernel: mm: cachestat: fix two shmem bugs (CVE-2024-35797)
- kernel: x86/coco: Require seeding RNG with RDRAND on CoCo systems (CVE-2024-35875)
- kernel: mm/hugetlb: fix missing hugetlb_lock for resv uncharge (CVE-2024-36000)
- kernel: iommufd: Fix missing update of domains_itree after splitting iopt_area (CVE-2023-52801)
- kernel: net: fix out-of-bounds access in ops_init (CVE-2024-36883)
- kernel: regmap: maple: Fix cache corruption in regcache_maple_drop() (CVE-2024-36019)
- kernel: usb-storage: alauda: Check whether the media is initialized (CVE-2024-38619)
- kernel: net: bridge: mst: fix vlan use-after-free (CVE-2024-36979)
- kernel: scsi: qedf: Ensure the copied buf is NUL terminated (CVE-2024-38559)
- kernel: xhci: Handle TD clearing for multiple streams case (CVE-2024-40927)
- kernel: cxl/region: Fix memregion leaks in devm_cxl_add_region() (CVE-2024-40936)
- kernel: net/sched: Fix UAF when resolving a clash (CVE-2024-41040)
- kernel: ppp: reject claimed-as-LCP but actually malformed packets (CVE-2024-41044)
- kernel: mm: prevent derefencing NULL ptr in pfn_section_valid() (CVE-2024-41055)
- kernel: PCI/MSI: Fix UAF in msi_capability_init (CVE-2024-41096)
- kernel: xdp: Remove WARN() from __xdp_reg_mem_model() (CVE-2024-42082)
- kernel: x86: stop playing stack games in profile_pc() (CVE-2024-42096)
- kernel: Revert "mm/writeback: fix possible divide-by-zero in wb_dirty_limits(), again" (CVE-2024-42102)
- kernel: mm: avoid overflows in dirty throttling logic (CVE-2024-42131)
- kernel: nvme: avoid double free special payload (CVE-2024-41073)
For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.
- Record
ALSA-2024:6567- Updated
- 2026-11-02
OSVCLSA-2024-1728936982 No score
kernel: Fix of 86 CVEs
- drm/amd/pm: Fix negative array index read {CVE-2024-46821}
- drm/amd/display: Check gpio_id before used as array index {CVE-2024-46818}
- drm/amd/display: Check link_index before accessing dc->links[] {CVE-2024-46813}
- drm/amd/display: Fix index may exceed array range within fpu_update_bw_bounding_box {CVE-2024-46811}
- Squashfs: sanity check symbolic link size {CVE-2024-46744}
- platform/x86: panasonic-laptop: Fix SINF array out of bounds accesses {CVE-2024-46859}
- net/sched: act_api: fix possible infinite loop in tcf_idr_check_alloc() {CVE-2024-40995}
- net/sched: act_api: rely on rcu in tcf_idr_check_alloc {CVE-2024-40995}
- netfilter: bridge: confirm multicast packets before passing them up the stack {CVE-2024-27415}
- netfilter: let reset rules clean out conntrack entries {CVE-2024-27415}
- mm/filemap: make MAX_PAGECACHE_ORDER acceptable to xarray {CVE-2024-42243}
- gpiolib: cdev: Fix use after free in lineinfo_changed_notify {CVE-2024-36899}
- bpf, sockmap: Prevent lock inversion deadlock in map delete elem {CVE-2024-35895}
- bpf, sockmap: Fix preempt_rt splat when using raw_spin_lock_t {CVE-2024-35895}
- mm/huge_memory: don't unpoison huge_zero_folio {CVE-2024-40914}
- cxgb4: fix use after free bugs caused by circular dependency problem {CVE-2023-4133}
- timers: Restore ABI Compatibility with timer_delete Functions {CVE-2023-4133}
- timers: Provide timer_shutdown_sync {CVE-2023-4133}
- timers: Add shutdown mechanism to the internal functions {CVE-2023-4133}
- timers: Split [try_to_]del_timer_sync to prepare for shutdown mode {CVE-2023-4133}
- timers: Silently ignore timers with a NULL function {CVE-2023-4133}
- timers: Rename del_timer() to timer_delete() {CVE-2023-4133}
- timers: Rename del_timer_sync() to timer_delete_sync() {CVE-2023-4133}
- timers: Use del_timer_sync() even on UP {CVE-2023-4133}
- timers: Update kernel-doc for various functions {CVE-2023-4133}
- timers: Replace BUG_ON()s {CVE-2023-4133}
- timers: Get rid of del_singleshot_timer_sync() {CVE-2023-4133}
- clocksource/drivers/sp804: Do not use timer namespace for timer_shutdown() function {CVE-2023-4133}
- clocksource/drivers/arm_arch_timer: Do not use timer namespace for timer_shutdown() function {CVE-2023-4133}
- mm: avoid overflows in dirty throttling logic {CVE-2024-42131}
- ring-buffer: Fix a race between readers and resize checks {CVE-2024-38601}
- igc: avoid returning frame twice in XDP_REDIRECT {CVE-2024-26853}
- igc: Avoid transmit queue timeout for XDP {CVE-2024-26853}
- nfsd: fix RELEASE_LOCKOWNER {CVE-2024-26629}
- tty: n_gsm: require CAP_NET_ADMIN to attach N_GSM0710 ldisc {CVE-2023-52880}
- nvmet: fix a possible leak when destroy a ctrl during qp establishment {CVE-2024-42152}
- net: ntb_netdev: Move ntb_netdev_rx_handler() to call netif_rx() from __netif_rx() {CVE-2024-42110}
- x86: stop playing stack games in profile_pc() {CVE-2024-42096}
- xdp: Remove WARN() from __xdp_reg_mem_model() {CVE-2024-42082}
- NFSv4: Fix memory leak in nfs4_set_security_label {CVE-2024-41076}
- ppp: reject claimed-as-LCP but actually malformed packets {CVE-2024-41044}
- udp: Set SOCK_RCU_FREE earlier in udp_lib_get_port(). {CVE-2024-41041}
- sched/deadline: Fix task_struct reference leak {CVE-2024-41023}
- tipc: force a dst refcount before doing decryption {CVE-2024-40983}
- scsi: qedi: Fix crash while reading debugfs attribute {CVE-2024-40978}
- wifi: iwlwifi: mvm: don't read past the mfuart notifcation {CVE-2024-40941}
- wifi: iwlwifi: mvm: check n_ssids before accessing the ssids {CVE-2024-40929}
- xhci: Handle TD clearing for multiple streams case {CVE-2024-40927}
- wifi: mac80211: Fix deadlock in ieee80211_sta_ps_deliver_wakeup() {CVE-2024-40912}
- wifi: cfg80211: Lock wiphy in cfg80211_get_station {CVE-2024-40911}
- ipv6: fix possible race in __fib6_drop_pcpu_from() {CVE-2024-40905}
- md/raid5: fix deadlock that raid5d() wait for itself to clear MD_SB_CHANGE_PENDING {CVE-2024-39476}
- usb-storage: alauda: Check whether the media is…
- Record
CLSA-2024-1728936982- Updated
- 2026-11-02
OSVCLSA-2025-1763722365 No score
kernel: Fix of 63 CVEs
- wifi: mwifiex: Fix OOB and integer underflow when rx packets {CVE-2023-53226} {CVE-2023-53226}
- wifi: mac80211: check S1G action frame size {CVE-2023-53257} {CVE-2023-53257}
- wifi: cfg80211: fix use-after-free in cmp_bss() {CVE-2025-39864} {CVE-2025-39864}
- partitions: mac: fix handling of bogus partition table {CVE-2025-21772} {CVE-2025-21772}
- wifi: brcmsmac: add gain range check to wlc_phy_iqcal_gainparams_nphy() {CVE-2024-58014} {CVE-2024-58014}
- wifi: at76c50x: fix use after free access in at76_disconnect {CVE-2025-37796} {CVE-2025-37796}
- dma-direct: Leak pages on dma_set_decrypted() failure {CVE-2024-35939} {CVE-2024-35939}
- Bluetooth: L2CAP: Fix user-after-free {CVE-2022-50386} {CVE-2022-50386}
- efivarfs: Fix slab-out-of-bounds in efivarfs_d_compare {CVE-2025-39817} {CVE-2025-39817}
- wifi: cfg80211: check A-MSDU format more carefully {CVE-2024-35937} {CVE-2024-35937}
- nfs: fix UAF in direct writes {CVE-2024-26958} {CVE-2024-26958}
- wifi: iwlwifi: mvm: guard against invalid STA ID on removal {CVE-2024-36921} {CVE-2024-36921}
- net/smc: avoid data corruption caused by decline {CVE-2023-52775} {CVE-2023-52775}
- bonding: Fix out-of-bounds read in bond_option_arp_ip_targets_set() {CVE-2024-39487} {CVE-2024-39487}
- scsi: qedi: Fix crash while reading debugfs attribute {CVE-2024-40978} {CVE-2024-40978}
- mac802154: fix llsec key resources release in mac802154_llsec_key_del {CVE-2024-26961} {CVE-2024-26961}
- platform/x86: wmi: Fix opening of char device {CVE-2023-52864} {CVE-2023-52864}
- net/sched: act_mirred: don't override retval if we already lost the skb {CVE-2024-26739} {CVE-2024-26739}
- drm/dp_mst: Fix resetting msg rx state after topology removal {CVE-2024-57876} {CVE-2024-57876}
- net/mlx5: Add a timeout to acquire the command queue semaphore {CVE-2024-38556} {CVE-2024-38556}
- of: Fix double free in of_parse_phandle_with_args_map {CVE-2023-52679} {CVE-2023-52679}
- xhci: Handle TD clearing for multiple streams case {CVE-2024-40927} {CVE-2024-40927}
- wifi: mac80211: fix potential key use-after-free {CVE-2023-52530} {CVE-2023-52530}
- net: openvswitch: Fix Use-After-Free in ovs_ct_exit {CVE-2024-27395} {CVE-2024-27395}
- r8169: Fix possible ring buffer corruption on fragmented Tx packets. {CVE-2024-38586} {CVE-2024-38586}
- media: gspca: cpia1: shift-out-of-bounds in set_flicker {CVE-2023-52764} {CVE-2023-52764}
- media: bttv: fix use after free error due to btv->timeout timer {CVE-2023-52847} {CVE-2023-52847}
- vsock: Fix transport_* TOCTOU {CVE-2025-38461} {CVE-2025-38461}
- ppdev: Add an error check in register_device {CVE-2024-36015} {CVE-2024-36015}
- HID: core: Harden s32ton() against conversion to 0 bits {CVE-2025-38556} {CVE-2025-38556}
- iio: adc: at91: call input_free_device() on allocated iio_dev {CVE-2024-57904} {CVE-2024-57904}
- perf/aux: Fix AUX buffer serialization {CVE-2024-46713} {CVE-2024-46713}
- net_sched: hfsc: Fix a UAF vulnerability in class handling {CVE-2025-37797} {CVE-2025-37797}
- wifi: rtlwifi: remove unused check_buddy_priv {CVE-2024-58072} {CVE-2024-58072}
- wifi: rtlwifi: remove unused dualmac control leftovers {CVE-2024-58072} {CVE-2024-58072}
- wifi: rtlwifi: remove unused timer and related code {CVE-2024-58072} {CVE-2024-58072}
- ext4: fix out-of-bound read in ext4_xattr_inode_dec_ref_all() {CVE-2025-22121} {CVE-2025-22121}
- ext4: move where set the MAY_INLINE_DATA flag is set {CVE-2025-22121} {CVE-2025-22121}
- ext4: introduce ITAIL helper {CVE-2025-22121} {CVE-2025-22121}
- ext4: improve xattr consistency checking and error reporting {CVE-2025-22121} {CVE-2025-22121}
- mm: fix zswap writeback race condition {CVE-2023-53178} {CVE-2023-53178}
- fs: fix UAF/GPF bug in nilfs_mdt_destroy {CVE-2022-50367} {CVE-2022-50367}
- ALSA: hda/ca0132: Fix buffer overflow in add_tuning_control
- ALSA: usb-audio: Validate UAC3 cluster segment descriptors {CVE-2025-39757} {CVE-2025-39757}
- smb: client: fix use-after-free in cifs_oplock_break {CVE-2025-38527} {CVE-2025-38527} -…
- Record
CLSA-2025-1763722365- Updated
- 2026-11-02
OSV No score
xhci: Handle TD clearing for multiple streams case
In the Linux kernel, the following vulnerability has been resolved:
xhci: Handle TD clearing for multiple streams case
When multiple streams are in use, multiple TDs might be in flight when an endpoint is stopped. We need to issue a Set TR Dequeue Pointer for each, to ensure everything is reset properly and the caches cleared. Change the logic so that any N>1 TDs found active for different streams are deferred until after the first one is processed, calling xhci_invalidate_cancelled_tds() again from xhci_handle_cmd_set_deq() to queue another command until we are done with all of them. Also change the error/"should never happen" paths to ensure we at least clear any affected TDs, even if we can't issue a command to clear the hardware cache, and complain loudly with an xhci_warn() if this ever happens.
This problem case dates back to commit e9df17eb1408 ("USB: xhci: Correct assumptions about number of rings per endpoint.") early on in the XHCI driver's life, when stream support was first added. It was then identified but not fixed nor made into a warning in commit 674f8438c121 ("xhci: split handling halted endpoints into two steps"), which added a FIXME comment for the problem case (without materially changing the behavior as far as I can tell, though the new logic made the problem more obvious).
Then later, in commit 94f339147fc3 ("xhci: Fix failure to give back some cached cancelled URBs."), it was acknowledged again.
[Mathias: commit 94f339147fc3 ("xhci: Fix failure to give back some cached cancelled URBs.") was a targeted regression fix to the previously mentioned patch. Users reported issues with usb stuck after unmounting/disconnecting UAS devices. This rolled back the TD clearing of multiple streams to its original state.]
Apparently the commit author was aware of the problem (yet still chose to submit it): It was still mentioned as a FIXME, an xhci_dbg() was added to log the problem condition, and the remaining issue was mentioned in the commit description. The choice of making the log type xhci_dbg() for what is, at this point, a completely unhandled and known broken condition is puzzling and unfortunate, as it guarantees that no actual users would see the log in production, thereby making it nigh undebuggable (indeed, even if you turn on DEBUG, the message doesn't really hint at there being a problem at all).
It took me months of random xHC crashes to finally find a reliable repro and be able to do a deep dive debug session, which could all have been avoided had this unhandled, broken condition been actually reported with a warning, as it should have been as a bug intentionally left in unfixed (never mind that it shouldn't have been left in at all).
Another fix to solve clearing the caches of all stream rings with cancelled TDs is needed, but not as urgent.
3 years after that statement and 14 years after the original bug was introduced, I think it's finally time to fix it. And maybe next time let's not leave bugs unfixed (that are actually worse than the original bug), and let's actually get people to review kernel commits please.
Fixes xHC crashes and IOMMU faults with UAS devices when handling
errors/faults. Easiest repro is to use hdparm to mark an early sector
(e.g. 1024) on a disk as bad, then cat /dev/sdX > /dev/null in a loop.
At least in the case of JMicron controllers, the read errors end up
having to cancel two TDs (for two queued requests to different streams)
and the one that didn't get cleared properly ends up faulting the xHC
entirely when it tries to access DMA pages that have since been unmapped,
referred to by the stale TDs. This normally happens quickly (after two
or three loops). After this fix, I left the cat in a loop running
overnight and experienced no xHC failures, with all read errors
recovered properly. Repro'd and tested on an Apple M1 Mac Mini
(dwc3 host).
On systems without an IOMMU, this bug would instead silently corrupt freed memory, making this a ---truncated---
- Record
CVE-2024-40927- 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
OSVRLSA-2024:6567 No score
Moderate: kernel security update
The kernel packages contain the Linux kernel, the core of any Linux operating system.
Security Fix(es):
-
kernel: efivarfs: force RO when remounting if SetVariable is not supported (CVE-2023-52463)
-
kernel: nfsd: fix RELEASE_LOCKOWNER (CVE-2024-26629)
-
kernel: mm: cachestat: fix folio read-after-free in cache walk (CVE-2024-26630)
-
kernel: mm/writeback: fix possible divide-by-zero in wb_dirty_limits(), again (CVE-2024-26720)
-
kernel: Bluetooth: af_bluetooth: Fix deadlock (CVE-2024-26886)
-
kernel: kprobes/x86: Use copy_from_kernel_nofault() to read from unsafe address (CVE-2024-26946)
-
kernel: KVM: SVM: Flush pages under kvm->lock to fix UAF in svm_register_enc_region() (CVE-2024-35791)
-
kernel: mm: cachestat: fix two shmem bugs (CVE-2024-35797)
-
kernel: x86/coco: Require seeding RNG with RDRAND on CoCo systems (CVE-2024-35875)
-
kernel: mm/hugetlb: fix missing hugetlb_lock for resv uncharge (CVE-2024-36000)
-
kernel: iommufd: Fix missing update of domains_itree after splitting iopt_area (CVE-2023-52801)
-
kernel: net: fix out-of-bounds access in ops_init (CVE-2024-36883)
-
kernel: regmap: maple: Fix cache corruption in regcache_maple_drop() (CVE-2024-36019)
-
kernel: usb-storage: alauda: Check whether the media is initialized (CVE-2024-38619)
-
kernel: net: bridge: mst: fix vlan use-after-free (CVE-2024-36979)
-
kernel: scsi: qedf: Ensure the copied buf is NUL terminated (CVE-2024-38559)
-
kernel: xhci: Handle TD clearing for multiple streams case (CVE-2024-40927)
-
kernel: cxl/region: Fix memregion leaks in devm_cxl_add_region() (CVE-2024-40936)
-
kernel: net/sched: Fix UAF when resolving a clash (CVE-2024-41040)
-
kernel: ppp: reject claimed-as-LCP but actually malformed packets (CVE-2024-41044)
-
kernel: mm: prevent derefencing NULL ptr in pfn_section_valid() (CVE-2024-41055)
-
kernel: PCI/MSI: Fix UAF in msi_capability_init (CVE-2024-41096)
-
kernel: xdp: Remove WARN() from __xdp_reg_mem_model() (CVE-2024-42082)
-
kernel: x86: stop playing stack games in profile_pc() (CVE-2024-42096)
-
kernel: Revert "mm/writeback: fix possible divide-by-zero in wb_dirty_limits(), again" (CVE-2024-42102)
-
kernel: mm: avoid overflows in dirty throttling logic (CVE-2024-42131)
-
kernel: nvme: avoid double free special payload (CVE-2024-41073)
For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.
- Record
RLSA-2024:6567- 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
OSVRXSA-2024:6567 No score
Moderate: kernel security update
The kernel packages contain the Linux kernel, the core of any Linux operating system.
Security Fix(es):
-
kernel: efivarfs: force RO when remounting if SetVariable is not supported (CVE-2023-52463)
-
kernel: nfsd: fix RELEASE_LOCKOWNER (CVE-2024-26629)
-
kernel: mm: cachestat: fix folio read-after-free in cache walk (CVE-2024-26630)
-
kernel: mm/writeback: fix possible divide-by-zero in wb_dirty_limits(), again (CVE-2024-26720)
-
kernel: Bluetooth: af_bluetooth: Fix deadlock (CVE-2024-26886)
-
kernel: kprobes/x86: Use copy_from_kernel_nofault() to read from unsafe address (CVE-2024-26946)
-
kernel: KVM: SVM: Flush pages under kvm->lock to fix UAF in svm_register_enc_region() (CVE-2024-35791)
-
kernel: mm: cachestat: fix two shmem bugs (CVE-2024-35797)
-
kernel: x86/coco: Require seeding RNG with RDRAND on CoCo systems (CVE-2024-35875)
-
kernel: mm/hugetlb: fix missing hugetlb_lock for resv uncharge (CVE-2024-36000)
-
kernel: iommufd: Fix missing update of domains_itree after splitting iopt_area (CVE-2023-52801)
-
kernel: net: fix out-of-bounds access in ops_init (CVE-2024-36883)
-
kernel: regmap: maple: Fix cache corruption in regcache_maple_drop() (CVE-2024-36019)
-
kernel: usb-storage: alauda: Check whether the media is initialized (CVE-2024-38619)
-
kernel: net: bridge: mst: fix vlan use-after-free (CVE-2024-36979)
-
kernel: scsi: qedf: Ensure the copied buf is NUL terminated (CVE-2024-38559)
-
kernel: xhci: Handle TD clearing for multiple streams case (CVE-2024-40927)
-
kernel: cxl/region: Fix memregion leaks in devm_cxl_add_region() (CVE-2024-40936)
-
kernel: net/sched: Fix UAF when resolving a clash (CVE-2024-41040)
-
kernel: ppp: reject claimed-as-LCP but actually malformed packets (CVE-2024-41044)
-
kernel: mm: prevent derefencing NULL ptr in pfn_section_valid() (CVE-2024-41055)
-
kernel: PCI/MSI: Fix UAF in msi_capability_init (CVE-2024-41096)
-
kernel: xdp: Remove WARN() from __xdp_reg_mem_model() (CVE-2024-42082)
-
kernel: x86: stop playing stack games in profile_pc() (CVE-2024-42096)
-
kernel: Revert "mm/writeback: fix possible divide-by-zero in wb_dirty_limits(), again" (CVE-2024-42102)
-
kernel: mm: avoid overflows in dirty throttling logic (CVE-2024-42131)
-
kernel: nvme: avoid double free special payload (CVE-2024-41073)
For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.
- Record
RXSA-2024:6567- Updated
- 2026-11-02
OSVSUSE-SU-2024:2894-1 No score
Security update for the Linux Kernel
The SUSE Linux Enterprise 15 SP5 RT kernel was updated to receive various security bugfixes.
The following security bugs were fixed:
- CVE-2021-47086: phonet/pep: refuse to enable an unbound pipe (bsc#1220952).
- CVE-2021-47103: net: sock: preserve kabi for sock (bsc#1221010).
- CVE-2021-47186: tipc: check for null after calling kmemdup (bsc#1222702).
- CVE-2021-47546: Kabi fix for ipv6: fix memory leak in fib6_rule_suppress (bsc#1225504).
- CVE-2021-47547: net: tulip: de4x5: fix the problem that the array 'lp->phy' may be out of bound (bsc#1225505).
- CVE-2021-47588: sit: do not call ipip6_dev_free() from sit_init_net() (bsc#1226568).
- CVE-2021-47590: mptcp: fix deadlock in __mptcp_push_pending() (bsc#1226565).
- CVE-2021-47591: mptcp: remove tcp ulp setsockopt support (bsc#1226570).
- CVE-2021-47593: mptcp: clear 'kern' flag from fallback sockets (bsc#1226551).
- CVE-2021-47598: sch_cake: do not call cake_destroy() from cake_init() (bsc#1226574).
- CVE-2021-47599: btrfs: use latest_dev in btrfs_show_devname (bsc#1226571)
- CVE-2021-47606: net: netlink: af_netlink: Prevent empty skb by adding a check on len (bsc#1226555).
- CVE-2021-47623: powerpc/fixmap: Fix VM debug warning on unmap (bsc#1227919).
- CVE-2022-48785: ipv6: mcast: use rcu-safe version of ipv6_get_lladdr() (bsc#1227927)
- CVE-2022-48810: ipmr,ip6mr: acquire RTNL before calling ip[6]mr_free_table() on failure path (bsc#1227936).
- CVE-2022-48850: net-sysfs: add check for netdevice being present to speed_show (bsc#1228071)
- CVE-2022-48855: sctp: fix kernel-infoleak for SCTP sockets (bsc#1228003).
- CVE-2023-52435: net: prevent mss overflow in skb_segment() (bsc#1220138).
- CVE-2023-52573: net: rds: Fix possible NULL-pointer dereference (bsc#1220869)
- CVE-2023-52580: net/core: Fix ETH_P_1588 flow dissector (bsc#1220876).
- CVE-2023-52751: smb: client: fix use-after-free in smb2_query_info_compound() (bsc#1225489).
- CVE-2023-52775: net/smc: avoid data corruption caused by decline (bsc#1225088).
- CVE-2023-52812: drm/amd: check num of link levels when update pcie param (bsc#1225564).
- CVE-2023-52857: drm/mediatek: Fix coverity issue with unintentional integer overflow (bsc#1225581).
- CVE-2023-52863: hwmon: (axi-fan-control) Fix possible NULL pointer dereference (bsc#1225586).
- CVE-2024-26585: Fixed race between tx work scheduling and socket close (bsc#1220187).
- CVE-2024-26615: net/smc: fix illegal rmb_desc access in SMC-D connection dump (bsc#1220942).
- CVE-2024-26633: ip6_tunnel: fix NEXTHDR_FRAGMENT handling in ip6_tnl_parse_tlv_enc_lim() (bsc#1221647).
- CVE-2024-26635: llc: Drop support for ETH_P_TR_802_2 (bsc#1221656).
- CVE-2024-26636: llc: make llc_ui_sendmsg() more robust against bonding changes (bsc#1221659).
- CVE-2024-26641: ip6_tunnel: make sure to pull inner header in __ip6_tnl_rcv() (bsc#1221654).
- CVE-2024-26661: drm/amd/display: Add NULL test for 'timing generator' in (bsc#1222323)
- CVE-2024-26663: tipc: Check the bearer type before calling tipc_udp_nl_bearer_add() (bsc#1222326).
- CVE-2024-26665: tunnels: fix out of bounds access when building IPv6 PMTU error (bsc#1222328).
- CVE-2024-26802: stmmac: Clear variable when destroying workqueue (bsc#1222799).
- CVE-2024-26863: hsr: Fix uninit-value access in hsr_get_node() (bsc#1223021).
- CVE-2024-26961: mac802154: fix llsec key resources release in mac802154_llsec_key_del (bsc#1223652).
- CVE-2024-27015: netfilter: flowtable: incorrect pppoe tuple (bsc#1223806).
- CVE-2024-27019: netfilter: nf_tables: Fix potential data-race in __nft_obj_type_get() (bsc#1223813)
- CVE-2024-27020: netfilter: nf_tables: Fix potential data-race in __nft_expr_type_get() (bsc#1223815)
- CVE-2024-27025: nbd: null check for nla_nest_start (bsc#1223778)
- CVE-2024-27065: netfilter: nf_tables: do not compare internal table flags on updates (bsc#1223836).
- CVE-2024-27402: phonet/pep: fix racy skb_queue_empty() use (bsc#1224414).
- CVE-2024-27437: vfio/pci: Disable auto-enable of exclusive INTx IRQ…
- Record
SUSE-SU-2024:2894-1- Updated
- 2026-11-02
OSVSUSE-SU-2024:2939-1 No score
Security update for the Linux Kernel
The SUSE Linux Enterprise 15 SP5 kernel was updated to receive various security bugfixes.
The following security bugs were fixed:
- CVE-2021-47086: phonet/pep: refuse to enable an unbound pipe (bsc#1220952).
- CVE-2021-47089: kfence: fix memory leak when cat kfence objects (bsc#1220958).
- CVE-2021-47103: net: sock: preserve kabi for sock (bsc#1221010).
- CVE-2021-47186: tipc: check for null after calling kmemdup (bsc#1222702).
- CVE-2021-47432: lib/generic-radix-tree.c: Do not overflow in peek() (bsc#1225391).
- CVE-2021-47515: seg6: fix the iif in the IPv6 socket control block (bsc#1225426).
- CVE-2021-47538: rxrpc: Fix rxrpc_local leak in rxrpc_lookup_peer() (bsc#1225448).
- CVE-2021-47539: rxrpc: Fix rxrpc_peer leak in rxrpc_look_up_bundle() (bsc#1225452).
- CVE-2021-47546: ipv6: fix memory leak in fib6_rule_suppress (bsc#1225504).
- CVE-2021-47547: net: tulip: de4x5: fix the problem that the array 'lp->phy' may be out of bound (bsc#1225505).
- CVE-2021-47555: net: vlan: fix underflow for the real_dev refcnt (bsc#1225467).
- CVE-2021-47566: Fix clearing user buffer by properly using clear_user() (bsc#1225514).
- CVE-2021-47571: staging: rtl8192e: Fix use after free in _rtl92e_pci_disconnect() (bsc#1225518).
- CVE-2021-47572: net: nexthop: fix null pointer dereference when IPv6 is not enabled (bsc#1225389).
- CVE-2021-47588: sit: do not call ipip6_dev_free() from sit_init_net() (bsc#1226568).
- CVE-2021-47590: mptcp: fix deadlock in __mptcp_push_pending() (bsc#1226565).
- CVE-2021-47591: mptcp: remove tcp ulp setsockopt support (bsc#1226570).
- CVE-2021-47593: mptcp: clear 'kern' flag from fallback sockets (bsc#1226551).
- CVE-2021-47598: sch_cake: do not call cake_destroy() from cake_init() (bsc#1226574).
- CVE-2021-47599: btrfs: use latest_dev in btrfs_show_devname (bsc#1226571).
- CVE-2021-47606: net: netlink: af_netlink: Prevent empty skb by adding a check on len. (bsc#1226555).
- CVE-2021-47623: powerpc/fixmap: Fix VM debug warning on unmap (bsc#1227919).
- CVE-2022-48716: ASoC: codecs: wcd938x: fix incorrect used of portid (bsc#1226678).
- CVE-2022-48785: ipv6: mcast: use rcu-safe version of ipv6_get_lladdr() (bsc#1227927)
- CVE-2022-48810: ipmr,ip6mr: acquire RTNL before calling ip[6]mr_free_table() on failure path (bsc#1227936).
- CVE-2022-48850: net-sysfs: add check for netdevice being present to speed_show (bsc#1228071).
- CVE-2022-48855: sctp: fix kernel-infoleak for SCTP sockets (bsc#1228003).
- CVE-2023-24023: Bluetooth: Add more enc key size check (bsc#1218148).
- CVE-2023-52435: net: prevent mss overflow in skb_segment() (bsc#1220138).
- CVE-2023-52573: net: rds: Fix possible NULL-pointer dereference (bsc#1220869).
- CVE-2023-52580: net/core: Fix ETH_P_1588 flow dissector (bsc#1220876).
- CVE-2023-52622: ext4: avoid online resizing failures due to oversized flex bg (bsc#1222080).
- CVE-2023-52658: Revert 'net/mlx5: Block entering switchdev mode with ns inconsistency' (bsc#1224719).
- CVE-2023-52667: net/mlx5e: fix a potential double-free in fs_any_create_groups (bsc#1224603).
- CVE-2023-52670: rpmsg: virtio: Free driver_override when rpmsg_remove() (bsc#1224696).
- CVE-2023-52672: pipe: wakeup wr_wait after setting max_usage (bsc#1224614).
- CVE-2023-52675: powerpc/imc-pmu: Add a null pointer check in update_events_in_group() (bsc#1224504).
- CVE-2023-52735: bpf, sockmap: Don't let sock_map_{close,destroy,unhash} call itself (bsc#1225475).
- CVE-2023-52737: btrfs: lock the inode in shared mode before starting fiemap (bsc#1225484).
- CVE-2023-52751: smb: client: fix use-after-free in smb2_query_info_compound() (bsc#1225489).
- CVE-2023-52752: smb: client: fix use-after-free bug in cifs_debug_data_proc_show() (bsc#1225487).
- CVE-2023-52762: virtio-blk: fix implicit overflow on virtio_max_dma_size (bsc#1225573).
- CVE-2023-52775: net/smc: avoid data corruption caused by decline (bsc#1225088).
- CVE-2023-52784: bonding: stop the device in bond_setup_by_slave() (bsc#1224946).
- CVE-2023-52787: blk-mq: make…
- Record
SUSE-SU-2024:2939-1- Updated
- 2026-11-02
OSVSUSE-SU-2024:2947-1 No score
Security update for the Linux Kernel
The SUSE Linux Enterprise 15 SP5 Azure kernel was updated to receive various security bugfixes.
The following security bugs were fixed:
- CVE-2021-47086: phonet/pep: refuse to enable an unbound pipe (bsc#1220952).
- CVE-2021-47103: net: sock: preserve kabi for sock (bsc#1221010).
- CVE-2021-47186: ipc: check for null after calling kmemdup (bsc#1222702).
- CVE-2021-47546: Kabi fix for ipv6: fix memory leak in fib6_rule_suppress (bsc#1225504).
- CVE-2021-47547: net: tulip: de4x5: fix the problem that the array 'lp->phy' may be out of bound (bsc#1225505).
- CVE-2021-47588: sit: do not call ipip6_dev_free() from sit_init_net() (bsc#1226568).
- CVE-2021-47590: mptcp: fix deadlock in __mptcp_push_pending() (bsc#1226565).
- CVE-2021-47591: mptcp: remove tcp ulp setsockopt support (bsc#1226570).
- CVE-2021-47593: mptcp: clear 'kern' flag from fallback sockets (bsc#1226551).
- CVE-2021-47598: sch_cake: do not call cake_destroy() from cake_init() (bsc#1226574).
- CVE-2021-47599: btrfs: use latest_dev in btrfs_show_devname (bsc#1226571)
- CVE-2021-47606: net: netlink: af_netlink: Prevent empty skb by adding a check on len (bsc#1226555).
- CVE-2021-47623: powerpc/fixmap: Fix VM debug warning on unmap (bsc#1227919).
- CVE-2022-48785: ipv6: mcast: use rcu-safe version of ipv6_get_lladdr() (bsc#1227927)
- CVE-2022-48810: ipmr,ip6mr: acquire RTNL before calling ip[6]mr_free_table() on failure path (bsc#1227936).
- CVE-2022-48850: net-sysfs: add check for netdevice being present to speed_show (bsc#1228071)
- CVE-2022-48855: sctp: fix kernel-infoleak for SCTP sockets (bsc#1228003).
- CVE-2023-52435: net: prevent mss overflow in skb_segment() (bsc#1220138).
- CVE-2023-52573: net: rds: Fix possible NULL-pointer dereference (bsc#1220869)
- CVE-2023-52580: net/core: Fix ETH_P_1588 flow dissector (bsc#1220876).
- CVE-2023-52751: smb: client: fix use-after-free in smb2_query_info_compound() (bsc#1225489).
- CVE-2023-52775: net/smc: avoid data corruption caused by decline (bsc#1225088).
- CVE-2023-52812: drm/amd: check num of link levels when update pcie param (bsc#1225564).
- CVE-2023-52857: drm/mediatek: Fix coverity issue with unintentional integer overflow (bsc#1225581).
- CVE-2023-52863: hwmon: (axi-fan-control) Fix possible NULL pointer dereference (bsc#1225586).
- CVE-2024-26585: Fixed race between tx work scheduling and socket close (bsc#1220187).
- CVE-2024-26615: net/smc: fix illegal rmb_desc access in SMC-D connection dump (bsc#1220942).
- CVE-2024-26633: ip6_tunnel: fix NEXTHDR_FRAGMENT handling in ip6_tnl_parse_tlv_enc_lim() (bsc#1221647).
- CVE-2024-26635: llc: Drop support for ETH_P_TR_802_2 (bsc#1221656).
- CVE-2024-26636: llc: make llc_ui_sendmsg() more robust against bonding changes (bsc#1221659).
- CVE-2024-26641: ip6_tunnel: make sure to pull inner header in __ip6_tnl_rcv() (bsc#1221654).
- CVE-2024-26661: drm/amd/display: Add NULL test for 'timing generator' in (bsc#1222323)
- CVE-2024-26663: tipc: Check the bearer type before calling tipc_udp_nl_bearer_add() (bsc#1222326).
- CVE-2024-26665: tunnels: fix out of bounds access when building IPv6 PMTU error (bsc#1222328).
- CVE-2024-26802: stmmac: Clear variable when destroying workqueue (bsc#1222799).
- CVE-2024-26863: hsr: Fix uninit-value access in hsr_get_node() (bsc#1223021).
- CVE-2024-26961: mac802154: fix llsec key resources release in mac802154_llsec_key_del (bsc#1223652).
- CVE-2024-27015: netfilter: flowtable: incorrect pppoe tuple (bsc#1223806).
- CVE-2024-27019: netfilter: nf_tables: Fix potential data-race in __nft_obj_type_get() (bsc#1223813)
- CVE-2024-27020: netfilter: nf_tables: Fix potential data-race in __nft_expr_type_get() (bsc#1223815)
- CVE-2024-27025: nbd: null check for nla_nest_start (bsc#1223778)
- CVE-2024-27065: netfilter: nf_tables: do not compare internal table flags on updates (bsc#1223836).
- CVE-2024-27402: phonet/pep: fix racy skb_queue_empty() use (bsc#1224414).
- CVE-2024-27437: vfio/pci: Disable auto-enable of exclusive INTx IRQ…
- Record
SUSE-SU-2024:2947-1- Updated
- 2026-11-02
OSVSUSE-SU-2024: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-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-6999-1 No score
linux, linux-aws, linux-gcp, linux-gke, linux-ibm, linux-lowlatency, linux-oem-6.8, linux-oracle vulnerabilities
Chenyuan Yang discovered that the CEC driver driver in the Linux kernel contained a use-after-free vulnerability. A local attacker could use this to cause a denial of service (system crash) or possibly execute arbitrary code. (CVE-2024-23848)
It was discovered that the JFS file system contained an out-of-bounds read vulnerability when printing xattr debug information. A local attacker could use this to cause a denial of service (system crash). (CVE-2024-40902)
Several security issues were discovered in the Linux kernel. An attacker could possibly use these to compromise the system. This update corrects flaws in the following subsystems:
- ARM64 architecture;
- MIPS architecture;
- PA-RISC architecture;
- PowerPC architecture;
- RISC-V architecture;
- x86 architecture;
- Block layer subsystem;
- ACPI drivers;
- Drivers core;
- Null block device driver;
- Character device driver;
- TPM device driver;
- Clock framework and drivers;
- CPU frequency scaling framework;
- Hardware crypto device drivers;
- CXL (Compute Express Link) drivers;
- Buffer Sharing and Synchronization framework;
- DMA engine subsystem;
- EFI core;
- FPGA Framework;
- GPU drivers;
- Greybus drivers;
- HID subsystem;
- HW tracing;
- I2C subsystem;
- IIO subsystem;
- InfiniBand drivers;
- Input Device (Mouse) drivers;
- Mailbox framework;
- Media drivers;
- Microchip PCI driver;
- VMware VMCI Driver;
- Network drivers;
- PCI subsystem;
- x86 platform drivers;
- PTP clock framework;
- S/390 drivers;
- SCSI drivers;
- SoundWire subsystem;
- Sonic Silicon Backplane drivers;
- Greybus lights staging drivers;
- Thermal drivers;
- TTY drivers;
- USB subsystem;
- VFIO drivers;
- Framebuffer layer;
- Watchdog drivers;
- 9P distributed file system;
- BTRFS file system;
- File systems infrastructure;
- Ext4 file system;
- F2FS file system;
- JFS file system;
- Network file system server daemon;
- NILFS2 file system;
- NTFS3 file system;
- SMB network file system;
- Tracing file system;
- Tracing infrastructure;
- io_uring subsystem;
- Core kernel;
- BPF subsystem;
- Kernel debugger infrastructure;
- DMA mapping infrastructure;
- IRQ subsystem;
- Memory management;
- 9P file system network protocol;
- Amateur Radio drivers;
- B.A.T.M.A.N. meshing protocol;
- Ethernet bridge;
- Networking core;
- Ethtool driver;
- IPv4 networking;
- IPv6 networking;
- MAC80211 subsystem;
- Multipath TCP;
- Netfilter;
- NET/ROM layer;
- NFC subsystem;
- Network traffic control;
- Sun RPC protocol;
- TIPC protocol;
- TLS protocol;
- Unix domain sockets;
- Wireless networking;
- XFRM subsystem;
- AppArmor security module;
- Integrity Measurement Architecture(IMA) framework;
- Landlock security;
- Linux Security Modules (LSM) Framework;
- SELinux security module;
- Simplified Mandatory Access Control Kernel framework;
- ALSA framework;
- HD-audio driver;
- SOF drivers;
- KVM core; (CVE-2024-40911, CVE-2024-37356, CVE-2024-40935, CVE-2024-40944, CVE-2024-41003, CVE-2024-40990, CVE-2024-40952, CVE-2024-40940, CVE-2024-40930, CVE-2024-40985, CVE-2024-40941, CVE-2024-38630, CVE-2024-39466, CVE-2024-40933, CVE-2024-38624, CVE-2024-40924, CVE-2024-40945, CVE-2024-40899, CVE-2024-38622, CVE-2024-40979, CVE-2024-36484, CVE-2024-41004, CVE-2024-39474, CVE-2022-48772, CVE-2024-36244, CVE-2024-38664, CVE-2024-40925, CVE-2024-40980, CVE-2024-39480, CVE-2024-36270, CVE-2024-40936, CVE-2024-40904, CVE-2024-38635, CVE-2024-40927, CVE-2024-36481, CVE-2024-40929, CVE-2024-40958, CVE-2024-36978, CVE-2024-40992, CVE-2024-40908, CVE-2024-39504, CVE-2024-41001, CVE-2024-40967, CVE-2023-52884, CVE-2024-40997, CVE-2024-40903, CVE-2024-40913, CVE-2024-34030, CVE-2024-39473, CVE-2024-40966, CVE-2024-40951, CVE-2024-40902, CVE-2024-40982, CVE-2024-40923, CVE-2024-39467, CVE-2024-40910, CVE-2024-40909, CVE-2024-39463,…
- Record
USN-6999-1- Updated
- 2026-11-02
OSVUSN-6999-2 No score
linux-raspi vulnerabilities
Chenyuan Yang discovered that the CEC driver driver in the Linux kernel contained a use-after-free vulnerability. A local attacker could use this to cause a denial of service (system crash) or possibly execute arbitrary code. (CVE-2024-23848)
It was discovered that the JFS file system contained an out-of-bounds read vulnerability when printing xattr debug information. A local attacker could use this to cause a denial of service (system crash). (CVE-2024-40902)
Several security issues were discovered in the Linux kernel. An attacker could possibly use these to compromise the system. This update corrects flaws in the following subsystems:
- ARM64 architecture;
- MIPS architecture;
- PA-RISC architecture;
- PowerPC architecture;
- RISC-V architecture;
- x86 architecture;
- Block layer subsystem;
- ACPI drivers;
- Drivers core;
- Null block device driver;
- Character device driver;
- TPM device driver;
- Clock framework and drivers;
- CPU frequency scaling framework;
- Hardware crypto device drivers;
- CXL (Compute Express Link) drivers;
- Buffer Sharing and Synchronization framework;
- DMA engine subsystem;
- EFI core;
- FPGA Framework;
- GPU drivers;
- Greybus drivers;
- HID subsystem;
- HW tracing;
- I2C subsystem;
- IIO subsystem;
- InfiniBand drivers;
- Input Device (Mouse) drivers;
- Mailbox framework;
- Media drivers;
- Microchip PCI driver;
- VMware VMCI Driver;
- Network drivers;
- PCI subsystem;
- x86 platform drivers;
- PTP clock framework;
- S/390 drivers;
- SCSI drivers;
- SoundWire subsystem;
- Sonic Silicon Backplane drivers;
- Greybus lights staging drivers;
- Thermal drivers;
- TTY drivers;
- USB subsystem;
- VFIO drivers;
- Framebuffer layer;
- Watchdog drivers;
- 9P distributed file system;
- BTRFS file system;
- File systems infrastructure;
- Ext4 file system;
- F2FS file system;
- JFS file system;
- Network file system server daemon;
- NILFS2 file system;
- NTFS3 file system;
- SMB network file system;
- Tracing file system;
- IOMMU subsystem;
- Tracing infrastructure;
- io_uring subsystem;
- Core kernel;
- BPF subsystem;
- Kernel debugger infrastructure;
- DMA mapping infrastructure;
- IRQ subsystem;
- Memory management;
- 9P file system network protocol;
- Amateur Radio drivers;
- B.A.T.M.A.N. meshing protocol;
- Ethernet bridge;
- Networking core;
- Ethtool driver;
- IPv4 networking;
- IPv6 networking;
- MAC80211 subsystem;
- Multipath TCP;
- Netfilter;
- NET/ROM layer;
- NFC subsystem;
- Network traffic control;
- Sun RPC protocol;
- TIPC protocol;
- TLS protocol;
- Unix domain sockets;
- Wireless networking;
- XFRM subsystem;
- AppArmor security module;
- Integrity Measurement Architecture(IMA) framework;
- Landlock security;
- Linux Security Modules (LSM) Framework;
- SELinux security module;
- Simplified Mandatory Access Control Kernel framework;
- ALSA framework;
- HD-audio driver;
- SOF drivers;
- KVM core; (CVE-2024-40978, CVE-2024-39504, CVE-2024-39483, CVE-2024-36478, CVE-2024-40928, CVE-2024-36971, CVE-2024-40947, CVE-2024-31076, CVE-2024-40934, CVE-2024-40909, CVE-2024-40962, CVE-2024-38635, CVE-2024-38632, CVE-2024-40912, CVE-2024-40967, CVE-2024-39492, CVE-2024-40974, CVE-2024-39466, CVE-2024-40939, CVE-2024-40988, CVE-2024-40951, CVE-2024-41005, CVE-2024-40968, CVE-2024-39493, CVE-2024-40949, CVE-2022-48772, CVE-2024-40944, CVE-2024-40998, CVE-2024-39490, CVE-2024-39467, CVE-2024-42078, CVE-2024-40953, CVE-2024-40990, CVE-2024-40902, CVE-2024-39461, CVE-2024-39301, CVE-2024-36978, CVE-2024-39475, CVE-2024-39496, CVE-2024-40901, CVE-2024-40985, CVE-2024-33621, CVE-2024-38663, CVE-2024-39497, CVE-2024-40937, CVE-2024-40941, CVE-2024-40987, CVE-2024-40918, CVE-2024-32936, CVE-2024-40999, CVE-2024-40938, CVE-2024-39488, CVE-2024-39510, CVE-2024-40924, CVE-2024-38661, CVE-2024-40989, CVE-2024-39509,…
- Record
USN-6999-2- Updated
- 2026-11-02
OSVUSN-7004-1 No score
linux-azure vulnerabilities
Chenyuan Yang discovered that the CEC driver driver in the Linux kernel contained a use-after-free vulnerability. A local attacker could use this to cause a denial of service (system crash) or possibly execute arbitrary code. (CVE-2024-23848)
It was discovered that the JFS file system contained an out-of-bounds read vulnerability when printing xattr debug information. A local attacker could use this to cause a denial of service (system crash). (CVE-2024-40902)
Several security issues were discovered in the Linux kernel. An attacker could possibly use these to compromise the system. This update corrects flaws in the following subsystems:
- ARM64 architecture;
- MIPS architecture;
- PA-RISC architecture;
- PowerPC architecture;
- RISC-V architecture;
- x86 architecture;
- Block layer subsystem;
- ACPI drivers;
- Drivers core;
- Null block device driver;
- Character device driver;
- TPM device driver;
- Clock framework and drivers;
- CPU frequency scaling framework;
- Hardware crypto device drivers;
- CXL (Compute Express Link) drivers;
- Buffer Sharing and Synchronization framework;
- DMA engine subsystem;
- EFI core;
- FPGA Framework;
- GPU drivers;
- Greybus drivers;
- HID subsystem;
- HW tracing;
- I2C subsystem;
- IIO subsystem;
- InfiniBand drivers;
- Input Device (Mouse) drivers;
- Mailbox framework;
- Media drivers;
- Microchip PCI driver;
- VMware VMCI Driver;
- Network drivers;
- PCI subsystem;
- x86 platform drivers;
- PTP clock framework;
- S/390 drivers;
- SCSI drivers;
- SoundWire subsystem;
- Sonic Silicon Backplane drivers;
- Greybus lights staging drivers;
- Thermal drivers;
- TTY drivers;
- USB subsystem;
- VFIO drivers;
- Framebuffer layer;
- Watchdog drivers;
- 9P distributed file system;
- BTRFS file system;
- File systems infrastructure;
- Ext4 file system;
- F2FS file system;
- JFS file system;
- Network file system server daemon;
- NILFS2 file system;
- NTFS3 file system;
- SMB network file system;
- Tracing file system;
- IOMMU subsystem;
- Tracing infrastructure;
- io_uring subsystem;
- Core kernel;
- BPF subsystem;
- Kernel debugger infrastructure;
- DMA mapping infrastructure;
- IRQ subsystem;
- Memory management;
- 9P file system network protocol;
- Amateur Radio drivers;
- B.A.T.M.A.N. meshing protocol;
- Ethernet bridge;
- Networking core;
- Ethtool driver;
- IPv4 networking;
- IPv6 networking;
- MAC80211 subsystem;
- Multipath TCP;
- Netfilter;
- NET/ROM layer;
- NFC subsystem;
- Network traffic control;
- Sun RPC protocol;
- TIPC protocol;
- TLS protocol;
- Unix domain sockets;
- Wireless networking;
- XFRM subsystem;
- AppArmor security module;
- Integrity Measurement Architecture(IMA) framework;
- Landlock security;
- Linux Security Modules (LSM) Framework;
- SELinux security module;
- Simplified Mandatory Access Control Kernel framework;
- ALSA framework;
- HD-audio driver;
- SOF drivers;
- KVM core; (CVE-2024-36270, CVE-2024-38627, CVE-2024-39508, CVE-2024-41001, CVE-2024-38634, CVE-2024-40979, CVE-2024-40903, CVE-2024-34030, CVE-2024-38621, CVE-2024-34027, CVE-2024-39504, CVE-2024-38385, CVE-2024-36288, CVE-2024-39301, CVE-2024-38628, CVE-2024-42270, CVE-2024-39507, CVE-2024-36286, CVE-2024-40960, CVE-2024-36479, CVE-2024-41002, CVE-2024-36974, CVE-2024-40943, CVE-2024-40976, CVE-2024-38662, CVE-2024-40995, CVE-2024-39497, CVE-2024-31076, CVE-2024-39371, CVE-2024-40983, CVE-2024-40985, CVE-2024-38618, CVE-2024-40914, CVE-2024-40989, CVE-2024-40973, CVE-2024-38663, CVE-2024-39463, CVE-2024-38633, CVE-2024-36978, CVE-2024-40970, CVE-2024-40932, CVE-2024-39480, CVE-2024-39471, CVE-2024-40962, CVE-2024-40986, CVE-2024-40937, CVE-2024-39469, CVE-2024-40904, CVE-2024-39466, CVE-2024-38388, CVE-2024-39494, CVE-2024-41004, CVE-2024-38381, CVE-2022-48772, CVE-2024-33847, CVE-2024-40969, CVE-2024-40957,…
- Record
USN-7004-1- Updated
- 2026-11-02
OSVUSN-7005-1 No score
linux-nvidia, linux-nvidia-lowlatency vulnerabilities
Chenyuan Yang discovered that the CEC driver driver in the Linux kernel contained a use-after-free vulnerability. A local attacker could use this to cause a denial of service (system crash) or possibly execute arbitrary code. (CVE-2024-23848)
It was discovered that the JFS file system contained an out-of-bounds read vulnerability when printing xattr debug information. A local attacker could use this to cause a denial of service (system crash). (CVE-2024-40902)
Several security issues were discovered in the Linux kernel. An attacker could possibly use these to compromise the system. This update corrects flaws in the following subsystems:
- ARM64 architecture;
- MIPS architecture;
- PA-RISC architecture;
- PowerPC architecture;
- RISC-V architecture;
- x86 architecture;
- Block layer subsystem;
- ACPI drivers;
- Drivers core;
- Null block device driver;
- Character device driver;
- Clock framework and drivers;
- CPU frequency scaling framework;
- Hardware crypto device drivers;
- CXL (Compute Express Link) drivers;
- Buffer Sharing and Synchronization framework;
- DMA engine subsystem;
- EFI core;
- FPGA Framework;
- GPU drivers;
- Greybus drivers;
- HID subsystem;
- HW tracing;
- I2C subsystem;
- IIO subsystem;
- InfiniBand drivers;
- Input Device (Mouse) drivers;
- Mailbox framework;
- Media drivers;
- Microchip PCI driver;
- VMware VMCI Driver;
- Network drivers;
- PCI subsystem;
- x86 platform drivers;
- PTP clock framework;
- S/390 drivers;
- SCSI drivers;
- SoundWire subsystem;
- Sonic Silicon Backplane drivers;
- Greybus lights staging drivers;
- Thermal drivers;
- TTY drivers;
- USB subsystem;
- VFIO drivers;
- Framebuffer layer;
- Watchdog drivers;
- 9P distributed file system;
- BTRFS file system;
- File systems infrastructure;
- Ext4 file system;
- F2FS file system;
- JFS file system;
- Network file system server daemon;
- NILFS2 file system;
- NTFS3 file system;
- SMB network file system;
- Tracing file system;
- IOMMU subsystem;
- Tracing infrastructure;
- io_uring subsystem;
- Core kernel;
- BPF subsystem;
- Kernel debugger infrastructure;
- DMA mapping infrastructure;
- IRQ subsystem;
- Memory management;
- 9P file system network protocol;
- Amateur Radio drivers;
- B.A.T.M.A.N. meshing protocol;
- Ethernet bridge;
- Networking core;
- Ethtool driver;
- IPv4 networking;
- IPv6 networking;
- MAC80211 subsystem;
- Multipath TCP;
- Netfilter;
- NET/ROM layer;
- NFC subsystem;
- Network traffic control;
- Sun RPC protocol;
- TIPC protocol;
- TLS protocol;
- Unix domain sockets;
- Wireless networking;
- XFRM subsystem;
- AppArmor security module;
- Integrity Measurement Architecture(IMA) framework;
- Landlock security;
- Linux Security Modules (LSM) Framework;
- SELinux security module;
- Simplified Mandatory Access Control Kernel framework;
- ALSA framework;
- HD-audio driver;
- SOF drivers;
- KVM core; (CVE-2024-40963, CVE-2024-40994, CVE-2024-36481, CVE-2024-39301, CVE-2024-38390, CVE-2024-40976, CVE-2024-40934, CVE-2024-40902, CVE-2024-40916, CVE-2024-39298, CVE-2024-38659, CVE-2024-38384, CVE-2024-38635, CVE-2024-39494, CVE-2024-40926, CVE-2024-40956, CVE-2024-40948, CVE-2024-40920, CVE-2024-38624, CVE-2024-39498, CVE-2024-38780, CVE-2024-39503, CVE-2024-40919, CVE-2024-39505, CVE-2024-40988, CVE-2024-36972, CVE-2024-36974, CVE-2024-39495, CVE-2024-40992, CVE-2024-36015, CVE-2024-38618, CVE-2024-39478, CVE-2024-40975, CVE-2024-39507, CVE-2024-39479, CVE-2024-39291, CVE-2024-40925, CVE-2024-39493, CVE-2024-41005, CVE-2024-40932, CVE-2024-39467, CVE-2024-40973, CVE-2024-38634, CVE-2024-34027, CVE-2024-39462, CVE-2024-40949, CVE-2024-40908, CVE-2024-40929, CVE-2024-38662, CVE-2024-39489, CVE-2024-40953, CVE-2024-38306, CVE-2024-40915, CVE-2024-39470, CVE-2024-40969, CVE-2024-31076, CVE-2024-38663, CVE-2024-38629,…
- Record
USN-7005-1- Updated
- 2026-11-02
OSVUSN-7005-2 No score
linux-nvidia-6.8 vulnerabilities
Chenyuan Yang discovered that the CEC driver driver in the Linux kernel contained a use-after-free vulnerability. A local attacker could use this to cause a denial of service (system crash) or possibly execute arbitrary code. (CVE-2024-23848)
It was discovered that the JFS file system contained an out-of-bounds read vulnerability when printing xattr debug information. A local attacker could use this to cause a denial of service (system crash). (CVE-2024-40902)
Several security issues were discovered in the Linux kernel. An attacker could possibly use these to compromise the system. This update corrects flaws in the following subsystems:
- ARM64 architecture;
- MIPS architecture;
- PA-RISC architecture;
- PowerPC architecture;
- RISC-V architecture;
- x86 architecture;
- Block layer subsystem;
- ACPI drivers;
- Drivers core;
- Null block device driver;
- Character device driver;
- Clock framework and drivers;
- CPU frequency scaling framework;
- Hardware crypto device drivers;
- CXL (Compute Express Link) drivers;
- Buffer Sharing and Synchronization framework;
- DMA engine subsystem;
- EFI core;
- FPGA Framework;
- GPU drivers;
- Greybus drivers;
- HID subsystem;
- HW tracing;
- I2C subsystem;
- IIO subsystem;
- InfiniBand drivers;
- Input Device (Mouse) drivers;
- Mailbox framework;
- Media drivers;
- Microchip PCI driver;
- VMware VMCI Driver;
- Network drivers;
- PCI subsystem;
- x86 platform drivers;
- PTP clock framework;
- S/390 drivers;
- SCSI drivers;
- SoundWire subsystem;
- Sonic Silicon Backplane drivers;
- Greybus lights staging drivers;
- Thermal drivers;
- TTY drivers;
- USB subsystem;
- VFIO drivers;
- Framebuffer layer;
- Watchdog drivers;
- 9P distributed file system;
- BTRFS file system;
- File systems infrastructure;
- Ext4 file system;
- F2FS file system;
- JFS file system;
- Network file system server daemon;
- NILFS2 file system;
- NTFS3 file system;
- SMB network file system;
- Tracing file system;
- IOMMU subsystem;
- Tracing infrastructure;
- io_uring subsystem;
- Core kernel;
- BPF subsystem;
- Kernel debugger infrastructure;
- DMA mapping infrastructure;
- IRQ subsystem;
- Memory management;
- 9P file system network protocol;
- Amateur Radio drivers;
- B.A.T.M.A.N. meshing protocol;
- Ethernet bridge;
- Networking core;
- Ethtool driver;
- IPv4 networking;
- IPv6 networking;
- MAC80211 subsystem;
- Multipath TCP;
- Netfilter;
- NET/ROM layer;
- NFC subsystem;
- Network traffic control;
- Sun RPC protocol;
- TIPC protocol;
- TLS protocol;
- Unix domain sockets;
- Wireless networking;
- XFRM subsystem;
- AppArmor security module;
- Integrity Measurement Architecture(IMA) framework;
- Landlock security;
- Linux Security Modules (LSM) Framework;
- SELinux security module;
- Simplified Mandatory Access Control Kernel framework;
- ALSA framework;
- HD-audio driver;
- SOF drivers;
- KVM core; (CVE-2024-39465, CVE-2024-39492, CVE-2024-40976, CVE-2024-40956, CVE-2024-39480, CVE-2024-39467, CVE-2024-39478, CVE-2024-39489, CVE-2024-41003, CVE-2024-39510, CVE-2024-39498, CVE-2024-40994, CVE-2024-40937, CVE-2024-39488, CVE-2024-40990, CVE-2024-40955, CVE-2024-40905, CVE-2024-39496, CVE-2024-36478, CVE-2024-40920, CVE-2024-40954, CVE-2024-32936, CVE-2024-40919, CVE-2024-40947, CVE-2024-40975, CVE-2024-39481, CVE-2024-40983, CVE-2024-39276, CVE-2024-37026, CVE-2024-40980, CVE-2022-48772, CVE-2024-39470, CVE-2024-40951, CVE-2024-40927, CVE-2024-38635, CVE-2024-40974, CVE-2024-39468, CVE-2024-38384, CVE-2024-37354, CVE-2024-40992, CVE-2024-40934, CVE-2024-40925, CVE-2024-40935, CVE-2024-39473, CVE-2024-40910, CVE-2024-40979, CVE-2024-39501, CVE-2024-38628, CVE-2024-39298, CVE-2024-40909, CVE-2024-38629, CVE-2024-41000, CVE-2024-40989, CVE-2024-40924, CVE-2024-40943, CVE-2024-41006, CVE-2024-38621, CVE-2024-39462,…
- Record
USN-7005-2- Updated
- 2026-11-02
OSVUSN-7007-1 No score
linux, linux-aws, linux-aws-5.15, linux-gcp, linux-gcp-5.15, linux-gke, linux-gkeop, linux-gkeop-5.15, linux-hwe-5.15, linux-ibm, linux-intel-iotg, linux-intel-iotg-5.15, linux-kvm, linux-nvidia, linux-oracle, linux-raspi vulnerabilities
Chenyuan Yang discovered that the CEC driver driver in the Linux kernel contained a use-after-free vulnerability. A local attacker could use this to cause a denial of service (system crash) or possibly execute arbitrary code. (CVE-2024-23848)
Chenyuan Yang discovered that the USB Gadget subsystem in the Linux kernel did not properly check for the device to be enabled before writing. A local attacker could possibly use this to cause a denial of service. (CVE-2024-25741)
It was discovered that the JFS file system contained an out-of-bounds read vulnerability when printing xattr debug information. A local attacker could use this to cause a denial of service (system crash). (CVE-2024-40902)
Several security issues were discovered in the Linux kernel. An attacker could possibly use these to compromise the system. This update corrects flaws in the following subsystems:
- ARM64 architecture;
- M68K architecture;
- MIPS architecture;
- PowerPC architecture;
- RISC-V architecture;
- x86 architecture;
- Block layer subsystem;
- Cryptographic API;
- Accessibility subsystem;
- ACPI drivers;
- Serial ATA and Parallel ATA drivers;
- Drivers core;
- Bluetooth drivers;
- Character device driver;
- CPU frequency scaling framework;
- Hardware crypto device drivers;
- Buffer Sharing and Synchronization framework;
- DMA engine subsystem;
- FPGA Framework;
- GPIO subsystem;
- GPU drivers;
- Greybus drivers;
- HID subsystem;
- HW tracing;
- I2C subsystem;
- IIO subsystem;
- InfiniBand drivers;
- Input Device (Mouse) drivers;
- Macintosh device drivers;
- Multiple devices driver;
- Media drivers;
- VMware VMCI Driver;
- Network drivers;
- Near Field Communication (NFC) drivers;
- NVME drivers;
- Pin controllers subsystem;
- PTP clock framework;
- S/390 drivers;
- SCSI drivers;
- SoundWire subsystem;
- Greybus lights staging drivers;
- Media staging drivers;
- Thermal drivers;
- TTY drivers;
- USB subsystem;
- DesignWare USB3 driver;
- Framebuffer layer;
- ACRN Hypervisor Service Module driver;
- eCrypt file system;
- File systems infrastructure;
- Ext4 file system;
- F2FS file system;
- JFFS2 file system;
- JFS file system;
- NILFS2 file system;
- NTFS3 file system;
- SMB network file system;
- IOMMU subsystem;
- Memory management;
- Netfilter;
- BPF subsystem;
- Kernel debugger infrastructure;
- DMA mapping infrastructure;
- IRQ subsystem;
- Tracing infrastructure;
- 9P file system network protocol;
- B.A.T.M.A.N. meshing protocol;
- CAN network layer;
- Ceph Core library;
- Networking core;
- IPv4 networking;
- IPv6 networking;
- IUCV driver;
- MAC80211 subsystem;
- Multipath TCP;
- NET/ROM layer;
- NFC subsystem;
- Open vSwitch;
- Network traffic control;
- TIPC protocol;
- TLS protocol;
- Unix domain sockets;
- Wireless networking;
- XFRM subsystem;
- ALSA framework;
- SoC Audio for Freescale CPUs drivers;
- Kirkwood ASoC drivers; (CVE-2024-40961, CVE-2024-38597, CVE-2024-39468, CVE-2024-36978, CVE-2024-42161, CVE-2024-38573, CVE-2024-40905, CVE-2024-42094, CVE-2024-36894, CVE-2024-40914, CVE-2024-40956, CVE-2024-42106, CVE-2024-38610, CVE-2024-39506, CVE-2024-42098, CVE-2024-42232, CVE-2024-38590, CVE-2024-39488, CVE-2024-42127, CVE-2024-41006, CVE-2024-42131, CVE-2024-41005, CVE-2024-40963, CVE-2024-38559, CVE-2024-42130, CVE-2024-37078, CVE-2024-42082, CVE-2024-40984, CVE-2024-38560, CVE-2024-42090, CVE-2024-33621, CVE-2024-40974, CVE-2024-42115, CVE-2024-40971, CVE-2024-40943, CVE-2024-38627, CVE-2024-38548, CVE-2024-40934, CVE-2024-38579, CVE-2024-38558, CVE-2024-39495, CVE-2023-52884, CVE-2024-42225, CVE-2024-38659, CVE-2024-40927, CVE-2024-40967, CVE-2024-38624, CVE-2024-38583, CVE-2024-41047, CVE-2024-38623, CVE-2024-39509, CVE-2024-36971, CVE-2024-42120, CVE-2024-38589, CVE-2024-36270, CVE-2024-42105, CVE-2024-36032, CVE-2024-42101, CVE-2024-40908,…
- Record
USN-7007-1- Updated
- 2026-11-02
OSVUSN-7007-2 No score
linux-ibm-5.15, linux-oracle-5.15 vulnerabilities
Chenyuan Yang discovered that the CEC driver driver in the Linux kernel contained a use-after-free vulnerability. A local attacker could use this to cause a denial of service (system crash) or possibly execute arbitrary code. (CVE-2024-23848)
Chenyuan Yang discovered that the USB Gadget subsystem in the Linux kernel did not properly check for the device to be enabled before writing. A local attacker could possibly use this to cause a denial of service. (CVE-2024-25741)
It was discovered that the JFS file system contained an out-of-bounds read vulnerability when printing xattr debug information. A local attacker could use this to cause a denial of service (system crash). (CVE-2024-40902)
Several security issues were discovered in the Linux kernel. An attacker could possibly use these to compromise the system. This update corrects flaws in the following subsystems:
- ARM64 architecture;
- M68K architecture;
- MIPS architecture;
- PowerPC architecture;
- RISC-V architecture;
- x86 architecture;
- Block layer subsystem;
- Cryptographic API;
- Accessibility subsystem;
- ACPI drivers;
- Serial ATA and Parallel ATA drivers;
- Drivers core;
- Bluetooth drivers;
- Character device driver;
- CPU frequency scaling framework;
- Hardware crypto device drivers;
- Buffer Sharing and Synchronization framework;
- DMA engine subsystem;
- FPGA Framework;
- GPIO subsystem;
- GPU drivers;
- Greybus drivers;
- HID subsystem;
- HW tracing;
- I2C subsystem;
- IIO subsystem;
- InfiniBand drivers;
- Input Device (Mouse) drivers;
- Macintosh device drivers;
- Multiple devices driver;
- Media drivers;
- VMware VMCI Driver;
- Network drivers;
- Near Field Communication (NFC) drivers;
- NVME drivers;
- Pin controllers subsystem;
- PTP clock framework;
- S/390 drivers;
- SCSI drivers;
- SoundWire subsystem;
- Greybus lights staging drivers;
- Media staging drivers;
- Thermal drivers;
- TTY drivers;
- USB subsystem;
- DesignWare USB3 driver;
- Framebuffer layer;
- ACRN Hypervisor Service Module driver;
- eCrypt file system;
- File systems infrastructure;
- Ext4 file system;
- F2FS file system;
- JFFS2 file system;
- JFS file system;
- NILFS2 file system;
- NTFS3 file system;
- SMB network file system;
- IOMMU subsystem;
- Memory management;
- Netfilter;
- BPF subsystem;
- Kernel debugger infrastructure;
- DMA mapping infrastructure;
- IRQ subsystem;
- Tracing infrastructure;
- 9P file system network protocol;
- B.A.T.M.A.N. meshing protocol;
- CAN network layer;
- Ceph Core library;
- Networking core;
- IPv4 networking;
- IPv6 networking;
- IUCV driver;
- MAC80211 subsystem;
- Multipath TCP;
- NET/ROM layer;
- NFC subsystem;
- Open vSwitch;
- Network traffic control;
- TIPC protocol;
- TLS protocol;
- Unix domain sockets;
- Wireless networking;
- XFRM subsystem;
- ALSA framework;
- SoC Audio for Freescale CPUs drivers;
- Kirkwood ASoC drivers; (CVE-2024-42140, CVE-2024-38580, CVE-2024-38555, CVE-2024-38591, CVE-2024-40942, CVE-2024-42130, CVE-2024-41095, CVE-2024-40994, CVE-2024-39469, CVE-2024-38610, CVE-2024-42097, CVE-2024-42137, CVE-2024-31076, CVE-2024-38552, CVE-2024-36489, CVE-2024-40983, CVE-2024-40908, CVE-2024-39493, CVE-2024-40970, CVE-2024-40901, CVE-2024-38567, CVE-2024-38599, CVE-2024-38605, CVE-2024-42119, CVE-2024-38590, CVE-2024-38558, CVE-2023-52884, CVE-2024-41000, CVE-2024-42101, CVE-2024-40943, CVE-2024-39507, CVE-2024-42115, CVE-2024-40968, CVE-2024-42095, CVE-2024-41034, CVE-2024-38618, CVE-2024-38633, CVE-2024-40904, CVE-2024-42070, CVE-2024-38583, CVE-2024-39471, CVE-2024-38578, CVE-2024-38637, CVE-2024-40987, CVE-2024-39506, CVE-2024-39482, CVE-2024-42124, CVE-2024-40981, CVE-2024-35927, CVE-2022-48772, CVE-2024-38588, CVE-2023-52887, CVE-2024-40941, CVE-2024-34027, CVE-2024-38627, CVE-2024-42106, CVE-2024-40927, CVE-2024-38559, CVE-2024-39499,…
- Record
USN-7007-2- Updated
- 2026-11-02
OSVUSN-7007-3 No score
linux-lowlatency, linux-lowlatency-hwe-5.15 vulnerabilities
Chenyuan Yang discovered that the CEC driver driver in the Linux kernel contained a use-after-free vulnerability. A local attacker could use this to cause a denial of service (system crash) or possibly execute arbitrary code. (CVE-2024-23848)
Chenyuan Yang discovered that the USB Gadget subsystem in the Linux kernel did not properly check for the device to be enabled before writing. A local attacker could possibly use this to cause a denial of service. (CVE-2024-25741)
It was discovered that the JFS file system contained an out-of-bounds read vulnerability when printing xattr debug information. A local attacker could use this to cause a denial of service (system crash). (CVE-2024-40902)
Several security issues were discovered in the Linux kernel. An attacker could possibly use these to compromise the system. This update corrects flaws in the following subsystems:
- ARM64 architecture;
- M68K architecture;
- MIPS architecture;
- PowerPC architecture;
- RISC-V architecture;
- x86 architecture;
- Block layer subsystem;
- Cryptographic API;
- Accessibility subsystem;
- ACPI drivers;
- Serial ATA and Parallel ATA drivers;
- Drivers core;
- Bluetooth drivers;
- Character device driver;
- CPU frequency scaling framework;
- Hardware crypto device drivers;
- Buffer Sharing and Synchronization framework;
- DMA engine subsystem;
- FPGA Framework;
- GPIO subsystem;
- GPU drivers;
- Greybus drivers;
- HID subsystem;
- HW tracing;
- I2C subsystem;
- IIO subsystem;
- InfiniBand drivers;
- Input Device (Mouse) drivers;
- Macintosh device drivers;
- Multiple devices driver;
- Media drivers;
- VMware VMCI Driver;
- Network drivers;
- Near Field Communication (NFC) drivers;
- NVME drivers;
- Pin controllers subsystem;
- PTP clock framework;
- S/390 drivers;
- SCSI drivers;
- SoundWire subsystem;
- Greybus lights staging drivers;
- Media staging drivers;
- Thermal drivers;
- TTY drivers;
- USB subsystem;
- DesignWare USB3 driver;
- Framebuffer layer;
- ACRN Hypervisor Service Module driver;
- eCrypt file system;
- File systems infrastructure;
- Ext4 file system;
- F2FS file system;
- JFFS2 file system;
- JFS file system;
- NILFS2 file system;
- NTFS3 file system;
- SMB network file system;
- IOMMU subsystem;
- Memory management;
- Netfilter;
- BPF subsystem;
- Kernel debugger infrastructure;
- DMA mapping infrastructure;
- IRQ subsystem;
- Tracing infrastructure;
- 9P file system network protocol;
- B.A.T.M.A.N. meshing protocol;
- CAN network layer;
- Ceph Core library;
- Networking core;
- IPv4 networking;
- IPv6 networking;
- IUCV driver;
- MAC80211 subsystem;
- Multipath TCP;
- NET/ROM layer;
- NFC subsystem;
- Open vSwitch;
- Network traffic control;
- TIPC protocol;
- TLS protocol;
- Unix domain sockets;
- Wireless networking;
- XFRM subsystem;
- ALSA framework;
- SoC Audio for Freescale CPUs drivers;
- Kirkwood ASoC drivers; (CVE-2024-42105, CVE-2024-41002, CVE-2024-38558, CVE-2023-52887, CVE-2024-39487, CVE-2024-39276, CVE-2024-42077, CVE-2024-39493, CVE-2024-40934, CVE-2024-39277, CVE-2024-42087, CVE-2024-38598, CVE-2024-38618, CVE-2024-40981, CVE-2024-42127, CVE-2024-38607, CVE-2024-38586, CVE-2024-40901, CVE-2024-40916, CVE-2024-42247, CVE-2024-42093, CVE-2024-36489, CVE-2024-38615, CVE-2024-42120, CVE-2024-38567, CVE-2024-40957, CVE-2024-39501, CVE-2024-42140, CVE-2024-33621, CVE-2024-38573, CVE-2023-52884, CVE-2024-39468, CVE-2024-41092, CVE-2024-40931, CVE-2024-42145, CVE-2024-39490, CVE-2024-38555, CVE-2024-42086, CVE-2024-38597, CVE-2024-40956, CVE-2024-42223, CVE-2024-36894, CVE-2024-40961, CVE-2024-42076, CVE-2024-40994, CVE-2024-38619, CVE-2024-39467, CVE-2024-39466, CVE-2022-48772, CVE-2024-39507, CVE-2024-40914, CVE-2024-41046, CVE-2024-42094, CVE-2024-38591, CVE-2024-42098, CVE-2024-41027, CVE-2024-41040, CVE-2024-41089, CVE-2024-40945,…
- Record
USN-7007-3- Updated
- 2026-11-02
OSVUSN-7008-1 No score
linux-lowlatency-hwe-6.8 vulnerabilities
Chenyuan Yang discovered that the CEC driver driver in the Linux kernel contained a use-after-free vulnerability. A local attacker could use this to cause a denial of service (system crash) or possibly execute arbitrary code. (CVE-2024-23848)
It was discovered that the JFS file system contained an out-of-bounds read vulnerability when printing xattr debug information. A local attacker could use this to cause a denial of service (system crash). (CVE-2024-40902)
Several security issues were discovered in the Linux kernel. An attacker could possibly use these to compromise the system. This update corrects flaws in the following subsystems:
- ARM64 architecture;
- MIPS architecture;
- PA-RISC architecture;
- PowerPC architecture;
- RISC-V architecture;
- User-Mode Linux (UML);
- x86 architecture;
- Block layer subsystem;
- ACPI drivers;
- Drivers core;
- Null block device driver;
- Character device driver;
- TPM device driver;
- Clock framework and drivers;
- CPU frequency scaling framework;
- Hardware crypto device drivers;
- CXL (Compute Express Link) drivers;
- Buffer Sharing and Synchronization framework;
- DMA engine subsystem;
- EFI core;
- FPGA Framework;
- GPU drivers;
- Greybus drivers;
- HID subsystem;
- HW tracing;
- I2C subsystem;
- IIO subsystem;
- InfiniBand drivers;
- Input Device (Mouse) drivers;
- Mailbox framework;
- Media drivers;
- Microchip PCI driver;
- VMware VMCI Driver;
- MMC subsystem;
- Network drivers;
- PCI subsystem;
- x86 platform drivers;
- PTP clock framework;
- S/390 drivers;
- SCSI drivers;
- SoundWire subsystem;
- Sonic Silicon Backplane drivers;
- Greybus lights staging drivers;
- Thermal drivers;
- TTY drivers;
- USB subsystem;
- VFIO drivers;
- Framebuffer layer;
- Watchdog drivers;
- 9P distributed file system;
- BTRFS file system;
- File systems infrastructure;
- Ext4 file system;
- F2FS file system;
- JFS file system;
- Network file system server daemon;
- NILFS2 file system;
- NTFS3 file system;
- SMB network file system;
- Tracing file system;
- IOMMU subsystem;
- Tracing infrastructure;
- io_uring subsystem;
- Core kernel;
- BPF subsystem;
- Kernel debugger infrastructure;
- DMA mapping infrastructure;
- IRQ subsystem;
- Memory management;
- 9P file system network protocol;
- Amateur Radio drivers;
- B.A.T.M.A.N. meshing protocol;
- Ethernet bridge;
- Networking core;
- Ethtool driver;
- IPv4 networking;
- IPv6 networking;
- MAC80211 subsystem;
- Multipath TCP;
- Netfilter;
- NET/ROM layer;
- NFC subsystem;
- Network traffic control;
- Sun RPC protocol;
- TIPC protocol;
- TLS protocol;
- Unix domain sockets;
- Wireless networking;
- XFRM subsystem;
- AppArmor security module;
- Integrity Measurement Architecture(IMA) framework;
- Landlock security;
- Linux Security Modules (LSM) Framework;
- SELinux security module;
- Simplified Mandatory Access Control Kernel framework;
- ALSA framework;
- HD-audio driver;
- SOF drivers;
- KVM core; (CVE-2024-38623, CVE-2024-38662, CVE-2024-39484, CVE-2024-42148, CVE-2024-39493, CVE-2024-38637, CVE-2024-40962, CVE-2024-36281, CVE-2024-40922, CVE-2024-40958, CVE-2024-40920, CVE-2024-40986, CVE-2024-40929, CVE-2024-40967, CVE-2024-39296, CVE-2024-40900, CVE-2024-40995, CVE-2024-40974, CVE-2024-40942, CVE-2024-39464, CVE-2024-40916, CVE-2024-40952, CVE-2024-40997, CVE-2024-41004, CVE-2024-40970, CVE-2024-40911, CVE-2024-40972, CVE-2024-36477, CVE-2024-40996, CVE-2024-40988, CVE-2024-38619, CVE-2024-40998, CVE-2024-38627, CVE-2024-36971, CVE-2024-37021, CVE-2024-40989, CVE-2024-40947, CVE-2024-40957, CVE-2024-39508, CVE-2024-41005, CVE-2024-40931, CVE-2024-34777, CVE-2024-38633, CVE-2024-38663, CVE-2024-36288, CVE-2024-40955, CVE-2024-40973, CVE-2024-39483, CVE-2024-38388, CVE-2024-40976, CVE-2024-38622, CVE-2024-40915, CVE-2024-38661, CVE-2024-38306,…
- Record
USN-7008-1- Updated
- 2026-11-02
OSVUSN-7009-1 No score
linux-azure, linux-azure-5.15, linux-azure-fde vulnerabilities
Chenyuan Yang discovered that the CEC driver driver in the Linux kernel contained a use-after-free vulnerability. A local attacker could use this to cause a denial of service (system crash) or possibly execute arbitrary code. (CVE-2024-23848)
Chenyuan Yang discovered that the USB Gadget subsystem in the Linux kernel did not properly check for the device to be enabled before writing. A local attacker could possibly use this to cause a denial of service. (CVE-2024-25741)
It was discovered that the JFS file system contained an out-of-bounds read vulnerability when printing xattr debug information. A local attacker could use this to cause a denial of service (system crash). (CVE-2024-40902)
Several security issues were discovered in the Linux kernel. An attacker could possibly use these to compromise the system. This update corrects flaws in the following subsystems:
- ARM64 architecture;
- M68K architecture;
- MIPS architecture;
- PowerPC architecture;
- RISC-V architecture;
- x86 architecture;
- Block layer subsystem;
- Cryptographic API;
- Accessibility subsystem;
- ACPI drivers;
- Serial ATA and Parallel ATA drivers;
- Drivers core;
- Bluetooth drivers;
- Character device driver;
- CPU frequency scaling framework;
- Hardware crypto device drivers;
- Buffer Sharing and Synchronization framework;
- DMA engine subsystem;
- FPGA Framework;
- GPIO subsystem;
- GPU drivers;
- Greybus drivers;
- HID subsystem;
- HW tracing;
- I2C subsystem;
- IIO subsystem;
- InfiniBand drivers;
- Input Device (Mouse) drivers;
- Macintosh device drivers;
- Multiple devices driver;
- Media drivers;
- VMware VMCI Driver;
- Network drivers;
- Near Field Communication (NFC) drivers;
- NVME drivers;
- Pin controllers subsystem;
- PTP clock framework;
- S/390 drivers;
- SCSI drivers;
- SoundWire subsystem;
- Greybus lights staging drivers;
- Media staging drivers;
- Thermal drivers;
- TTY drivers;
- USB subsystem;
- DesignWare USB3 driver;
- Framebuffer layer;
- ACRN Hypervisor Service Module driver;
- eCrypt file system;
- File systems infrastructure;
- Ext4 file system;
- F2FS file system;
- JFFS2 file system;
- JFS file system;
- NILFS2 file system;
- NTFS3 file system;
- SMB network file system;
- IOMMU subsystem;
- Memory management;
- Netfilter;
- BPF subsystem;
- Kernel debugger infrastructure;
- DMA mapping infrastructure;
- IRQ subsystem;
- Tracing infrastructure;
- 9P file system network protocol;
- B.A.T.M.A.N. meshing protocol;
- CAN network layer;
- Ceph Core library;
- Networking core;
- IPv4 networking;
- IPv6 networking;
- IUCV driver;
- MAC80211 subsystem;
- Multipath TCP;
- NET/ROM layer;
- NFC subsystem;
- Open vSwitch;
- Network traffic control;
- TIPC protocol;
- TLS protocol;
- Unix domain sockets;
- Wireless networking;
- XFRM subsystem;
- ALSA framework;
- SoC Audio for Freescale CPUs drivers;
- Kirkwood ASoC drivers; (CVE-2024-38613, CVE-2024-42096, CVE-2024-40908, CVE-2024-42137, CVE-2024-38590, CVE-2024-41044, CVE-2024-39480, CVE-2024-39469, CVE-2024-39471, CVE-2024-42089, CVE-2024-38588, CVE-2024-41092, CVE-2024-42120, CVE-2024-40901, CVE-2024-40981, CVE-2024-42127, CVE-2024-40932, CVE-2024-39475, CVE-2024-40957, CVE-2024-39501, CVE-2024-42090, CVE-2024-40904, CVE-2024-40978, CVE-2022-48772, CVE-2024-40934, CVE-2024-38548, CVE-2024-41005, CVE-2024-36489, CVE-2024-36978, CVE-2024-38573, CVE-2024-42106, CVE-2024-42104, CVE-2024-42085, CVE-2024-38621, CVE-2024-42098, CVE-2024-38662, CVE-2024-38587, CVE-2024-41089, CVE-2024-42095, CVE-2024-40916, CVE-2024-39487, CVE-2024-42229, CVE-2023-52884, CVE-2024-40974, CVE-2024-40980, CVE-2024-42225, CVE-2024-39502, CVE-2024-37356, CVE-2024-39488, CVE-2024-40912, CVE-2024-39507, CVE-2024-38591, CVE-2024-31076, CVE-2024-40984, CVE-2024-39500, CVE-2024-38582, CVE-2024-34027, CVE-2024-36270, CVE-2024-42076,…
- Record
USN-7009-1- Updated
- 2026-11-02
OSVUSN-7009-2 No score
linux-azure-fde-5.15 vulnerabilities
Chenyuan Yang discovered that the CEC driver driver in the Linux kernel contained a use-after-free vulnerability. A local attacker could use this to cause a denial of service (system crash) or possibly execute arbitrary code. (CVE-2024-23848)
Chenyuan Yang discovered that the USB Gadget subsystem in the Linux kernel did not properly check for the device to be enabled before writing. A local attacker could possibly use this to cause a denial of service. (CVE-2024-25741)
It was discovered that the JFS file system contained an out-of-bounds read vulnerability when printing xattr debug information. A local attacker could use this to cause a denial of service (system crash). (CVE-2024-40902)
Several security issues were discovered in the Linux kernel. An attacker could possibly use these to compromise the system. This update corrects flaws in the following subsystems:
- ARM64 architecture;
- M68K architecture;
- MIPS architecture;
- PowerPC architecture;
- RISC-V architecture;
- x86 architecture;
- Block layer subsystem;
- Cryptographic API;
- Accessibility subsystem;
- ACPI drivers;
- Serial ATA and Parallel ATA drivers;
- Drivers core;
- Bluetooth drivers;
- Character device driver;
- CPU frequency scaling framework;
- Hardware crypto device drivers;
- Buffer Sharing and Synchronization framework;
- DMA engine subsystem;
- FPGA Framework;
- GPIO subsystem;
- GPU drivers;
- Greybus drivers;
- HID subsystem;
- HW tracing;
- I2C subsystem;
- IIO subsystem;
- InfiniBand drivers;
- Input Device (Mouse) drivers;
- Macintosh device drivers;
- Multiple devices driver;
- Media drivers;
- VMware VMCI Driver;
- Network drivers;
- Near Field Communication (NFC) drivers;
- NVME drivers;
- Pin controllers subsystem;
- PTP clock framework;
- S/390 drivers;
- SCSI drivers;
- SoundWire subsystem;
- Greybus lights staging drivers;
- Media staging drivers;
- Thermal drivers;
- TTY drivers;
- USB subsystem;
- DesignWare USB3 driver;
- Framebuffer layer;
- ACRN Hypervisor Service Module driver;
- eCrypt file system;
- File systems infrastructure;
- Ext4 file system;
- F2FS file system;
- JFFS2 file system;
- JFS file system;
- NILFS2 file system;
- NTFS3 file system;
- SMB network file system;
- IOMMU subsystem;
- Memory management;
- Netfilter;
- BPF subsystem;
- Kernel debugger infrastructure;
- DMA mapping infrastructure;
- IRQ subsystem;
- Tracing infrastructure;
- 9P file system network protocol;
- B.A.T.M.A.N. meshing protocol;
- CAN network layer;
- Ceph Core library;
- Networking core;
- IPv4 networking;
- IPv6 networking;
- IUCV driver;
- MAC80211 subsystem;
- Multipath TCP;
- NET/ROM layer;
- NFC subsystem;
- Open vSwitch;
- Network traffic control;
- TIPC protocol;
- TLS protocol;
- Unix domain sockets;
- Wireless networking;
- XFRM subsystem;
- ALSA framework;
- SoC Audio for Freescale CPUs drivers;
- Kirkwood ASoC drivers; (CVE-2024-42076, CVE-2024-40994, CVE-2024-40932, CVE-2024-41000, CVE-2024-42224, CVE-2024-38633, CVE-2024-40954, CVE-2024-36270, CVE-2024-38623, CVE-2024-38549, CVE-2024-42225, CVE-2024-42085, CVE-2024-42157, CVE-2024-42229, CVE-2024-42109, CVE-2024-41040, CVE-2024-38607, CVE-2024-39493, CVE-2024-38546, CVE-2024-41046, CVE-2024-38567, CVE-2024-42092, CVE-2024-39501, CVE-2024-41005, CVE-2024-42223, CVE-2024-39480, CVE-2024-38571, CVE-2024-41048, CVE-2024-38605, CVE-2024-42094, CVE-2024-38598, CVE-2024-38559, CVE-2024-38558, CVE-2024-40931, CVE-2024-40942, CVE-2024-39495, CVE-2024-40981, CVE-2024-40911, CVE-2024-42148, CVE-2024-33621, CVE-2024-39502, CVE-2024-41095, CVE-2024-40960, CVE-2024-36286, CVE-2024-42232, CVE-2024-42130, CVE-2024-42154, CVE-2024-41087, CVE-2024-41004, CVE-2024-39277, CVE-2024-38560, CVE-2024-36978, CVE-2024-42089, CVE-2024-37356, CVE-2024-38547, CVE-2024-38381, CVE-2024-36015, CVE-2024-38548, CVE-2024-42120,…
- Record
USN-7009-2- Updated
- 2026-11-02
OSVUSN-7019-1 No score
linux-xilinx-zynqmp vulnerabilities
Ziming Zhang discovered that the DRM driver for VMware Virtual GPU did not properly handle certain error conditions, leading to a NULL pointer dereference. A local attacker could possibly trigger this vulnerability to cause a denial of service. (CVE-2022-38096)
Gui-Dong Han discovered that the software RAID driver in the Linux kernel contained a race condition, leading to an integer overflow vulnerability. A privileged attacker could possibly use this to cause a denial of service (system crash). (CVE-2024-23307)
Chenyuan Yang discovered that the CEC driver driver in the Linux kernel contained a use-after-free vulnerability. A local attacker could use this to cause a denial of service (system crash) or possibly execute arbitrary code. (CVE-2024-23848)
It was discovered that a race condition existed in the Bluetooth subsystem in the Linux kernel when modifying certain settings values through debugfs. A privileged local attacker could use this to cause a denial of service. (CVE-2024-24857, CVE-2024-24858, CVE-2024-24859)
Bai Jiaju discovered that the Xceive XC4000 silicon tuner device driver in the Linux kernel contained a race condition, leading to an integer overflow vulnerability. An attacker could possibly use this to cause a denial of service (system crash). (CVE-2024-24861)
Chenyuan Yang discovered that the Unsorted Block Images (UBI) flash device volume management subsystem did not properly validate logical eraseblock sizes in certain situations. An attacker could possibly use this to cause a denial of service (system crash). (CVE-2024-25739)
Chenyuan Yang discovered that the USB Gadget subsystem in the Linux kernel did not properly check for the device to be enabled before writing. A local attacker could possibly use this to cause a denial of service. (CVE-2024-25741)
Benedict Schlüter, Supraja Sridhara, Andrin Bertschi, and Shweta Shinde discovered that an untrusted hypervisor could inject malicious #VC interrupts and compromise the security guarantees of AMD SEV-SNP. This flaw is known as WeSee. A local attacker in control of the hypervisor could use this to expose sensitive information or possibly execute arbitrary code in the trusted execution environment. (CVE-2024-25742)
It was discovered that the JFS file system contained an out-of-bounds read vulnerability when printing xattr debug information. A local attacker could use this to cause a denial of service (system crash). (CVE-2024-40902)
Several security issues were discovered in the Linux kernel. An attacker could possibly use these to compromise the system. This update corrects flaws in the following subsystems:
- ARM32 architecture;
- ARM64 architecture;
- M68K architecture;
- MIPS architecture;
- PowerPC architecture;
- RISC-V architecture;
- SuperH RISC architecture;
- User-Mode Linux (UML);
- x86 architecture;
- Block layer subsystem;
- Cryptographic API;
- Accessibility subsystem;
- ACPI drivers;
- Android drivers;
- Serial ATA and Parallel ATA drivers;
- Drivers core;
- Bluetooth drivers;
- Character device driver;
- Clock framework and drivers;
- Data acquisition framework and drivers;
- CPU frequency scaling framework;
- Hardware crypto device drivers;
- Buffer Sharing and Synchronization framework;
- DMA engine subsystem;
- FireWire subsystem;
- FPGA Framework;
- GPIO subsystem;
- GPU drivers;
- Greybus drivers;
- HID subsystem;
- HW tracing;
- I2C subsystem;
- IIO subsystem;
- InfiniBand drivers;
- Input Device (Mouse) drivers;
- IRQ chip drivers;
- Macintosh device drivers;
- Multiple devices driver;
- Media drivers;
- EEPROM drivers;
- VMware VMCI Driver;
- MMC subsystem;
- Network drivers;
- Near Field Communication (NFC) drivers;
- NVME drivers;
- Device tree and open firmware driver;
- PCI subsystem;
- Pin controllers subsystem;
- PTP clock framework;
- Remote Processor subsystem;
- S/390 drivers;
- SCSI drivers;
- Freescale SoC…
- Record
USN-7019-1- Updated
- 2026-11-02
OSVUSN-7029-1 No score
linux-hwe-6.8
Chenyuan Yang discovered that the CEC driver driver in the Linux kernel contained a use-after-free vulnerability. A local attacker could use this to cause a denial of service (system crash) or possibly execute arbitrary code. (CVE-2024-23848)
It was discovered that the JFS file system contained an out-of-bounds read vulnerability when printing xattr debug information. A local attacker could use this to cause a denial of service (system crash). (CVE-2024-40902)
Several security issues were discovered in the Linux kernel. An attacker could possibly use these to compromise the system. This update corrects flaws in the following subsystems:
- ARM64 architecture;
- MIPS architecture;
- PA-RISC architecture;
- PowerPC architecture;
- RISC-V architecture;
- User-Mode Linux (UML);
- x86 architecture;
- Block layer subsystem;
- ACPI drivers;
- Drivers core;
- Null block device driver;
- Character device driver;
- TPM device driver;
- Clock framework and drivers;
- CPU frequency scaling framework;
- Hardware crypto device drivers;
- CXL (Compute Express Link) drivers;
- Buffer Sharing and Synchronization framework;
- DMA engine subsystem;
- EFI core;
- FPGA Framework;
- GPU drivers;
- Greybus drivers;
- HID subsystem;
- HW tracing;
- I2C subsystem;
- IIO subsystem;
- InfiniBand drivers;
- Input Device (Mouse) drivers;
- Mailbox framework;
- Media drivers;
- Microchip PCI driver;
- VMware VMCI Driver;
- MMC subsystem;
- Network drivers;
- PCI subsystem;
- x86 platform drivers;
- PTP clock framework;
- S/390 drivers;
- SCSI drivers;
- SoundWire subsystem;
- Sonic Silicon Backplane drivers;
- Greybus lights staging drivers;
- Thermal drivers;
- TTY drivers;
- USB subsystem;
- VFIO drivers;
- Framebuffer layer;
- Watchdog drivers;
- 9P distributed file system;
- BTRFS file system;
- File systems infrastructure;
- Ext4 file system;
- F2FS file system;
- JFS file system;
- Network file system server daemon;
- NILFS2 file system;
- NTFS3 file system;
- SMB network file system;
- Tracing file system;
- IOMMU subsystem;
- Tracing infrastructure;
- io_uring subsystem;
- Core kernel;
- BPF subsystem;
- Kernel debugger infrastructure;
- DMA mapping infrastructure;
- IRQ subsystem;
- Memory management;
- 9P file system network protocol;
- Amateur Radio drivers;
- B.A.T.M.A.N. meshing protocol;
- Ethernet bridge;
- Networking core;
- Ethtool driver;
- IPv4 networking;
- IPv6 networking;
- MAC80211 subsystem;
- Multipath TCP;
- Netfilter;
- NET/ROM layer;
- NFC subsystem;
- Network traffic control;
- Sun RPC protocol;
- TIPC protocol;
- TLS protocol;
- Unix domain sockets;
- Wireless networking;
- XFRM subsystem;
- AppArmor security module;
- Integrity Measurement Architecture(IMA) framework;
- Landlock security;
- Linux Security Modules (LSM) Framework;
- SELinux security module;
- Simplified Mandatory Access Control Kernel framework;
- ALSA framework;
- HD-audio driver;
- SOF drivers;
- KVM core; (CVE-2024-39498, CVE-2024-33847, CVE-2024-39510, CVE-2024-39462, CVE-2024-40930, CVE-2024-38634, CVE-2024-40962, CVE-2024-37078, CVE-2024-39371, CVE-2024-40972, CVE-2024-41002, CVE-2024-40920, CVE-2024-40982, CVE-2024-40915, CVE-2024-40942, CVE-2024-42154, CVE-2024-40937, CVE-2024-40967, CVE-2024-40909, CVE-2024-36244, CVE-2024-33619, CVE-2024-39277, CVE-2024-40900, CVE-2024-38661, CVE-2024-40974, CVE-2024-38618, CVE-2024-32936, CVE-2024-40906, CVE-2024-40919, CVE-2024-39470, CVE-2024-38390, CVE-2024-40966, CVE-2024-39467, CVE-2024-40938, CVE-2024-39471, CVE-2024-39485, CVE-2024-39495, CVE-2024-39492, CVE-2024-39475, CVE-2024-40953, CVE-2024-40939, CVE-2024-39493, CVE-2024-38637, CVE-2024-40945, CVE-2024-41006, CVE-2024-39461, CVE-2024-40948, CVE-2024-40916, CVE-2024-40925, CVE-2024-40956, CVE-2024-40970, CVE-2024-40912, CVE-2024-33621, CVE-2024-40989,…
- Record
USN-7029-1- Updated
- 2026-11-02
Affected products
Affected packages
| Package | Affected | Fixed |
|---|---|---|
bpftoolAlmaLinux:8 |
before 4.18.0-553.16.1.el8_10 | 4.18.0-553.16.1.el8_10 |
kernelAlmaLinux:8 |
before 4.18.0-553.16.1.el8_10 | 4.18.0-553.16.1.el8_10 |
kernel-abi-stablelistsAlmaLinux:8 |
before 4.18.0-553.16.1.el8_10 | 4.18.0-553.16.1.el8_10 |
kernel-coreAlmaLinux:8 |
before 4.18.0-553.16.1.el8_10 | 4.18.0-553.16.1.el8_10 |
kernel-cross-headersAlmaLinux:8 |
before 4.18.0-553.16.1.el8_10 | 4.18.0-553.16.1.el8_10 |
kernel-debugAlmaLinux:8 |
before 4.18.0-553.16.1.el8_10 | 4.18.0-553.16.1.el8_10 |
kernel-debug-coreAlmaLinux:8 |
before 4.18.0-553.16.1.el8_10 | 4.18.0-553.16.1.el8_10 |
kernel-debug-develAlmaLinux:8 |
before 4.18.0-553.16.1.el8_10 | 4.18.0-553.16.1.el8_10 |
kernel-debug-modulesAlmaLinux:8 |
before 4.18.0-553.16.1.el8_10 | 4.18.0-553.16.1.el8_10 |
kernel-debug-modules-extraAlmaLinux:8 |
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 |
before 4.18.0-553.16.1.el8_10 | 4.18.0-553.16.1.el8_10 |
kernel-docAlmaLinux:8 |
before 4.18.0-553.16.1.el8_10 | 4.18.0-553.16.1.el8_10 |
kernel-headersAlmaLinux:8 |
before 4.18.0-553.16.1.el8_10 | 4.18.0-553.16.1.el8_10 |
kernel-modulesAlmaLinux:8 |
before 4.18.0-553.16.1.el8_10 | 4.18.0-553.16.1.el8_10 |
kernel-modules-extraAlmaLinux:8 |
before 4.18.0-553.16.1.el8_10 | 4.18.0-553.16.1.el8_10 |
kernel-toolsAlmaLinux:8 |
before 4.18.0-553.16.1.el8_10 | 4.18.0-553.16.1.el8_10 |
kernel-tools-libsAlmaLinux:8 |
before 4.18.0-553.16.1.el8_10 | 4.18.0-553.16.1.el8_10 |
kernel-tools-libs-develAlmaLinux:8 |
before 4.18.0-553.16.1.el8_10 | 4.18.0-553.16.1.el8_10 |
kernel-zfcpdumpAlmaLinux:8 |
before 4.18.0-553.16.1.el8_10 | 4.18.0-553.16.1.el8_10 |
kernel-zfcpdump-coreAlmaLinux:8 |
before 4.18.0-553.16.1.el8_10 | 4.18.0-553.16.1.el8_10 |
kernel-zfcpdump-develAlmaLinux:8 |
before 4.18.0-553.16.1.el8_10 | 4.18.0-553.16.1.el8_10 |
kernel-zfcpdump-modulesAlmaLinux:8 |
before 4.18.0-553.16.1.el8_10 | 4.18.0-553.16.1.el8_10 |
kernel-zfcpdump-modules-extraAlmaLinux:8 |
before 4.18.0-553.16.1.el8_10 | 4.18.0-553.16.1.el8_10 |
perfAlmaLinux:8 |
before 4.18.0-553.16.1.el8_10 | 4.18.0-553.16.1.el8_10 |
python3-perfAlmaLinux:8 |
before 4.18.0-553.16.1.el8_10 | 4.18.0-553.16.1.el8_10 |
kernel-rtAlmaLinux:8 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
before 4.18.0-553.16.1.rt7.357.el8_10 | 4.18.0-553.16.1.rt7.357.el8_10 |
bpftoolAlmaLinux:9 |
before 7.3.0-427.35.1.el9_4 | 7.3.0-427.35.1.el9_4 |
kernelAlmaLinux:9 |
before 5.14.0-427.35.1.el9_4 | 5.14.0-427.35.1.el9_4 |
kernel-64kAlmaLinux:9 |
before 5.14.0-427.35.1.el9_4 | 5.14.0-427.35.1.el9_4 |
kernel-64k-coreAlmaLinux:9 |
before 5.14.0-427.35.1.el9_4 | 5.14.0-427.35.1.el9_4 |
kernel-64k-debugAlmaLinux:9 |
before 5.14.0-427.35.1.el9_4 | 5.14.0-427.35.1.el9_4 |
kernel-64k-debug-coreAlmaLinux:9 |
before 5.14.0-427.35.1.el9_4 | 5.14.0-427.35.1.el9_4 |
kernel-64k-debug-develAlmaLinux:9 |
before 5.14.0-427.35.1.el9_4 | 5.14.0-427.35.1.el9_4 |
kernel-64k-debug-devel-matchedAlmaLinux:9 |
before 5.14.0-427.35.1.el9_4 | 5.14.0-427.35.1.el9_4 |
kernel-64k-debug-modulesAlmaLinux:9 |
before 5.14.0-427.35.1.el9_4 | 5.14.0-427.35.1.el9_4 |
kernel-64k-debug-modules-coreAlmaLinux:9 |
before 5.14.0-427.35.1.el9_4 | 5.14.0-427.35.1.el9_4 |
kernel-64k-debug-modules-extraAlmaLinux:9 |
before 5.14.0-427.35.1.el9_4 | 5.14.0-427.35.1.el9_4 |
kernel-64k-develAlmaLinux:9 |
before 5.14.0-427.35.1.el9_4 | 5.14.0-427.35.1.el9_4 |
linux-ltsAlpaquita:23 |
6.1.92-r0 up to 6.1.97-r0 | 6.1.97-r0 |
linux-ltsAlpaquita:25 |
6.6.89-r0 up to 6.12.41-r0 | 6.12.41-r0 |
linux-ltsAlpaquita:stream |
6.6.100-r0 up to 6.12.41-r0 | 6.12.41-r0 |
bpftoolTuxCare:AlmaLinux:9.2 |
before 7.0.0-284.30.1.el9_2.tuxcare.els8 | 7.0.0-284.30.1.el9_2.tuxcare.els8 |
kernelTuxCare:AlmaLinux:9.2 |
before 5.14.0-284.30.1.el9_2.tuxcare.els8 | 5.14.0-284.30.1.el9_2.tuxcare.els8 |
kernel-abi-stablelistsTuxCare:AlmaLinux:9.2 |
before 5.14.0-284.30.1.el9_2.tuxcare.els8 | 5.14.0-284.30.1.el9_2.tuxcare.els8 |
kernel-coreTuxCare:AlmaLinux:9.2 |
before 5.14.0-284.30.1.el9_2.tuxcare.els8 | 5.14.0-284.30.1.el9_2.tuxcare.els8 |
kernel-cross-headersTuxCare:AlmaLinux:9.2 |
before 5.14.0-284.30.1.el9_2.tuxcare.els8 | 5.14.0-284.30.1.el9_2.tuxcare.els8 |
kernel-debugTuxCare:AlmaLinux:9.2 |
before 5.14.0-284.30.1.el9_2.tuxcare.els8 | 5.14.0-284.30.1.el9_2.tuxcare.els8 |
kernel-debug-coreTuxCare:AlmaLinux:9.2 |
before 5.14.0-284.30.1.el9_2.tuxcare.els8 | 5.14.0-284.30.1.el9_2.tuxcare.els8 |
kernel-debug-develTuxCare:AlmaLinux:9.2 |
before 5.14.0-284.30.1.el9_2.tuxcare.els8 | 5.14.0-284.30.1.el9_2.tuxcare.els8 |
kernel-debug-devel-matchedTuxCare:AlmaLinux:9.2 |
before 5.14.0-284.30.1.el9_2.tuxcare.els8 | 5.14.0-284.30.1.el9_2.tuxcare.els8 |
kernel-debug-modulesTuxCare:AlmaLinux:9.2 |
before 5.14.0-284.30.1.el9_2.tuxcare.els8 | 5.14.0-284.30.1.el9_2.tuxcare.els8 |
kernel-debug-modules-coreTuxCare:AlmaLinux:9.2 |
before 5.14.0-284.30.1.el9_2.tuxcare.els8 | 5.14.0-284.30.1.el9_2.tuxcare.els8 |
kernel-debug-modules-extraTuxCare:AlmaLinux:9.2 |
before 5.14.0-284.30.1.el9_2.tuxcare.els8 | 5.14.0-284.30.1.el9_2.tuxcare.els8 |
kernel-debug-modules-internalTuxCare:AlmaLinux:9.2 |
before 5.14.0-284.30.1.el9_2.tuxcare.els8 | 5.14.0-284.30.1.el9_2.tuxcare.els8 |
kernel-debug-modules-partnerTuxCare:AlmaLinux:9.2 |
before 5.14.0-284.30.1.el9_2.tuxcare.els8 | 5.14.0-284.30.1.el9_2.tuxcare.els8 |
kernel-debug-uki-virtTuxCare:AlmaLinux:9.2 |
before 5.14.0-284.30.1.el9_2.tuxcare.els8 | 5.14.0-284.30.1.el9_2.tuxcare.els8 |
kernel-develTuxCare:AlmaLinux:9.2 |
before 5.14.0-284.30.1.el9_2.tuxcare.els8 | 5.14.0-284.30.1.el9_2.tuxcare.els8 |
kernel-devel-matchedTuxCare:AlmaLinux:9.2 |
before 5.14.0-284.30.1.el9_2.tuxcare.els8 | 5.14.0-284.30.1.el9_2.tuxcare.els8 |
kernel-docTuxCare:AlmaLinux:9.2 |
before 5.14.0-284.30.1.el9_2.tuxcare.els8 | 5.14.0-284.30.1.el9_2.tuxcare.els8 |
kernel-headersTuxCare:AlmaLinux:9.2 |
before 5.14.0-284.30.1.el9_2.tuxcare.els8 | 5.14.0-284.30.1.el9_2.tuxcare.els8 |
kernel-ipaclones-internalTuxCare:AlmaLinux:9.2 |
before 5.14.0-284.30.1.el9_2.tuxcare.els8 | 5.14.0-284.30.1.el9_2.tuxcare.els8 |
kernel-modulesTuxCare:AlmaLinux:9.2 |
before 5.14.0-284.30.1.el9_2.tuxcare.els8 | 5.14.0-284.30.1.el9_2.tuxcare.els8 |
kernel-modules-coreTuxCare:AlmaLinux:9.2 |
before 5.14.0-284.30.1.el9_2.tuxcare.els8 | 5.14.0-284.30.1.el9_2.tuxcare.els8 |
kernel-modules-extraTuxCare:AlmaLinux:9.2 |
before 5.14.0-284.30.1.el9_2.tuxcare.els8 | 5.14.0-284.30.1.el9_2.tuxcare.els8 |
kernel-modules-internalTuxCare:AlmaLinux:9.2 |
before 5.14.0-284.30.1.el9_2.tuxcare.els8 | 5.14.0-284.30.1.el9_2.tuxcare.els8 |
kernel-modules-partnerTuxCare:AlmaLinux:9.2 |
before 5.14.0-284.30.1.el9_2.tuxcare.els8 | 5.14.0-284.30.1.el9_2.tuxcare.els8 |
kernel-selftests-internalTuxCare:AlmaLinux:9.2 |
before 5.14.0-284.30.1.el9_2.tuxcare.els8 | 5.14.0-284.30.1.el9_2.tuxcare.els8 |
kernel-toolsTuxCare:AlmaLinux:9.2 |
before 5.14.0-284.30.1.el9_2.tuxcare.els8 | 5.14.0-284.30.1.el9_2.tuxcare.els8 |
kernel-tools-libsTuxCare:AlmaLinux:9.2 |
before 5.14.0-284.30.1.el9_2.tuxcare.els8 | 5.14.0-284.30.1.el9_2.tuxcare.els8 |
kernel-tools-libs-develTuxCare:AlmaLinux:9.2 |
before 5.14.0-284.30.1.el9_2.tuxcare.els8 | 5.14.0-284.30.1.el9_2.tuxcare.els8 |
kernel-uki-virtTuxCare:AlmaLinux:9.2 |
before 5.14.0-284.30.1.el9_2.tuxcare.els8 | 5.14.0-284.30.1.el9_2.tuxcare.els8 |
perfTuxCare:AlmaLinux:9.2 |
before 5.14.0-284.30.1.el9_2.tuxcare.els8 | 5.14.0-284.30.1.el9_2.tuxcare.els8 |
python3-perfTuxCare:AlmaLinux:9.2 |
before 5.14.0-284.30.1.el9_2.tuxcare.els8 | 5.14.0-284.30.1.el9_2.tuxcare.els8 |
rtlaTuxCare:AlmaLinux:9.2 |
before 5.14.0-284.30.1.el9_2.tuxcare.els8 | 5.14.0-284.30.1.el9_2.tuxcare.els8 |
bpftoolTuxCare:CentOS-Stream:8 |
before 4.18.0-553.6.1.el8_10.tuxcare.els14 | 4.18.0-553.6.1.el8_10.tuxcare.els14 |
kernelTuxCare:CentOS-Stream:8 |
before 4.18.0-553.6.1.el8_10.tuxcare.els14 | 4.18.0-553.6.1.el8_10.tuxcare.els14 |
kernel-coreTuxCare:CentOS-Stream:8 |
before 4.18.0-553.6.1.el8_10.tuxcare.els14 | 4.18.0-553.6.1.el8_10.tuxcare.els14 |
kernel-cross-headersTuxCare:CentOS-Stream:8 |
before 4.18.0-553.6.1.el8_10.tuxcare.els14 | 4.18.0-553.6.1.el8_10.tuxcare.els14 |
kernel-debugTuxCare:CentOS-Stream:8 |
before 4.18.0-553.6.1.el8_10.tuxcare.els14 | 4.18.0-553.6.1.el8_10.tuxcare.els14 |
kernel-debug-coreTuxCare:CentOS-Stream:8 |
before 4.18.0-553.6.1.el8_10.tuxcare.els14 | 4.18.0-553.6.1.el8_10.tuxcare.els14 |
kernel-debug-develTuxCare:CentOS-Stream:8 |
before 4.18.0-553.6.1.el8_10.tuxcare.els14 | 4.18.0-553.6.1.el8_10.tuxcare.els14 |
kernel-debug-modulesTuxCare:CentOS-Stream:8 |
before 4.18.0-553.6.1.el8_10.tuxcare.els14 | 4.18.0-553.6.1.el8_10.tuxcare.els14 |
kernel-debug-modules-extraTuxCare:CentOS-Stream:8 |
before 4.18.0-553.6.1.el8_10.tuxcare.els14 | 4.18.0-553.6.1.el8_10.tuxcare.els14 |
kernel-debug-modules-internalTuxCare:CentOS-Stream:8 |
before 4.18.0-553.6.1.el8_10.tuxcare.els14 | 4.18.0-553.6.1.el8_10.tuxcare.els14 |
kernel-develTuxCare:CentOS-Stream:8 |
before 4.18.0-553.6.1.el8_10.tuxcare.els14 | 4.18.0-553.6.1.el8_10.tuxcare.els14 |
kernel-headersTuxCare:CentOS-Stream:8 |
before 4.18.0-553.6.1.el8_10.tuxcare.els14 | 4.18.0-553.6.1.el8_10.tuxcare.els14 |
kernel-ipaclones-internalTuxCare:CentOS-Stream:8 |
before 4.18.0-553.6.1.el8_10.tuxcare.els14 | 4.18.0-553.6.1.el8_10.tuxcare.els14 |
kernel-modulesTuxCare:CentOS-Stream:8 |
before 4.18.0-553.6.1.el8_10.tuxcare.els14 | 4.18.0-553.6.1.el8_10.tuxcare.els14 |
kernel-modules-extraTuxCare:CentOS-Stream:8 |
before 4.18.0-553.6.1.el8_10.tuxcare.els14 | 4.18.0-553.6.1.el8_10.tuxcare.els14 |
KernelLinux |
2.6.35 up to 5.15.162, 5.16.0 up to 6.1.95, 6.2.0 up to 6.6.35, 6.7.0 up to 6.9.6 | 5.15.1626.1.956.6.356.9.6 |
linuxDebian:12 |
before 6.1.99-1, plus listed versions 6.1.27-16.1.37-16.1.38-16.1.38-26.1.38-2~bpo11+1 Show 20 moreShow less6.1.38-36.1.38-46.1.38-4~bpo11+16.1.52-16.1.55-16.1.55-1~bpo11+16.1.64-16.1.66-16.1.67-16.1.69-16.1.69-1~bpo11+16.1.76-16.1.76-1~bpo11+16.1.82-16.1.85-16.1.90-16.1.90-1~bpo11+16.1.94-16.1.94-1~bpo11+16.1.98-1 |
6.1.99-1 |
linuxDebian:13 |
before 6.9.7-1 | 6.9.7-1 |
linuxDebian:14 |
before 6.9.7-1 | 6.9.7-1 |
linux-6.1Debian:11 |
before 6.1.119-1~deb11u1, plus listed versions 6.1.106-3~deb11u16.1.106-3~deb11u26.1.106-3~deb11u36.1.112-1~deb11u1 |
6.1.119-1~deb11u1 |
kernelopenEuler:22.03-LTS-SP3 |
before 5.10.0-240.0.0.142.oe2203sp3 | 5.10.0-240.0.0.142.oe2203sp3 |
kernelopenEuler:24.03-LTS |
before 6.6.0-64.0.0.61.oe2403 | 6.6.0-64.0.0.61.oe2403 |
kernelopenEuler:22.03-LTS-SP4 |
before 5.10.0-242.0.0.141.oe2203sp4 | 5.10.0-242.0.0.141.oe2203sp4 |
bpftoolRed Hat:enterprise_linux:8::baseos |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
before 0:4.18.0-553.16.1.el8_10 | 0:4.18.0-553.16.1.el8_10 |
kernel-rtRocky Linux:8 |
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:9 |
before 0:5.14.0-427.35.1.el9_4 | 0:5.14.0-427.35.1.el9_4 |
linuxRoot:Debian:11 |
before 5.10.262-1.aikido.113 | 5.10.262-1.aikido.1135.10.262-1.aikido.114 |
rootio-linuxRoot:Debian:11 |
before 5.10.262-1.aikido.113 | 5.10.262-1.aikido.1135.10.262-1.aikido.114 |
kernelRocky Linux:8 |
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 |
kernelRocky Linux:9 |
before 0:5.14.0-427.35.1.el9_4.cloud.1.0 | 0:5.14.0-427.35.1.el9_4.cloud.1.0 |
kernel-rtSUSE:Linux Enterprise Micro 5.5 |
before 5.14.21-150500.13.64.1 | 5.14.21-150500.13.64.1 |
kernel-source-rtSUSE:Linux Enterprise Micro 5.5 |
before 5.14.21-150500.13.64.1 | 5.14.21-150500.13.64.1 |
kernel-livepatch-SLE15-SP5-RT_Update_18SUSE:Linux Enterprise Live Patching 15 SP5 |
before 1-150500.11.3.1 | 1-150500.11.3.1 |
kernel-rtSUSE:Real Time Module 15 SP5 |
before 5.14.21-150500.13.64.1 | 5.14.21-150500.13.64.1 |
kernel-rt_debugSUSE:Real Time Module 15 SP5 |
before 5.14.21-150500.13.64.1 | 5.14.21-150500.13.64.1 |
kernel-source-rtSUSE:Real Time Module 15 SP5 |
before 5.14.21-150500.13.64.1 | 5.14.21-150500.13.64.1 |
kernel-syms-rtSUSE:Real Time Module 15 SP5 |
before 5.14.21-150500.13.64.1 | 5.14.21-150500.13.64.1 |
kernel-rtopenSUSE:Leap Micro 5.5 |
before 5.14.21-150500.13.64.1 | 5.14.21-150500.13.64.1 |
kernel-rtopenSUSE:Leap 15.5 |
before 5.14.21-150500.13.64.1 | 5.14.21-150500.13.64.1 |
kernel-rt_debugopenSUSE:Leap 15.5 |
before 5.14.21-150500.13.64.1 | 5.14.21-150500.13.64.1 |
kernel-source-rtopenSUSE:Leap 15.5 |
before 5.14.21-150500.13.64.1 | 5.14.21-150500.13.64.1 |
kernel-syms-rtopenSUSE:Leap 15.5 |
before 5.14.21-150500.13.64.1 | 5.14.21-150500.13.64.1 |
kernel-defaultSUSE:Linux Enterprise Micro 5.5 |
before 5.14.21-150500.55.73.1 | 5.14.21-150500.55.73.1 |
kernel-default-baseSUSE:Linux Enterprise Micro 5.5 |
before 5.14.21-150500.55.73.1.150500.6.33.8 | 5.14.21-150500.55.73.1.150500.6.33.8 |
kernel-64kbSUSE:Linux Enterprise Module for Basesystem 15 SP5 |
before 5.14.21-150500.55.73.1 | 5.14.21-150500.55.73.1 |
kernel-defaultSUSE:Linux Enterprise Module for Basesystem 15 SP5 |
before 5.14.21-150500.55.73.1 | 5.14.21-150500.55.73.1 |
kernel-default-baseSUSE:Linux Enterprise Module for Basesystem 15 SP5 |
before 5.14.21-150500.55.73.1.150500.6.33.8 | 5.14.21-150500.55.73.1.150500.6.33.8 |
kernel-sourceSUSE:Linux Enterprise Module for Basesystem 15 SP5 |
before 5.14.21-150500.55.73.1 | 5.14.21-150500.55.73.1 |
kernel-zfcpdumpSUSE:Linux Enterprise Module for Basesystem 15 SP5 |
before 5.14.21-150500.55.73.1 | 5.14.21-150500.55.73.1 |
kernel-docsSUSE:Linux Enterprise Module for Development Tools 15 SP5 |
before 5.14.21-150500.55.73.2 | 5.14.21-150500.55.73.2 |
kernel-obs-buildSUSE:Linux Enterprise Module for Development Tools 15 SP5 |
before 5.14.21-150500.55.73.1 | 5.14.21-150500.55.73.1 |
kernel-sourceSUSE:Linux Enterprise Module for Development Tools 15 SP5 |
before 5.14.21-150500.55.73.1 | 5.14.21-150500.55.73.1 |
kernel-symsSUSE:Linux Enterprise Module for Development Tools 15 SP5 |
before 5.14.21-150500.55.73.1 | 5.14.21-150500.55.73.1 |
kernel-defaultSUSE:Linux Enterprise Module for Legacy 15 SP5 |
before 5.14.21-150500.55.73.1 | 5.14.21-150500.55.73.1 |
kernel-defaultSUSE:Linux Enterprise Live Patching 15 SP5 |
before 5.14.21-150500.55.73.1 | 5.14.21-150500.55.73.1 |
kernel-livepatch-SLE15-SP5_Update_17SUSE:Linux Enterprise Live Patching 15 SP5 |
before 1-150500.11.3.1 | 1-150500.11.3.1 |
kernel-defaultSUSE:Linux Enterprise High Availability Extension 15 SP5 |
before 5.14.21-150500.55.73.1 | 5.14.21-150500.55.73.1 |
kernel-defaultSUSE:Linux Enterprise Workstation Extension 15 SP5 |
before 5.14.21-150500.55.73.1 | 5.14.21-150500.55.73.1 |
kernel-defaultopenSUSE:Leap Micro 5.5 |
before 5.14.21-150500.55.73.1 | 5.14.21-150500.55.73.1 |
kernel-default-baseopenSUSE:Leap Micro 5.5 |
before 5.14.21-150500.55.73.1.150500.6.33.8 | 5.14.21-150500.55.73.1.150500.6.33.8 |
dtb-aarch64openSUSE:Leap 15.5 |
before 5.14.21-150500.55.73.1 | 5.14.21-150500.55.73.1 |
kernel-64kbopenSUSE:Leap 15.5 |
before 5.14.21-150500.55.73.1 | 5.14.21-150500.55.73.1 |
kernel-debugopenSUSE:Leap 15.5 |
before 5.14.21-150500.55.73.1 | 5.14.21-150500.55.73.1 |
kernel-defaultopenSUSE:Leap 15.5 |
before 5.14.21-150500.55.73.1 | 5.14.21-150500.55.73.1 |
kernel-default-baseopenSUSE:Leap 15.5 |
before 5.14.21-150500.55.73.1.150500.6.33.8 | 5.14.21-150500.55.73.1.150500.6.33.8 |
kernel-docsopenSUSE:Leap 15.5 |
before 5.14.21-150500.55.73.2 | 5.14.21-150500.55.73.2 |
kernel-kvmsmallopenSUSE:Leap 15.5 |
before 5.14.21-150500.55.73.1 | 5.14.21-150500.55.73.1 |
kernel-obs-buildopenSUSE:Leap 15.5 |
before 5.14.21-150500.55.73.1 | 5.14.21-150500.55.73.1 |
kernel-obs-qaopenSUSE:Leap 15.5 |
before 5.14.21-150500.55.73.1 | 5.14.21-150500.55.73.1 |
kernel-sourceopenSUSE:Leap 15.5 |
before 5.14.21-150500.55.73.1 | 5.14.21-150500.55.73.1 |
kernel-symsopenSUSE:Leap 15.5 |
before 5.14.21-150500.55.73.1 | 5.14.21-150500.55.73.1 |
kernel-zfcpdumpopenSUSE:Leap 15.5 |
before 5.14.21-150500.55.73.1 | 5.14.21-150500.55.73.1 |
kernel-azureSUSE:Linux Enterprise Module for Public Cloud 15 SP5 |
before 5.14.21-150500.33.63.1 | 5.14.21-150500.33.63.1 |
kernel-source-azureSUSE:Linux Enterprise Module for Public Cloud 15 SP5 |
before 5.14.21-150500.33.63.1 | 5.14.21-150500.33.63.1 |
kernel-syms-azureSUSE:Linux Enterprise Module for Public Cloud 15 SP5 |
before 5.14.21-150500.33.63.1 | 5.14.21-150500.33.63.1 |
kernel-azureopenSUSE:Leap 15.5 |
before 5.14.21-150500.33.63.1 | 5.14.21-150500.33.63.1 |
kernel-source-azureopenSUSE:Leap 15.5 |
before 5.14.21-150500.33.63.1 | 5.14.21-150500.33.63.1 |
kernel-syms-azureopenSUSE:Leap 15.5 |
before 5.14.21-150500.33.63.1 | 5.14.21-150500.33.63.1 |
kernel-azureSUSE:Linux Enterprise Module for Public Cloud 15 SP6 |
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 |
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 |
before 6.4.0-150600.8.11.1 | 6.4.0-150600.8.11.1 |
kernel-azureopenSUSE:Leap 15.6 |
before 6.4.0-150600.8.11.1 | 6.4.0-150600.8.11.1 |
kernel-source-azureopenSUSE:Leap 15.6 |
before 6.4.0-150600.8.11.1 | 6.4.0-150600.8.11.1 |
kernel-syms-azureopenSUSE:Leap 15.6 |
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 |
before 1-150600.1.3.2 | 1-150600.1.3.2 |
kernel-rtSUSE:Real Time Module 15 SP6 |
before 6.4.0-150600.10.8.3 | 6.4.0-150600.10.8.3 |
kernel-rt_debugSUSE:Real Time Module 15 SP6 |
before 6.4.0-150600.10.8.3 | 6.4.0-150600.10.8.3 |
kernel-source-rtSUSE:Real Time Module 15 SP6 |
before 6.4.0-150600.10.8.3 | 6.4.0-150600.10.8.3 |
kernel-syms-rtSUSE:Real Time Module 15 SP6 |
before 6.4.0-150600.10.8.1 | 6.4.0-150600.10.8.1 |
kernel-rtopenSUSE:Leap 15.6 |
before 6.4.0-150600.10.8.3 | 6.4.0-150600.10.8.3 |
kernel-rt_debugopenSUSE:Leap 15.6 |
before 6.4.0-150600.10.8.3 | 6.4.0-150600.10.8.3 |
kernel-source-rtopenSUSE:Leap 15.6 |
before 6.4.0-150600.10.8.3 | 6.4.0-150600.10.8.3 |
kernel-syms-rtopenSUSE:Leap 15.6 |
before 6.4.0-150600.10.8.1 | 6.4.0-150600.10.8.1 |
kernel-64kbSUSE:Linux Enterprise Module for Basesystem 15 SP6 |
before 6.4.0-150600.23.22.1 | 6.4.0-150600.23.22.1 |
kernel-defaultSUSE:Linux Enterprise Module for Basesystem 15 SP6 |
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 |
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 |
before 6.4.0-150600.23.22.1 | 6.4.0-150600.23.22.1 |
kernel-zfcpdumpSUSE:Linux Enterprise Module for Basesystem 15 SP6 |
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 |
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 |
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 |
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 |
before 6.4.0-150600.23.22.1 | 6.4.0-150600.23.22.1 |
kernel-defaultSUSE:Linux Enterprise Module for Legacy 15 SP6 |
before 6.4.0-150600.23.22.1 | 6.4.0-150600.23.22.1 |
kernel-defaultSUSE:Linux Enterprise Live Patching 15 SP6 |
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 |
before 1-150600.13.3.3 | 1-150600.13.3.3 |
kernel-defaultSUSE:Linux Enterprise High Availability Extension 15 SP6 |
before 6.4.0-150600.23.22.1 | 6.4.0-150600.23.22.1 |
kernel-defaultSUSE:Linux Enterprise Workstation Extension 15 SP6 |
before 6.4.0-150600.23.22.1 | 6.4.0-150600.23.22.1 |
dtb-aarch64openSUSE:Leap 15.6 |
before 6.4.0-150600.23.22.1 | 6.4.0-150600.23.22.1 |
kernel-64kbopenSUSE:Leap 15.6 |
before 6.4.0-150600.23.22.1 | 6.4.0-150600.23.22.1 |
kernel-debugopenSUSE:Leap 15.6 |
before 6.4.0-150600.23.22.1 | 6.4.0-150600.23.22.1 |
kernel-defaultopenSUSE:Leap 15.6 |
before 6.4.0-150600.23.22.1 | 6.4.0-150600.23.22.1 |
kernel-default-baseopenSUSE:Leap 15.6 |
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 |
before 6.4.0-150600.23.22.1 | 6.4.0-150600.23.22.1 |
kernel-kvmsmallopenSUSE:Leap 15.6 |
before 6.4.0-150600.23.22.1 | 6.4.0-150600.23.22.1 |
kernel-obs-buildopenSUSE:Leap 15.6 |
before 6.4.0-150600.23.22.1 | 6.4.0-150600.23.22.1 |
kernel-obs-qaopenSUSE:Leap 15.6 |
before 6.4.0-150600.23.22.1 | 6.4.0-150600.23.22.1 |
kernel-sourceopenSUSE:Leap 15.6 |
before 6.4.0-150600.23.22.1 | 6.4.0-150600.23.22.1 |
kernel-symsopenSUSE:Leap 15.6 |
before 6.4.0-150600.23.22.1 | 6.4.0-150600.23.22.1 |
kernel-zfcpdumpopenSUSE:Leap 15.6 |
before 6.4.0-150600.23.22.1 | 6.4.0-150600.23.22.1 |
linuxUbuntu:Pro:14.04:LTS |
All versions, plus listed versions 3.11.0-12.193.12.0-1.33.12.0-2.53.12.0-2.73.12.0-3.8 Show 45 moreShow less3.12.0-3.93.12.0-4.103.12.0-4.123.12.0-5.133.12.0-7.153.13.0-1.163.13.0-2.173.13.0-3.183.13.0-4.193.13.0-5.203.13.0-6.233.13.0-7.253.13.0-7.263.13.0-8.273.13.0-8.283.13.0-10.303.13.0-11.313.13.0-12.323.13.0-13.333.13.0-14.343.13.0-15.353.13.0-16.363.13.0-17.373.13.0-18.383.13.0-19.393.13.0-19.403.13.0-20.423.13.0-21.433.13.0-22.443.13.0-23.453.13.0-24.463.13.0-24.473.13.0-27.503.13.0-29.533.13.0-30.543.13.0-30.553.13.0-32.573.13.0-33.583.13.0-34.603.13.0-35.623.13.0-36.633.13.0-37.643.13.0-39.663.13.0-40.693.13.0-41.70 |
None known |
linux-awsUbuntu:Pro:14.04:LTS |
All versions, plus listed versions 4.4.0-1002.24.4.0-1003.34.4.0-1005.54.4.0-1006.64.4.0-1009.9 Show 45 moreShow less4.4.0-1010.104.4.0-1011.114.4.0-1012.124.4.0-1014.144.4.0-1016.164.4.0-1017.174.4.0-1019.194.4.0-1022.224.4.0-1023.234.4.0-1024.254.4.0-1025.264.4.0-1027.304.4.0-1028.314.4.0-1029.324.4.0-1031.344.4.0-1032.354.4.0-1034.374.4.0-1036.394.4.0-1037.404.4.0-1038.414.4.0-1039.424.4.0-1040.434.4.0-1042.454.4.0-1044.474.4.0-1045.484.4.0-1046.504.4.0-1048.524.4.0-1050.544.4.0-1052.564.4.0-1054.584.4.0-1055.594.4.0-1056.604.4.0-1058.624.4.0-1059.634.4.0-1060.644.4.0-1061.654.4.0-1062.664.4.0-1064.684.4.0-1065.694.4.0-1066.704.4.0-1067.714.4.0-1073.774.4.0-1074.784.4.0-1075.794.4.0-1076.80 |
None known |
linux-azureUbuntu:Pro:14.04:LTS |
All versions, plus listed versions 4.15.0-1023.24~14.04.14.15.0-1030.31~14.04.14.15.0-1031.32~14.04.14.15.0-1032.33~14.04.24.15.0-1035.36~14.04.2 Show 45 moreShow less4.15.0-1036.38~14.04.24.15.0-1037.39~14.04.24.15.0-1039.41~14.04.24.15.0-1040.44~14.04.14.15.0-1041.45~14.04.14.15.0-1042.46~14.04.14.15.0-1045.49~14.04.14.15.0-1046.50~14.04.14.15.0-1047.51~14.04.14.15.0-1049.54~14.04.14.15.0-1050.55~14.04.14.15.0-1051.56~14.04.14.15.0-1052.57~14.04.14.15.0-1055.60~14.04.14.15.0-1056.61~14.04.14.15.0-1057.62~14.04.14.15.0-1059.64~14.04.14.15.0-1060.65~14.04.14.15.0-1061.66~14.04.14.15.0-1063.68~14.04.14.15.0-1064.69~14.04.14.15.0-1066.71~14.04.14.15.0-1067.72~14.04.14.15.0-1069.74~14.04.14.15.0-1071.76~14.04.14.15.0-1074.79~14.04.14.15.0-1077.82~14.04.14.15.0-1082.92~14.04.14.15.0-1083.93~14.04.14.15.0-1089.99~14.04.14.15.0-1091.101~14.04.14.15.0-1092.102~14.04.14.15.0-1093.103~14.04.14.15.0-1095.105~14.04.14.15.0-1096.106~14.04.14.15.0-1098.109~14.04.14.15.0-1100.111~14.04.14.15.0-1102.113~14.04.14.15.0-1103.114~14.04.14.15.0-1106.118~14.04.14.15.0-1108.120~14.04.14.15.0-1109.121~14.04.14.15.0-1110.122~14.04.14.15.0-1111.123~14.04.14.15.0-1112.124~14.04.1 |
None known |
linux-lts-xenialUbuntu:Pro:14.04:LTS |
All versions, plus listed versions 4.4.0-13.29~14.04.14.4.0-14.30~14.04.24.4.0-15.31~14.04.14.4.0-18.34~14.04.14.4.0-21.37~14.04.1 Show 45 moreShow less4.4.0-22.39~14.04.14.4.0-22.40~14.04.14.4.0-24.43~14.04.14.4.0-28.47~14.04.14.4.0-31.50~14.04.14.4.0-34.53~14.04.14.4.0-36.55~14.04.14.4.0-38.57~14.04.14.4.0-42.62~14.04.14.4.0-45.66~14.04.14.4.0-47.68~14.04.14.4.0-51.72~14.04.14.4.0-53.74~14.04.14.4.0-57.78~14.04.14.4.0-59.80~14.04.14.4.0-62.83~14.04.14.4.0-63.84~14.04.24.4.0-64.85~14.04.14.4.0-66.87~14.04.14.4.0-67.88~14.04.14.4.0-70.91~14.04.14.4.0-71.92~14.04.14.4.0-72.93~14.04.14.4.0-75.96~14.04.14.4.0-78.99~14.04.24.4.0-79.100~14.04.14.4.0-81.104~14.04.14.4.0-83.106~14.04.14.4.0-87.110~14.04.14.4.0-89.112~14.04.14.4.0-91.114~14.04.14.4.0-92.115~14.04.14.4.0-93.116~14.04.14.4.0-96.119~14.04.14.4.0-97.120~14.04.14.4.0-98.121~14.04.14.4.0-101.124~14.04.14.4.0-103.126~14.04.14.4.0-104.127~14.04.14.4.0-108.131~14.04.14.4.0-109.132~14.04.14.4.0-111.134~14.04.14.4.0-112.135~14.04.14.4.0-116.140~14.04.14.4.0-119.143~14.04.1 |
None known |
linuxUbuntu:Pro:16.04:LTS |
All versions, plus listed versions 4.2.0-16.194.2.0-17.214.2.0-19.234.3.0-1.104.3.0-2.11 Show 45 moreShow less4.3.0-5.164.3.0-6.174.3.0-7.184.4.0-2.164.4.0-4.194.4.0-6.214.4.0-7.224.4.0-8.234.4.0-9.244.4.0-10.254.4.0-11.264.4.0-12.284.4.0-13.294.4.0-14.304.4.0-15.314.4.0-16.324.4.0-17.334.4.0-18.344.4.0-21.374.4.0-22.394.4.0-22.404.4.0-24.434.4.0-28.474.4.0-31.504.4.0-34.534.4.0-36.554.4.0-38.574.4.0-42.624.4.0-43.634.4.0-45.664.4.0-47.684.4.0-51.724.4.0-53.744.4.0-57.784.4.0-59.804.4.0-62.834.4.0-63.844.4.0-64.854.4.0-65.864.4.0-66.874.4.0-67.884.4.0-70.914.4.0-71.924.4.0-72.934.4.0-75.96 |
None known |
linux-awsUbuntu:Pro:16.04:LTS |
All versions, plus listed versions 4.4.0-1001.104.4.0-1003.124.4.0-1004.134.4.0-1007.164.4.0-1009.18 Show 45 moreShow less4.4.0-1011.204.4.0-1012.214.4.0-1013.224.4.0-1016.254.4.0-1017.264.4.0-1018.274.4.0-1020.294.4.0-1022.314.4.0-1026.354.4.0-1028.374.4.0-1030.394.4.0-1031.404.4.0-1032.414.4.0-1035.444.4.0-1037.464.4.0-1038.474.4.0-1039.484.4.0-1041.504.4.0-1043.524.4.0-1044.534.4.0-1047.564.4.0-1048.574.4.0-1049.584.4.0-1050.594.4.0-1052.614.4.0-1054.634.4.0-1055.644.4.0-1057.664.4.0-1060.694.4.0-1061.704.4.0-1062.714.4.0-1063.724.4.0-1065.754.4.0-1066.764.4.0-1067.774.4.0-1069.794.4.0-1070.804.4.0-1072.824.4.0-1073.834.4.0-1074.844.4.0-1075.854.4.0-1077.874.4.0-1079.894.4.0-1081.914.4.0-1083.93 |
None known |
linux-aws-hweUbuntu:Pro:16.04:LTS |
All versions, plus listed versions 4.15.0-1030.31~16.04.14.15.0-1031.33~16.04.14.15.0-1032.34~16.04.14.15.0-1033.35~16.04.14.15.0-1035.37~16.04.1 Show 45 moreShow less4.15.0-1036.38~16.04.14.15.0-1039.41~16.04.14.15.0-1040.42~16.04.14.15.0-1041.43~16.04.14.15.0-1043.45~16.04.14.15.0-1044.46~16.04.14.15.0-1045.47~16.04.14.15.0-1047.49~16.04.14.15.0-1048.50~16.04.14.15.0-1050.52~16.04.14.15.0-1051.53~16.04.14.15.0-1052.54~16.04.14.15.0-1054.56~16.04.14.15.0-1056.58~16.04.14.15.0-1057.59~16.04.14.15.0-1058.60~16.04.14.15.0-1060.62~16.04.14.15.0-1063.67~16.04.14.15.0-1065.69~16.04.14.15.0-1066.70~16.04.14.15.0-1067.71~16.04.14.15.0-1073.77~16.04.14.15.0-1074.78~16.04.14.15.0-1079.83~16.04.14.15.0-1080.84~16.04.14.15.0-1082.86~16.04.14.15.0-1083.87~16.04.14.15.0-1085.90~16.04.14.15.0-1088.93~16.04.14.15.0-1090.95~16.04.14.15.0-1091.96~16.04.14.15.0-1093.99~16.04.14.15.0-1094.101~16.04.14.15.0-1095.102~16.04.14.15.0-1096.103~16.04.14.15.0-1097.104~16.04.14.15.0-1098.105~16.04.14.15.0-1099.106~16.04.14.15.0-1102.109~16.04.14.15.0-1103.110~16.04.14.15.0-1106.113~16.04.14.15.0-1109.116~16.04.14.15.0-1110.117~16.04.14.15.0-1111.118~16.04.14.15.0-1112.119~16.04.1 |
None known |
linux-azureUbuntu:Pro:16.04:LTS |
All versions, plus listed versions 4.11.0-1009.94.11.0-1011.114.11.0-1013.134.11.0-1014.144.11.0-1015.15 Show 45 moreShow less4.11.0-1016.164.13.0-1005.74.13.0-1006.84.13.0-1007.94.13.0-1009.124.13.0-1011.144.13.0-1012.154.13.0-1014.174.13.0-1016.194.13.0-1018.214.15.0-1013.13~16.04.24.15.0-1014.14~16.04.14.15.0-1018.18~16.04.14.15.0-1019.19~16.04.14.15.0-1021.21~16.04.14.15.0-1022.22~16.04.14.15.0-1023.24~16.04.14.15.0-1025.26~16.04.14.15.0-1028.29~16.04.14.15.0-1030.31~16.04.14.15.0-1031.32~16.04.14.15.0-1032.33~16.04.14.15.0-1035.36~16.04.14.15.0-1036.38~16.04.14.15.0-1037.39~16.04.14.15.0-1039.434.15.0-1040.444.15.0-1041.454.15.0-1042.464.15.0-1045.494.15.0-1046.504.15.0-1047.514.15.0-1049.544.15.0-1050.554.15.0-1051.564.15.0-1052.574.15.0-1055.604.15.0-1056.614.15.0-1057.624.15.0-1059.644.15.0-1060.654.15.0-1061.664.15.0-1063.684.15.0-1064.694.15.0-1066.71 |
None known |
linux-gcpUbuntu:Pro:16.04:LTS |
All versions, plus listed versions 4.10.0-1004.44.10.0-1006.64.10.0-1007.74.10.0-1008.84.10.0-1009.9 Show 45 moreShow less4.13.0-1002.54.13.0-1006.94.13.0-1007.104.13.0-1008.114.13.0-1011.154.13.0-1012.164.13.0-1013.174.13.0-1015.194.13.0-1017.214.13.0-1019.234.15.0-1014.14~16.04.14.15.0-1015.15~16.04.14.15.0-1017.18~16.04.14.15.0-1018.19~16.04.24.15.0-1019.20~16.04.14.15.0-1021.22~16.04.14.15.0-1023.24~16.04.14.15.0-1024.25~16.04.24.15.0-1025.26~16.04.14.15.0-1026.27~16.04.14.15.0-1027.28~16.04.14.15.0-1028.29~16.04.14.15.0-1029.31~16.04.14.15.0-1030.32~16.04.14.15.0-1032.34~16.04.14.15.0-1033.35~16.04.14.15.0-1034.36~16.04.14.15.0-1036.38~16.04.14.15.0-1037.39~16.04.14.15.0-1040.42~16.04.14.15.0-1041.434.15.0-1042.444.15.0-1044.464.15.0-1046.494.15.0-1047.504.15.0-1049.524.15.0-1050.534.15.0-1052.564.15.0-1055.594.15.0-1058.624.15.0-1060.644.15.0-1061.654.15.0-1071.81~16.04.14.15.0-1077.87~16.04.14.15.0-1078.88~16.04.1 |
None known |
linux-hweUbuntu:Pro:16.04:LTS |
All versions, plus listed versions 4.8.0-36.36~16.04.14.8.0-39.42~16.04.14.8.0-41.44~16.04.14.8.0-42.45~16.04.14.8.0-44.47~16.04.1 Show 45 moreShow less4.8.0-45.48~16.04.14.8.0-46.49~16.04.14.8.0-49.52~16.04.14.8.0-51.54~16.04.14.8.0-52.55~16.04.14.8.0-53.56~16.04.14.8.0-54.57~16.04.14.8.0-56.61~16.04.14.8.0-58.63~16.04.14.10.0-27.30~16.04.24.10.0-28.32~16.04.24.10.0-30.34~16.04.14.10.0-32.36~16.04.14.10.0-33.37~16.04.14.10.0-35.39~16.04.14.10.0-37.41~16.04.14.10.0-38.42~16.04.14.10.0-40.44~16.04.14.10.0-42.46~16.04.14.13.0-26.29~16.04.24.13.0-31.34~16.04.14.13.0-32.35~16.04.14.13.0-36.40~16.04.14.13.0-37.42~16.04.14.13.0-38.43~16.04.14.13.0-39.44~16.04.14.13.0-41.46~16.04.14.13.0-43.48~16.04.14.13.0-45.50~16.04.14.15.0-24.26~16.04.14.15.0-29.31~16.04.14.15.0-30.32~16.04.14.15.0-32.35~16.04.14.15.0-33.36~16.04.14.15.0-34.37~16.04.14.15.0-36.39~16.04.14.15.0-38.41~16.04.14.15.0-39.42~16.04.14.15.0-42.45~16.04.14.15.0-43.46~16.04.14.15.0-45.48~16.04.14.15.0-46.49~16.04.14.15.0-47.50~16.04.14.15.0-48.51~16.04.14.15.0-50.54~16.04.1 |
None known |
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-kvmUbuntu:Pro:16.04:LTS |
All versions, plus listed versions 4.4.0-1004.94.4.0-1007.124.4.0-1008.134.4.0-1009.144.4.0-1010.15 Show 45 moreShow less4.4.0-1012.174.4.0-1013.184.4.0-1015.204.4.0-1017.224.4.0-1019.244.4.0-1020.254.4.0-1021.264.4.0-1023.284.4.0-1026.314.4.0-1027.324.4.0-1029.344.4.0-1031.374.4.0-1032.384.4.0-1033.394.4.0-1035.414.4.0-1036.424.4.0-1037.434.4.0-1038.444.4.0-1039.454.4.0-1040.464.4.0-1041.474.4.0-1043.494.4.0-1044.504.4.0-1046.524.4.0-1047.534.4.0-1048.554.4.0-1051.584.4.0-1052.594.4.0-1054.614.4.0-1056.634.4.0-1058.654.4.0-1059.664.4.0-1060.674.4.0-1062.694.4.0-1063.704.4.0-1064.714.4.0-1065.724.4.0-1066.734.4.0-1068.754.4.0-1069.764.4.0-1070.774.4.0-1071.784.4.0-1075.824.4.0-1076.834.4.0-1077.84 |
None known |
linux-oracleUbuntu:Pro:16.04:LTS |
All versions, plus listed versions 4.15.0-1007.9~16.04.14.15.0-1008.10~16.04.14.15.0-1009.11~16.04.14.15.0-1010.12~16.04.14.15.0-1011.13~16.04.1 Show 45 moreShow less4.15.0-1013.15~16.04.14.15.0-1014.16~16.04.14.15.0-1015.17~16.04.14.15.0-1017.19~16.04.24.15.0-1018.20~16.04.14.15.0-1021.23~16.04.14.15.0-1022.25~16.04.14.15.0-1023.26~16.04.14.15.0-1025.28~16.04.14.15.0-1026.29~16.04.14.15.0-1027.30~16.04.14.15.0-1029.32~16.04.14.15.0-1030.33~16.04.14.15.0-1031.34~16.04.14.15.0-1033.36~16.04.14.15.0-1035.38~16.04.14.15.0-1037.41~16.04.14.15.0-1038.42~16.04.14.15.0-1039.43~16.04.14.15.0-1045.49~16.04.14.15.0-1046.50~16.04.14.15.0-1050.54~16.04.14.15.0-1051.55~16.04.14.15.0-1053.57~16.04.14.15.0-1054.58~16.04.14.15.0-1056.61~16.04.14.15.0-1058.64~16.04.14.15.0-1059.65~16.04.14.15.0-1061.67~16.04.14.15.0-1062.68~16.04.14.15.0-1064.71~16.04.14.15.0-1065.73~16.04.14.15.0-1066.74~16.04.14.15.0-1067.75~16.04.14.15.0-1068.76~16.04.14.15.0-1069.77~16.04.14.15.0-1070.78~16.04.14.15.0-1071.79~16.04.14.15.0-1072.80~16.04.14.15.0-1075.83~16.04.14.15.0-1078.86~16.04.14.15.0-1079.87~16.04.14.15.0-1080.88~16.04.14.15.0-1081.89~16.04.14.15.0-1082.90~16.04.1 |
None known |
linux-fipsUbuntu:Pro:FIPS-updates:16.04:LTS |
All versions, plus listed versions 4.4.0-1003.34.4.0-1005.54.4.0-1006.64.4.0-1008.104.4.0-1010.13 Show 45 moreShow less4.4.0-1011.144.4.0-1012.164.4.0-1013.174.4.0-1015.204.4.0-1017.224.4.0-1019.244.4.0-1021.264.4.0-1022.274.4.0-1023.284.4.0-1025.304.4.0-1026.314.4.0-1027.324.4.0-1028.334.4.0-1029.344.4.0-1031.364.4.0-1032.374.4.0-1033.384.4.0-1034.394.4.0-1041.464.4.0-1042.474.4.0-1043.484.4.0-1044.494.4.0-1045.504.4.0-1046.514.4.0-1048.534.4.0-1049.554.4.0-1051.574.4.0-1052.584.4.0-1054.604.4.0-1055.614.4.0-1056.624.4.0-1057.634.4.0-1058.644.4.0-1060.664.4.0-1061.674.4.0-1062.684.4.0-1063.694.4.0-1064.704.4.0-1065.714.4.0-1066.724.4.0-1067.734.4.0-1068.744.4.0-1069.754.4.0-1071.774.4.0-1072.78 |
None known |
linux-fipsUbuntu:Pro:FIPS:16.04:LTS |
All versions, plus listed versions 4.4.0-1001.14.4.0-1002.2 |
None known |
linuxUbuntu:Pro:18.04:LTS |
All versions, plus listed versions 4.13.0-16.194.13.0-17.204.13.0-25.294.13.0-32.354.15.0-10.11 Show 45 moreShow less4.15.0-12.134.15.0-13.144.15.0-15.164.15.0-19.204.15.0-20.214.15.0-22.244.15.0-23.254.15.0-24.264.15.0-29.314.15.0-30.324.15.0-32.354.15.0-33.364.15.0-34.374.15.0-36.394.15.0-38.414.15.0-39.424.15.0-42.454.15.0-43.464.15.0-44.474.15.0-45.484.15.0-46.494.15.0-47.504.15.0-48.514.15.0-50.544.15.0-51.554.15.0-52.564.15.0-54.584.15.0-55.604.15.0-58.644.15.0-60.674.15.0-62.694.15.0-64.734.15.0-65.744.15.0-66.754.15.0-69.784.15.0-70.794.15.0-72.814.15.0-74.844.15.0-76.864.15.0-88.884.15.0-91.924.15.0-96.974.15.0-99.1004.15.0-101.1024.15.0-106.107 |
None known |
linux-awsUbuntu:Pro: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-1007.7 Show 45 moreShow less4.15.0-1009.94.15.0-1010.104.15.0-1011.114.15.0-1016.164.15.0-1017.174.15.0-1019.194.15.0-1020.204.15.0-1021.214.15.0-1023.234.15.0-1025.254.15.0-1027.274.15.0-1029.304.15.0-1031.334.15.0-1032.344.15.0-1033.354.15.0-1034.364.15.0-1035.374.15.0-1037.394.15.0-1039.414.15.0-1040.424.15.0-1041.434.15.0-1043.454.15.0-1044.464.15.0-1045.474.15.0-1047.494.15.0-1048.504.15.0-1050.524.15.0-1051.534.15.0-1052.544.15.0-1054.564.15.0-1056.584.15.0-1057.594.15.0-1058.604.15.0-1060.624.15.0-1063.674.15.0-1065.694.15.0-1066.704.15.0-1067.714.15.0-1073.774.15.0-1076.804.15.0-1077.814.15.0-1079.834.15.0-1080.844.15.0-1082.864.15.0-1083.87 |
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-aws-5.4Ubuntu:Pro:18.04:LTS |
All versions, plus listed versions 5.4.0-1018.18~18.04.15.4.0-1020.20~18.04.25.4.0-1022.22~18.04.15.4.0-1024.24~18.04.15.4.0-1025.25~18.04.1 Show 45 moreShow less5.4.0-1028.29~18.04.15.4.0-1029.30~18.04.15.4.0-1030.31~18.04.15.4.0-1032.33~18.04.15.4.0-1034.35~18.04.15.4.0-1035.37~18.04.15.4.0-1037.39~18.04.15.4.0-1038.40~18.04.15.4.0-1039.41~18.04.15.4.0-1041.43~18.04.15.4.0-1043.45~18.04.15.4.0-1045.47~18.04.15.4.0-1047.49~18.04.15.4.0-1048.50~18.04.15.4.0-1049.51~18.04.15.4.0-1051.53~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-1058.61~18.04.35.4.0-1059.62~18.04.15.4.0-1060.63~18.04.15.4.0-1061.64~18.04.15.4.0-1063.66~18.04.15.4.0-1064.67~18.04.15.4.0-1065.68~18.04.15.4.0-1066.69~18.04.15.4.0-1068.72~18.04.15.4.0-1069.73~18.04.15.4.0-1071.76~18.04.15.4.0-1072.77~18.04.15.4.0-1075.80~18.04.15.4.0-1078.84~18.04.15.4.0-1080.87~18.04.15.4.0-1081.88~18.04.15.4.0-1083.90~18.04.15.4.0-1084.91~18.04.15.4.0-1085.92~18.04.15.4.0-1086.93~18.04.15.4.0-1088.96~18.04.15.4.0-1089.97~18.04.15.4.0-1090.98~18.04.15.4.0-1092.100~18.04.25.4.0-1093.102~18.04.2 |
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-4.15Ubuntu:Pro:18.04:LTS |
All versions, plus listed versions 4.15.0-1082.924.15.0-1083.934.15.0-1089.994.15.0-1091.1014.15.0-1092.102 Show 45 moreShow less4.15.0-1093.1034.15.0-1095.1054.15.0-1096.1064.15.0-1099.1104.15.0-1100.1114.15.0-1102.1134.15.0-1103.1144.15.0-1104.1164.15.0-1106.1184.15.0-1108.1204.15.0-1109.1214.15.0-1110.1224.15.0-1111.1234.15.0-1112.1254.15.0-1113.1264.15.0-1114.1274.15.0-1115.1284.15.0-1118.1314.15.0-1121.1344.15.0-1122.1354.15.0-1123.1364.15.0-1124.1374.15.0-1125.1384.15.0-1126.1394.15.0-1127.1404.15.0-1129.1424.15.0-1130.1434.15.0-1131.1444.15.0-1133.1464.15.0-1134.1474.15.0-1136.1494.15.0-1137.1504.15.0-1138.1514.15.0-1139.1524.15.0-1142.1564.15.0-1145.1604.15.0-1146.1614.15.0-1149.1644.15.0-1150.1654.15.0-1151.1664.15.0-1153.1684.15.0-1157.1724.15.0-1158.1734.15.0-1159.1744.15.0-1161.176 |
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-5.4Ubuntu:Pro:18.04:LTS |
All versions, plus listed versions 5.4.0-1020.20~18.04.15.4.0-1022.22~18.04.15.4.0-1023.23~18.04.15.4.0-1025.25~18.04.15.4.0-1026.26~18.04.1 Show 45 moreShow less5.4.0-1031.32~18.04.15.4.0-1032.33~18.04.15.4.0-1034.35~18.04.15.4.0-1035.36~18.04.15.4.0-1036.38~18.04.15.4.0-1039.41~18.04.15.4.0-1040.42~18.04.15.4.0-1041.43~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-1047.49~18.04.15.4.0-1048.50~18.04.15.4.0-1049.51~18.04.15.4.0-1051.53~18.04.15.4.0-1055.57~18.04.15.4.0-1056.58~18.04.15.4.0-1058.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-1064.67~18.04.15.4.0-1065.68~18.04.15.4.0-1067.70~18.04.15.4.0-1068.71~18.04.15.4.0-1069.72~18.04.15.4.0-1070.73~18.04.15.4.0-1072.75~18.04.15.4.0-1073.76~18.04.15.4.0-1074.77~18.04.15.4.0-1077.80~18.04.15.4.0-1078.81~18.04.15.4.0-1080.83~18.04.25.4.0-1083.87~18.04.15.4.0-1085.90~18.04.15.4.0-1086.91~18.04.15.4.0-1089.94~18.04.15.4.0-1090.95~18.04.15.4.0-1091.96~18.04.15.4.0-1094.100~18.04.15.4.0-1095.101~18.04.15.4.0-1098.104~18.04.25.4.0-1100.106~18.04.15.4.0-1101.107~18.04.1 |
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-4.15Ubuntu:Pro:18.04:LTS |
All versions, plus listed versions 4.15.0-1071.814.15.0-1077.874.15.0-1078.884.15.0-1080.904.15.0-1081.92 Show 45 moreShow less4.15.0-1083.944.15.0-1084.954.15.0-1086.984.15.0-1087.1004.15.0-1088.1014.15.0-1090.1034.15.0-1091.1044.15.0-1092.1054.15.0-1093.1064.15.0-1094.1074.15.0-1095.1084.15.0-1096.1094.15.0-1097.1104.15.0-1098.1114.15.0-1099.1124.15.0-1100.1134.15.0-1103.1164.15.0-1106.1204.15.0-1107.1214.15.0-1108.1224.15.0-1109.1234.15.0-1110.1244.15.0-1111.1254.15.0-1112.1264.15.0-1114.1284.15.0-1115.1294.15.0-1116.1304.15.0-1118.1324.15.0-1119.1334.15.0-1120.1344.15.0-1121.1354.15.0-1122.1364.15.0-1124.1384.15.0-1127.1424.15.0-1130.1464.15.0-1131.1474.15.0-1134.1504.15.0-1135.1514.15.0-1136.1524.15.0-1137.1534.15.0-1138.1544.15.0-1141.1574.15.0-1142.1584.15.0-1143.1594.15.0-1145.161 |
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-gcp-5.4Ubuntu:Pro:18.04:LTS |
All versions, plus listed versions 5.4.0-1019.19~18.04.25.4.0-1021.21~18.04.15.4.0-1022.22~18.04.15.4.0-1024.24~18.04.15.4.0-1025.25~18.04.1 Show 45 moreShow less5.4.0-1028.29~18.04.15.4.0-1029.31~18.04.15.4.0-1030.32~18.04.15.4.0-1032.34~18.04.15.4.0-1033.35~18.04.15.4.0-1034.37~18.04.15.4.0-1036.39~18.04.15.4.0-1037.40~18.04.15.4.0-1038.41~18.04.15.4.0-1040.43~18.04.15.4.0-1041.44~18.04.15.4.0-1042.45~18.04.15.4.0-1043.46~18.04.15.4.0-1044.47~18.04.25.4.0-1046.49~18.04.15.4.0-1049.53~18.04.15.4.0-1051.55~18.04.15.4.0-1052.56~18.04.15.4.0-1053.57~18.04.15.4.0-1055.59~18.04.15.4.0-1056.60~18.04.15.4.0-1057.61~18.04.15.4.0-1058.62~18.04.15.4.0-1059.63~18.04.15.4.0-1060.64~18.04.15.4.0-1062.66~18.04.15.4.0-1063.67~18.04.15.4.0-1064.68~18.04.15.4.0-1065.69~18.04.15.4.0-1067.71~18.04.15.4.0-1068.72~18.04.15.4.0-1069.73~18.04.15.4.0-1072.77~18.04.15.4.0-1073.78~18.04.15.4.0-1075.80~18.04.15.4.0-1078.84~18.04.15.4.0-1080.87~18.04.15.4.0-1083.91~18.04.15.4.0-1084.92~18.04.15.4.0-1086.94~18.04.15.4.0-1087.95~18.04.15.4.0-1089.97~18.04.15.4.0-1092.101~18.04.15.4.0-1093.102~18.04.15.4.0-1096.105~18.04.2 |
None known |
linux-gke-4.15Ubuntu:18.04:LTS |
All versions, plus listed versions 4.15.0-1030.324.15.0-1032.344.15.0-1033.354.15.0-1034.364.15.0-1036.38 Show 28 moreShow less4.15.0-1037.394.15.0-1040.424.15.0-1041.434.15.0-1042.444.15.0-1044.464.15.0-1045.484.15.0-1046.494.15.0-1048.514.15.0-1049.524.15.0-1050.534.15.0-1052.554.15.0-1055.584.15.0-1057.604.15.0-1058.614.15.0-1059.624.15.0-1063.664.15.0-1064.674.15.0-1066.694.15.0-1067.704.15.0-1069.724.15.0-1070.734.15.0-1072.764.15.0-1073.784.15.0-1074.794.15.0-1076.814.15.0-1077.824.15.0-1078.834.15.0-1079.84 |
None known |
linux-gke-5.4Ubuntu:18.04:LTS |
All versions, plus listed versions 5.4.0-1025.25~18.04.15.4.0-1027.28~18.04.15.4.0-1029.31~18.04.15.4.0-1030.32~18.04.15.4.0-1032.34~18.04.1 Show 32 moreShow less5.4.0-1033.35~18.04.15.4.0-1035.37~18.04.15.4.0-1036.38~18.04.15.4.0-1037.39~18.04.15.4.0-1039.41~18.04.15.4.0-1040.42~18.04.15.4.0-1042.44~18.04.15.4.0-1043.45~18.04.15.4.0-1044.46~18.04.15.4.0-1046.48~18.04.15.4.0-1049.52~18.04.15.4.0-1051.54~18.04.15.4.0-1052.55~18.04.15.4.0-1053.56~18.04.15.4.0-1054.57~18.04.15.4.0-1055.58~18.04.15.4.0-1056.59~18.04.15.4.0-1057.60~18.04.15.4.0-1059.62~18.04.15.4.0-1061.64~18.04.15.4.0-1062.65~18.04.15.4.0-1063.66~18.04.15.4.0-1065.68~18.04.15.4.0-1066.69~18.04.15.4.0-1067.70~18.04.15.4.0-1068.71~18.04.15.4.0-1071.76~18.04.35.4.0-1072.77~18.04.15.4.0-1074.79~18.04.15.4.0-1076.82~18.04.15.4.0-1078.84~18.04.15.4.0-1080.86~18.04.1 |
None known |
linux-gkeop-5.4Ubuntu:18.04:LTS |
All versions, plus listed versions 5.4.0-1001.15.4.0-1003.35.4.0-1004.55.4.0-1005.65.4.0-1007.8~18.04.1 Show 32 moreShow less5.4.0-1008.9~18.04.15.4.0-1009.10~18.04.15.4.0-1010.11~18.04.15.4.0-1011.12~18.04.25.4.0-1012.13~18.04.15.4.0-1013.14~18.04.15.4.0-1014.15~18.04.15.4.0-1015.16~18.04.15.4.0-1016.17~18.04.15.4.0-1018.19~18.04.15.4.0-1021.22~18.04.15.4.0-1022.23~18.04.15.4.0-1023.24~18.04.15.4.0-1024.25~18.04.15.4.0-1025.26~18.04.15.4.0-1026.27~18.04.15.4.0-1027.28~18.04.15.4.0-1029.30~18.04.25.4.0-1031.32~18.04.15.4.0-1032.33~18.04.15.4.0-1033.34~18.04.15.4.0-1034.35~18.04.15.4.0-1036.37~18.04.15.4.0-1037.38~18.04.15.4.0-1038.39~18.04.15.4.0-1039.40~18.04.15.4.0-1040.41~18.04.15.4.0-1043.44~18.04.15.4.0-1046.48~18.04.15.4.0-1048.51~18.04.15.4.0-1049.52~18.04.15.4.0-1051.54~18.04.1 |
None known |
linux-hweUbuntu:18.04:LTS |
All versions, plus listed versions 4.18.0-13.14~18.04.14.18.0-14.15~18.04.14.18.0-15.16~18.04.14.18.0-16.17~18.04.14.18.0-17.18~18.04.1 Show 38 moreShow less4.18.0-18.19~18.04.14.18.0-20.21~18.04.14.18.0-21.22~18.04.14.18.0-22.23~18.04.14.18.0-24.25~18.04.14.18.0-25.26~18.04.15.0.0-23.24~18.04.15.0.0-25.26~18.04.15.0.0-27.28~18.04.15.0.0-29.31~18.04.15.0.0-31.33~18.04.15.0.0-32.34~18.04.25.0.0-35.38~18.04.15.0.0-36.39~18.04.15.0.0-37.40~18.04.15.3.0-26.28~18.04.15.3.0-28.30~18.04.15.3.0-40.32~18.04.15.3.0-42.34~18.04.15.3.0-45.37~18.04.15.3.0-46.38~18.04.15.3.0-51.44~18.04.25.3.0-53.47~18.04.15.3.0-59.53~18.04.15.3.0-61.55~18.04.15.3.0-62.56~18.04.15.3.0-64.58~18.04.15.3.0-65.595.3.0-66.605.3.0-67.615.3.0-68.635.3.0-69.655.3.0-70.665.3.0-72.685.3.0-73.695.3.0-74.705.3.0-75.715.3.0-76.72 |
None known |
linux-hwe-5.4Ubuntu:Pro:18.04:LTS |
All versions, plus listed versions 5.4.0-37.41~18.04.15.4.0-39.43~18.04.15.4.0-40.44~18.04.15.4.0-42.46~18.04.15.4.0-45.49~18.04.2 Show 45 moreShow less5.4.0-47.51~18.04.15.4.0-48.52~18.04.15.4.0-51.56~18.04.15.4.0-52.57~18.04.15.4.0-53.59~18.04.15.4.0-54.60~18.04.15.4.0-56.62~18.04.15.4.0-58.64~18.04.15.4.0-59.65~18.04.15.4.0-60.67~18.04.15.4.0-62.70~18.04.15.4.0-64.72~18.04.15.4.0-65.73~18.04.15.4.0-66.74~18.04.25.4.0-67.75~18.04.15.4.0-70.78~18.04.15.4.0-71.79~18.04.15.4.0-72.80~18.04.15.4.0-73.82~18.04.15.4.0-74.83~18.04.15.4.0-77.86~18.04.15.4.0-80.90~18.04.15.4.0-81.91~18.04.15.4.0-84.94~18.04.15.4.0-86.97~18.04.15.4.0-87.98~18.04.15.4.0-89.100~18.04.15.4.0-90.101~18.04.15.4.0-91.102~18.04.15.4.0-92.103~18.04.25.4.0-94.106~18.04.15.4.0-96.109~18.04.15.4.0-97.110~18.04.15.4.0-99.112~18.04.15.4.0-100.113~18.04.15.4.0-104.118~18.04.15.4.0-105.119~18.04.15.4.0-107.121~18.04.15.4.0-109.123~18.04.15.4.0-110.124~18.04.15.4.0-113.127~18.04.15.4.0-117.132~18.04.15.4.0-120.136~18.04.15.4.0-121.137~18.04.15.4.0-122.138~18.04.1 |
None known |
linux-hwe-edgeUbuntu:18.04:LTS |
All versions, plus listed versions 5.0.0-15.16~18.04.15.0.0-16.17~18.04.15.0.0-17.18~18.04.15.0.0-19.20~18.04.15.0.0-20.21~18.04.1 Show 5 moreShow less5.3.0-19.20~18.04.25.3.0-22.24~18.04.15.3.0-23.25~18.04.15.3.0-23.25~18.04.25.3.0-24.26~18.04.2 |
None known |
linux-ibm-5.4Ubuntu:Pro:18.04:LTS |
All versions, plus listed versions 5.4.0-1010.11~18.04.25.4.0-1012.13~18.04.15.4.0-1014.15~18.04.15.4.0-1015.16~18.04.15.4.0-1017.19~18.04.1 Show 45 moreShow less5.4.0-1018.20~18.04.15.4.0-1019.21~18.04.15.4.0-1020.22~18.04.15.4.0-1021.23~18.04.15.4.0-1023.25~18.04.15.4.0-1026.29~18.04.15.4.0-1028.32~18.04.15.4.0-1029.33~18.04.15.4.0-1031.35~18.04.15.4.0-1032.36~18.04.15.4.0-1033.37~18.04.15.4.0-1034.38~18.04.15.4.0-1036.41~18.04.15.4.0-1037.42~18.04.15.4.0-1040.45~18.04.25.4.0-1041.46~18.04.15.4.0-1042.47~18.04.15.4.0-1044.49~18.04.15.4.0-1045.50~18.04.15.4.0-1046.51~18.04.15.4.0-1047.52~18.04.15.4.0-1048.53~18.04.15.4.0-1049.54~18.04.15.4.0-1050.55~18.04.15.4.0-1051.56~18.04.15.4.0-1052.57~18.04.15.4.0-1053.58~18.04.15.4.0-1054.59~18.04.15.4.0-1056.61~18.04.15.4.0-1057.62~18.04.15.4.0-1058.63~18.04.15.4.0-1059.64~18.04.15.4.0-1060.65~18.04.15.4.0-1061.66~18.04.15.4.0-1063.68~18.04.15.4.0-1064.69~18.04.15.4.0-1065.70~18.04.15.4.0-1066.71~18.04.15.4.0-1067.72~18.04.15.4.0-1068.73~18.04.15.4.0-1069.74~18.04.15.4.0-1070.75~18.04.15.4.0-1071.76~18.04.15.4.0-1072.77~18.04.15.4.0-1073.78~18.04.1 |
None known |
linux-kvmUbuntu:Pro:18.04:LTS |
All versions, plus listed versions 4.15.0-1002.24.15.0-1003.34.15.0-1004.44.15.0-1006.64.15.0-1008.8 Show 45 moreShow less4.15.0-1010.104.15.0-1011.114.15.0-1012.124.15.0-1016.164.15.0-1017.174.15.0-1019.194.15.0-1020.204.15.0-1021.214.15.0-1023.234.15.0-1025.254.15.0-1026.264.15.0-1027.274.15.0-1028.284.15.0-1029.294.15.0-1030.304.15.0-1031.314.15.0-1032.324.15.0-1034.344.15.0-1035.354.15.0-1036.364.15.0-1038.384.15.0-1039.394.15.0-1042.424.15.0-1043.434.15.0-1044.444.15.0-1046.464.15.0-1047.474.15.0-1048.484.15.0-1050.504.15.0-1051.514.15.0-1052.524.15.0-1053.534.15.0-1056.574.15.0-1058.594.15.0-1059.604.15.0-1060.614.15.0-1067.684.15.0-1069.704.15.0-1071.724.15.0-1072.734.15.0-1074.754.15.0-1075.764.15.0-1077.794.15.0-1079.814.15.0-1081.83 |
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-oracleUbuntu:Pro:18.04:LTS |
All versions, plus listed versions 4.15.0-1007.94.15.0-1008.104.15.0-1009.114.15.0-1010.124.15.0-1011.13 Show 45 moreShow less4.15.0-1013.154.15.0-1014.164.15.0-1015.174.15.0-1017.194.15.0-1018.204.15.0-1021.234.15.0-1022.254.15.0-1023.264.15.0-1025.284.15.0-1026.294.15.0-1027.304.15.0-1029.324.15.0-1030.334.15.0-1031.344.15.0-1033.364.15.0-1035.394.15.0-1037.414.15.0-1038.424.15.0-1039.434.15.0-1045.494.15.0-1047.514.15.0-1048.524.15.0-1050.544.15.0-1051.554.15.0-1053.574.15.0-1054.584.15.0-1057.624.15.0-1058.644.15.0-1059.654.15.0-1061.674.15.0-1062.684.15.0-1063.704.15.0-1064.714.15.0-1065.734.15.0-1066.744.15.0-1067.754.15.0-1068.764.15.0-1069.774.15.0-1070.784.15.0-1071.794.15.0-1072.804.15.0-1075.834.15.0-1078.864.15.0-1079.874.15.0-1080.88 |
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-oracle-5.4Ubuntu:Pro:18.04:LTS |
All versions, plus listed versions 5.4.0-1019.19~18.04.15.4.0-1021.21~18.04.15.4.0-1022.22~18.04.15.4.0-1024.24~18.04.15.4.0-1025.25~18.04.1 Show 45 moreShow less5.4.0-1028.29~18.04.15.4.0-1029.31~18.04.15.4.0-1030.32~18.04.15.4.0-1033.355.4.0-1034.36~18.04.15.4.0-1035.38~18.04.15.4.0-1037.40~18.04.15.4.0-1038.41~18.04.15.4.0-1039.42~18.04.15.4.0-1041.44~18.04.15.4.0-1042.45~18.04.15.4.0-1043.46~18.04.15.4.0-1044.47~18.04.15.4.0-1046.50~18.04.25.4.0-1048.52~18.04.15.4.0-1049.53~18.04.15.4.0-1052.56~18.04.15.4.0-1053.57~18.04.15.4.0-1054.58~18.04.15.4.0-1055.59~18.04.15.4.0-1056.60~18.04.15.4.0-1057.61~18.04.15.4.0-1058.62~18.04.15.4.0-1059.63~18.04.15.4.0-1061.65~18.04.15.4.0-1062.66~18.04.15.4.0-1063.67~18.04.15.4.0-1064.68~18.04.15.4.0-1066.71~18.04.15.4.0-1067.72~18.04.15.4.0-1069.75~18.04.15.4.0-1070.76~18.04.15.4.0-1071.77~18.04.15.4.0-1073.79~18.04.15.4.0-1076.83~18.04.15.4.0-1078.86~18.04.15.4.0-1079.87~18.04.15.4.0-1081.89~18.04.15.4.0-1082.90~18.04.15.4.0-1083.91~18.04.15.4.0-1084.92~18.04.15.4.0-1086.95~18.04.15.4.0-1087.96~18.04.15.4.0-1090.99~18.04.25.4.0-1091.100~18.04.1 |
None known |
linux-raspi-5.4Ubuntu:Pro:18.04:LTS |
All versions, plus listed versions 5.4.0-1013.13~18.04.15.4.0-1015.15~18.04.15.4.0-1016.17~18.04.15.4.0-1018.20~18.04.15.4.0-1019.21~18.04.1 Show 45 moreShow less5.4.0-1021.24~18.04.15.4.0-1022.25~18.04.15.4.0-1023.26~18.04.15.4.0-1025.28~18.04.15.4.0-1026.29~18.04.15.4.0-1028.31~18.04.15.4.0-1029.32~18.04.15.4.0-1030.33~18.04.15.4.0-1032.35~18.04.15.4.0-1033.36~18.04.15.4.0-1034.37~18.04.15.4.0-1035.38~18.04.15.4.0-1036.39~18.04.15.4.0-1038.41~18.04.15.4.0-1041.45~18.04.15.4.0-1042.46~18.04.35.4.0-1043.47~18.04.15.4.0-1044.48~18.04.15.4.0-1045.49~18.04.15.4.0-1046.50~18.04.15.4.0-1047.52~18.04.15.4.0-1048.53~18.04.15.4.0-1050.56~18.04.15.4.0-1052.58~18.04.15.4.0-1053.60~18.04.15.4.0-1055.62~18.04.15.4.0-1056.63~18.04.15.4.0-1058.65~18.04.15.4.0-1059.66~18.04.15.4.0-1060.68~18.04.15.4.0-1062.70~18.04.15.4.0-1065.75~18.04.15.4.0-1066.76~18.04.15.4.0-1068.78~18.04.15.4.0-1069.79~18.04.15.4.0-1070.80~18.04.15.4.0-1071.81~18.04.15.4.0-1073.84~18.04.15.4.0-1074.85~18.04.15.4.0-1077.88~18.04.25.4.0-1078.89~18.04.15.4.0-1079.90~18.04.15.4.0-1080.91~18.04.15.4.0-1081.92~18.04.15.4.0-1082.93~18.04.1 |
None known |
linux-aws-fipsUbuntu:Pro:FIPS-updates:18.04:LTS |
All versions, plus listed versions 4.15.0-2000.44.15.0-2018.184.15.0-2021.214.15.0-2022.224.15.0-2024.24 Show 45 moreShow less4.15.0-2025.254.15.0-2026.264.15.0-2027.274.15.0-2030.314.15.0-2031.324.15.0-2033.344.15.0-2034.354.15.0-2035.374.15.0-2036.384.15.0-2037.394.15.0-2038.404.15.0-2039.414.15.0-2040.424.15.0-2041.434.15.0-2042.444.15.0-2044.464.15.0-2045.474.15.0-2048.504.15.0-2051.534.15.0-2052.544.15.0-2053.554.15.0-2054.564.15.0-2055.574.15.0-2056.584.15.0-2057.594.15.0-2059.614.15.0-2060.624.15.0-2061.634.15.0-2063.664.15.0-2064.674.15.0-2065.684.15.0-2066.694.15.0-2067.704.15.0-2069.724.15.0-2072.764.15.0-2075.804.15.0-2076.814.15.0-2078.834.15.0-2079.844.15.0-2080.854.15.0-2081.874.15.0-2082.884.15.0-2083.894.15.0-2085.914.15.0-2087.93 |
None known |
linux-azure-fipsUbuntu:Pro:FIPS-updates:18.04:LTS |
All versions, plus listed versions 4.15.0-1002.24.15.0-2006.74.15.0-2007.84.15.0-2008.94.15.0-2009.10 Show 45 moreShow less4.15.0-2012.144.15.0-2013.154.15.0-2015.174.15.0-2016.184.15.0-2017.204.15.0-2018.214.15.0-2020.234.15.0-2021.244.15.0-2022.254.15.0-2023.264.15.0-2024.274.15.0-2025.284.15.0-2026.294.15.0-2027.304.15.0-2030.334.15.0-2033.374.15.0-2034.384.15.0-2035.394.15.0-2036.404.15.0-2037.414.15.0-2038.424.15.0-2039.434.15.0-2041.454.15.0-2042.464.15.0-2043.474.15.0-2045.494.15.0-2046.504.15.0-2047.514.15.0-2048.524.15.0-2049.534.15.0-2050.544.15.0-2053.584.15.0-2056.624.15.0-2057.634.15.0-2059.654.15.0-2060.664.15.0-2062.684.15.0-2066.724.15.0-2067.734.15.0-2068.744.15.0-2070.764.15.0-2071.774.15.0-2072.784.15.0-2073.794.15.0-2074.80 |
None known |
linux-fipsUbuntu:Pro:FIPS-updates:18.04:LTS |
All versions, plus listed versions 4.15.0-1027.324.15.0-1029.344.15.0-1034.394.15.0-1035.404.15.0-1037.42 Show 45 moreShow less4.15.0-1038.434.15.0-1039.444.15.0-1040.454.15.0-1041.464.15.0-1044.504.15.0-1045.524.15.0-1046.534.15.0-1048.554.15.0-1049.564.15.0-1050.584.15.0-1051.594.15.0-1052.604.15.0-1053.614.15.0-1054.624.15.0-1055.634.15.0-1056.644.15.0-1057.654.15.0-1058.664.15.0-1059.674.15.0-1060.684.15.0-1063.714.15.0-1066.754.15.0-1067.764.15.0-1068.774.15.0-1069.784.15.0-1070.794.15.0-1071.804.15.0-1072.814.15.0-1073.824.15.0-1075.844.15.0-1076.854.15.0-1078.874.15.0-1080.894.15.0-1081.904.15.0-1083.924.15.0-1084.934.15.0-1085.944.15.0-1087.964.15.0-1090.1004.15.0-1093.1044.15.0-1094.1054.15.0-1096.1074.15.0-1097.1084.15.0-1098.1094.15.0-1099.110 |
None known |
linux-gcp-fipsUbuntu:Pro:FIPS-updates:18.04:LTS |
All versions, plus listed versions 4.15.0-2013.144.15.0-2016.184.15.0-2017.194.15.0-2018.204.15.0-2019.21 Show 45 moreShow less4.15.0-2020.224.15.0-2021.234.15.0-2022.244.15.0-2024.264.15.0-2025.274.15.0-2026.284.15.0-2028.314.15.0-2029.324.15.0-2030.334.15.0-2031.344.15.0-2032.354.15.0-2034.374.15.0-2037.414.15.0-2040.454.15.0-2041.464.15.0-2043.484.15.0-2044.494.15.0-2045.504.15.0-2047.524.15.0-2050.554.15.0-2052.574.15.0-2054.594.15.0-2055.604.15.0-2056.614.15.0-2057.624.15.0-2058.634.15.0-2059.644.15.0-2060.654.15.0-2061.664.15.0-2062.674.15.0-2063.684.15.0-2064.694.15.0-2065.704.15.0-2066.714.15.0-2067.724.15.0-2068.734.15.0-2069.744.15.0-2070.754.15.0-2071.764.15.0-2072.774.15.0-2073.784.15.0-2074.794.15.0-2075.804.15.0-2076.814.15.0-2077.83 |
None known |
linux-aws-fipsUbuntu:Pro:FIPS:18.04:LTS |
All versions, plus listed versions 4.15.0-2000.4 |
None known |
History
| Recorded | Changed | Sources |
|---|---|---|
| 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-40927 is a high vulnerability (CVSS 7.8) in Linux, published July 12, 2024. No source lists public exploit code. EPSS puts the chance of exploitation in the next 30 days at 0.29%, the 21st percentile. Fixed in bpftool 4.18.0-553.16.1.el8_10.
References
git.kernel.org/stable/c/26460c1afa311524f588e288a4941432f0de6228
git.kernel.org/stable/c/633f72cb6124ecda97b641fbc119340bd88d51a9
git.kernel.org/stable/c/949be4ec5835e0ccb3e2a8ab0e46179cb5512518
git.kernel.org/stable/c/61593dc413c3655e4328a351555235bc3089486a
git.kernel.org/stable/c/5ceac4402f5d975e5a01c806438eb4e554771577
lists.debian.org/debian-lts-announce/2025/01/msg00001.html
Show 194 moreShow less
nvd.nist.gov/vuln/detail/CVE-2024-40927
github.com/advisories/GHSA-38vr-8qrj-3x4h
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
access.redhat.com/security/cve/CVE-2023-28746
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
bugzilla.redhat.com/2272795
errata.almalinux.org/8/ALSA-2024-5101.html
errata.almalinux.org/8/ALSA-2024-5102.html
errata.almalinux.org/9/ALSA-2024-6567.html
docs.bell-sw.com/security/cves/CVE-2024-40927
errata.tuxcare.com/almalinux9.2-esu/CLSA-2024-1728936982.html
errata.tuxcare.com/els_os/centos-stream8els/CLSA-2025-1763722365.html
nvd.nist.gov/vuln/detail/CVE-2022-2905
nvd.nist.gov/vuln/detail/CVE-2022-2978
nvd.nist.gov/vuln/detail/CVE-2022-49985
nvd.nist.gov/vuln/detail/CVE-2022-50367
nvd.nist.gov/vuln/detail/CVE-2022-50386
nvd.nist.gov/vuln/detail/CVE-2023-52530
nvd.nist.gov/vuln/detail/CVE-2023-52764
nvd.nist.gov/vuln/detail/CVE-2023-52775
nvd.nist.gov/vuln/detail/CVE-2023-52847
nvd.nist.gov/vuln/detail/CVE-2023-52864
nvd.nist.gov/vuln/detail/CVE-2023-53125
nvd.nist.gov/vuln/detail/CVE-2023-53178
nvd.nist.gov/vuln/detail/CVE-2023-53226
nvd.nist.gov/vuln/detail/CVE-2023-53257
nvd.nist.gov/vuln/detail/CVE-2023-53305
nvd.nist.gov/vuln/detail/CVE-2023-53373
nvd.nist.gov/vuln/detail/CVE-2024-26739
nvd.nist.gov/vuln/detail/CVE-2024-26958
github.com/CVEProject/cvelistV5/tree/main/cves/2024/40xxx/CVE-2024-40927.json
git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
security-tracker.debian.org/tracker/CVE-2024-40927
openeuler.org/zh/security/security-bulletins/detail?id=openEuler-SA-2024-2534
openeuler.org/zh/security/security-bulletins/detail?id=openEuler-SA-2024-2537
openeuler.org/zh/security/security-bulletins/detail?id=openEuler-SA-2024-2571
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
cve.org/CVERecord?id=CVE-2022-50495
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
lore.kernel.org/linux-cve-announce/2024022335-CVE-2023-52463-6195@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
git.kernel.org/stable/c/3cd9b9bee33f39f6c6d52360fe381b89a7b12695
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
security.access.redhat.com/data/csaf/v2/advisories/2024/rhsa-2024_6567.json
errata.rockylinux.org/RLSA-2024:5101
errata.rockylinux.org/RLSA-2024:5102
errata.rockylinux.org/RLSA-2024:6567
errata.rockylinux.org/RXSA-2024:5101
errata.rockylinux.org/RXSA-2024:6567
suse.com/support/update/announcement/2024/suse-su-20242894-1
bugzilla.suse.com/1082555
bugzilla.suse.com/1193454
bugzilla.suse.com/1193554
bugzilla.suse.com/1193787
bugzilla.suse.com/1194324
bugzilla.suse.com/1194869
bugzilla.suse.com/1195357
bugzilla.suse.com/1195668
bugzilla.suse.com/1195927
bugzilla.suse.com/1195957
bugzilla.suse.com/1196018
bugzilla.suse.com/1196823
bugzilla.suse.com/1197146
bugzilla.suse.com/1197246
bugzilla.suse.com/1197762
bugzilla.suse.com/1202346
bugzilla.suse.com/1202686
bugzilla.suse.com/1208783
bugzilla.suse.com/1209636
suse.com/security/cve/CVE-2021-47086
suse.com/security/cve/CVE-2021-47103
suse.com/security/cve/CVE-2021-47186
suse.com/security/cve/CVE-2021-47402
suse.com/security/cve/CVE-2021-47546
suse.com/security/cve/CVE-2021-47547
suse.com/security/cve/CVE-2021-47588
suse.com/security/cve/CVE-2021-47590
suse.com/security/cve/CVE-2021-47591
suse.com/security/cve/CVE-2021-47593
suse.com/security/cve/CVE-2021-47598
suse.com/security/cve/CVE-2021-47599
suse.com/security/cve/CVE-2021-47606
suse.com/security/cve/CVE-2021-47622
suse.com/security/cve/CVE-2021-47623
suse.com/security/cve/CVE-2021-47624
suse.com/security/cve/CVE-2022-48713
suse.com/security/cve/CVE-2022-48730
ubuntu.com/security/CVE-2024-40927
ubuntu.com/security/notices/USN-6999-1
ubuntu.com/security/notices/USN-7004-1
ubuntu.com/security/notices/USN-7005-1
ubuntu.com/security/notices/USN-7007-1
ubuntu.com/security/notices/USN-7008-1
ubuntu.com/security/notices/USN-7005-2
ubuntu.com/security/notices/USN-7009-1
ubuntu.com/security/notices/USN-7019-1
ubuntu.com/security/notices/USN-7007-2
ubuntu.com/security/notices/USN-6999-2
ubuntu.com/security/notices/USN-7007-3
ubuntu.com/security/notices/USN-7029-1
ubuntu.com/security/notices/USN-7009-2
ubuntu.com/security/CVE-2022-48772
ubuntu.com/security/CVE-2023-52884
ubuntu.com/security/CVE-2024-23848
ubuntu.com/security/CVE-2024-31076
ubuntu.com/security/CVE-2024-32936
Left out here: 378 package rows, 2,222 versions, 3,543 references and the rest of 26 source descriptions. The JSON record has them.