Every CVE Search/ Get API key

CVE-2024-40918

parisc: Try to fix random segmentation faults in package builds

7.8 HighFix available

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

parisc: Try to fix random segmentation faults in package builds

PA-RISC systems with PA8800 and PA8900 processors have had problems with random segmentation faults for many years. Systems with earlier processors are much more stable.

Systems with PA8800 and PA8900 processors have a large L2 cache which needs per page flushing for decent performance when a large range is flushed. The combined cache in these systems is also more sensitive to non-equivalent aliases than the caches in earlier systems.

The majority of random segmentation faults that I have looked at appear to be memory corruption in memory allocated using mmap and malloc.

My first attempt at fixing the random faults didn't work. On reviewing the cache code, I realized that there were two issues which the existing code didn't handle correctly. Both relate to cache move-in. Another issue is that the present bit in PTEs is racy.

  1. PA-RISC caches have a mind of their own and they can speculatively load data and instructions for a page as long as there is a entry in the TLB for the page which allows move-in. TLBs are local to each CPU. Thus, the TLB entry for a page must be purged before flushing the page. This is particularly important on SMP systems.

In some of the flush routines, the flush routine would be called and then the TLB entry would be purged. This was because the flush routine needed the TLB entry to do the flush.

  1. My initial approach to trying the fix the random faults was to try and use flush_cache_page_if_present for all flush operations. This actually made things worse and led to a couple of hardware lockups. It finally dawned on me that some lines weren't being flushed because the pte check code was racy. This resulted in random inequivalent mappings to physical pages.

The __flush_cache_page tmpalias flush sets up its own TLB entry and it doesn't need the existing TLB entry. As long as we can find the pte pointer for the vm page, we can get the pfn and physical address of the page. We can also purge the TLB entry for the page before doing the flush. Further, __flush_cache_page uses a special TLB entry that inhibits cache move-in.

When switching page mappings, we need to ensure that lines are removed from the cache. It is not sufficient to just flush the lines to memory as they may come back.

This made it clear that we needed to implement all the required flush operations using tmpalias routines. This includes flushes for user and kernel pages.

After modifying the code to use tmpalias flushes, it became clear that the random segmentation faults were not fully resolved. The frequency of faults was worse on systems with a 64 MB L2 (PA8900) and systems with more CPUs (rp4440).

The warning that I added to flush_cache_page_if_present to detect pages that couldn't be flushed triggered frequently on some systems.

Helge and I looked at the pages that couldn't be flushed and found that the PTE was either cleared or for a swap page. Ignoring pages that were swapped out seemed okay but pages with cleared PTEs seemed problematic.

I looked at routines related to pte_clear and noticed ptep_clear_flush. The default implementation just flushes the TLB entry. However, it was obvious that on parisc we need to flush the cache page as well. If we don't flush the cache page, stale lines will be left in the cache and cause random corruption. Once a PTE is cleared, there is no way to find the physical address associated with the PTE and flush the associated page at a later time.

I implemented an updated change with a parisc specific version of ptep_clear_flush. It fixed the random data corruption on Helge's rp4440 and rp3440, as well as on my c8000.

At this point, I realized that I could restore the code where we only flush in flush_cache_page_if_present if the page has been accessed. However, for this, we also need to flush the cache when the accessed bit is cleared in ---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

0.29%Up 0.2 points since Jul 13, 2024
90%50%10%1%

What each source reports

CVE List Score used 7.8

parisc: Try to fix random segmentation faults in package builds

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

parisc: Try to fix random segmentation faults in package builds

PA-RISC systems with PA8800 and PA8900 processors have had problems with random segmentation faults for many years. Systems with earlier processors are much more stable.

Systems with PA8800 and PA8900 processors have a large L2 cache which needs per page flushing for decent performance when a large range is flushed. The combined cache in these systems is also more sensitive to non-equivalent aliases than the caches in earlier systems.

The majority of random segmentation faults that I have looked at appear to be memory corruption in memory allocated using mmap and malloc.

My first attempt at fixing the random faults didn't work. On reviewing the cache code, I realized that there were two issues which the existing code didn't handle correctly. Both relate to cache move-in. Another issue is that the present bit in PTEs is racy.

  1. PA-RISC caches have a mind of their own and they can speculatively load data and instructions for a page as long as there is a entry in the TLB for the page which allows move-in. TLBs are local to each CPU. Thus, the TLB entry for a page must be purged before flushing the page. This is particularly important on SMP systems.

In some of the flush routines, the flush routine would be called and then the TLB entry would be purged. This was because the flush routine needed the TLB entry to do the flush.

  1. My initial approach to trying the fix the random faults was to try and use flush_cache_page_if_present for all flush operations. This actually made things worse and led to a couple of hardware lockups. It finally dawned on me that some lines weren't being flushed because the pte check code was racy. This resulted in random inequivalent mappings to physical pages.

The __flush_cache_page tmpalias flush sets up its own TLB entry and it doesn't need the existing TLB entry. As long as we can find the pte pointer for the vm page, we can get the pfn and physical address of the page. We can also purge the TLB entry for the page before doing the flush. Further, __flush_cache_page uses a special TLB entry that inhibits cache move-in.

When switching page mappings, we need to ensure that lines are removed from the cache. It is not sufficient to just flush the lines to memory as they may come back.

This made it clear that we needed to implement all the required flush operations using tmpalias routines. This includes flushes for user and kernel pages.

After modifying the code to use tmpalias flushes, it became clear that the random segmentation faults were not fully resolved. The frequency of faults was worse on systems with a 64 MB L2 (PA8900) and systems with more CPUs (rp4440).

The warning that I added to flush_cache_page_if_present to detect pages that couldn't be flushed triggered frequently on some systems.

Helge and I looked at the pages that couldn't be flushed and found that the PTE was either cleared or for a swap page. Ignoring pages that were swapped out seemed okay but pages with cleared PTEs seemed problematic.

I looked at routines related to pte_clear and noticed ptep_clear_flush. The default implementation just flushes the TLB entry. However, it was obvious that on parisc we need to flush the cache page as well. If we don't flush the cache page, stale lines will be left in the cache and cause random corruption. Once a PTE is cleared, there is no way to find the physical address associated with the PTE and flush the associated page at a later time.

I implemented an updated change with a parisc specific version of ptep_clear_flush. It fixed the random data corruption on Helge's rp4440 and rp3440, as well as on my c8000.

At this point, I realized that I could restore the code where we only flush in flush_cache_page_if_present if the page has been accessed. However, for this, we also need to flush the cache when the accessed bit is cleared in ---truncated---

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

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

parisc: Try to fix random segmentation faults in package builds

PA-RISC systems with PA8800 and PA8900 processors have had problems with random segmentation faults for many years. Systems with earlier processors are much more stable.

Systems with PA8800 and PA8900 processors have a large L2 cache which needs per page flushing for decent performance when a large range is flushed. The combined cache in these systems is also more sensitive to non-equivalent aliases than the caches in earlier systems.

The majority of random segmentation faults that I have looked at appear to be memory corruption in memory allocated using mmap and malloc.

My first attempt at fixing the random faults didn't work. On reviewing the cache code, I realized that there were two issues which the existing code didn't handle correctly. Both relate to cache move-in. Another issue is that the present bit in PTEs is racy.

  1. PA-RISC caches have a mind of their own and they can speculatively load data and instructions for a page as long as there is a entry in the TLB for the page which allows move-in. TLBs are local to each CPU. Thus, the TLB entry for a page must be purged before flushing the page. This is particularly important on SMP systems.

In some of the flush routines, the flush routine would be called and then the TLB entry would be purged. This was because the flush routine needed the TLB entry to do the flush.

  1. My initial approach to trying the fix the random faults was to try and use flush_cache_page_if_present for all flush operations. This actually made things worse and led to a couple of hardware lockups. It finally dawned on me that some lines weren't being flushed because the pte check code was racy. This resulted in random inequivalent mappings to physical pages.

The __flush_cache_page tmpalias flush sets up its own TLB entry and it doesn't need the existing TLB entry. As long as we can find the pte pointer for the vm page, we can get the pfn and physical address of the page. We can also purge the TLB entry for the page before doing the flush. Further, __flush_cache_page uses a special TLB entry that inhibits cache move-in.

When switching page mappings, we need to ensure that lines are removed from the cache. It is not sufficient to just flush the lines to memory as they may come back.

This made it clear that we needed to implement all the required flush operations using tmpalias routines. This includes flushes for user and kernel pages.

After modifying the code to use tmpalias flushes, it became clear that the random segmentation faults were not fully resolved. The frequency of faults was worse on systems with a 64 MB L2 (PA8900) and systems with more CPUs (rp4440).

The warning that I added to flush_cache_page_if_present to detect pages that couldn't be flushed triggered frequently on some systems.

Helge and I looked at the pages that couldn't be flushed and found that the PTE was either cleared or for a swap page. Ignoring pages that were swapped out seemed okay but pages with cleared PTEs seemed problematic.

I looked at routines related to pte_clear and noticed ptep_clear_flush. The default implementation just flushes the TLB entry. However, it was obvious that on parisc we need to flush the cache page as well. If we don't flush the cache page, stale lines will be left in the cache and cause random corruption. Once a PTE is cleared, there is no way to find the physical address associated with the PTE and flush the associated page at a later time.

I implemented an updated change with a parisc specific version of ptep_clear_flush. It fixed the random data corruption on Helge's rp4440 and rp3440, as well as on my c8000.

At this point, I realized that I could restore the code where we only flush in flush_cache_page_if_present if the page has been accessed. However, for this, we also need to flush the cache when the accessed bit is cleared in ---truncated---

Record
EUVD-2024-38729
CVSS 3.1
7.8 HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Updated
2026-11-02
GitHub AdvisoriesGHSA-43g8-4r39-vq2f 6.3

In the Linux kernel, the following vulnerability has been resolved: parisc: Try to fix random...

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

parisc: Try to fix random segmentation faults in package builds

PA-RISC systems with PA8800 and PA8900 processors have had problems with random segmentation faults for many years. Systems with earlier processors are much more stable.

Systems with PA8800 and PA8900 processors have a large L2 cache which needs per page flushing for decent performance when a large range is flushed. The combined cache in these systems is also more sensitive to non-equivalent aliases than the caches in earlier systems.

The majority of random segmentation faults that I have looked at appear to be memory corruption in memory allocated using mmap and malloc.

My first attempt at fixing the random faults didn't work. On reviewing the cache code, I realized that there were two issues which the existing code didn't handle correctly. Both relate to cache move-in. Another issue is that the present bit in PTEs is racy.

  1. PA-RISC caches have a mind of their own and they can speculatively load data and instructions for a page as long as there is a entry in the TLB for the page which allows move-in. TLBs are local to each CPU. Thus, the TLB entry for a page must be purged before flushing the page. This is particularly important on SMP systems.

In some of the flush routines, the flush routine would be called and then the TLB entry would be purged. This was because the flush routine needed the TLB entry to do the flush.

  1. My initial approach to trying the fix the random faults was to try and use flush_cache_page_if_present for all flush operations. This actually made things worse and led to a couple of hardware lockups. It finally dawned on me that some lines weren't being flushed because the pte check code was racy. This resulted in random inequivalent mappings to physical pages.

The __flush_cache_page tmpalias flush sets up its own TLB entry and it doesn't need the existing TLB entry. As long as we can find the pte pointer for the vm page, we can get the pfn and physical address of the page. We can also purge the TLB entry for the page before doing the flush. Further, __flush_cache_page uses a special TLB entry that inhibits cache move-in.

When switching page mappings, we need to ensure that lines are removed from the cache. It is not sufficient to just flush the lines to memory as they may come back.

This made it clear that we needed to implement all the required flush operations using tmpalias routines. This includes flushes for user and kernel pages.

After modifying the code to use tmpalias flushes, it became clear that the random segmentation faults were not fully resolved. The frequency of faults was worse on systems with a 64 MB L2 (PA8900) and systems with more CPUs (rp4440).

The warning that I added to flush_cache_page_if_present to detect pages that couldn't be flushed triggered frequently on some systems.

Helge and I looked at the pages that couldn't be flushed and found that the PTE was either cleared or for a swap page. Ignoring pages that were swapped out seemed okay but pages with cleared PTEs seemed problematic.

I looked at routines related to pte_clear and noticed ptep_clear_flush. The default implementation just flushes the TLB entry. However, it was obvious that on parisc we need to flush the cache page as well. If we don't flush the cache page, stale lines will be left in the cache and cause random corruption. Once a PTE is cleared, there is no way to find the physical address associated with the PTE and flush the associated page at a later time.

I implemented an updated change with a parisc specific version of ptep_clear_flush. It fixed the random data corruption on Helge's rp4440 and rp3440, as well as on my c8000.

At this point, I realized that I could restore the code where we only flush in flush_cache_page_if_present if the page has been accessed. However, for this, we also need to flush the cache when the accessed bit is cleared in ---truncated---

Record
GHSA-43g8-4r39-vq2f
CVSS 3.1
6.3 MediumCVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:H
Updated
2026-11-02
NVD 7.8

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

parisc: Try to fix random segmentation faults in package builds

PA-RISC systems with PA8800 and PA8900 processors have had problems with random segmentation faults for many years. Systems with earlier processors are much more stable.

Systems with PA8800 and PA8900 processors have a large L2 cache which needs per page flushing for decent performance when a large range is flushed. The combined cache in these systems is also more sensitive to non-equivalent aliases than the caches in earlier systems.

The majority of random segmentation faults that I have looked at appear to be memory corruption in memory allocated using mmap and malloc.

My first attempt at fixing the random faults didn't work. On reviewing the cache code, I realized that there were two issues which the existing code didn't handle correctly. Both relate to cache move-in. Another issue is that the present bit in PTEs is racy.

  1. PA-RISC caches have a mind of their own and they can speculatively load data and instructions for a page as long as there is a entry in the TLB for the page which allows move-in. TLBs are local to each CPU. Thus, the TLB entry for a page must be purged before flushing the page. This is particularly important on SMP systems.

In some of the flush routines, the flush routine would be called and then the TLB entry would be purged. This was because the flush routine needed the TLB entry to do the flush.

  1. My initial approach to trying the fix the random faults was to try and use flush_cache_page_if_present for all flush operations. This actually made things worse and led to a couple of hardware lockups. It finally dawned on me that some lines weren't being flushed because the pte check code was racy. This resulted in random inequivalent mappings to physical pages.

The __flush_cache_page tmpalias flush sets up its own TLB entry and it doesn't need the existing TLB entry. As long as we can find the pte pointer for the vm page, we can get the pfn and physical address of the page. We can also purge the TLB entry for the page before doing the flush. Further, __flush_cache_page uses a special TLB entry that inhibits cache move-in.

When switching page mappings, we need to ensure that lines are removed from the cache. It is not sufficient to just flush the lines to memory as they may come back.

This made it clear that we needed to implement all the required flush operations using tmpalias routines. This includes flushes for user and kernel pages.

After modifying the code to use tmpalias flushes, it became clear that the random segmentation faults were not fully resolved. The frequency of faults was worse on systems with a 64 MB L2 (PA8900) and systems with more CPUs (rp4440).

The warning that I added to flush_cache_page_if_present to detect pages that couldn't be flushed triggered frequently on some systems.

Helge and I looked at the pages that couldn't be flushed and found that the PTE was either cleared or for a swap page. Ignoring pages that were swapped out seemed okay but pages with cleared PTEs seemed problematic.

I looked at routines related to pte_clear and noticed ptep_clear_flush. The default implementation just flushes the TLB entry. However, it was obvious that on parisc we need to flush the cache page as well. If we don't flush the cache page, stale lines will be left in the cache and cause random corruption. Once a PTE is cleared, there is no way to find the physical address associated with the PTE and flush the associated page at a later time.

I implemented an updated change with a parisc specific version of ptep_clear_flush. It fixed the random data corruption on Helge's rp4440 and rp3440, as well as on my c8000.

At this point, I realized that I could restore the code where we only flush in flush_cache_page_if_present if the page has been accessed. However, for this, we also need to flush the cache when the accessed bit is cleared in ---truncated---

Record
CVE-2024-40918
CVSS 3.1
7.8 HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CVSS 3.1
6.3 MediumCVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:H
Updated
2026-11-02
OSVBELL-CVE-2024-40918 6.3
Record
BELL-CVE-2024-40918
CVSS 3.1
6.3 MediumCVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:H
Updated
2026-11-02
OSV 7.8

parisc: Try to fix random segmentation faults in package builds

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

parisc: Try to fix random segmentation faults in package builds

PA-RISC systems with PA8800 and PA8900 processors have had problems with random segmentation faults for many years. Systems with earlier processors are much more stable.

Systems with PA8800 and PA8900 processors have a large L2 cache which needs per page flushing for decent performance when a large range is flushed. The combined cache in these systems is also more sensitive to non-equivalent aliases than the caches in earlier systems.

The majority of random segmentation faults that I have looked at appear to be memory corruption in memory allocated using mmap and malloc.

My first attempt at fixing the random faults didn't work. On reviewing the cache code, I realized that there were two issues which the existing code didn't handle correctly. Both relate to cache move-in. Another issue is that the present bit in PTEs is racy.

  1. PA-RISC caches have a mind of their own and they can speculatively load data and instructions for a page as long as there is a entry in the TLB for the page which allows move-in. TLBs are local to each CPU. Thus, the TLB entry for a page must be purged before flushing the page. This is particularly important on SMP systems.

In some of the flush routines, the flush routine would be called and then the TLB entry would be purged. This was because the flush routine needed the TLB entry to do the flush.

  1. My initial approach to trying the fix the random faults was to try and use flush_cache_page_if_present for all flush operations. This actually made things worse and led to a couple of hardware lockups. It finally dawned on me that some lines weren't being flushed because the pte check code was racy. This resulted in random inequivalent mappings to physical pages.

The __flush_cache_page tmpalias flush sets up its own TLB entry and it doesn't need the existing TLB entry. As long as we can find the pte pointer for the vm page, we can get the pfn and physical address of the page. We can also purge the TLB entry for the page before doing the flush. Further, __flush_cache_page uses a special TLB entry that inhibits cache move-in.

When switching page mappings, we need to ensure that lines are removed from the cache. It is not sufficient to just flush the lines to memory as they may come back.

This made it clear that we needed to implement all the required flush operations using tmpalias routines. This includes flushes for user and kernel pages.

After modifying the code to use tmpalias flushes, it became clear that the random segmentation faults were not fully resolved. The frequency of faults was worse on systems with a 64 MB L2 (PA8900) and systems with more CPUs (rp4440).

The warning that I added to flush_cache_page_if_present to detect pages that couldn't be flushed triggered frequently on some systems.

Helge and I looked at the pages that couldn't be flushed and found that the PTE was either cleared or for a swap page. Ignoring pages that were swapped out seemed okay but pages with cleared PTEs seemed problematic.

I looked at routines related to pte_clear and noticed ptep_clear_flush. The default implementation just flushes the TLB entry. However, it was obvious that on parisc we need to flush the cache page as well. If we don't flush the cache page, stale lines will be left in the cache and cause random corruption. Once a PTE is cleared, there is no way to find the physical address associated with the PTE and flush the associated page at a later time.

I implemented an updated change with a parisc specific version of ptep_clear_flush. It fixed the random data corruption on Helge's rp4440 and rp3440, as well as on my c8000.

At this point, I realized that I could restore the code where we only flush in flush_cache_page_if_present if the page has been accessed. However, for this, we also need to flush the cache when the accessed bit is cleared in ---truncated---

Record
CVE-2024-40918
CVSS 3.1
7.8 HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Updated
2026-11-02
Show 12 moreShow less
OSVDEBIAN-CVE-2024-40918 6.3

In the Linux kernel, the following vulnerability has been resolved: parisc: Try to fix random segmentation faults in package builds PA-RISC systems with PA8800 and PA8900 processors have had problems with random segmentation faults for many years. Systems with earlier processors are much more stable. Systems with PA8800 and PA8900 processors have a large L2 cache which needs per page flushing for decent performance when a large range is flushed. The combined cache in these systems is also more sensitive to non-equivalent aliases than the caches in earlier systems. The majority of random segmentation faults that I have looked at appear to be memory corruption in memory allocated using mmap and malloc. My first attempt at fixing the random faults didn't work. On reviewing the cache code, I realized that there were two issues which the existing code didn't handle correctly. Both relate to cache move-in. Another issue is that the present bit in PTEs is racy. 1) PA-RISC caches have a mind of their own and they can speculatively load data and instructions for a page as long as there is a entry in the TLB for the page which allows move-in. TLBs are local to each CPU. Thus, the TLB entry for a page must be purged before flushing the page. This is particularly important on SMP systems. In some of the flush routines, the flush routine would be called and then the TLB entry would be purged. This was because the flush routine needed the TLB entry to do the flush. 2) My initial approach to trying the fix the random faults was to try and use flush_cache_page_if_present for all flush operations. This actually made things worse and led to a couple of hardware lockups. It finally dawned on me that some lines weren't being flushed because the pte check code was racy. This resulted in random inequivalent mappings to physical pages. The __flush_cache_page tmpalias flush sets up its own TLB entry and it doesn't need the existing TLB entry. As long as we can find the pte pointer for the vm page, we can get the pfn and physical address of the page. We can also purge the TLB entry for the page before doing the flush. Further, __flush_cache_page uses a special TLB entry that inhibits cache move-in. When switching page mappings, we need to ensure that lines are removed from the cache. It is not sufficient to just flush the lines to memory as they may come back. This made it clear that we needed to implement all the required flush operations using tmpalias routines. This includes flushes for user and kernel pages. After modifying the code to use tmpalias flushes, it became clear that the random segmentation faults were not fully resolved. The frequency of faults was worse on systems with a 64 MB L2 (PA8900) and systems with more CPUs (rp4440). The warning that I added to flush_cache_page_if_present to detect pages that couldn't be flushed triggered frequently on some systems. Helge and I looked at the pages that couldn't be flushed and found that the PTE was either cleared or for a swap page. Ignoring pages that were swapped out seemed okay but pages with cleared PTEs seemed problematic. I looked at routines related to pte_clear and noticed ptep_clear_flush. The default implementation just flushes the TLB entry. However, it was obvious that on parisc we need to flush the cache page as well. If we don't flush the cache page, stale lines will be left in the cache and cause random corruption. Once a PTE is cleared, there is no way to find the physical address associated with the PTE and flush the associated page at a later time. I implemented an updated change with a parisc specific version of ptep_clear_flush. It fixed the random data corruption on Helge's rp4440 and rp3440, as well as on my c8000. At this point, I realized that I could restore the code where we only flush in flush_cache_page_if_present if the page has been accessed. However, for this, we also need to flush the cache when the accessed bit is cleared in ---truncated---

Record
DEBIAN-CVE-2024-40918
CVSS 3.1
6.3 MediumCVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:H
Updated
2026-11-02
OSVOESA-2024-1897 9.8

kernel security update

The Linux Kernel, the operating system core itself.

Security Fix(es):

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

PCI: of_property: Return error for int_map allocation failure

Return -ENOMEM from of_pci_prop_intr_map() if kcalloc() fails to prevent a NULL pointer dereference in this case.

bhelgaas: commit log

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

drm/arm/malidp: fix a possible null pointer dereference

In malidp_mw_connector_reset, new memory is allocated with kzalloc, but no check is performed. In order to prevent null pointer dereferencing, ensure that mw_state is checked before calling __drm_atomic_helper_connector_reset.(CVE-2024-36014)

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

tty: n_gsm: fix possible out-of-bounds in gsm0_receive()

Assuming the following:

  • side A configures the n_gsm in basic option mode
  • side B sends the header of a basic option mode frame with data length 1
  • side A switches to advanced option mode
  • side B sends 2 data bytes which exceeds gsm->len Reason: gsm->len is not used in advanced option mode.
  • side A switches to basic option mode
  • side B keeps sending until gsm0_receive() writes past gsm->buf Reason: Neither gsm->state nor gsm->len have been reset after reconfiguration.

Fix this by changing gsm->count to gsm->len comparison from equal to less than. Also add upper limit checks against the constant MAX_MRU in gsm0_receive() and gsm1_receive() to harden against memory corruption of gsm->len and gsm->mru.

All other checks remain as we still need to limit the data according to the user configuration and actual payload size.(CVE-2024-36016)

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

keys: Fix overwrite of key expiration on instantiation

The expiry time of a key is unconditionally overwritten during instantiation, defaulting to turn it permanent. This causes a problem for DNS resolution as the expiration set by user-space is overwritten to TIME64_MAX, disabling further DNS updates. Fix this by restoring the condition that key_set_expiry is only called when the pre-parser sets a specific expiry.(CVE-2024-36031)

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

mm/userfaultfd: reset ptes when close() for wr-protected ones

Userfaultfd unregister includes a step to remove wr-protect bits from all the relevant pgtable entries, but that only covered an explicit UFFDIO_UNREGISTER ioctl, not a close() on the userfaultfd itself. Cover that too. This fixes a WARN trace.

The only user visible side effect is the user can observe leftover wr-protect bits even if the user close()ed on an userfaultfd when releasing the last reference of it. However hopefully that should be harmless, and nothing bad should happen even if so.

This change is now more important after the recent page-table-check patch we merged in mm-unstable (446dd9ad37d0 ("mm/page_table_check: support userfault wr-protect entries")), as we'll do sanity check on uffd-wp bits without vma context. So it's better if we can 100% guarantee no uffd-wp bit leftovers, to make sure each report will be valid.(CVE-2024-36881)

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

nfs: Handle error of rpc_proc_register() in nfs_net_init().

syzkaller reported a warning [0] triggered while destroying immature netns.

rpc_proc_register() was called in init_nfs_fs(), but its error has been ignored since at least the initial commit 1da177e4c3f4 ("Linux-2.6.12-rc2").

Recently, commit d47151b79e32 ("nfs: expose /proc/net/sunrpc/nfs in net namespaces") converted the procfs to per-netns and made the problem more visible.

Even when rpc_proc_register() fails, nfs_net_init() could succeed, and thus nfs_net_exit() will be called while destroying the netns.

Then,…

Record
OESA-2024-1897
CVSS 3.1
9.8 CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Updated
2026-11-02
OSVROOT-OS-DEBIAN-12-CVE-2024-40918 6.3

CVE-2024-40918 in linux - Patched by Root

Root has patched CVE-2024-40918 in the linux package for Root:Debian:12. Multiple fixed versions available.

Record
ROOT-OS-DEBIAN-12-CVE-2024-40918
CVSS 3.1
6.3 MediumCVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:H
Updated
2026-11-02
OSVROOT-OS-UBUNTU-2204-CVE-2024-40918 6.3

CVE-2024-40918 in linux - Patched by Root

Root has patched CVE-2024-40918 in the linux package for Root:Ubuntu:22.04. Multiple fixed versions available.

Record
ROOT-OS-UBUNTU-2204-CVE-2024-40918
CVSS 3.1
6.3 MediumCVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:H
Updated
2026-11-06
OSVUBUNTU-CVE-2024-40918 5.8

In the Linux kernel, the following vulnerability has been resolved: parisc: Try to fix random segmentation faults in package builds PA-RISC systems with PA8800 and PA8900 processors have had problems with random segmentation faults for many years. Systems with earlier processors are much more stable. Systems with PA8800 and PA8900 processors have a large L2 cache which needs per page flushing for decent performance when a large range is flushed. The combined cache in these systems is also more sensitive to non-equivalent aliases than the caches in earlier systems. The majority of random segmentation faults that I have looked at appear to be memory corruption in memory allocated using mmap and malloc. My first attempt at fixing the random faults didn't work. On reviewing the cache code, I realized that there were two issues which the existing code didn't handle correctly. Both relate to cache move-in. Another issue is that the present bit in PTEs is racy. 1) PA-RISC caches have a mind of their own and they can speculatively load data and instructions for a page as long as there is a entry in the TLB for the page which allows move-in. TLBs are local to each CPU. Thus, the TLB entry for a page must be purged before flushing the page. This is particularly important on SMP systems. In some of the flush routines, the flush routine would be called and then the TLB entry would be purged. This was because the flush routine needed the TLB entry to do the flush. 2) My initial approach to trying the fix the random faults was to try and use flush_cache_page_if_present for all flush operations. This actually made things worse and led to a couple of hardware lockups. It finally dawned on me that some lines weren't being flushed because the pte check code was racy. This resulted in random inequivalent mappings to physical pages. The __flush_cache_page tmpalias flush sets up its own TLB entry and it doesn't need the existing TLB entry. As long as we can find the pte pointer for the vm page, we can get the pfn and physical address of the page. We can also purge the TLB entry for the page before doing the flush. Further, __flush_cache_page uses a special TLB entry that inhibits cache move-in. When switching page mappings, we need to ensure that lines are removed from the cache. It is not sufficient to just flush the lines to memory as they may come back. This made it clear that we needed to implement all the required flush operations using tmpalias routines. This includes flushes for user and kernel pages. After modifying the code to use tmpalias flushes, it became clear that the random segmentation faults were not fully resolved. The frequency of faults was worse on systems with a 64 MB L2 (PA8900) and systems with more CPUs (rp4440). The warning that I added to flush_cache_page_if_present to detect pages that couldn't be flushed triggered frequently on some systems. Helge and I looked at the pages that couldn't be flushed and found that the PTE was either cleared or for a swap page. Ignoring pages that were swapped out seemed okay but pages with cleared PTEs seemed problematic. I looked at routines related to pte_clear and noticed ptep_clear_flush. The default implementation just flushes the TLB entry. However, it was obvious that on parisc we need to flush the cache page as well. If we don't flush the cache page, stale lines will be left in the cache and cause random corruption. Once a PTE is cleared, there is no way to find the physical address associated with the PTE and flush the associated page at a later time. I implemented an updated change with a parisc specific version of ptep_clear_flush. It fixed the random data corruption on Helge's rp4440 and rp3440, as well as on my c8000. At this point, I realized that I could restore the code where we only flush in flush_cache_page_if_present if the page has been accessed. However, for this, we also need to flush the cache when the accessed bit is cleared in ---truncated---

Record
UBUNTU-CVE-2024-40918
CVSS 4.0
5.8 MediumCVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:N/VC:N/VI:L/VA:H/SC:N/SI:N/SA:N
CVSS 3.1
6.3 MediumCVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:H
CVSS 3.1
7.8 HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Updated
2026-11-02
OSVUSN-6999-1 No score

linux, linux-aws, linux-gcp, linux-gke, linux-ibm, linux-lowlatency, linux-oem-6.8, linux-oracle vulnerabilities

Chenyuan Yang discovered that the CEC driver driver in the Linux kernel contained a use-after-free vulnerability. A local attacker could use this to cause a denial of service (system crash) or possibly execute arbitrary code. (CVE-2024-23848)

It was discovered that the JFS file system contained an out-of-bounds read vulnerability when printing xattr debug information. A local attacker could use this to cause a denial of service (system crash). (CVE-2024-40902)

Several security issues were discovered in the Linux kernel. An attacker could possibly use these to compromise the system. This update corrects flaws in the following subsystems:

  • ARM64 architecture;
  • MIPS architecture;
  • PA-RISC architecture;
  • PowerPC architecture;
  • RISC-V architecture;
  • x86 architecture;
  • Block layer subsystem;
  • ACPI drivers;
  • Drivers core;
  • Null block device driver;
  • Character device driver;
  • TPM device driver;
  • Clock framework and drivers;
  • CPU frequency scaling framework;
  • Hardware crypto device drivers;
  • CXL (Compute Express Link) drivers;
  • Buffer Sharing and Synchronization framework;
  • DMA engine subsystem;
  • EFI core;
  • FPGA Framework;
  • GPU drivers;
  • Greybus drivers;
  • HID subsystem;
  • HW tracing;
  • I2C subsystem;
  • IIO subsystem;
  • InfiniBand drivers;
  • Input Device (Mouse) drivers;
  • Mailbox framework;
  • Media drivers;
  • Microchip PCI driver;
  • VMware VMCI Driver;
  • Network drivers;
  • PCI subsystem;
  • x86 platform drivers;
  • PTP clock framework;
  • S/390 drivers;
  • SCSI drivers;
  • SoundWire subsystem;
  • Sonic Silicon Backplane drivers;
  • Greybus lights staging drivers;
  • Thermal drivers;
  • TTY drivers;
  • USB subsystem;
  • VFIO drivers;
  • Framebuffer layer;
  • Watchdog drivers;
  • 9P distributed file system;
  • BTRFS file system;
  • File systems infrastructure;
  • Ext4 file system;
  • F2FS file system;
  • JFS file system;
  • Network file system server daemon;
  • NILFS2 file system;
  • NTFS3 file system;
  • SMB network file system;
  • Tracing file system;
  • Tracing infrastructure;
  • io_uring subsystem;
  • Core kernel;
  • BPF subsystem;
  • Kernel debugger infrastructure;
  • DMA mapping infrastructure;
  • IRQ subsystem;
  • Memory management;
  • 9P file system network protocol;
  • Amateur Radio drivers;
  • B.A.T.M.A.N. meshing protocol;
  • Ethernet bridge;
  • Networking core;
  • Ethtool driver;
  • IPv4 networking;
  • IPv6 networking;
  • MAC80211 subsystem;
  • Multipath TCP;
  • Netfilter;
  • NET/ROM layer;
  • NFC subsystem;
  • Network traffic control;
  • Sun RPC protocol;
  • TIPC protocol;
  • TLS protocol;
  • Unix domain sockets;
  • Wireless networking;
  • XFRM subsystem;
  • AppArmor security module;
  • Integrity Measurement Architecture(IMA) framework;
  • Landlock security;
  • Linux Security Modules (LSM) Framework;
  • SELinux security module;
  • Simplified Mandatory Access Control Kernel framework;
  • ALSA framework;
  • HD-audio driver;
  • SOF drivers;
  • KVM core; (CVE-2024-40911, CVE-2024-37356, CVE-2024-40935, CVE-2024-40944, CVE-2024-41003, CVE-2024-40990, CVE-2024-40952, CVE-2024-40940, CVE-2024-40930, CVE-2024-40985, CVE-2024-40941, CVE-2024-38630, CVE-2024-39466, CVE-2024-40933, CVE-2024-38624, CVE-2024-40924, CVE-2024-40945, CVE-2024-40899, CVE-2024-38622, CVE-2024-40979, CVE-2024-36484, CVE-2024-41004, CVE-2024-39474, CVE-2022-48772, CVE-2024-36244, CVE-2024-38664, CVE-2024-40925, CVE-2024-40980, CVE-2024-39480, CVE-2024-36270, CVE-2024-40936, CVE-2024-40904, CVE-2024-38635, CVE-2024-40927, CVE-2024-36481, CVE-2024-40929, CVE-2024-40958, CVE-2024-36978, CVE-2024-40992, CVE-2024-40908, CVE-2024-39504, CVE-2024-41001, CVE-2024-40967, CVE-2023-52884, CVE-2024-40997, CVE-2024-40903, CVE-2024-40913, CVE-2024-34030, CVE-2024-39473, CVE-2024-40966, CVE-2024-40951, CVE-2024-40902, CVE-2024-40982, CVE-2024-40923, CVE-2024-39467, CVE-2024-40910, CVE-2024-40909, CVE-2024-39463,…
Record
USN-6999-1
Updated
2026-11-02
OSVUSN-6999-2 No score

linux-raspi vulnerabilities

Chenyuan Yang discovered that the CEC driver driver in the Linux kernel contained a use-after-free vulnerability. A local attacker could use this to cause a denial of service (system crash) or possibly execute arbitrary code. (CVE-2024-23848)

It was discovered that the JFS file system contained an out-of-bounds read vulnerability when printing xattr debug information. A local attacker could use this to cause a denial of service (system crash). (CVE-2024-40902)

Several security issues were discovered in the Linux kernel. An attacker could possibly use these to compromise the system. This update corrects flaws in the following subsystems:

  • ARM64 architecture;
  • MIPS architecture;
  • PA-RISC architecture;
  • PowerPC architecture;
  • RISC-V architecture;
  • x86 architecture;
  • Block layer subsystem;
  • ACPI drivers;
  • Drivers core;
  • Null block device driver;
  • Character device driver;
  • TPM device driver;
  • Clock framework and drivers;
  • CPU frequency scaling framework;
  • Hardware crypto device drivers;
  • CXL (Compute Express Link) drivers;
  • Buffer Sharing and Synchronization framework;
  • DMA engine subsystem;
  • EFI core;
  • FPGA Framework;
  • GPU drivers;
  • Greybus drivers;
  • HID subsystem;
  • HW tracing;
  • I2C subsystem;
  • IIO subsystem;
  • InfiniBand drivers;
  • Input Device (Mouse) drivers;
  • Mailbox framework;
  • Media drivers;
  • Microchip PCI driver;
  • VMware VMCI Driver;
  • Network drivers;
  • PCI subsystem;
  • x86 platform drivers;
  • PTP clock framework;
  • S/390 drivers;
  • SCSI drivers;
  • SoundWire subsystem;
  • Sonic Silicon Backplane drivers;
  • Greybus lights staging drivers;
  • Thermal drivers;
  • TTY drivers;
  • USB subsystem;
  • VFIO drivers;
  • Framebuffer layer;
  • Watchdog drivers;
  • 9P distributed file system;
  • BTRFS file system;
  • File systems infrastructure;
  • Ext4 file system;
  • F2FS file system;
  • JFS file system;
  • Network file system server daemon;
  • NILFS2 file system;
  • NTFS3 file system;
  • SMB network file system;
  • Tracing file system;
  • IOMMU subsystem;
  • Tracing infrastructure;
  • io_uring subsystem;
  • Core kernel;
  • BPF subsystem;
  • Kernel debugger infrastructure;
  • DMA mapping infrastructure;
  • IRQ subsystem;
  • Memory management;
  • 9P file system network protocol;
  • Amateur Radio drivers;
  • B.A.T.M.A.N. meshing protocol;
  • Ethernet bridge;
  • Networking core;
  • Ethtool driver;
  • IPv4 networking;
  • IPv6 networking;
  • MAC80211 subsystem;
  • Multipath TCP;
  • Netfilter;
  • NET/ROM layer;
  • NFC subsystem;
  • Network traffic control;
  • Sun RPC protocol;
  • TIPC protocol;
  • TLS protocol;
  • Unix domain sockets;
  • Wireless networking;
  • XFRM subsystem;
  • AppArmor security module;
  • Integrity Measurement Architecture(IMA) framework;
  • Landlock security;
  • Linux Security Modules (LSM) Framework;
  • SELinux security module;
  • Simplified Mandatory Access Control Kernel framework;
  • ALSA framework;
  • HD-audio driver;
  • SOF drivers;
  • KVM core; (CVE-2024-40978, CVE-2024-39504, CVE-2024-39483, CVE-2024-36478, CVE-2024-40928, CVE-2024-36971, CVE-2024-40947, CVE-2024-31076, CVE-2024-40934, CVE-2024-40909, CVE-2024-40962, CVE-2024-38635, CVE-2024-38632, CVE-2024-40912, CVE-2024-40967, CVE-2024-39492, CVE-2024-40974, CVE-2024-39466, CVE-2024-40939, CVE-2024-40988, CVE-2024-40951, CVE-2024-41005, CVE-2024-40968, CVE-2024-39493, CVE-2024-40949, CVE-2022-48772, CVE-2024-40944, CVE-2024-40998, CVE-2024-39490, CVE-2024-39467, CVE-2024-42078, CVE-2024-40953, CVE-2024-40990, CVE-2024-40902, CVE-2024-39461, CVE-2024-39301, CVE-2024-36978, CVE-2024-39475, CVE-2024-39496, CVE-2024-40901, CVE-2024-40985, CVE-2024-33621, CVE-2024-38663, CVE-2024-39497, CVE-2024-40937, CVE-2024-40941, CVE-2024-40987, CVE-2024-40918, CVE-2024-32936, CVE-2024-40999, CVE-2024-40938, CVE-2024-39488, CVE-2024-39510, CVE-2024-40924, CVE-2024-38661, CVE-2024-40989, CVE-2024-39509,…
Record
USN-6999-2
Updated
2026-11-02
OSVUSN-7004-1 No score

linux-azure vulnerabilities

Chenyuan Yang discovered that the CEC driver driver in the Linux kernel contained a use-after-free vulnerability. A local attacker could use this to cause a denial of service (system crash) or possibly execute arbitrary code. (CVE-2024-23848)

It was discovered that the JFS file system contained an out-of-bounds read vulnerability when printing xattr debug information. A local attacker could use this to cause a denial of service (system crash). (CVE-2024-40902)

Several security issues were discovered in the Linux kernel. An attacker could possibly use these to compromise the system. This update corrects flaws in the following subsystems:

  • ARM64 architecture;
  • MIPS architecture;
  • PA-RISC architecture;
  • PowerPC architecture;
  • RISC-V architecture;
  • x86 architecture;
  • Block layer subsystem;
  • ACPI drivers;
  • Drivers core;
  • Null block device driver;
  • Character device driver;
  • TPM device driver;
  • Clock framework and drivers;
  • CPU frequency scaling framework;
  • Hardware crypto device drivers;
  • CXL (Compute Express Link) drivers;
  • Buffer Sharing and Synchronization framework;
  • DMA engine subsystem;
  • EFI core;
  • FPGA Framework;
  • GPU drivers;
  • Greybus drivers;
  • HID subsystem;
  • HW tracing;
  • I2C subsystem;
  • IIO subsystem;
  • InfiniBand drivers;
  • Input Device (Mouse) drivers;
  • Mailbox framework;
  • Media drivers;
  • Microchip PCI driver;
  • VMware VMCI Driver;
  • Network drivers;
  • PCI subsystem;
  • x86 platform drivers;
  • PTP clock framework;
  • S/390 drivers;
  • SCSI drivers;
  • SoundWire subsystem;
  • Sonic Silicon Backplane drivers;
  • Greybus lights staging drivers;
  • Thermal drivers;
  • TTY drivers;
  • USB subsystem;
  • VFIO drivers;
  • Framebuffer layer;
  • Watchdog drivers;
  • 9P distributed file system;
  • BTRFS file system;
  • File systems infrastructure;
  • Ext4 file system;
  • F2FS file system;
  • JFS file system;
  • Network file system server daemon;
  • NILFS2 file system;
  • NTFS3 file system;
  • SMB network file system;
  • Tracing file system;
  • IOMMU subsystem;
  • Tracing infrastructure;
  • io_uring subsystem;
  • Core kernel;
  • BPF subsystem;
  • Kernel debugger infrastructure;
  • DMA mapping infrastructure;
  • IRQ subsystem;
  • Memory management;
  • 9P file system network protocol;
  • Amateur Radio drivers;
  • B.A.T.M.A.N. meshing protocol;
  • Ethernet bridge;
  • Networking core;
  • Ethtool driver;
  • IPv4 networking;
  • IPv6 networking;
  • MAC80211 subsystem;
  • Multipath TCP;
  • Netfilter;
  • NET/ROM layer;
  • NFC subsystem;
  • Network traffic control;
  • Sun RPC protocol;
  • TIPC protocol;
  • TLS protocol;
  • Unix domain sockets;
  • Wireless networking;
  • XFRM subsystem;
  • AppArmor security module;
  • Integrity Measurement Architecture(IMA) framework;
  • Landlock security;
  • Linux Security Modules (LSM) Framework;
  • SELinux security module;
  • Simplified Mandatory Access Control Kernel framework;
  • ALSA framework;
  • HD-audio driver;
  • SOF drivers;
  • KVM core; (CVE-2024-36270, CVE-2024-38627, CVE-2024-39508, CVE-2024-41001, CVE-2024-38634, CVE-2024-40979, CVE-2024-40903, CVE-2024-34030, CVE-2024-38621, CVE-2024-34027, CVE-2024-39504, CVE-2024-38385, CVE-2024-36288, CVE-2024-39301, CVE-2024-38628, CVE-2024-42270, CVE-2024-39507, CVE-2024-36286, CVE-2024-40960, CVE-2024-36479, CVE-2024-41002, CVE-2024-36974, CVE-2024-40943, CVE-2024-40976, CVE-2024-38662, CVE-2024-40995, CVE-2024-39497, CVE-2024-31076, CVE-2024-39371, CVE-2024-40983, CVE-2024-40985, CVE-2024-38618, CVE-2024-40914, CVE-2024-40989, CVE-2024-40973, CVE-2024-38663, CVE-2024-39463, CVE-2024-38633, CVE-2024-36978, CVE-2024-40970, CVE-2024-40932, CVE-2024-39480, CVE-2024-39471, CVE-2024-40962, CVE-2024-40986, CVE-2024-40937, CVE-2024-39469, CVE-2024-40904, CVE-2024-39466, CVE-2024-38388, CVE-2024-39494, CVE-2024-41004, CVE-2024-38381, CVE-2022-48772, CVE-2024-33847, CVE-2024-40969, CVE-2024-40957,…
Record
USN-7004-1
Updated
2026-11-02
OSVUSN-7005-1 No score

linux-nvidia, linux-nvidia-lowlatency vulnerabilities

Chenyuan Yang discovered that the CEC driver driver in the Linux kernel contained a use-after-free vulnerability. A local attacker could use this to cause a denial of service (system crash) or possibly execute arbitrary code. (CVE-2024-23848)

It was discovered that the JFS file system contained an out-of-bounds read vulnerability when printing xattr debug information. A local attacker could use this to cause a denial of service (system crash). (CVE-2024-40902)

Several security issues were discovered in the Linux kernel. An attacker could possibly use these to compromise the system. This update corrects flaws in the following subsystems:

  • ARM64 architecture;
  • MIPS architecture;
  • PA-RISC architecture;
  • PowerPC architecture;
  • RISC-V architecture;
  • x86 architecture;
  • Block layer subsystem;
  • ACPI drivers;
  • Drivers core;
  • Null block device driver;
  • Character device driver;
  • Clock framework and drivers;
  • CPU frequency scaling framework;
  • Hardware crypto device drivers;
  • CXL (Compute Express Link) drivers;
  • Buffer Sharing and Synchronization framework;
  • DMA engine subsystem;
  • EFI core;
  • FPGA Framework;
  • GPU drivers;
  • Greybus drivers;
  • HID subsystem;
  • HW tracing;
  • I2C subsystem;
  • IIO subsystem;
  • InfiniBand drivers;
  • Input Device (Mouse) drivers;
  • Mailbox framework;
  • Media drivers;
  • Microchip PCI driver;
  • VMware VMCI Driver;
  • Network drivers;
  • PCI subsystem;
  • x86 platform drivers;
  • PTP clock framework;
  • S/390 drivers;
  • SCSI drivers;
  • SoundWire subsystem;
  • Sonic Silicon Backplane drivers;
  • Greybus lights staging drivers;
  • Thermal drivers;
  • TTY drivers;
  • USB subsystem;
  • VFIO drivers;
  • Framebuffer layer;
  • Watchdog drivers;
  • 9P distributed file system;
  • BTRFS file system;
  • File systems infrastructure;
  • Ext4 file system;
  • F2FS file system;
  • JFS file system;
  • Network file system server daemon;
  • NILFS2 file system;
  • NTFS3 file system;
  • SMB network file system;
  • Tracing file system;
  • IOMMU subsystem;
  • Tracing infrastructure;
  • io_uring subsystem;
  • Core kernel;
  • BPF subsystem;
  • Kernel debugger infrastructure;
  • DMA mapping infrastructure;
  • IRQ subsystem;
  • Memory management;
  • 9P file system network protocol;
  • Amateur Radio drivers;
  • B.A.T.M.A.N. meshing protocol;
  • Ethernet bridge;
  • Networking core;
  • Ethtool driver;
  • IPv4 networking;
  • IPv6 networking;
  • MAC80211 subsystem;
  • Multipath TCP;
  • Netfilter;
  • NET/ROM layer;
  • NFC subsystem;
  • Network traffic control;
  • Sun RPC protocol;
  • TIPC protocol;
  • TLS protocol;
  • Unix domain sockets;
  • Wireless networking;
  • XFRM subsystem;
  • AppArmor security module;
  • Integrity Measurement Architecture(IMA) framework;
  • Landlock security;
  • Linux Security Modules (LSM) Framework;
  • SELinux security module;
  • Simplified Mandatory Access Control Kernel framework;
  • ALSA framework;
  • HD-audio driver;
  • SOF drivers;
  • KVM core; (CVE-2024-40963, CVE-2024-40994, CVE-2024-36481, CVE-2024-39301, CVE-2024-38390, CVE-2024-40976, CVE-2024-40934, CVE-2024-40902, CVE-2024-40916, CVE-2024-39298, CVE-2024-38659, CVE-2024-38384, CVE-2024-38635, CVE-2024-39494, CVE-2024-40926, CVE-2024-40956, CVE-2024-40948, CVE-2024-40920, CVE-2024-38624, CVE-2024-39498, CVE-2024-38780, CVE-2024-39503, CVE-2024-40919, CVE-2024-39505, CVE-2024-40988, CVE-2024-36972, CVE-2024-36974, CVE-2024-39495, CVE-2024-40992, CVE-2024-36015, CVE-2024-38618, CVE-2024-39478, CVE-2024-40975, CVE-2024-39507, CVE-2024-39479, CVE-2024-39291, CVE-2024-40925, CVE-2024-39493, CVE-2024-41005, CVE-2024-40932, CVE-2024-39467, CVE-2024-40973, CVE-2024-38634, CVE-2024-34027, CVE-2024-39462, CVE-2024-40949, CVE-2024-40908, CVE-2024-40929, CVE-2024-38662, CVE-2024-39489, CVE-2024-40953, CVE-2024-38306, CVE-2024-40915, CVE-2024-39470, CVE-2024-40969, CVE-2024-31076, CVE-2024-38663, CVE-2024-38629,…
Record
USN-7005-1
Updated
2026-11-02
OSVUSN-7005-2 No score

linux-nvidia-6.8 vulnerabilities

Chenyuan Yang discovered that the CEC driver driver in the Linux kernel contained a use-after-free vulnerability. A local attacker could use this to cause a denial of service (system crash) or possibly execute arbitrary code. (CVE-2024-23848)

It was discovered that the JFS file system contained an out-of-bounds read vulnerability when printing xattr debug information. A local attacker could use this to cause a denial of service (system crash). (CVE-2024-40902)

Several security issues were discovered in the Linux kernel. An attacker could possibly use these to compromise the system. This update corrects flaws in the following subsystems:

  • ARM64 architecture;
  • MIPS architecture;
  • PA-RISC architecture;
  • PowerPC architecture;
  • RISC-V architecture;
  • x86 architecture;
  • Block layer subsystem;
  • ACPI drivers;
  • Drivers core;
  • Null block device driver;
  • Character device driver;
  • Clock framework and drivers;
  • CPU frequency scaling framework;
  • Hardware crypto device drivers;
  • CXL (Compute Express Link) drivers;
  • Buffer Sharing and Synchronization framework;
  • DMA engine subsystem;
  • EFI core;
  • FPGA Framework;
  • GPU drivers;
  • Greybus drivers;
  • HID subsystem;
  • HW tracing;
  • I2C subsystem;
  • IIO subsystem;
  • InfiniBand drivers;
  • Input Device (Mouse) drivers;
  • Mailbox framework;
  • Media drivers;
  • Microchip PCI driver;
  • VMware VMCI Driver;
  • Network drivers;
  • PCI subsystem;
  • x86 platform drivers;
  • PTP clock framework;
  • S/390 drivers;
  • SCSI drivers;
  • SoundWire subsystem;
  • Sonic Silicon Backplane drivers;
  • Greybus lights staging drivers;
  • Thermal drivers;
  • TTY drivers;
  • USB subsystem;
  • VFIO drivers;
  • Framebuffer layer;
  • Watchdog drivers;
  • 9P distributed file system;
  • BTRFS file system;
  • File systems infrastructure;
  • Ext4 file system;
  • F2FS file system;
  • JFS file system;
  • Network file system server daemon;
  • NILFS2 file system;
  • NTFS3 file system;
  • SMB network file system;
  • Tracing file system;
  • IOMMU subsystem;
  • Tracing infrastructure;
  • io_uring subsystem;
  • Core kernel;
  • BPF subsystem;
  • Kernel debugger infrastructure;
  • DMA mapping infrastructure;
  • IRQ subsystem;
  • Memory management;
  • 9P file system network protocol;
  • Amateur Radio drivers;
  • B.A.T.M.A.N. meshing protocol;
  • Ethernet bridge;
  • Networking core;
  • Ethtool driver;
  • IPv4 networking;
  • IPv6 networking;
  • MAC80211 subsystem;
  • Multipath TCP;
  • Netfilter;
  • NET/ROM layer;
  • NFC subsystem;
  • Network traffic control;
  • Sun RPC protocol;
  • TIPC protocol;
  • TLS protocol;
  • Unix domain sockets;
  • Wireless networking;
  • XFRM subsystem;
  • AppArmor security module;
  • Integrity Measurement Architecture(IMA) framework;
  • Landlock security;
  • Linux Security Modules (LSM) Framework;
  • SELinux security module;
  • Simplified Mandatory Access Control Kernel framework;
  • ALSA framework;
  • HD-audio driver;
  • SOF drivers;
  • KVM core; (CVE-2024-39465, CVE-2024-39492, CVE-2024-40976, CVE-2024-40956, CVE-2024-39480, CVE-2024-39467, CVE-2024-39478, CVE-2024-39489, CVE-2024-41003, CVE-2024-39510, CVE-2024-39498, CVE-2024-40994, CVE-2024-40937, CVE-2024-39488, CVE-2024-40990, CVE-2024-40955, CVE-2024-40905, CVE-2024-39496, CVE-2024-36478, CVE-2024-40920, CVE-2024-40954, CVE-2024-32936, CVE-2024-40919, CVE-2024-40947, CVE-2024-40975, CVE-2024-39481, CVE-2024-40983, CVE-2024-39276, CVE-2024-37026, CVE-2024-40980, CVE-2022-48772, CVE-2024-39470, CVE-2024-40951, CVE-2024-40927, CVE-2024-38635, CVE-2024-40974, CVE-2024-39468, CVE-2024-38384, CVE-2024-37354, CVE-2024-40992, CVE-2024-40934, CVE-2024-40925, CVE-2024-40935, CVE-2024-39473, CVE-2024-40910, CVE-2024-40979, CVE-2024-39501, CVE-2024-38628, CVE-2024-39298, CVE-2024-40909, CVE-2024-38629, CVE-2024-41000, CVE-2024-40989, CVE-2024-40924, CVE-2024-40943, CVE-2024-41006, CVE-2024-38621, CVE-2024-39462,…
Record
USN-7005-2
Updated
2026-11-02
OSVUSN-7008-1 No score

linux-lowlatency-hwe-6.8 vulnerabilities

Chenyuan Yang discovered that the CEC driver driver in the Linux kernel contained a use-after-free vulnerability. A local attacker could use this to cause a denial of service (system crash) or possibly execute arbitrary code. (CVE-2024-23848)

It was discovered that the JFS file system contained an out-of-bounds read vulnerability when printing xattr debug information. A local attacker could use this to cause a denial of service (system crash). (CVE-2024-40902)

Several security issues were discovered in the Linux kernel. An attacker could possibly use these to compromise the system. This update corrects flaws in the following subsystems:

  • ARM64 architecture;
  • MIPS architecture;
  • PA-RISC architecture;
  • PowerPC architecture;
  • RISC-V architecture;
  • User-Mode Linux (UML);
  • x86 architecture;
  • Block layer subsystem;
  • ACPI drivers;
  • Drivers core;
  • Null block device driver;
  • Character device driver;
  • TPM device driver;
  • Clock framework and drivers;
  • CPU frequency scaling framework;
  • Hardware crypto device drivers;
  • CXL (Compute Express Link) drivers;
  • Buffer Sharing and Synchronization framework;
  • DMA engine subsystem;
  • EFI core;
  • FPGA Framework;
  • GPU drivers;
  • Greybus drivers;
  • HID subsystem;
  • HW tracing;
  • I2C subsystem;
  • IIO subsystem;
  • InfiniBand drivers;
  • Input Device (Mouse) drivers;
  • Mailbox framework;
  • Media drivers;
  • Microchip PCI driver;
  • VMware VMCI Driver;
  • MMC subsystem;
  • Network drivers;
  • PCI subsystem;
  • x86 platform drivers;
  • PTP clock framework;
  • S/390 drivers;
  • SCSI drivers;
  • SoundWire subsystem;
  • Sonic Silicon Backplane drivers;
  • Greybus lights staging drivers;
  • Thermal drivers;
  • TTY drivers;
  • USB subsystem;
  • VFIO drivers;
  • Framebuffer layer;
  • Watchdog drivers;
  • 9P distributed file system;
  • BTRFS file system;
  • File systems infrastructure;
  • Ext4 file system;
  • F2FS file system;
  • JFS file system;
  • Network file system server daemon;
  • NILFS2 file system;
  • NTFS3 file system;
  • SMB network file system;
  • Tracing file system;
  • IOMMU subsystem;
  • Tracing infrastructure;
  • io_uring subsystem;
  • Core kernel;
  • BPF subsystem;
  • Kernel debugger infrastructure;
  • DMA mapping infrastructure;
  • IRQ subsystem;
  • Memory management;
  • 9P file system network protocol;
  • Amateur Radio drivers;
  • B.A.T.M.A.N. meshing protocol;
  • Ethernet bridge;
  • Networking core;
  • Ethtool driver;
  • IPv4 networking;
  • IPv6 networking;
  • MAC80211 subsystem;
  • Multipath TCP;
  • Netfilter;
  • NET/ROM layer;
  • NFC subsystem;
  • Network traffic control;
  • Sun RPC protocol;
  • TIPC protocol;
  • TLS protocol;
  • Unix domain sockets;
  • Wireless networking;
  • XFRM subsystem;
  • AppArmor security module;
  • Integrity Measurement Architecture(IMA) framework;
  • Landlock security;
  • Linux Security Modules (LSM) Framework;
  • SELinux security module;
  • Simplified Mandatory Access Control Kernel framework;
  • ALSA framework;
  • HD-audio driver;
  • SOF drivers;
  • KVM core; (CVE-2024-38623, CVE-2024-38662, CVE-2024-39484, CVE-2024-42148, CVE-2024-39493, CVE-2024-38637, CVE-2024-40962, CVE-2024-36281, CVE-2024-40922, CVE-2024-40958, CVE-2024-40920, CVE-2024-40986, CVE-2024-40929, CVE-2024-40967, CVE-2024-39296, CVE-2024-40900, CVE-2024-40995, CVE-2024-40974, CVE-2024-40942, CVE-2024-39464, CVE-2024-40916, CVE-2024-40952, CVE-2024-40997, CVE-2024-41004, CVE-2024-40970, CVE-2024-40911, CVE-2024-40972, CVE-2024-36477, CVE-2024-40996, CVE-2024-40988, CVE-2024-38619, CVE-2024-40998, CVE-2024-38627, CVE-2024-36971, CVE-2024-37021, CVE-2024-40989, CVE-2024-40947, CVE-2024-40957, CVE-2024-39508, CVE-2024-41005, CVE-2024-40931, CVE-2024-34777, CVE-2024-38633, CVE-2024-38663, CVE-2024-36288, CVE-2024-40955, CVE-2024-40973, CVE-2024-39483, CVE-2024-38388, CVE-2024-40976, CVE-2024-38622, CVE-2024-40915, CVE-2024-38661, CVE-2024-38306,…
Record
USN-7008-1
Updated
2026-11-02
OSVUSN-7029-1 No score

linux-hwe-6.8

Chenyuan Yang discovered that the CEC driver driver in the Linux kernel contained a use-after-free vulnerability. A local attacker could use this to cause a denial of service (system crash) or possibly execute arbitrary code. (CVE-2024-23848)

It was discovered that the JFS file system contained an out-of-bounds read vulnerability when printing xattr debug information. A local attacker could use this to cause a denial of service (system crash). (CVE-2024-40902)

Several security issues were discovered in the Linux kernel. An attacker could possibly use these to compromise the system. This update corrects flaws in the following subsystems:

  • ARM64 architecture;
  • MIPS architecture;
  • PA-RISC architecture;
  • PowerPC architecture;
  • RISC-V architecture;
  • User-Mode Linux (UML);
  • x86 architecture;
  • Block layer subsystem;
  • ACPI drivers;
  • Drivers core;
  • Null block device driver;
  • Character device driver;
  • TPM device driver;
  • Clock framework and drivers;
  • CPU frequency scaling framework;
  • Hardware crypto device drivers;
  • CXL (Compute Express Link) drivers;
  • Buffer Sharing and Synchronization framework;
  • DMA engine subsystem;
  • EFI core;
  • FPGA Framework;
  • GPU drivers;
  • Greybus drivers;
  • HID subsystem;
  • HW tracing;
  • I2C subsystem;
  • IIO subsystem;
  • InfiniBand drivers;
  • Input Device (Mouse) drivers;
  • Mailbox framework;
  • Media drivers;
  • Microchip PCI driver;
  • VMware VMCI Driver;
  • MMC subsystem;
  • Network drivers;
  • PCI subsystem;
  • x86 platform drivers;
  • PTP clock framework;
  • S/390 drivers;
  • SCSI drivers;
  • SoundWire subsystem;
  • Sonic Silicon Backplane drivers;
  • Greybus lights staging drivers;
  • Thermal drivers;
  • TTY drivers;
  • USB subsystem;
  • VFIO drivers;
  • Framebuffer layer;
  • Watchdog drivers;
  • 9P distributed file system;
  • BTRFS file system;
  • File systems infrastructure;
  • Ext4 file system;
  • F2FS file system;
  • JFS file system;
  • Network file system server daemon;
  • NILFS2 file system;
  • NTFS3 file system;
  • SMB network file system;
  • Tracing file system;
  • IOMMU subsystem;
  • Tracing infrastructure;
  • io_uring subsystem;
  • Core kernel;
  • BPF subsystem;
  • Kernel debugger infrastructure;
  • DMA mapping infrastructure;
  • IRQ subsystem;
  • Memory management;
  • 9P file system network protocol;
  • Amateur Radio drivers;
  • B.A.T.M.A.N. meshing protocol;
  • Ethernet bridge;
  • Networking core;
  • Ethtool driver;
  • IPv4 networking;
  • IPv6 networking;
  • MAC80211 subsystem;
  • Multipath TCP;
  • Netfilter;
  • NET/ROM layer;
  • NFC subsystem;
  • Network traffic control;
  • Sun RPC protocol;
  • TIPC protocol;
  • TLS protocol;
  • Unix domain sockets;
  • Wireless networking;
  • XFRM subsystem;
  • AppArmor security module;
  • Integrity Measurement Architecture(IMA) framework;
  • Landlock security;
  • Linux Security Modules (LSM) Framework;
  • SELinux security module;
  • Simplified Mandatory Access Control Kernel framework;
  • ALSA framework;
  • HD-audio driver;
  • SOF drivers;
  • KVM core; (CVE-2024-39498, CVE-2024-33847, CVE-2024-39510, CVE-2024-39462, CVE-2024-40930, CVE-2024-38634, CVE-2024-40962, CVE-2024-37078, CVE-2024-39371, CVE-2024-40972, CVE-2024-41002, CVE-2024-40920, CVE-2024-40982, CVE-2024-40915, CVE-2024-40942, CVE-2024-42154, CVE-2024-40937, CVE-2024-40967, CVE-2024-40909, CVE-2024-36244, CVE-2024-33619, CVE-2024-39277, CVE-2024-40900, CVE-2024-38661, CVE-2024-40974, CVE-2024-38618, CVE-2024-32936, CVE-2024-40906, CVE-2024-40919, CVE-2024-39470, CVE-2024-38390, CVE-2024-40966, CVE-2024-39467, CVE-2024-40938, CVE-2024-39471, CVE-2024-39485, CVE-2024-39495, CVE-2024-39492, CVE-2024-39475, CVE-2024-40953, CVE-2024-40939, CVE-2024-39493, CVE-2024-38637, CVE-2024-40945, CVE-2024-41006, CVE-2024-39461, CVE-2024-40948, CVE-2024-40916, CVE-2024-40925, CVE-2024-40956, CVE-2024-40970, CVE-2024-40912, CVE-2024-33621, CVE-2024-40989,…
Record
USN-7029-1
Updated
2026-11-02

Affected products

Affected packages

Affected packages
PackageAffectedFixed
linux-lts
Alpaquita:23
 6.1.134-r0 and later None known
linux-lts
Alpaquita:25
 6.6.89-r0 up to 6.12.41-r0
6.12.41-r0
linux-lts
Alpaquita:stream
 6.6.100-r0 up to 6.12.41-r0
6.12.41-r0
Kernel
Linux
 5.18.0 up to 6.6.35, 6.7.0 up to 6.9.6
6.6.356.9.6
linux
Debian:12
 All versions, plus listed versions
6.1.106-16.1.106-26.1.106-36.1.112-16.1.115-1
Show 45 moreShow less
6.1.119-16.1.123-16.1.124-16.1.128-16.1.129-16.1.133-16.1.135-16.1.137-16.1.139-16.1.140-16.1.147-16.1.148-16.1.153-16.1.158-16.1.159-16.1.162-16.1.164-16.1.170-16.1.170-26.1.170-36.1.172-16.1.174-16.1.176-16.1.177-16.1.180-16.1.187-16.1.190-16.1.27-16.1.37-16.1.38-16.1.38-26.1.38-2~bpo11+16.1.38-36.1.38-46.1.38-4~bpo11+16.1.52-16.1.55-16.1.55-1~bpo11+16.1.64-16.1.66-16.1.67-16.1.69-16.1.69-1~bpo11+16.1.76-16.1.76-1~bpo11+1
 None known
linux
Debian:13
 before 6.9.7-1
6.9.7-1
linux
Debian:14
 before 6.9.7-1
6.9.7-1
kernel
openEuler:24.03-LTS
From an advisory covering 42 CVEs
 before 6.6.0-35.0.0.43.oe2403
6.6.0-35.0.0.43.oe2403
linux
Root:Debian:12
 before 6.1.190-1.aikido.167
6.1.190-1.aikido.167
rootio-linux
Root:Debian:12
 before 6.1.190-1.aikido.167
6.1.190-1.aikido.167
Show 121 moreShow less
Affected packages
PackageAffectedFixed
linux
Root:Ubuntu:22.04
 before 5.15.0-203.213.aikido.119
5.15.0-203.213.aikido.119
rootio-linux
Root:Ubuntu:22.04
 before 5.15.0-203.213.aikido.119
5.15.0-203.213.aikido.119
linux-hwe-edge
Ubuntu:16.04:LTS
 All versions, plus listed versions
4.8.0-28.30~16.04.14.8.0-30.32~16.04.14.8.0-32.34~16.04.14.8.0-34.36~16.04.14.10.0-14.16~16.04.1
Show 18 moreShow less
4.10.0-19.21~16.04.14.10.0-20.22~16.04.14.10.0-21.23~16.04.14.10.0-22.24~16.04.14.10.0-24.28~16.04.14.10.0-26.30~16.04.14.11.0-13.19~16.04.14.11.0-14.20~16.04.14.13.0-16.19~16.04.34.13.0-17.20~16.04.14.13.0-19.22~16.04.14.13.0-21.24~16.04.14.13.0-25.29~16.04.24.15.0-13.14~16.04.14.15.0-15.16~16.04.14.15.0-20.21~16.04.14.15.0-22.24~16.04.14.15.0-23.25~16.04.1
 None known
linux-aws-5.0
Ubuntu:18.04:LTS
 All versions, plus listed versions
5.0.0-1021.24~18.04.15.0.0-1022.25~18.04.15.0.0-1023.26~18.04.15.0.0-1024.27~18.04.15.0.0-1025.285.0.0-1027.30
 None known
linux-aws-5.3
Ubuntu:18.04:LTS
 All versions, plus listed versions
5.3.0-1016.17~18.04.15.3.0-1017.18~18.04.15.3.0-1019.21~18.04.15.3.0-1023.25~18.04.15.3.0-1028.30~18.04.1
Show 5 moreShow less
5.3.0-1030.32~18.04.15.3.0-1032.34~18.04.25.3.0-1033.355.3.0-1034.365.3.0-1035.37
 None known
linux-azure
Ubuntu:18.04:LTS
 All versions, plus listed versions
4.15.0-1002.24.15.0-1003.34.15.0-1004.44.15.0-1008.84.15.0-1009.9
Show 39 moreShow less
4.15.0-1012.124.15.0-1013.134.15.0-1014.144.15.0-1018.184.15.0-1019.194.15.0-1021.214.15.0-1022.234.15.0-1023.244.15.0-1025.264.15.0-1028.294.15.0-1030.314.15.0-1031.324.15.0-1032.334.15.0-1035.364.15.0-1036.384.15.0-1037.394.18.0-1011.11~18.04.14.18.0-1013.13~18.04.14.18.0-1014.14~18.04.14.18.0-1018.18~18.04.14.18.0-1019.19~18.04.14.18.0-1020.20~18.04.14.18.0-1023.24~18.04.14.18.0-1024.25~18.04.14.18.0-1025.27~18.04.15.0.0-1014.14~18.04.15.0.0-1016.17~18.04.15.0.0-1018.19~18.04.15.0.0-1020.21~18.04.15.0.0-1022.23~18.04.15.0.0-1023.24~18.04.15.0.0-1025.27~18.04.15.0.0-1027.29~18.04.15.0.0-1028.30~18.04.15.0.0-1029.31~18.04.15.0.0-1031.335.0.0-1032.345.0.0-1035.375.0.0-1036.38
 None known
linux-azure-5.3
Ubuntu:18.04:LTS
 All versions, plus listed versions
5.3.0-1007.8~18.04.15.3.0-1008.9~18.04.15.3.0-1009.10~18.04.15.3.0-1010.11~18.04.15.3.0-1012.13~18.04.1
Show 11 moreShow less
5.3.0-1013.14~18.04.15.3.0-1016.17~18.04.15.3.0-1018.19~18.04.15.3.0-1019.20~18.04.15.3.0-1020.21~18.04.15.3.0-1022.23~18.04.15.3.0-1028.29~18.04.15.3.0-1031.32~18.04.15.3.0-1032.33~18.04.15.3.0-1034.35~18.04.15.3.0-1035.36
 None known
linux-azure-edge
Ubuntu:18.04:LTS
 All versions, plus listed versions
4.18.0-1006.6~18.04.14.18.0-1007.7~18.04.14.18.0-1008.8~18.04.15.0.0-1012.12~18.04.2
 None known
linux-gcp
Ubuntu:18.04:LTS
 All versions, plus listed versions
4.15.0-1001.14.15.0-1003.34.15.0-1005.54.15.0-1006.64.15.0-1008.8
Show 33 moreShow less
4.15.0-1009.94.15.0-1010.104.15.0-1014.144.15.0-1015.154.15.0-1017.184.15.0-1018.194.15.0-1019.204.15.0-1021.224.15.0-1023.244.15.0-1024.254.15.0-1025.264.15.0-1026.274.15.0-1027.284.15.0-1028.294.15.0-1029.314.15.0-1030.324.15.0-1032.344.15.0-1033.354.15.0-1034.364.15.0-1036.384.15.0-1037.394.15.0-1040.424.15.0-1042.454.15.0-1044.705.0.0-1020.20~18.04.15.0.0-1021.21~18.04.15.0.0-1025.26~18.04.15.0.0-1026.27~18.04.15.0.0-1028.29~18.04.15.0.0-1029.30~18.04.15.0.0-1031.325.0.0-1033.345.0.0-1034.35
 None known
linux-gcp-5.3
Ubuntu:18.04:LTS
 All versions, plus listed versions
5.3.0-1008.9~18.04.15.3.0-1009.10~18.04.15.3.0-1010.11~18.04.15.3.0-1012.13~18.04.15.3.0-1014.15~18.04.1
Show 8 moreShow less
5.3.0-1016.17~18.04.15.3.0-1017.18~18.04.15.3.0-1018.19~18.04.15.3.0-1020.22~18.04.15.3.0-1026.28~18.04.15.3.0-1029.31~18.04.15.3.0-1030.32~18.04.15.3.0-1032.34~18.04.1
 None known
linux-gke-4.15
Ubuntu:18.04:LTS
 All versions, plus listed versions
4.15.0-1030.324.15.0-1032.344.15.0-1033.354.15.0-1034.364.15.0-1036.38
Show 28 moreShow less
4.15.0-1037.394.15.0-1040.424.15.0-1041.434.15.0-1042.444.15.0-1044.464.15.0-1045.484.15.0-1046.494.15.0-1048.514.15.0-1049.524.15.0-1050.534.15.0-1052.554.15.0-1055.584.15.0-1057.604.15.0-1058.614.15.0-1059.624.15.0-1063.664.15.0-1064.674.15.0-1066.694.15.0-1067.704.15.0-1069.724.15.0-1070.734.15.0-1072.764.15.0-1073.784.15.0-1074.794.15.0-1076.814.15.0-1077.824.15.0-1078.834.15.0-1079.84
 None known
linux-gke-5.4
Ubuntu:18.04:LTS
 All versions, plus listed versions
5.4.0-1025.25~18.04.15.4.0-1027.28~18.04.15.4.0-1029.31~18.04.15.4.0-1030.32~18.04.15.4.0-1032.34~18.04.1
Show 32 moreShow less
5.4.0-1033.35~18.04.15.4.0-1035.37~18.04.15.4.0-1036.38~18.04.15.4.0-1037.39~18.04.15.4.0-1039.41~18.04.15.4.0-1040.42~18.04.15.4.0-1042.44~18.04.15.4.0-1043.45~18.04.15.4.0-1044.46~18.04.15.4.0-1046.48~18.04.15.4.0-1049.52~18.04.15.4.0-1051.54~18.04.15.4.0-1052.55~18.04.15.4.0-1053.56~18.04.15.4.0-1054.57~18.04.15.4.0-1055.58~18.04.15.4.0-1056.59~18.04.15.4.0-1057.60~18.04.15.4.0-1059.62~18.04.15.4.0-1061.64~18.04.15.4.0-1062.65~18.04.15.4.0-1063.66~18.04.15.4.0-1065.68~18.04.15.4.0-1066.69~18.04.15.4.0-1067.70~18.04.15.4.0-1068.71~18.04.15.4.0-1071.76~18.04.35.4.0-1072.77~18.04.15.4.0-1074.79~18.04.15.4.0-1076.82~18.04.15.4.0-1078.84~18.04.15.4.0-1080.86~18.04.1
 None known
linux-gkeop-5.4
Ubuntu:18.04:LTS
 All versions, plus listed versions
5.4.0-1001.15.4.0-1003.35.4.0-1004.55.4.0-1005.65.4.0-1007.8~18.04.1
Show 32 moreShow less
5.4.0-1008.9~18.04.15.4.0-1009.10~18.04.15.4.0-1010.11~18.04.15.4.0-1011.12~18.04.25.4.0-1012.13~18.04.15.4.0-1013.14~18.04.15.4.0-1014.15~18.04.15.4.0-1015.16~18.04.15.4.0-1016.17~18.04.15.4.0-1018.19~18.04.15.4.0-1021.22~18.04.15.4.0-1022.23~18.04.15.4.0-1023.24~18.04.15.4.0-1024.25~18.04.15.4.0-1025.26~18.04.15.4.0-1026.27~18.04.15.4.0-1027.28~18.04.15.4.0-1029.30~18.04.25.4.0-1031.32~18.04.15.4.0-1032.33~18.04.15.4.0-1033.34~18.04.15.4.0-1034.35~18.04.15.4.0-1036.37~18.04.15.4.0-1037.38~18.04.15.4.0-1038.39~18.04.15.4.0-1039.40~18.04.15.4.0-1040.41~18.04.15.4.0-1043.44~18.04.15.4.0-1046.48~18.04.15.4.0-1048.51~18.04.15.4.0-1049.52~18.04.15.4.0-1051.54~18.04.1
 None known
linux-hwe
Ubuntu:18.04:LTS
 All versions, plus listed versions
4.18.0-13.14~18.04.14.18.0-14.15~18.04.14.18.0-15.16~18.04.14.18.0-16.17~18.04.14.18.0-17.18~18.04.1
Show 38 moreShow less
4.18.0-18.19~18.04.14.18.0-20.21~18.04.14.18.0-21.22~18.04.14.18.0-22.23~18.04.14.18.0-24.25~18.04.14.18.0-25.26~18.04.15.0.0-23.24~18.04.15.0.0-25.26~18.04.15.0.0-27.28~18.04.15.0.0-29.31~18.04.15.0.0-31.33~18.04.15.0.0-32.34~18.04.25.0.0-35.38~18.04.15.0.0-36.39~18.04.15.0.0-37.40~18.04.15.3.0-26.28~18.04.15.3.0-28.30~18.04.15.3.0-40.32~18.04.15.3.0-42.34~18.04.15.3.0-45.37~18.04.15.3.0-46.38~18.04.15.3.0-51.44~18.04.25.3.0-53.47~18.04.15.3.0-59.53~18.04.15.3.0-61.55~18.04.15.3.0-62.56~18.04.15.3.0-64.58~18.04.15.3.0-65.595.3.0-66.605.3.0-67.615.3.0-68.635.3.0-69.655.3.0-70.665.3.0-72.685.3.0-73.695.3.0-74.705.3.0-75.715.3.0-76.72
 None known
linux-hwe-edge
Ubuntu:18.04:LTS
 All versions, plus listed versions
5.0.0-15.16~18.04.15.0.0-16.17~18.04.15.0.0-17.18~18.04.15.0.0-19.20~18.04.15.0.0-20.21~18.04.1
Show 5 moreShow less
5.3.0-19.20~18.04.25.3.0-22.24~18.04.15.3.0-23.25~18.04.15.3.0-23.25~18.04.25.3.0-24.26~18.04.2
 None known
linux-oem
Ubuntu:18.04:LTS
 All versions, plus listed versions
4.15.0-1002.34.15.0-1004.54.15.0-1006.94.15.0-1008.114.15.0-1009.12
Show 45 moreShow less
4.15.0-1012.154.15.0-1013.164.15.0-1015.184.15.0-1017.204.15.0-1018.214.15.0-1021.244.15.0-1024.294.15.0-1026.314.15.0-1028.334.15.0-1030.354.15.0-1033.384.15.0-1034.394.15.0-1035.404.15.0-1036.414.15.0-1038.434.15.0-1039.444.15.0-1043.484.15.0-1045.504.15.0-1050.574.15.0-1056.654.15.0-1057.664.15.0-1059.684.15.0-1063.724.15.0-1064.734.15.0-1065.754.15.0-1066.764.15.0-1067.774.15.0-1069.794.15.0-1073.834.15.0-1076.864.15.0-1079.894.15.0-1080.904.15.0-1081.914.15.0-1087.974.15.0-1090.1004.15.0-1091.1014.15.0-1093.1034.15.0-1094.1044.15.0-1096.1064.15.0-1097.1074.15.0-1099.1094.15.0-1100.1104.15.0-1101.1124.15.0-1102.1134.15.0-1103.114
 None known
linux-oracle-5.0
Ubuntu:18.04:LTS
 All versions, plus listed versions
5.0.0-1007.12~18.04.15.0.0-1008.13~18.04.15.0.0-1009.14~18.04.15.0.0-1010.15~18.04.15.0.0-1011.165.0.0-1013.185.0.0-1014.19
 None known
linux-oracle-5.3
Ubuntu:18.04:LTS
 All versions, plus listed versions
5.3.0-1011.12~18.04.15.3.0-1013.14~18.04.15.3.0-1014.15~18.04.15.3.0-1016.18~18.04.15.3.0-1018.20~18.04.1
Show 4 moreShow less
5.3.0-1024.26~18.04.15.3.0-1027.29~18.04.15.3.0-1028.30~18.04.15.3.0-1030.32~18.04.1
 None known
linux-aws-5.11
Ubuntu:20.04:LTS
 All versions, plus listed versions
5.11.0-1009.9~20.04.25.11.0-1014.15~20.04.15.11.0-1016.17~20.04.15.11.0-1017.18~20.04.15.11.0-1019.20~20.04.1
Show 7 moreShow less
5.11.0-1020.21~20.04.25.11.0-1021.22~20.04.25.11.0-1022.23~20.04.15.11.0-1023.24~20.04.15.11.0-1025.27~20.04.15.11.0-1027.30~20.04.15.11.0-1028.31~20.04.1
 None known
linux-aws-5.13
Ubuntu:20.04:LTS
 All versions, plus listed versions
5.13.0-1008.9~20.04.25.13.0-1011.12~20.04.15.13.0-1012.13~20.04.15.13.0-1014.15~20.04.15.13.0-1017.19~20.04.1
Show 8 moreShow less
5.13.0-1019.21~20.04.15.13.0-1021.23~20.04.25.13.0-1022.24~20.04.15.13.0-1023.25~20.04.15.13.0-1025.27~20.04.15.13.0-1028.31~20.04.15.13.0-1029.32~20.04.15.13.0-1031.35~20.04.1
 None known
linux-aws-5.8
Ubuntu:20.04:LTS
 All versions, plus listed versions
5.8.0-1035.37~20.04.15.8.0-1038.40~20.04.15.8.0-1041.43~20.04.15.8.0-1042.44~20.04.1
 None known
linux-azure-5.11
Ubuntu:20.04:LTS
 All versions, plus listed versions
5.11.0-1007.7~20.04.25.11.0-1012.13~20.04.15.11.0-1013.14~20.04.15.11.0-1015.16~20.04.15.11.0-1017.18~20.04.1
Show 8 moreShow less
5.11.0-1019.20~20.04.15.11.0-1020.21~20.04.15.11.0-1021.22~20.04.15.11.0-1022.23~20.04.15.11.0-1023.24~20.04.15.11.0-1025.27~20.04.15.11.0-1027.30~20.04.15.11.0-1028.31~20.04.2
 None known
linux-azure-5.13
Ubuntu:20.04:LTS
 All versions, plus listed versions
5.13.0-1009.10~20.04.25.13.0-1012.14~20.04.15.13.0-1013.15~20.04.15.13.0-1014.16~20.04.15.13.0-1017.19~20.04.1
Show 7 moreShow less
5.13.0-1021.24~20.04.15.13.0-1022.26~20.04.15.13.0-1023.27~20.04.15.13.0-1025.29~20.04.15.13.0-1028.33~20.04.15.13.0-1029.34~20.04.15.13.0-1031.37~20.04.1
 None known
linux-azure-5.8
Ubuntu:20.04:LTS
 All versions, plus listed versions
5.8.0-1033.35~20.04.15.8.0-1036.38~20.04.15.8.0-1039.42~20.04.15.8.0-1040.43~20.04.15.8.0-1041.44~20.04.15.8.0-1042.45~20.04.15.8.0-1043.46~20.04.1
 None known
linux-azure-fde
Ubuntu:20.04:LTS
 All versions, plus listed versions
5.4.0-1063.66+cvm2.25.4.0-1063.66+cvm3.25.4.0-1064.67+cvm1.15.4.0-1065.68+cvm2.15.4.0-1067.70+cvm1.1
Show 21 moreShow less
5.4.0-1068.71+cvm1.15.4.0-1069.72+cvm1.15.4.0-1070.73+cvm1.15.4.0-1072.75+cvm1.15.4.0-1073.76+cvm1.15.4.0-1074.77+cvm1.15.4.0-1076.79+cvm1.15.4.0-1078.81+cvm1.15.4.0-1080.83+cvm1.15.4.0-1083.87+cvm1.15.4.0-1085.90+cvm1.15.4.0-1085.90+cvm2.15.4.0-1086.91+cvm1.15.4.0-1089.94+cvm1.25.4.0-1090.95+cvm1.15.4.0-1091.96+cvm1.15.4.0-1092.97+cvm1.15.4.0-1095.101+cvm1.15.4.0-1098.104+cvm1.15.4.0-1100.106+cvm1.15.4.0-1103.109+cvm1.1
 None known
linux-gcp-5.11
Ubuntu:20.04:LTS
 All versions, plus listed versions
5.11.0-1009.10~20.04.15.11.0-1014.16~20.04.15.11.0-1017.19~20.04.15.11.0-1018.20~20.04.25.11.0-1020.22~20.04.1
Show 7 moreShow less
5.11.0-1021.23~20.04.15.11.0-1022.24~20.04.15.11.0-1023.25~20.04.15.11.0-1024.26~20.04.15.11.0-1026.29~20.04.15.11.0-1028.32~20.04.15.11.0-1029.33~20.04.3
 None known
linux-gcp-5.13
Ubuntu:20.04:LTS
 All versions, plus listed versions
5.13.0-1008.9~20.04.35.13.0-1012.15~20.04.15.13.0-1013.16~20.04.15.13.0-1015.18~20.04.15.13.0-1019.23~20.04.1
Show 8 moreShow less
5.13.0-1021.25~20.04.15.13.0-1023.28~20.04.15.13.0-1024.29~20.04.15.13.0-1025.30~20.04.15.13.0-1027.32~20.04.15.13.0-1030.36~20.04.15.13.0-1031.37~20.04.15.13.0-1033.40~20.04.1
 None known
linux-gcp-5.8
Ubuntu:20.04:LTS
 All versions, plus listed versions
5.8.0-1032.34~20.04.15.8.0-1035.37~20.04.15.8.0-1038.40~20.04.15.8.0-1039.41
 None known
linux-gke
Ubuntu:20.04:LTS
 All versions, plus listed versions
5.4.0-1033.355.4.0-1035.375.4.0-1036.385.4.0-1037.395.4.0-1039.41
Show 45 moreShow less
5.4.0-1041.435.4.0-1042.445.4.0-1043.455.4.0-1044.465.4.0-1046.485.4.0-1049.525.4.0-1051.545.4.0-1052.555.4.0-1053.565.4.0-1054.575.4.0-1055.585.4.0-1056.595.4.0-1057.605.4.0-1059.625.4.0-1061.645.4.0-1062.655.4.0-1063.665.4.0-1065.685.4.0-1066.695.4.0-1067.705.4.0-1068.715.4.0-1071.765.4.0-1072.775.4.0-1074.795.4.0-1076.825.4.0-1078.845.4.0-1080.865.4.0-1081.875.4.0-1083.895.4.0-1084.905.4.0-1086.935.4.0-1087.945.4.0-1090.975.4.0-1091.985.4.0-1094.1015.4.0-1095.1025.4.0-1096.1035.4.0-1097.1045.4.0-1098.1055.4.0-1099.1065.4.0-1100.1075.4.0-1101.1085.4.0-1102.1095.4.0-1103.1105.4.0-1104.111
 None known
linux-gke-5.15
Ubuntu:20.04:LTS
 All versions, plus listed versions
5.15.0-1011.14~20.04.15.15.0-1014.17~20.04.15.15.0-1015.18~20.04.15.15.0-1016.19~20.04.15.15.0-1019.23~20.04.1
Show 13 moreShow less
5.15.0-1020.25~20.04.15.15.0-1023.28~20.04.25.15.0-1027.32~20.04.15.15.0-1028.33~20.04.15.15.0-1029.34~20.04.15.15.0-1031.36~20.04.15.15.0-1032.37~20.04.15.15.0-1033.38~20.04.15.15.0-1034.39~20.04.15.15.0-1036.41~20.04.15.15.0-1037.42~20.04.15.15.0-1038.43~20.04.15.15.0-1039.44~20.04.1
 None known
linux-gkeop
Ubuntu:20.04:LTS
 All versions, plus listed versions
5.4.0-1008.95.4.0-1009.105.4.0-1010.115.4.0-1011.125.4.0-1012.13
Show 45 moreShow less
5.4.0-1013.145.4.0-1014.155.4.0-1015.165.4.0-1016.175.4.0-1018.195.4.0-1021.225.4.0-1022.235.4.0-1023.245.4.0-1024.255.4.0-1025.265.4.0-1026.275.4.0-1027.285.4.0-1029.305.4.0-1031.325.4.0-1032.335.4.0-1033.345.4.0-1034.355.4.0-1036.375.4.0-1037.385.4.0-1038.395.4.0-1039.405.4.0-1040.415.4.0-1043.445.4.0-1046.485.4.0-1048.515.4.0-1049.525.4.0-1051.545.4.0-1052.555.4.0-1053.565.4.0-1054.575.4.0-1056.605.4.0-1057.615.4.0-1060.645.4.0-1061.655.4.0-1062.665.4.0-1064.685.4.0-1065.695.4.0-1066.705.4.0-1067.715.4.0-1068.725.4.0-1069.735.4.0-1070.745.4.0-1071.755.4.0-1072.765.4.0-1073.77
 None known
linux-gkeop-5.15
Ubuntu:20.04:LTS
 All versions, plus listed versions
5.15.0-1003.5~20.04.25.15.0-1005.7~20.04.15.15.0-1007.10~20.04.15.15.0-1008.12~20.04.15.15.0-1011.15~20.04.2
Show 40 moreShow less
5.15.0-1012.16~20.04.15.15.0-1013.17~20.04.15.15.0-1015.19~20.04.15.15.0-1016.21~20.04.15.15.0-1017.22~20.04.15.15.0-1018.23~20.04.15.15.0-1019.24~20.04.15.15.0-1020.25~20.04.15.15.0-1021.26~20.04.15.15.0-1022.27~20.04.15.15.0-1023.28~20.04.15.15.0-1024.29~20.04.15.15.0-1025.30~20.04.15.15.0-1026.31~20.04.15.15.0-1027.32~20.04.15.15.0-1028.33~20.04.15.15.0-1030.35~20.04.15.15.0-1031.37~20.04.15.15.0-1032.38~20.04.15.15.0-1033.39~20.04.15.15.0-1034.40~20.04.15.15.0-1035.41~20.04.15.15.0-1036.42~20.04.15.15.0-1037.43~20.04.15.15.0-1038.44~20.04.15.15.0-1039.45~20.04.15.15.0-1040.46~20.04.15.15.0-1043.50~20.04.15.15.0-1044.51~20.04.15.15.0-1045.52~20.04.15.15.0-1046.53~20.04.15.15.0-1047.54~20.04.15.15.0-1048.55~20.04.15.15.0-1049.56~20.04.15.15.0-1050.57~20.04.15.15.0-1051.58~20.04.15.15.0-1052.59~20.04.15.15.0-1053.60~20.04.15.15.0-1054.61~20.04.15.15.0-1055.62~20.04.1
 None known
linux-hwe-5.11
Ubuntu:20.04:LTS
 All versions, plus listed versions
5.11.0-22.23~20.04.15.11.0-25.27~20.04.15.11.0-27.29~20.04.15.11.0-34.36~20.04.15.11.0-36.40~20.04.1
Show 7 moreShow less
5.11.0-37.41~20.04.25.11.0-38.42~20.04.15.11.0-40.44~20.04.25.11.0-41.45~20.04.15.11.0-43.47~20.04.25.11.0-44.48~20.04.25.11.0-46.51~20.04.1
 None known
linux-hwe-5.13
Ubuntu:20.04:LTS
 All versions, plus listed versions
5.13.0-21.21~20.04.15.13.0-22.22~20.04.15.13.0-23.23~20.04.25.13.0-25.26~20.04.15.13.0-27.29~20.04.1
Show 11 moreShow less
5.13.0-28.31~20.04.15.13.0-30.33~20.04.15.13.0-35.40~20.04.15.13.0-37.42~20.04.15.13.0-39.44~20.04.15.13.0-40.45~20.04.15.13.0-41.46~20.04.15.13.0-44.49~20.04.15.13.0-48.54~20.04.15.13.0-51.58~20.04.15.13.0-52.59~20.04.1
 None known
linux-hwe-5.8
Ubuntu:20.04:LTS
 All versions, plus listed versions
5.8.0-23.24~20.04.15.8.0-25.26~20.04.15.8.0-28.30~20.04.15.8.0-29.31~20.04.15.8.0-31.33~20.04.1
Show 16 moreShow less
5.8.0-33.36~20.04.15.8.0-34.37~20.04.25.8.0-36.40~20.04.15.8.0-38.43~20.04.15.8.0-40.45~20.04.15.8.0-41.46~20.04.15.8.0-43.49~20.04.15.8.0-44.50~20.04.15.8.0-45.51~20.04.15.8.0-48.54~20.04.15.8.0-49.55~20.04.15.8.0-50.56~20.04.15.8.0-53.60~20.04.15.8.0-55.62~20.04.15.8.0-59.66~20.04.15.8.0-63.71~20.04.1
 None known
linux-intel-5.13
Ubuntu:20.04:LTS
 All versions, plus listed versions
5.13.0-1007.75.13.0-1008.85.13.0-1009.95.13.0-1010.105.13.0-1011.115.13.0-1014.155.13.0-1017.19
 None known
linux-oem-5.10
Ubuntu:20.04:LTS
 All versions, plus listed versions
5.10.0-1008.95.10.0-1011.125.10.0-1013.145.10.0-1014.155.10.0-1016.17
Show 21 moreShow less
5.10.0-1017.185.10.0-1019.205.10.0-1021.225.10.0-1022.235.10.0-1023.245.10.0-1025.265.10.0-1026.275.10.0-1029.305.10.0-1032.335.10.0-1033.345.10.0-1034.355.10.0-1038.405.10.0-1044.465.10.0-1045.475.10.0-1049.515.10.0-1050.525.10.0-1051.535.10.0-1052.545.10.0-1053.555.10.0-1055.585.10.0-1057.61
 None known
linux-oem-5.13
Ubuntu:20.04:LTS
 All versions, plus listed versions
5.13.0-1009.105.13.0-1010.115.13.0-1012.165.13.0-1014.185.13.0-1017.21
Show 7 moreShow less
5.13.0-1019.235.13.0-1020.245.13.0-1021.255.13.0-1022.265.13.0-1026.325.13.0-1028.355.13.0-1029.36
 None known
linux-oem-5.14
Ubuntu:20.04:LTS
 All versions, plus listed versions
5.14.0-1004.45.14.0-1005.55.14.0-1007.75.14.0-1008.85.14.0-1010.10
Show 30 moreShow less
5.14.0-1011.115.14.0-1013.135.14.0-1018.195.14.0-1020.225.14.0-1022.245.14.0-1024.265.14.0-1027.305.14.0-1029.325.14.0-1031.345.14.0-1032.355.14.0-1033.365.14.0-1034.375.14.0-1036.405.14.0-1038.425.14.0-1042.475.14.0-1044.495.14.0-1045.515.14.0-1046.535.14.0-1047.545.14.0-1048.555.14.0-1049.565.14.0-1050.575.14.0-1051.585.14.0-1052.595.14.0-1054.615.14.0-1055.625.14.0-1056.635.14.0-1057.645.14.0-1058.665.14.0-1059.67
 None known
linux-oem-5.6
Ubuntu:20.04:LTS
 All versions, plus listed versions
5.6.0-1007.75.6.0-1008.85.6.0-1010.105.6.0-1011.115.6.0-1013.13
Show 24 moreShow less
5.6.0-1017.175.6.0-1018.185.6.0-1020.205.6.0-1021.215.6.0-1023.235.6.0-1026.265.6.0-1027.275.6.0-1028.285.6.0-1031.325.6.0-1032.335.6.0-1033.355.6.0-1034.365.6.0-1035.375.6.0-1036.395.6.0-1039.435.6.0-1042.465.6.0-1047.515.6.0-1048.525.6.0-1050.545.6.0-1052.565.6.0-1053.575.6.0-1054.585.6.0-1055.595.6.0-1056.60
 None known
linux-oracle-5.11
Ubuntu:20.04:LTS
 All versions, plus listed versions
5.11.0-1008.8~20.04.15.11.0-1013.14~20.04.15.11.0-1016.17~20.04.15.11.0-1017.18~20.04.15.11.0-1019.20~20.04.1
Show 7 moreShow less
5.11.0-1020.21~20.04.15.11.0-1021.22~20.04.15.11.0-1022.23~20.04.15.11.0-1023.24~20.04.15.11.0-1025.27~20.04.15.11.0-1027.30~20.04.15.11.0-1028.31~20.04.1
 None known
linux-oracle-5.13
Ubuntu:20.04:LTS
 All versions, plus listed versions
5.13.0-1011.13~20.04.25.13.0-1015.19~20.04.15.13.0-1016.20~20.04.15.13.0-1018.22~20.04.15.13.0-1021.26~20.04.1
Show 7 moreShow less
5.13.0-1025.30~20.04.15.13.0-1027.32~20.04.15.13.0-1028.33~20.04.15.13.0-1030.35~20.04.15.13.0-1033.39~20.04.15.13.0-1034.40~20.04.15.13.0-1036.43~20.04.1
 None known
linux-oracle-5.8
Ubuntu:20.04:LTS
 All versions, plus listed versions
5.8.0-1031.32~20.04.25.8.0-1033.34~20.04.15.8.0-1034.35~20.04.25.8.0-1037.38~20.04.15.8.0-1038.39~20.04.1
 None known
linux-raspi2
Ubuntu:20.04:LTS
 All versions, plus listed versions
5.3.0-1007.85.3.0-1014.165.3.0-1015.175.3.0-1017.195.4.0-1004.45.4.0-1006.6
 None known
linux-riscv
Ubuntu:20.04:LTS
 All versions, plus listed versions
5.4.0-24.285.4.0-26.305.4.0-27.315.4.0-28.325.4.0-30.34
Show 7 moreShow less
5.4.0-31.355.4.0-33.375.4.0-34.385.4.0-36.415.4.0-37.425.4.0-39.445.4.0-40.45
 None known
linux-riscv-5.11
Ubuntu:20.04:LTS
 All versions, plus listed versions
5.11.0-1015.16~20.04.15.11.0-1017.18~20.04.15.11.0-1018.19~20.04.25.11.0-1020.21~20.04.15.11.0-1021.22~20.04.1
Show 8 moreShow less
5.11.0-1022.23~20.04.15.11.0-1023.24~20.04.15.11.0-1024.25~20.04.15.11.0-1026.28~20.04.15.11.0-1028.31~20.04.15.11.0-1029.32~20.04.15.11.0-1030.345.11.0-1031.35
 None known
linux-riscv-5.8
Ubuntu:20.04:LTS
 All versions, plus listed versions
5.8.0-14.16~20.04.15.8.0-14.16~20.04.35.8.0-16.18~20.04.15.8.0-17.19~20.04.15.8.0-18.20~20.04.1
Show 5 moreShow less
5.8.0-20.22~20.04.15.8.0-22.24~20.04.15.8.0-25.27~20.04.15.8.0-26.28~20.04.15.8.0-29.31~20.04.1
 None known
linux-allwinner-5.19
Ubuntu:22.04:LTS
 All versions, plus listed versions
5.19.0-1007.7~22.04.15.19.0-1009.9~22.04.15.19.0-1010.10~22.04.15.19.0-1011.11~22.04.15.19.0-1012.12~22.04.15.19.0-1013.13~22.04.15.19.0-1014.14~22.04.15.19.0-1015.15~22.04.1
 None known
linux-aws-5.19
Ubuntu:22.04:LTS
 All versions, plus listed versions
5.19.0-1019.20~22.04.15.19.0-1020.21~22.04.15.19.0-1022.23~22.04.15.19.0-1023.24~22.04.15.19.0-1024.25~22.04.1
Show 5 moreShow less
5.19.0-1025.26~22.04.15.19.0-1026.27~22.04.15.19.0-1027.28~22.04.15.19.0-1028.29~22.04.15.19.0-1029.30~22.04.1
 None known
linux-aws-6.2
Ubuntu:22.04:LTS
 All versions, plus listed versions
6.2.0-1005.5~22.04.16.2.0-1006.6~22.04.16.2.0-1007.7~22.04.16.2.0-1008.8~22.04.16.2.0-1009.9~22.04.3
Show 9 moreShow less
6.2.0-1010.10~22.04.16.2.0-1011.11~22.04.16.2.0-1012.12~22.04.16.2.0-1013.13~22.04.16.2.0-1014.14~22.04.16.2.0-1015.15~22.04.16.2.0-1016.16~22.04.16.2.0-1017.17~22.04.16.2.0-1018.18~22.04.1
 None known
linux-aws-6.5
Ubuntu:22.04:LTS
 All versions, plus listed versions
6.5.0-1008.8~22.04.16.5.0-1010.10~22.04.16.5.0-1011.11~22.04.16.5.0-1012.12~22.04.16.5.0-1014.14~22.04.1
Show 9 moreShow less
6.5.0-1015.15~22.04.16.5.0-1016.16~22.04.16.5.0-1017.17~22.04.26.5.0-1018.18~22.04.16.5.0-1020.20~22.04.16.5.0-1021.21~22.04.16.5.0-1022.22~22.04.16.5.0-1023.23~22.04.16.5.0-1024.24~22.04.1
 None known
linux-aws-6.8
Ubuntu:22.04:LTS
 before 6.8.0-1015.16~22.04.1, plus listed versions
6.8.0-1009.9~22.04.26.8.0-1010.10~22.04.26.8.0-1011.12~22.04.16.8.0-1013.14~22.04.16.8.0-1014.15~22.04.1
6.8.0-1015.16~22.04.1
linux-azure-5.19
Ubuntu:22.04:LTS
 All versions, plus listed versions
5.19.0-1020.21~22.04.15.19.0-1021.22~22.04.15.19.0-1022.23~22.04.15.19.0-1023.24~22.04.15.19.0-1025.28~22.04.15.19.0-1026.29~22.04.15.19.0-1027.30~22.04.2
 None known
linux-azure-6.2
Ubuntu:22.04:LTS
 All versions, plus listed versions
6.2.0-1005.5~22.04.16.2.0-1006.6~22.04.16.2.0-1007.7~22.04.16.2.0-1008.8~22.04.16.2.0-1009.9~22.04.3
Show 8 moreShow less
6.2.0-1011.11~22.04.16.2.0-1012.12~22.04.16.2.0-1014.14~22.04.16.2.0-1015.15~22.04.16.2.0-1016.16~22.04.16.2.0-1017.17~22.04.16.2.0-1018.18~22.04.16.2.0-1019.19~22.04.1
 None known
linux-azure-6.5
Ubuntu:22.04:LTS
 All versions, plus listed versions
6.5.0-1007.7~22.04.16.5.0-1009.9~22.04.16.5.0-1010.10~22.04.16.5.0-1011.11~22.04.16.5.0-1015.15~22.04.1
Show 9 moreShow less
6.5.0-1016.16~22.04.16.5.0-1017.17~22.04.16.5.0-1018.19~22.04.26.5.0-1019.20~22.04.16.5.0-1021.22~22.04.16.5.0-1022.23~22.04.16.5.0-1023.24~22.04.16.5.0-1024.25~22.04.16.5.0-1025.26~22.04.1
 None known
linux-azure-6.8
Ubuntu:22.04:LTS
 before 6.8.0-1014.16~22.04.1, plus listed versions
6.8.0-1008.8~22.04.16.8.0-1009.9~22.04.16.8.0-1010.10~22.04.16.8.0-1012.14~22.04.16.8.0-1013.15~22.04.1
6.8.0-1014.16~22.04.1
linux-azure-fde-5.19
Ubuntu:22.04:LTS
 All versions, plus listed versions
5.19.0-1025.28~22.04.1.15.19.0-1026.29~22.04.1.15.19.0-1027.30~22.04.2.1
 None known
linux-azure-fde-6.2
Ubuntu:22.04:LTS
 All versions, plus listed versions
6.2.0-1008.8~22.04.1.16.2.0-1009.9~22.04.3.16.2.0-1011.11~22.04.1.16.2.0-1012.12~22.04.1.16.2.0-1014.14~22.04.1.1
Show 5 moreShow less
6.2.0-1015.15~22.04.1.16.2.0-1016.16~22.04.1.16.2.0-1017.17~22.04.1.16.2.0-1018.18~22.04.1.16.2.0-1019.19~22.04.1.1
 None known
linux-gcp-5.19
Ubuntu:22.04:LTS
 All versions, plus listed versions
5.19.0-1020.22~22.04.25.19.0-1021.23~22.04.15.19.0-1022.24~22.04.15.19.0-1024.26~22.04.15.19.0-1025.27~22.04.15.19.0-1026.28~22.04.15.19.0-1027.29~22.04.15.19.0-1030.32~22.04.1
 None known
linux-gcp-6.2
Ubuntu:22.04:LTS
 All versions, plus listed versions
6.2.0-1009.9~22.04.36.2.0-1010.10~22.04.16.2.0-1011.11~22.04.16.2.0-1011.11~22.04.36.2.0-1012.12~22.04.1
Show 7 moreShow less
6.2.0-1013.13~22.04.16.2.0-1014.14~22.04.16.2.0-1016.18~22.04.16.2.0-1017.19~22.04.16.2.0-1018.20~22.04.16.2.0-1019.21~22.04.16.2.0-1021.23~22.04.1
 None known
linux-gcp-6.5
Ubuntu:22.04:LTS
 All versions, plus listed versions
6.5.0-1010.10~22.04.36.5.0-1011.11~22.04.16.5.0-1013.13~22.04.16.5.0-1014.14~22.04.16.5.0-1015.15~22.04.1
Show 8 moreShow less
6.5.0-1016.16~22.04.16.5.0-1017.17~22.04.16.5.0-1018.18~22.04.16.5.0-1020.20~22.04.16.5.0-1022.24~22.04.16.5.0-1023.25~22.04.16.5.0-1024.26~22.04.16.5.0-1025.27~22.04.1
 None known
linux-gcp-6.8
Ubuntu:22.04:LTS
 before 6.8.0-1014.16~22.04.1, plus listed versions
6.8.0-1010.11~22.04.16.8.0-1011.12~22.04.16.8.0-1012.13~22.04.16.8.0-1013.14~22.04.1
6.8.0-1014.16~22.04.1
linux-hwe-5.19
Ubuntu:22.04:LTS
 All versions, plus listed versions
5.19.0-28.29~22.04.15.19.0-32.33~22.04.15.19.0-35.36~22.04.15.19.0-38.39~22.04.15.19.0-40.41~22.04.1
Show 6 moreShow less
5.19.0-41.42~22.04.15.19.0-42.43~22.04.15.19.0-43.44~22.04.15.19.0-45.46~22.04.15.19.0-46.47~22.04.15.19.0-50.50
 None known
linux-hwe-6.2
Ubuntu:22.04:LTS
 All versions, plus listed versions
6.2.0-25.25~22.04.26.2.0-26.26~22.04.16.2.0-31.31~22.04.16.2.0-32.32~22.04.16.2.0-33.33~22.04.1
Show 5 moreShow less
6.2.0-34.34~22.04.16.2.0-35.35~22.04.16.2.0-36.37~22.04.16.2.0-37.38~22.04.16.2.0-39.40~22.04.1
 None known
linux-hwe-6.5
Ubuntu:22.04:LTS
 All versions, plus listed versions
6.5.0-14.14~22.04.16.5.0-15.15~22.04.16.5.0-17.17~22.04.16.5.0-18.18~22.04.16.5.0-21.21~22.04.1
Show 8 moreShow less
6.5.0-25.25~22.04.16.5.0-26.26~22.04.16.5.0-27.28~22.04.16.5.0-28.29~22.04.16.5.0-35.35~22.04.16.5.0-41.41~22.04.26.5.0-44.44~22.04.16.5.0-45.45~22.04.1
 None known
linux-hwe-6.8
Ubuntu:22.04:LTS
 before 6.8.0-45.45~22.04.1, plus listed versions
6.8.0-38.38~22.04.16.8.0-39.39~22.04.16.8.0-40.40~22.04.3
6.8.0-45.45~22.04.1
linux-ibm-6.8
Ubuntu:22.04:LTS
 before 6.8.0-1012.12~22.04.1, plus listed versions
6.8.0-1008.8~22.04.16.8.0-1010.10~22.04.16.8.0-1011.11~22.04.1
6.8.0-1012.12~22.04.1
linux-intel-iot-realtime
Ubuntu:22.04:LTS
 All versions, plus listed versions
5.15.0-1073.75
 None known
linux-lowlatency-hwe-5.19
Ubuntu:22.04:LTS
 All versions, plus listed versions
5.19.0-1017.18~22.04.15.19.0-1018.19~22.04.15.19.0-1021.22~22.04.15.19.0-1022.23~22.04.15.19.0-1023.24~22.04.1
Show 5 moreShow less
5.19.0-1024.25~22.04.15.19.0-1025.26~22.04.15.19.0-1027.28~22.04.15.19.0-1028.29~22.04.15.19.0-1030.30
 None known
linux-lowlatency-hwe-6.2
Ubuntu:22.04:LTS
 All versions, plus listed versions
6.2.0-1008.8~22.04.16.2.0-1009.9~22.04.16.2.0-1011.11~22.04.16.2.0-1012.12~22.04.16.2.0-1013.13~22.04.1
Show 5 moreShow less
6.2.0-1014.14~22.04.16.2.0-1015.15~22.04.16.2.0-1016.16~22.04.16.2.0-1017.17~22.04.16.2.0-1018.18~22.04.1
 None known
linux-lowlatency-hwe-6.5
Ubuntu:22.04:LTS
 All versions, plus listed versions
6.5.0-14.14.1~22.04.16.5.0-15.15.1.1~22.04.16.5.0-17.17.1.1.1~22.04.16.5.0-21.21.1~22.04.16.5.0-25.25.1~22.04.1
Show 8 moreShow less
6.5.0-26.26.1~22.04.16.5.0-27.28.1~22.04.16.5.0-28.29.1~22.04.16.5.0-35.35.1~22.04.16.5.0-41.41.1~22.04.16.5.0-42.42.1~22.04.16.5.0-44.44.1~22.04.16.5.0-45.45.1~22.04.1
 None known
linux-lowlatency-hwe-6.8
Ubuntu:22.04:LTS
 before 6.8.0-44.44.1~22.04.1, plus listed versions
6.8.0-38.38.1~22.04.26.8.0-40.40.1~22.04.1
6.8.0-44.44.1~22.04.1
linux-nvidia-6.2
Ubuntu:22.04:LTS
 All versions, plus listed versions
6.2.0-1003.3~22.04.16.2.0-1009.96.2.0-1010.106.2.0-1011.116.2.0-1012.126.2.0-1013.136.2.0-1015.15
 None known
linux-nvidia-6.5
Ubuntu:22.04:LTS
 All versions, plus listed versions
6.5.0-1004.46.5.0-1007.76.5.0-1013.136.5.0-1014.146.5.0-1015.15
Show 6 moreShow less
6.5.0-1018.186.5.0-1019.196.5.0-1021.226.5.0-1022.236.5.0-1023.246.5.0-1024.25
 None known
linux-nvidia-6.8
Ubuntu:22.04:LTS
 before 6.8.0-1013.14~22.04.1, plus listed versions
6.8.0-1008.8~22.04.16.8.0-1009.9~22.04.16.8.0-1010.10~22.04.16.8.0-1011.11~22.04.16.8.0-1012.12~22.04.1
6.8.0-1013.14~22.04.1
linux-oem-5.17
Ubuntu:22.04:LTS
 All versions, plus listed versions
5.17.0-1003.35.17.0-1004.45.17.0-1006.65.17.0-1011.125.17.0-1012.13
Show 21 moreShow less
5.17.0-1013.145.17.0-1014.155.17.0-1015.165.17.0-1016.175.17.0-1017.185.17.0-1018.195.17.0-1019.205.17.0-1020.215.17.0-1021.225.17.0-1024.255.17.0-1025.265.17.0-1026.275.17.0-1027.285.17.0-1028.295.17.0-1029.305.17.0-1030.315.17.0-1031.325.17.0-1032.335.17.0-1033.345.17.0-1034.355.17.0-1035.36
 None known
linux-oem-6.0
Ubuntu:22.04:LTS
 All versions, plus listed versions
6.0.0-1006.66.0.0-1007.76.0.0-1008.86.0.0-1009.96.0.0-1010.10
Show 11 moreShow less
6.0.0-1011.116.0.0-1012.126.0.0-1013.136.0.0-1014.146.0.0-1015.156.0.0-1016.166.0.0-1017.176.0.0-1018.186.0.0-1019.196.0.0-1020.206.0.0-1021.21
 None known
linux-oem-6.1
Ubuntu:22.04:LTS
 All versions, plus listed versions
6.1.0-1004.46.1.0-1006.66.1.0-1007.76.1.0-1008.86.1.0-1009.9
Show 22 moreShow less
6.1.0-1010.106.1.0-1012.126.1.0-1013.136.1.0-1014.146.1.0-1015.156.1.0-1016.166.1.0-1017.176.1.0-1019.196.1.0-1020.206.1.0-1021.216.1.0-1022.226.1.0-1023.236.1.0-1024.246.1.0-1025.256.1.0-1026.266.1.0-1027.276.1.0-1028.286.1.0-1029.296.1.0-1033.336.1.0-1034.346.1.0-1035.356.1.0-1036.36
 None known
linux-oem-6.5
Ubuntu:22.04:LTS
 All versions, plus listed versions
6.5.0-1003.36.5.0-1004.46.5.0-1006.66.5.0-1007.76.5.0-1008.8
Show 14 moreShow less
6.5.0-1009.106.5.0-1011.126.5.0-1013.146.5.0-1014.156.5.0-1015.166.5.0-1016.176.5.0-1018.196.5.0-1019.206.5.0-1020.216.5.0-1022.236.5.0-1023.246.5.0-1024.256.5.0-1025.266.5.0-1027.28
 None known
linux-oracle-6.5
Ubuntu:22.04:LTS
 All versions, plus listed versions
6.5.0-1013.13~22.04.46.5.0-1014.14~22.04.16.5.0-1015.15~22.04.16.5.0-1016.16~22.04.16.5.0-1018.18~22.04.1
Show 8 moreShow less
6.5.0-1019.19~22.04.16.5.0-1020.20~22.04.16.5.0-1021.21~22.04.16.5.0-1023.23~22.04.16.5.0-1024.24~22.04.16.5.0-1025.25~22.04.16.5.0-1026.26~22.04.16.5.0-1027.27~22.04.1
 None known
linux-oracle-6.8
Ubuntu:22.04:LTS
 before 6.8.0-1012.12~22.04.1, plus listed versions
6.8.0-1006.6~22.04.36.8.0-1008.8~22.04.16.8.0-1010.10~22.04.16.8.0-1011.11~22.04.1
6.8.0-1012.12~22.04.1
linux-realtime
Ubuntu:22.04:LTS
 All versions, plus listed versions
5.15.0-1032.35
 None known
linux-riscv
Ubuntu:22.04:LTS
 All versions, plus listed versions
5.13.0-1004.45.13.0-1006.6+22.04.15.13.0-1007.7+22.04.15.13.0-1010.11+22.04.15.15.0-1004.4
Show 18 moreShow less
5.15.0-1005.55.15.0-1006.65.15.0-1007.75.15.0-1008.85.15.0-1011.125.15.0-1012.135.15.0-1014.165.15.0-1015.175.15.0-1016.185.15.0-1017.195.15.0-1018.215.15.0-1019.225.15.0-1020.235.15.0-1022.265.15.0-1023.275.15.0-1026.305.15.0-1027.315.15.0-1028.32
 None known
linux-riscv-5.19
Ubuntu:22.04:LTS
 All versions, plus listed versions
5.19.0-1012.13~22.04.15.19.0-1015.16~22.04.15.19.0-1016.17~22.04.15.19.0-1017.18~22.04.15.19.0-1018.19~22.04.15.19.0-1019.21~22.04.15.19.0-1020.22~22.04.15.19.0-1021.23~22.04.1
 None known
linux-riscv-6.5
Ubuntu:22.04:LTS
 All versions, plus listed versions
6.5.0-17.17.1.1~22.04.16.5.0-21.21.1~22.04.16.5.0-25.25.1~22.04.16.5.0-26.26.1~22.04.16.5.0-27.28.1~22.04.1
Show 5 moreShow less
6.5.0-28.29.1~22.04.16.5.0-35.35.1~22.04.16.5.0-40.40.1~22.04.16.5.0-42.42.1~22.04.16.5.0-45.45.1~22.04.1
 None known
linux-riscv-6.8
Ubuntu:22.04:LTS
 before 6.8.0-44.44.1~22.04.1, plus listed versions
6.8.0-38.38.1~22.04.16.8.0-39.39.1~22.04.16.8.0-40.40.1~22.04.16.8.0-41.41.1~22.04.1
6.8.0-44.44.1~22.04.1
linux-starfive-5.19
Ubuntu:22.04:LTS
 All versions, plus listed versions
5.19.0-1014.16~22.04.15.19.0-1015.17~22.04.15.19.0-1016.18~22.04.15.19.0-1017.19~22.04.15.19.0-1018.20~22.04.15.19.0-1019.21~22.04.15.19.0-1020.22~22.04.1
 None known
linux-starfive-6.2
Ubuntu:22.04:LTS
 All versions, plus listed versions
6.2.0-1006.7~22.04.16.2.0-1007.8~22.04.16.2.0-1009.10~22.04.1
 None known
linux-starfive-6.5
Ubuntu:22.04:LTS
 All versions, plus listed versions
6.5.0-1007.8~22.04.16.5.0-1008.9~22.04.16.5.0-1009.10~22.04.16.5.0-1010.11~22.04.16.5.0-1011.12~22.04.1
Show 6 moreShow less
6.5.0-1012.13~22.04.16.5.0-1014.15~22.04.16.5.0-1015.16~22.04.16.5.0-1016.17~22.04.16.5.0-1017.18~22.04.16.5.0-1018.19~22.04.1
 None known
linux-realtime-6.8
Ubuntu:Pro:Realtime:22.04:LTS
 before 6.8.1-1008.8~22.04.1, plus listed versions
6.8.1-1004.4~22.04.16.8.1-1005.5~22.04.26.8.1-1006.6~22.04.16.8.1-1007.7~22.04.1
6.8.1-1008.8~22.04.1
linux
Ubuntu:24.04:LTS
 before 6.8.0-44.44, plus listed versions
6.5.0-9.96.6.0-14.146.8.0-11.116.8.0-20.206.8.0-22.22
Show 8 moreShow less
6.8.0-28.286.8.0-31.316.8.0-35.356.8.0-36.366.8.0-38.386.8.0-39.396.8.0-40.406.8.0-41.41
6.8.0-44.44
linux-aws
Ubuntu:24.04:LTS
 before 6.8.0-1015.16, plus listed versions
6.5.0-1008.86.6.0-1001.16.8.0-1001.16.8.0-1006.66.8.0-1008.8
Show 6 moreShow less
6.8.0-1009.96.8.0-1010.106.8.0-1011.126.8.0-1012.136.8.0-1013.146.8.0-1014.15
6.8.0-1015.16
linux-azure
Ubuntu:24.04:LTS
 before 6.8.0-1014.16, plus listed versions
6.5.0-1007.76.6.0-1001.16.8.0-1001.16.8.0-1005.56.8.0-1006.6
Show 6 moreShow less
6.8.0-1007.76.8.0-1008.86.8.0-1009.96.8.0-1010.106.8.0-1012.146.8.0-1013.15
6.8.0-1014.16
linux-gcp
Ubuntu:24.04:LTS
 before 6.8.0-1014.16, plus listed versions
6.5.0-1007.76.6.0-1001.16.8.0-1002.26.8.0-1005.56.8.0-1006.6
Show 7 moreShow less
6.8.0-1007.76.8.0-1008.96.8.0-1009.106.8.0-1010.116.8.0-1011.126.8.0-1012.136.8.0-1013.14
6.8.0-1014.16
linux-gke
Ubuntu:24.04:LTS
 before 6.8.0-1010.13, plus listed versions
6.8.0-1003.56.8.0-1004.76.8.0-1005.86.8.0-1006.96.8.0-1007.106.8.0-1008.116.8.0-1009.12
6.8.0-1010.13
linux-ibm
Ubuntu:24.04:LTS
 before 6.8.0-1012.12, plus listed versions
6.5.0-1009.96.8.0-1001.16.8.0-1003.36.8.0-1004.46.8.0-1005.5
Show 6 moreShow less
6.8.0-1006.66.8.0-1007.76.8.0-1008.86.8.0-1009.96.8.0-1010.106.8.0-1011.11
6.8.0-1012.12
linux-lowlatency
Ubuntu:24.04:LTS
 before 6.8.0-44.44.1, plus listed versions
6.5.0-9.9.16.6.0-14.14.16.8.0-7.7.16.8.0-25.25.36.8.0-28.28.1
Show 7 moreShow less
6.8.0-31.31.16.8.0-35.35.16.8.0-36.36.16.8.0-38.38.16.8.0-39.39.16.8.0-40.40.16.8.0-41.41.1
6.8.0-44.44.1
linux-nvidia
Ubuntu:24.04:LTS
 before 6.8.0-1013.14, plus listed versions
6.8.0-1007.76.8.0-1008.86.8.0-1009.96.8.0-1010.106.8.0-1011.116.8.0-1012.12
6.8.0-1013.14
linux-nvidia-lowlatency
Ubuntu:24.04:LTS
 before 6.8.0-1013.14.1, plus listed versions
6.8.0-1009.9.16.8.0-1011.11.16.8.0-1012.12.1
6.8.0-1013.14.1
linux-oem-6.8
Ubuntu:24.04:LTS
 before 6.8.0-1012.12, plus listed versions
6.8.0-1003.36.8.0-1004.46.8.0-1005.56.8.0-1006.66.8.0-1007.7
Show 4 moreShow less
6.8.0-1008.86.8.0-1009.96.8.0-1010.106.8.0-1011.11
6.8.0-1012.12
linux-oracle
Ubuntu:24.04:LTS
 before 6.8.0-1012.12, plus listed versions
6.5.0-1010.106.6.0-1001.16.8.0-1001.16.8.0-1004.46.8.0-1005.5
Show 4 moreShow less
6.8.0-1006.66.8.0-1008.86.8.0-1010.106.8.0-1011.11
6.8.0-1012.12
linux-raspi
Ubuntu:24.04:LTS
 before 6.8.0-1011.12, plus listed versions
6.5.0-1005.76.7.0-1001.16.8.0-1001.16.8.0-1002.26.8.0-1003.3
Show 7 moreShow less
6.8.0-1004.46.8.0-1005.56.8.0-1006.66.8.0-1007.76.8.0-1008.86.8.0-1009.106.8.0-1010.11
6.8.0-1011.12
linux-riscv
Ubuntu:24.04:LTS
 before 6.8.0-44.44.1, plus listed versions
6.5.0-9.9.16.8.0-20.20.16.8.0-28.28.16.8.0-31.31.16.8.0-35.35.1
Show 5 moreShow less
6.8.0-36.36.16.8.0-38.38.16.8.0-39.39.16.8.0-40.40.16.8.0-41.41.1
6.8.0-44.44.1
linux-raspi-realtime
Ubuntu:Pro:Realtime:24.04:LTS
 before 6.8.0-2010.10, plus listed versions
6.7.0-2001.16.8.0-2001.16.8.0-2002.26.8.0-2004.46.8.0-2005.5
Show 4 moreShow less
6.8.0-2006.66.8.0-2007.76.8.0-2008.86.8.0-2009.9
6.8.0-2010.10
linux-realtime
Ubuntu:Pro:Realtime:24.04:LTS
 before 6.8.1-1008.8, plus listed versions
6.8.0-1008.196.8.1-1001.16.8.1-1002.26.8.1-1003.36.8.1-1004.46.8.1-1005.56.8.1-1006.66.8.1-1007.7
6.8.1-1008.8
linux-fips
Ubuntu:Pro:FIPS-updates:24.04:LTS
 before 6.8.0-78.78+fips1, plus listed versions
6.8.0-38.38+fips4
6.8.0-78.78+fips1
linux
Ubuntu:24.04:LTS
From an advisory covering 220 CVEs
 before 6.8.0-44.44, plus listed versions
6.5.0-9.96.6.0-14.146.8.0-11.116.8.0-20.206.8.0-22.22
Show 8 moreShow less
6.8.0-28.286.8.0-31.316.8.0-35.356.8.0-36.366.8.0-38.386.8.0-39.396.8.0-40.406.8.0-41.41
6.8.0-44.44
linux-aws
Ubuntu:24.04:LTS
From an advisory covering 220 CVEs
 before 6.8.0-1015.16, plus listed versions
6.5.0-1008.86.6.0-1001.16.8.0-1001.16.8.0-1006.66.8.0-1008.8
Show 6 moreShow less
6.8.0-1009.96.8.0-1010.106.8.0-1011.126.8.0-1012.136.8.0-1013.146.8.0-1014.15
6.8.0-1015.16
linux-gcp
Ubuntu:24.04:LTS
From an advisory covering 220 CVEs
 before 6.8.0-1014.16, plus listed versions
6.5.0-1007.76.6.0-1001.16.8.0-1002.26.8.0-1005.56.8.0-1006.6
Show 7 moreShow less
6.8.0-1007.76.8.0-1008.96.8.0-1009.106.8.0-1010.116.8.0-1011.126.8.0-1012.136.8.0-1013.14
6.8.0-1014.16
linux-gke
Ubuntu:24.04:LTS
From an advisory covering 220 CVEs
 before 6.8.0-1010.13, plus listed versions
6.8.0-1003.56.8.0-1004.76.8.0-1005.86.8.0-1006.96.8.0-1007.106.8.0-1008.116.8.0-1009.12
6.8.0-1010.13
linux-ibm
Ubuntu:24.04:LTS
From an advisory covering 220 CVEs
 before 6.8.0-1012.12, plus listed versions
6.5.0-1009.96.8.0-1001.16.8.0-1003.36.8.0-1004.46.8.0-1005.5
Show 6 moreShow less
6.8.0-1006.66.8.0-1007.76.8.0-1008.86.8.0-1009.96.8.0-1010.106.8.0-1011.11
6.8.0-1012.12
linux-lowlatency
Ubuntu:24.04:LTS
From an advisory covering 220 CVEs
 before 6.8.0-44.44.1, plus listed versions
6.5.0-9.9.16.6.0-14.14.16.8.0-7.7.16.8.0-25.25.36.8.0-28.28.1
Show 7 moreShow less
6.8.0-31.31.16.8.0-35.35.16.8.0-36.36.16.8.0-38.38.16.8.0-39.39.16.8.0-40.40.16.8.0-41.41.1
6.8.0-44.44.1
linux-oem-6.8
Ubuntu:24.04:LTS
From an advisory covering 220 CVEs
 before 6.8.0-1012.12, plus listed versions
6.8.0-1003.36.8.0-1004.46.8.0-1005.56.8.0-1006.66.8.0-1007.7
Show 4 moreShow less
6.8.0-1008.86.8.0-1009.96.8.0-1010.106.8.0-1011.11
6.8.0-1012.12
linux-oracle
Ubuntu:24.04:LTS
From an advisory covering 220 CVEs
 before 6.8.0-1012.12, plus listed versions
6.5.0-1010.106.6.0-1001.16.8.0-1001.16.8.0-1004.46.8.0-1005.5
Show 4 moreShow less
6.8.0-1006.66.8.0-1008.86.8.0-1010.106.8.0-1011.11
6.8.0-1012.12
linux-raspi
Ubuntu:24.04:LTS
From an advisory covering 220 CVEs
 before 6.8.0-1011.12, plus listed versions
6.5.0-1005.76.7.0-1001.16.8.0-1001.16.8.0-1002.26.8.0-1003.3
Show 7 moreShow less
6.8.0-1004.46.8.0-1005.56.8.0-1006.66.8.0-1007.76.8.0-1008.86.8.0-1009.106.8.0-1010.11
6.8.0-1011.12
linux-azure
Ubuntu:24.04:LTS
From an advisory covering 221 CVEs
 before 6.8.0-1014.16, plus listed versions
6.5.0-1007.76.6.0-1001.16.8.0-1001.16.8.0-1005.56.8.0-1006.6
Show 6 moreShow less
6.8.0-1007.76.8.0-1008.86.8.0-1009.96.8.0-1010.106.8.0-1012.146.8.0-1013.15
6.8.0-1014.16
linux-nvidia
Ubuntu:24.04:LTS
From an advisory covering 219 CVEs
 before 6.8.0-1013.14, plus listed versions
6.8.0-1007.76.8.0-1008.86.8.0-1009.96.8.0-1010.106.8.0-1011.116.8.0-1012.12
6.8.0-1013.14
linux-nvidia-lowlatency
Ubuntu:24.04:LTS
From an advisory covering 219 CVEs
 before 6.8.0-1013.14.1, plus listed versions
6.8.0-1009.9.16.8.0-1011.11.16.8.0-1012.12.1
6.8.0-1013.14.1
linux-nvidia-6.8
Ubuntu:22.04:LTS
From an advisory covering 219 CVEs
 before 6.8.0-1013.14~22.04.1, plus listed versions
6.8.0-1008.8~22.04.16.8.0-1009.9~22.04.16.8.0-1010.10~22.04.16.8.0-1011.11~22.04.16.8.0-1012.12~22.04.1
6.8.0-1013.14~22.04.1
linux-lowlatency-hwe-6.8
Ubuntu:22.04:LTS
From an advisory covering 222 CVEs
 before 6.8.0-44.44.1~22.04.1, plus listed versions
6.8.0-38.38.1~22.04.26.8.0-40.40.1~22.04.1
6.8.0-44.44.1~22.04.1
linux-hwe-6.8
Ubuntu:22.04:LTS
From an advisory covering 227 CVEs
 before 6.8.0-45.45~22.04.1, plus listed versions
6.8.0-38.38~22.04.16.8.0-39.39~22.04.16.8.0-40.40~22.04.3
6.8.0-45.45~22.04.1

History

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

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

In short

CVE-2024-40918 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 22nd percentile. Fixed in linux-lts 6.12.41-r0.

References

Show 194 moreShow less
This page doesn't list everything

Left out here: 352 versions, 89 references and the rest of 8 source descriptions. The JSON record has them.

Pages All vulnerabilities Browse Docs Sources Guide Get API key
MoveEnter Open