Every CVESearch/Get API key

CVE-2026-23077

mm/vma: fix anon_vma UAF on mremap() faulted, unfaulted merge

7.8 HighFix available

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

mm/vma: fix anon_vma UAF on mremap() faulted, unfaulted merge

Patch series "mm/vma: fix anon_vma UAF on mremap() faulted, unfaulted merge", v2.

Commit 879bca0a2c4f ("mm/vma: fix incorrectly disallowed anonymous VMA merges") introduced the ability to merge previously unavailable VMA merge scenarios.

However, it is handling merges incorrectly when it comes to mremap() of a faulted VMA adjacent to an unfaulted VMA. The issues arise in three cases:

  1. Previous VMA unfaulted:

           copied -----|
                       v
    
    

    |-----------|.............| | unfaulted |(faulted VMA)| |-----------|.............| prev

  2. Next VMA unfaulted:

           copied -----|
                       v
             |.............|-----------|
             |(faulted VMA)| unfaulted |
                 |.............|-----------|
                           next
    
    
  3. Both adjacent VMAs unfaulted:

           copied -----|
                       v
    
    

    |-----------|.............|-----------| | unfaulted |(faulted VMA)| unfaulted | |-----------|.............|-----------| prev next

This series fixes each of these cases, and introduces self tests to assert that the issues are corrected.

I also test a further case which was already handled, to assert that my changes continues to correctly handle it:

  1. prev unfaulted, next faulted:

           copied -----|
                       v
    
    

    |-----------|.............|-----------| | unfaulted |(faulted VMA)| faulted | |-----------|.............|-----------| prev next

This bug was discovered via a syzbot report, linked to in the first patch in the series, I confirmed that this series fixes the bug.

I also discovered that we are failing to check that the faulted VMA was not forked when merging a copied VMA in cases 1-3 above, an issue this series also addresses.

I also added self tests to assert that this is resolved (and confirmed that the tests failed prior to this).

I also cleaned up vma_expand() as part of this work, renamed vma_had_uncowed_parents() to vma_is_fork_child() as the previous name was unduly confusing, and simplified the comments around this function.

This patch (of 4):

Commit 879bca0a2c4f ("mm/vma: fix incorrectly disallowed anonymous VMA merges") introduced the ability to merge previously unavailable VMA merge scenarios.

The key piece of logic introduced was the ability to merge a faulted VMA immediately next to an unfaulted VMA, which relies upon dup_anon_vma() to correctly handle anon_vma state.

In the case of the merge of an existing VMA (that is changing properties of a VMA and then merging if those properties are shared by adjacent VMAs), dup_anon_vma() is invoked correctly.

However in the case of the merge of a new VMA, a corner case peculiar to mremap() was missed.

The issue is that vma_expand() only performs dup_anon_vma() if the target (the VMA that will ultimately become the merged VMA): is not the next VMA, i.e. the one that appears after the range in which the new VMA is to be established.

A key insight here is that in all other cases other than mremap(), a new VMA merge either expands an existing VMA, meaning that the target VMA will be that VMA, or would have anon_vma be NULL.

Specifically:

  • __mmap_region() - no anon_vma in place, initial mapping.
  • do_brk_flags() - expanding an existing VMA.
  • vma_merge_extend() - expanding an existing VMA.
  • relocate_vma_down() - no anon_vma in place, initial mapping.

In addition, we are in the unique situation of needing to duplicate anon_vma state from a VMA that is neither the previous or next VMA being merged with.

dup_anon_vma() deals exclusively with the target=unfaulted, src=faulted case. This leaves four possibilities, in each case where the copied VMA is faulted:

  1. Previous VMA unfaulted:

           copied -----|
    

---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.16%Up 0.1 points since Feb 5, 2026
90%50%10%1%

What each source reports

CVE List Score used7.8

mm/vma: fix anon_vma UAF on mremap() faulted, unfaulted merge

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

mm/vma: fix anon_vma UAF on mremap() faulted, unfaulted merge

Patch series "mm/vma: fix anon_vma UAF on mremap() faulted, unfaulted merge", v2.

Commit 879bca0a2c4f ("mm/vma: fix incorrectly disallowed anonymous VMA merges") introduced the ability to merge previously unavailable VMA merge scenarios.

However, it is handling merges incorrectly when it comes to mremap() of a faulted VMA adjacent to an unfaulted VMA. The issues arise in three cases:

  1. Previous VMA unfaulted:

           copied -----|
                       v
    
    

    |-----------|.............| | unfaulted |(faulted VMA)| |-----------|.............| prev

  2. Next VMA unfaulted:

           copied -----|
                       v
             |.............|-----------|
             |(faulted VMA)| unfaulted |
                 |.............|-----------|
                           next
    
    
  3. Both adjacent VMAs unfaulted:

           copied -----|
                       v
    
    

    |-----------|.............|-----------| | unfaulted |(faulted VMA)| unfaulted | |-----------|.............|-----------| prev next

This series fixes each of these cases, and introduces self tests to assert that the issues are corrected.

I also test a further case which was already handled, to assert that my changes continues to correctly handle it:

  1. prev unfaulted, next faulted:

           copied -----|
                       v
    
    

    |-----------|.............|-----------| | unfaulted |(faulted VMA)| faulted | |-----------|.............|-----------| prev next

This bug was discovered via a syzbot report, linked to in the first patch in the series, I confirmed that this series fixes the bug.

I also discovered that we are failing to check that the faulted VMA was not forked when merging a copied VMA in cases 1-3 above, an issue this series also addresses.

I also added self tests to assert that this is resolved (and confirmed that the tests failed prior to this).

I also cleaned up vma_expand() as part of this work, renamed vma_had_uncowed_parents() to vma_is_fork_child() as the previous name was unduly confusing, and simplified the comments around this function.

This patch (of 4):

Commit 879bca0a2c4f ("mm/vma: fix incorrectly disallowed anonymous VMA merges") introduced the ability to merge previously unavailable VMA merge scenarios.

The key piece of logic introduced was the ability to merge a faulted VMA immediately next to an unfaulted VMA, which relies upon dup_anon_vma() to correctly handle anon_vma state.

In the case of the merge of an existing VMA (that is changing properties of a VMA and then merging if those properties are shared by adjacent VMAs), dup_anon_vma() is invoked correctly.

However in the case of the merge of a new VMA, a corner case peculiar to mremap() was missed.

The issue is that vma_expand() only performs dup_anon_vma() if the target (the VMA that will ultimately become the merged VMA): is not the next VMA, i.e. the one that appears after the range in which the new VMA is to be established.

A key insight here is that in all other cases other than mremap(), a new VMA merge either expands an existing VMA, meaning that the target VMA will be that VMA, or would have anon_vma be NULL.

Specifically:

  • __mmap_region() - no anon_vma in place, initial mapping.
  • do_brk_flags() - expanding an existing VMA.
  • vma_merge_extend() - expanding an existing VMA.
  • relocate_vma_down() - no anon_vma in place, initial mapping.

In addition, we are in the unique situation of needing to duplicate anon_vma state from a VMA that is neither the previous or next VMA being merged with.

dup_anon_vma() deals exclusively with the target=unfaulted, src=faulted case. This leaves four possibilities, in each case where the copied VMA is faulted:

  1. Previous VMA unfaulted:

           copied -----|
    

---truncated---

Record
CVE-2026-23077
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-2026-54667.8

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

mm/vma: fix anon_vma UAF on mremap() faulted, unfaulted merge

Patch series "mm/vma: fix anon_vma UAF on mremap() faulted, unfaulted merge", v2.

Commit 879bca0a2c4f ("mm/vma: fix incorrectly disallowed anonymous VMA merges") introduced the ability to merge previously unavailable VMA merge scenarios.

However, it is handling merges incorrectly when it comes to mremap() of a faulted VMA adjacent to an unfaulted VMA. The issues arise in three cases:

  1. Previous VMA unfaulted:

           copied -----|
                       v
    
    

    |-----------|.............| | unfaulted |(faulted VMA)| |-----------|.............| prev

  2. Next VMA unfaulted:

           copied -----|
                       v
             |.............|-----------|
             |(faulted VMA)| unfaulted |
                 |.............|-----------|
                           next
    
    
  3. Both adjacent VMAs unfaulted:

           copied -----|
                       v
    
    

    |-----------|.............|-----------| | unfaulted |(faulted VMA)| unfaulted | |-----------|.............|-----------| prev next

This series fixes each of these cases, and introduces self tests to assert that the issues are corrected.

I also test a further case which was already handled, to assert that my changes continues to correctly handle it:

  1. prev unfaulted, next faulted:

           copied -----|
                       v
    
    

    |-----------|.............|-----------| | unfaulted |(faulted VMA)| faulted | |-----------|.............|-----------| prev next

This bug was discovered via a syzbot report, linked to in the first patch in the series, I confirmed that this series fixes the bug.

I also discovered that we are failing to check that the faulted VMA was not forked when merging a copied VMA in cases 1-3 above, an issue this series also addresses.

I also added self tests to assert that this is resolved (and confirmed that the tests failed prior to this).

I also cleaned up vma_expand() as part of this work, renamed vma_had_uncowed_parents() to vma_is_fork_child() as the previous name was unduly confusing, and simplified the comments around this function.

This patch (of 4):

Commit 879bca0a2c4f ("mm/vma: fix incorrectly disallowed anonymous VMA merges") introduced the ability to merge previously unavailable VMA merge scenarios.

The key piece of logic introduced was the ability to merge a faulted VMA immediately next to an unfaulted VMA, which relies upon dup_anon_vma() to correctly handle anon_vma state.

In the case of the merge of an existing VMA (that is changing properties of a VMA and then merging if those properties are shared by adjacent VMAs), dup_anon_vma() is invoked correctly.

However in the case of the merge of a new VMA, a corner case peculiar to mremap() was missed.

The issue is that vma_expand() only performs dup_anon_vma() if the target (the VMA that will ultimately become the merged VMA): is not the next VMA, i.e. the one that appears after the range in which the new VMA is to be established.

A key insight here is that in all other cases other than mremap(), a new VMA merge either expands an existing VMA, meaning that the target VMA will be that VMA, or would have anon_vma be NULL.

Specifically:

  • __mmap_region() - no anon_vma in place, initial mapping.
  • do_brk_flags() - expanding an existing VMA.
  • vma_merge_extend() - expanding an existing VMA.
  • relocate_vma_down() - no anon_vma in place, initial mapping.

In addition, we are in the unique situation of needing to duplicate anon_vma state from a VMA that is neither the previous or next VMA being merged with.

dup_anon_vma() deals exclusively with the target=unfaulted, src=faulted case. This leaves four possibilities, in each case where the copied VMA is faulted:

  1. Previous VMA unfaulted:

           copied -----|
    

---truncated---

Record
EUVD-2026-5466
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-jfpv-p5jh-pjp77.8

In the Linux kernel, the following vulnerability has been resolved: mm/vma: fix anon_vma UAF on...

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

mm/vma: fix anon_vma UAF on mremap() faulted, unfaulted merge

Patch series "mm/vma: fix anon_vma UAF on mremap() faulted, unfaulted merge", v2.

Commit 879bca0a2c4f ("mm/vma: fix incorrectly disallowed anonymous VMA merges") introduced the ability to merge previously unavailable VMA merge scenarios.

However, it is handling merges incorrectly when it comes to mremap() of a faulted VMA adjacent to an unfaulted VMA. The issues arise in three cases:

  1. Previous VMA unfaulted:

           copied -----|
                       v
    
    

    |-----------|.............| | unfaulted |(faulted VMA)| |-----------|.............| prev

  2. Next VMA unfaulted:

           copied -----|
                       v
             |.............|-----------|
             |(faulted VMA)| unfaulted |
                 |.............|-----------|
                           next
    
    
  3. Both adjacent VMAs unfaulted:

           copied -----|
                       v
    
    

    |-----------|.............|-----------| | unfaulted |(faulted VMA)| unfaulted | |-----------|.............|-----------| prev next

This series fixes each of these cases, and introduces self tests to assert that the issues are corrected.

I also test a further case which was already handled, to assert that my changes continues to correctly handle it:

  1. prev unfaulted, next faulted:

           copied -----|
                       v
    
    

    |-----------|.............|-----------| | unfaulted |(faulted VMA)| faulted | |-----------|.............|-----------| prev next

This bug was discovered via a syzbot report, linked to in the first patch in the series, I confirmed that this series fixes the bug.

I also discovered that we are failing to check that the faulted VMA was not forked when merging a copied VMA in cases 1-3 above, an issue this series also addresses.

I also added self tests to assert that this is resolved (and confirmed that the tests failed prior to this).

I also cleaned up vma_expand() as part of this work, renamed vma_had_uncowed_parents() to vma_is_fork_child() as the previous name was unduly confusing, and simplified the comments around this function.

This patch (of 4):

Commit 879bca0a2c4f ("mm/vma: fix incorrectly disallowed anonymous VMA merges") introduced the ability to merge previously unavailable VMA merge scenarios.

The key piece of logic introduced was the ability to merge a faulted VMA immediately next to an unfaulted VMA, which relies upon dup_anon_vma() to correctly handle anon_vma state.

In the case of the merge of an existing VMA (that is changing properties of a VMA and then merging if those properties are shared by adjacent VMAs), dup_anon_vma() is invoked correctly.

However in the case of the merge of a new VMA, a corner case peculiar to mremap() was missed.

The issue is that vma_expand() only performs dup_anon_vma() if the target (the VMA that will ultimately become the merged VMA): is not the next VMA, i.e. the one that appears after the range in which the new VMA is to be established.

A key insight here is that in all other cases other than mremap(), a new VMA merge either expands an existing VMA, meaning that the target VMA will be that VMA, or would have anon_vma be NULL.

Specifically:

  • __mmap_region() - no anon_vma in place, initial mapping.
  • do_brk_flags() - expanding an existing VMA.
  • vma_merge_extend() - expanding an existing VMA.
  • relocate_vma_down() - no anon_vma in place, initial mapping.

In addition, we are in the unique situation of needing to duplicate anon_vma state from a VMA that is neither the previous or next VMA being merged with.

dup_anon_vma() deals exclusively with the target=unfaulted, src=faulted case. This leaves four possibilities, in each case where the copied VMA is faulted:

  1. Previous VMA unfaulted:

           copied -----|
    

---truncated---

Record
GHSA-jfpv-p5jh-pjp7
CVSS 3.1
7.8 HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Weakness
CWE-416
Updated
2026-11-02
NVD7.8

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

mm/vma: fix anon_vma UAF on mremap() faulted, unfaulted merge

Patch series "mm/vma: fix anon_vma UAF on mremap() faulted, unfaulted merge", v2.

Commit 879bca0a2c4f ("mm/vma: fix incorrectly disallowed anonymous VMA merges") introduced the ability to merge previously unavailable VMA merge scenarios.

However, it is handling merges incorrectly when it comes to mremap() of a faulted VMA adjacent to an unfaulted VMA. The issues arise in three cases:

  1. Previous VMA unfaulted:

           copied -----|
                       v
    
    

    |-----------|.............| | unfaulted |(faulted VMA)| |-----------|.............| prev

  2. Next VMA unfaulted:

           copied -----|
                       v
             |.............|-----------|
             |(faulted VMA)| unfaulted |
                 |.............|-----------|
                           next
    
    
  3. Both adjacent VMAs unfaulted:

           copied -----|
                       v
    
    

    |-----------|.............|-----------| | unfaulted |(faulted VMA)| unfaulted | |-----------|.............|-----------| prev next

This series fixes each of these cases, and introduces self tests to assert that the issues are corrected.

I also test a further case which was already handled, to assert that my changes continues to correctly handle it:

  1. prev unfaulted, next faulted:

           copied -----|
                       v
    
    

    |-----------|.............|-----------| | unfaulted |(faulted VMA)| faulted | |-----------|.............|-----------| prev next

This bug was discovered via a syzbot report, linked to in the first patch in the series, I confirmed that this series fixes the bug.

I also discovered that we are failing to check that the faulted VMA was not forked when merging a copied VMA in cases 1-3 above, an issue this series also addresses.

I also added self tests to assert that this is resolved (and confirmed that the tests failed prior to this).

I also cleaned up vma_expand() as part of this work, renamed vma_had_uncowed_parents() to vma_is_fork_child() as the previous name was unduly confusing, and simplified the comments around this function.

This patch (of 4):

Commit 879bca0a2c4f ("mm/vma: fix incorrectly disallowed anonymous VMA merges") introduced the ability to merge previously unavailable VMA merge scenarios.

The key piece of logic introduced was the ability to merge a faulted VMA immediately next to an unfaulted VMA, which relies upon dup_anon_vma() to correctly handle anon_vma state.

In the case of the merge of an existing VMA (that is changing properties of a VMA and then merging if those properties are shared by adjacent VMAs), dup_anon_vma() is invoked correctly.

However in the case of the merge of a new VMA, a corner case peculiar to mremap() was missed.

The issue is that vma_expand() only performs dup_anon_vma() if the target (the VMA that will ultimately become the merged VMA): is not the next VMA, i.e. the one that appears after the range in which the new VMA is to be established.

A key insight here is that in all other cases other than mremap(), a new VMA merge either expands an existing VMA, meaning that the target VMA will be that VMA, or would have anon_vma be NULL.

Specifically:

  • __mmap_region() - no anon_vma in place, initial mapping.
  • do_brk_flags() - expanding an existing VMA.
  • vma_merge_extend() - expanding an existing VMA.
  • relocate_vma_down() - no anon_vma in place, initial mapping.

In addition, we are in the unique situation of needing to duplicate anon_vma state from a VMA that is neither the previous or next VMA being merged with.

dup_anon_vma() deals exclusively with the target=unfaulted, src=faulted case. This leaves four possibilities, in each case where the copied VMA is faulted:

  1. Previous VMA unfaulted:

           copied -----|
    

---truncated---

Record
CVE-2026-23077
CVSS 3.1
7.8 HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Weakness
CWE-416
Updated
2026-11-02
OSVBELL-CVE-2026-230777.8
Record
BELL-CVE-2026-23077
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
OSV7.8

mm/vma: fix anon_vma UAF on mremap() faulted, unfaulted merge

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

mm/vma: fix anon_vma UAF on mremap() faulted, unfaulted merge

Patch series "mm/vma: fix anon_vma UAF on mremap() faulted, unfaulted merge", v2.

Commit 879bca0a2c4f ("mm/vma: fix incorrectly disallowed anonymous VMA merges") introduced the ability to merge previously unavailable VMA merge scenarios.

However, it is handling merges incorrectly when it comes to mremap() of a faulted VMA adjacent to an unfaulted VMA. The issues arise in three cases:

  1. Previous VMA unfaulted:

           copied -----|
                       v
    
    

    |-----------|.............| | unfaulted |(faulted VMA)| |-----------|.............| prev

  2. Next VMA unfaulted:

           copied -----|
                       v
             |.............|-----------|
             |(faulted VMA)| unfaulted |
                 |.............|-----------|
                           next
    
    
  3. Both adjacent VMAs unfaulted:

           copied -----|
                       v
    
    

    |-----------|.............|-----------| | unfaulted |(faulted VMA)| unfaulted | |-----------|.............|-----------| prev next

This series fixes each of these cases, and introduces self tests to assert that the issues are corrected.

I also test a further case which was already handled, to assert that my changes continues to correctly handle it:

  1. prev unfaulted, next faulted:

           copied -----|
                       v
    
    

    |-----------|.............|-----------| | unfaulted |(faulted VMA)| faulted | |-----------|.............|-----------| prev next

This bug was discovered via a syzbot report, linked to in the first patch in the series, I confirmed that this series fixes the bug.

I also discovered that we are failing to check that the faulted VMA was not forked when merging a copied VMA in cases 1-3 above, an issue this series also addresses.

I also added self tests to assert that this is resolved (and confirmed that the tests failed prior to this).

I also cleaned up vma_expand() as part of this work, renamed vma_had_uncowed_parents() to vma_is_fork_child() as the previous name was unduly confusing, and simplified the comments around this function.

This patch (of 4):

Commit 879bca0a2c4f ("mm/vma: fix incorrectly disallowed anonymous VMA merges") introduced the ability to merge previously unavailable VMA merge scenarios.

The key piece of logic introduced was the ability to merge a faulted VMA immediately next to an unfaulted VMA, which relies upon dup_anon_vma() to correctly handle anon_vma state.

In the case of the merge of an existing VMA (that is changing properties of a VMA and then merging if those properties are shared by adjacent VMAs), dup_anon_vma() is invoked correctly.

However in the case of the merge of a new VMA, a corner case peculiar to mremap() was missed.

The issue is that vma_expand() only performs dup_anon_vma() if the target (the VMA that will ultimately become the merged VMA): is not the next VMA, i.e. the one that appears after the range in which the new VMA is to be established.

A key insight here is that in all other cases other than mremap(), a new VMA merge either expands an existing VMA, meaning that the target VMA will be that VMA, or would have anon_vma be NULL.

Specifically:

  • __mmap_region() - no anon_vma in place, initial mapping.
  • do_brk_flags() - expanding an existing VMA.
  • vma_merge_extend() - expanding an existing VMA.
  • relocate_vma_down() - no anon_vma in place, initial mapping.

In addition, we are in the unique situation of needing to duplicate anon_vma state from a VMA that is neither the previous or next VMA being merged with.

dup_anon_vma() deals exclusively with the target=unfaulted, src=faulted case. This leaves four possibilities, in each case where the copied VMA is faulted:

  1. Previous VMA unfaulted:

           copied -----|
    

---truncated---

Record
CVE-2026-23077
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 8 moreShow less
OSVDEBIAN-CVE-2026-230777.8

In the Linux kernel, the following vulnerability has been resolved: mm/vma: fix anon_vma UAF on mremap() faulted, unfaulted merge Patch series "mm/vma: fix anon_vma UAF on mremap() faulted, unfaulted merge", v2. Commit 879bca0a2c4f ("mm/vma: fix incorrectly disallowed anonymous VMA merges") introduced the ability to merge previously unavailable VMA merge scenarios. However, it is handling merges incorrectly when it comes to mremap() of a faulted VMA adjacent to an unfaulted VMA. The issues arise in three cases: 1. Previous VMA unfaulted: copied -----| v |-----------|.............| | unfaulted |(faulted VMA)| |-----------|.............| prev 2. Next VMA unfaulted: copied -----| v |.............|-----------| |(faulted VMA)| unfaulted | |.............|-----------| next 3. Both adjacent VMAs unfaulted: copied -----| v |-----------|.............|-----------| | unfaulted |(faulted VMA)| unfaulted | |-----------|.............|-----------| prev next This series fixes each of these cases, and introduces self tests to assert that the issues are corrected. I also test a further case which was already handled, to assert that my changes continues to correctly handle it: 4. prev unfaulted, next faulted: copied -----| v |-----------|.............|-----------| | unfaulted |(faulted VMA)| faulted | |-----------|.............|-----------| prev next This bug was discovered via a syzbot report, linked to in the first patch in the series, I confirmed that this series fixes the bug. I also discovered that we are failing to check that the faulted VMA was not forked when merging a copied VMA in cases 1-3 above, an issue this series also addresses. I also added self tests to assert that this is resolved (and confirmed that the tests failed prior to this). I also cleaned up vma_expand() as part of this work, renamed vma_had_uncowed_parents() to vma_is_fork_child() as the previous name was unduly confusing, and simplified the comments around this function. This patch (of 4): Commit 879bca0a2c4f ("mm/vma: fix incorrectly disallowed anonymous VMA merges") introduced the ability to merge previously unavailable VMA merge scenarios. The key piece of logic introduced was the ability to merge a faulted VMA immediately next to an unfaulted VMA, which relies upon dup_anon_vma() to correctly handle anon_vma state. In the case of the merge of an existing VMA (that is changing properties of a VMA and then merging if those properties are shared by adjacent VMAs), dup_anon_vma() is invoked correctly. However in the case of the merge of a new VMA, a corner case peculiar to mremap() was missed. The issue is that vma_expand() only performs dup_anon_vma() if the target (the VMA that will ultimately become the merged VMA): is not the next VMA, i.e. the one that appears after the range in which the new VMA is to be established. A key insight here is that in all other cases other than mremap(), a new VMA merge either expands an existing VMA, meaning that the target VMA will be that VMA, or would have anon_vma be NULL. Specifically: * __mmap_region() - no anon_vma in place, initial mapping. * do_brk_flags() - expanding an existing VMA. * vma_merge_extend() - expanding an existing VMA. * relocate_vma_down() - no anon_vma in place, initial mapping. In addition, we are in the unique situation of needing to duplicate anon_vma state from a VMA that is neither the previous or next VMA being merged with. dup_anon_vma() deals exclusively with the target=unfaulted, src=faulted case. This leaves four possibilities, in each case where the copied VMA is faulted: 1. Previous VMA unfaulted: copied -----| ---truncated---

Record
DEBIAN-CVE-2026-23077
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
OSVUBUNTU-CVE-2026-230777.3

In the Linux kernel, the following vulnerability has been resolved: mm/vma: fix anon_vma UAF on mremap() faulted, unfaulted merge Patch series "mm/vma: fix anon_vma UAF on mremap() faulted, unfaulted merge", v2. Commit 879bca0a2c4f ("mm/vma: fix incorrectly disallowed anonymous VMA merges") introduced the ability to merge previously unavailable VMA merge scenarios. However, it is handling merges incorrectly when it comes to mremap() of a faulted VMA adjacent to an unfaulted VMA. The issues arise in three cases: 1. Previous VMA unfaulted: copied -----| v |-----------|.............| | unfaulted |(faulted VMA)| |-----------|.............| prev 2. Next VMA unfaulted: copied -----| v |.............|-----------| |(faulted VMA)| unfaulted | |.............|-----------| next 3. Both adjacent VMAs unfaulted: copied -----| v |-----------|.............|-----------| | unfaulted |(faulted VMA)| unfaulted | |-----------|.............|-----------| prev next This series fixes each of these cases, and introduces self tests to assert that the issues are corrected. I also test a further case which was already handled, to assert that my changes continues to correctly handle it: 4. prev unfaulted, next faulted: copied -----| v |-----------|.............|-----------| | unfaulted |(faulted VMA)| faulted | |-----------|.............|-----------| prev next This bug was discovered via a syzbot report, linked to in the first patch in the series, I confirmed that this series fixes the bug. I also discovered that we are failing to check that the faulted VMA was not forked when merging a copied VMA in cases 1-3 above, an issue this series also addresses. I also added self tests to assert that this is resolved (and confirmed that the tests failed prior to this). I also cleaned up vma_expand() as part of this work, renamed vma_had_uncowed_parents() to vma_is_fork_child() as the previous name was unduly confusing, and simplified the comments around this function. This patch (of 4): Commit 879bca0a2c4f ("mm/vma: fix incorrectly disallowed anonymous VMA merges") introduced the ability to merge previously unavailable VMA merge scenarios. The key piece of logic introduced was the ability to merge a faulted VMA immediately next to an unfaulted VMA, which relies upon dup_anon_vma() to correctly handle anon_vma state. In the case of the merge of an existing VMA (that is changing properties of a VMA and then merging if those properties are shared by adjacent VMAs), dup_anon_vma() is invoked correctly. However in the case of the merge of a new VMA, a corner case peculiar to mremap() was missed. The issue is that vma_expand() only performs dup_anon_vma() if the target (the VMA that will ultimately become the merged VMA): is not the next VMA, i.e. the one that appears after the range in which the new VMA is to be established. A key insight here is that in all other cases other than mremap(), a new VMA merge either expands an existing VMA, meaning that the target VMA will be that VMA, or would have anon_vma be NULL. Specifically: * __mmap_region() - no anon_vma in place, initial mapping. * do_brk_flags() - expanding an existing VMA. * vma_merge_extend() - expanding an existing VMA. * relocate_vma_down() - no anon_vma in place, initial mapping. In addition, we are in the unique situation of needing to duplicate anon_vma state from a VMA that is neither the previous or next VMA being merged with. dup_anon_vma() deals exclusively with the target=unfaulted, src=faulted case. This leaves four possibilities, in each case where the copied VMA is faulted: 1. Previous VMA unfaulted: copied -----| ---truncated---

Record
UBUNTU-CVE-2026-23077
CVSS 4.0
7.3 HighCVSS:4.0/AV:L/AC:H/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
CVSS 3.1
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-8570-1No score

linux-gcp-6.17, linux-realtime-6.17 vulnerabilities

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

  • Foo-over-UDP (FOU);
  • ARM64 architecture;
  • x86 architecture;
  • Block layer subsystem;
  • Drivers core;
  • Null block device driver;
  • Bluetooth drivers;
  • Counter interface drivers;
  • DMA engine subsystem;
  • DPLL subsystem;
  • GPIO subsystem;
  • GPU drivers;
  • I2C subsystem;
  • IIO ADC drivers;
  • IIO subsystem;
  • On-Chip Interconnect management framework;
  • IOMMU subsystem;
  • IRQ chip drivers;
  • Modular ISDN driver;
  • LED subsystem;
  • Multiple devices driver;
  • UACCE accelerator framework;
  • MMC subsystem;
  • Ethernet bonding driver;
  • Network drivers;
  • Mellanox network drivers;
  • NVME drivers;
  • Device tree and open firmware driver;
  • PHY drivers;
  • x86 platform drivers;
  • i.MX PM domains;
  • SCSI subsystem;
  • SLIMbus drivers;
  • SPI subsystem;
  • TTY drivers;
  • USB Host Controller drivers;
  • W1 Dallas's 1-wire bus driver;
  • Xen hypervisor drivers;
  • BTRFS file system;
  • EFI Variable file system;
  • Ext4 file system;
  • File systems infrastructure;
  • FUSE (File system in Userspace);
  • Network file systems library;
  • Network file system (NFS) client;
  • Network file system (NFS) server daemon;
  • SMB network file system;
  • Memory Management;
  • Memory management;
  • Scheduler infrastructure;
  • Tracing infrastructure;
  • Netfilter;
  • NFC subsystem;
  • io_uring subsystem;
  • Perf events;
  • Hibernation control;
  • Timer subsystem;
  • BPF subsystem;
  • Floating proportions library;
  • Bluetooth subsystem;
  • CAN network layer;
  • Ceph Core library;
  • Networking core;
  • IPv4 networking;
  • IPv6 networking;
  • L2TP protocol;
  • MAC80211 subsystem;
  • Multipath TCP;
  • NET/ROM layer;
  • RxRPC session sockets;
  • Network traffic control;
  • SCTP protocol;
  • VMware vSockets driver;
  • Wireless networking;
  • ALSA AC97 driver;
  • Creative Sound Blaster X-Fi driver;
  • Texas InstrumentS Audio (ASoC/HDA) drivers;
  • USB sound devices; (CVE-2025-71158, CVE-2025-71160, CVE-2025-71161, CVE-2025-71162, CVE-2025-71163, CVE-2025-71180, CVE-2025-71182, CVE-2025-71183, CVE-2025-71184, CVE-2025-71185, CVE-2025-71186, CVE-2025-71187, CVE-2025-71188, CVE-2025-71189, CVE-2025-71190, CVE-2025-71191, CVE-2025-71192, CVE-2025-71193, CVE-2025-71194, CVE-2025-71195, CVE-2025-71196, CVE-2025-71197, CVE-2025-71198, CVE-2025-71199, CVE-2025-71200, CVE-2025-71201, CVE-2026-22976, CVE-2026-22977, CVE-2026-22978, CVE-2026-22979, CVE-2026-22980, CVE-2026-22981, CVE-2026-22982, CVE-2026-22985, CVE-2026-22986, CVE-2026-22987, CVE-2026-22989, CVE-2026-22990, CVE-2026-22991, CVE-2026-22992, CVE-2026-22993, CVE-2026-22994, CVE-2026-22996, CVE-2026-22997, CVE-2026-22998, CVE-2026-22999, CVE-2026-23000, CVE-2026-23001, CVE-2026-23002, CVE-2026-23003, CVE-2026-23004, CVE-2026-23005, CVE-2026-23006, CVE-2026-23007, CVE-2026-23008, CVE-2026-23009, CVE-2026-23010, CVE-2026-23011, CVE-2026-23012, CVE-2026-23013, CVE-2026-23014, CVE-2026-23015, CVE-2026-23017, CVE-2026-23018, CVE-2026-23019, CVE-2026-23020, CVE-2026-23021, CVE-2026-23022, CVE-2026-23023, CVE-2026-23024, CVE-2026-23025, CVE-2026-23026, CVE-2026-23030, CVE-2026-23031, CVE-2026-23032, CVE-2026-23033, CVE-2026-23034, CVE-2026-23035, CVE-2026-23036, CVE-2026-23037, CVE-2026-23038, CVE-2026-23042, CVE-2026-23044, CVE-2026-23045, CVE-2026-23046, CVE-2026-23047, CVE-2026-23049, CVE-2026-23050, CVE-2026-23051, CVE-2026-23052, CVE-2026-23053, CVE-2026-23054, CVE-2026-23055, CVE-2026-23056, CVE-2026-23057, CVE-2026-23058, CVE-2026-23059, CVE-2026-23061, CVE-2026-23062, CVE-2026-23063, CVE-2026-23064, CVE-2026-23065, CVE-2026-23066, CVE-2026-23067, CVE-2026-23068, CVE-2026-23069, CVE-2026-23070, CVE-2026-23071, CVE-2026-23072, CVE-2026-23073, CVE-2026-23075, CVE-2026-23076, CVE-2026-23077, CVE-2026-23078, CVE-2026-23079,…
Record
USN-8570-1
Updated
2026-11-06
OSVUSN-8570-2No score

linux-oracle-6.17 vulnerabilities

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

  • Foo-over-UDP (FOU);
  • ARM64 architecture;
  • x86 architecture;
  • Block layer subsystem;
  • Drivers core;
  • Null block device driver;
  • Bluetooth drivers;
  • Counter interface drivers;
  • DMA engine subsystem;
  • DPLL subsystem;
  • GPIO subsystem;
  • GPU drivers;
  • I2C subsystem;
  • IIO ADC drivers;
  • IIO subsystem;
  • On-Chip Interconnect management framework;
  • IOMMU subsystem;
  • IRQ chip drivers;
  • Modular ISDN driver;
  • LED subsystem;
  • Multiple devices driver;
  • UACCE accelerator framework;
  • MMC subsystem;
  • Ethernet bonding driver;
  • Network drivers;
  • Mellanox network drivers;
  • NVME drivers;
  • Device tree and open firmware driver;
  • PHY drivers;
  • x86 platform drivers;
  • i.MX PM domains;
  • SCSI subsystem;
  • SLIMbus drivers;
  • SPI subsystem;
  • TTY drivers;
  • USB Host Controller drivers;
  • W1 Dallas's 1-wire bus driver;
  • Xen hypervisor drivers;
  • BTRFS file system;
  • EFI Variable file system;
  • Ext4 file system;
  • File systems infrastructure;
  • FUSE (File system in Userspace);
  • Network file systems library;
  • Network file system (NFS) client;
  • Network file system (NFS) server daemon;
  • SMB network file system;
  • Memory Management;
  • Memory management;
  • Scheduler infrastructure;
  • Tracing infrastructure;
  • Netfilter;
  • NFC subsystem;
  • io_uring subsystem;
  • Perf events;
  • Hibernation control;
  • Timer subsystem;
  • BPF subsystem;
  • Floating proportions library;
  • Bluetooth subsystem;
  • CAN network layer;
  • Ceph Core library;
  • Networking core;
  • IPv4 networking;
  • IPv6 networking;
  • L2TP protocol;
  • MAC80211 subsystem;
  • Multipath TCP;
  • NET/ROM layer;
  • RxRPC session sockets;
  • Network traffic control;
  • SCTP protocol;
  • VMware vSockets driver;
  • Wireless networking;
  • ALSA AC97 driver;
  • Creative Sound Blaster X-Fi driver;
  • Texas InstrumentS Audio (ASoC/HDA) drivers;
  • USB sound devices; (CVE-2025-71158, CVE-2025-71160, CVE-2025-71161, CVE-2025-71162, CVE-2025-71163, CVE-2025-71180, CVE-2025-71182, CVE-2025-71183, CVE-2025-71184, CVE-2025-71185, CVE-2025-71186, CVE-2025-71187, CVE-2025-71188, CVE-2025-71189, CVE-2025-71190, CVE-2025-71191, CVE-2025-71192, CVE-2025-71193, CVE-2025-71194, CVE-2025-71195, CVE-2025-71196, CVE-2025-71197, CVE-2025-71198, CVE-2025-71199, CVE-2025-71200, CVE-2025-71201, CVE-2026-22976, CVE-2026-22977, CVE-2026-22978, CVE-2026-22979, CVE-2026-22980, CVE-2026-22981, CVE-2026-22982, CVE-2026-22985, CVE-2026-22986, CVE-2026-22987, CVE-2026-22989, CVE-2026-22990, CVE-2026-22991, CVE-2026-22992, CVE-2026-22993, CVE-2026-22994, CVE-2026-22996, CVE-2026-22997, CVE-2026-22998, CVE-2026-22999, CVE-2026-23000, CVE-2026-23001, CVE-2026-23002, CVE-2026-23003, CVE-2026-23004, CVE-2026-23005, CVE-2026-23006, CVE-2026-23007, CVE-2026-23008, CVE-2026-23009, CVE-2026-23010, CVE-2026-23011, CVE-2026-23012, CVE-2026-23013, CVE-2026-23014, CVE-2026-23015, CVE-2026-23017, CVE-2026-23018, CVE-2026-23019, CVE-2026-23020, CVE-2026-23021, CVE-2026-23022, CVE-2026-23023, CVE-2026-23024, CVE-2026-23025, CVE-2026-23026, CVE-2026-23030, CVE-2026-23031, CVE-2026-23032, CVE-2026-23033, CVE-2026-23034, CVE-2026-23035, CVE-2026-23036, CVE-2026-23037, CVE-2026-23038, CVE-2026-23042, CVE-2026-23044, CVE-2026-23045, CVE-2026-23046, CVE-2026-23047, CVE-2026-23049, CVE-2026-23050, CVE-2026-23051, CVE-2026-23052, CVE-2026-23053, CVE-2026-23054, CVE-2026-23055, CVE-2026-23056, CVE-2026-23057, CVE-2026-23058, CVE-2026-23059, CVE-2026-23061, CVE-2026-23062, CVE-2026-23063, CVE-2026-23064, CVE-2026-23065, CVE-2026-23066, CVE-2026-23067, CVE-2026-23068, CVE-2026-23069, CVE-2026-23070, CVE-2026-23071, CVE-2026-23072, CVE-2026-23073, CVE-2026-23075, CVE-2026-23076, CVE-2026-23077, CVE-2026-23078, CVE-2026-23079,…
Record
USN-8570-2
Updated
2026-11-06
OSVUSN-8594-1No score

linux-oem-6.17 vulnerabilities

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

  • Foo-over-UDP (FOU);
  • ARM64 architecture;
  • x86 architecture;
  • Block layer subsystem;
  • Drivers core;
  • Null block device driver;
  • Bluetooth drivers;
  • Counter interface drivers;
  • DMA engine subsystem;
  • DPLL subsystem;
  • GPIO subsystem;
  • GPU drivers;
  • I2C subsystem;
  • IIO ADC drivers;
  • IIO subsystem;
  • On-Chip Interconnect management framework;
  • IOMMU subsystem;
  • IRQ chip drivers;
  • Modular ISDN driver;
  • LED subsystem;
  • Multiple devices driver;
  • UACCE accelerator framework;
  • MMC subsystem;
  • Ethernet bonding driver;
  • Network drivers;
  • Mellanox network drivers;
  • NVME drivers;
  • Device tree and open firmware driver;
  • PHY drivers;
  • x86 platform drivers;
  • i.MX PM domains;
  • SCSI subsystem;
  • SLIMbus drivers;
  • SPI subsystem;
  • TTY drivers;
  • USB Host Controller drivers;
  • W1 Dallas's 1-wire bus driver;
  • Xen hypervisor drivers;
  • BTRFS file system;
  • EFI Variable file system;
  • Ext4 file system;
  • File systems infrastructure;
  • FUSE (File system in Userspace);
  • Network file systems library;
  • Network file system (NFS) client;
  • Network file system (NFS) server daemon;
  • SMB network file system;
  • Memory Management;
  • Memory management;
  • Scheduler infrastructure;
  • Tracing infrastructure;
  • Netfilter;
  • NFC subsystem;
  • io_uring subsystem;
  • Perf events;
  • Hibernation control;
  • Timer subsystem;
  • BPF subsystem;
  • Floating proportions library;
  • Bluetooth subsystem;
  • CAN network layer;
  • Ceph Core library;
  • Networking core;
  • IPv4 networking;
  • IPv6 networking;
  • L2TP protocol;
  • MAC80211 subsystem;
  • Multipath TCP;
  • NET/ROM layer;
  • RxRPC session sockets;
  • Network traffic control;
  • SCTP protocol;
  • VMware vSockets driver;
  • Wireless networking;
  • ALSA AC97 driver;
  • Creative Sound Blaster X-Fi driver;
  • Texas InstrumentS Audio (ASoC/HDA) drivers;
  • USB sound devices; (CVE-2025-71158, CVE-2025-71160, CVE-2025-71161, CVE-2025-71162, CVE-2025-71163, CVE-2025-71180, CVE-2025-71182, CVE-2025-71183, CVE-2025-71184, CVE-2025-71185, CVE-2025-71186, CVE-2025-71187, CVE-2025-71188, CVE-2025-71189, CVE-2025-71190, CVE-2025-71191, CVE-2025-71192, CVE-2025-71193, CVE-2025-71194, CVE-2025-71195, CVE-2025-71196, CVE-2025-71197, CVE-2025-71198, CVE-2025-71199, CVE-2025-71200, CVE-2025-71201, CVE-2026-22976, CVE-2026-22977, CVE-2026-22978, CVE-2026-22979, CVE-2026-22980, CVE-2026-22981, CVE-2026-22982, CVE-2026-22985, CVE-2026-22986, CVE-2026-22987, CVE-2026-22989, CVE-2026-22990, CVE-2026-22991, CVE-2026-22992, CVE-2026-22993, CVE-2026-22994, CVE-2026-22996, CVE-2026-22997, CVE-2026-22998, CVE-2026-22999, CVE-2026-23000, CVE-2026-23001, CVE-2026-23002, CVE-2026-23003, CVE-2026-23004, CVE-2026-23005, CVE-2026-23006, CVE-2026-23007, CVE-2026-23008, CVE-2026-23009, CVE-2026-23010, CVE-2026-23011, CVE-2026-23012, CVE-2026-23013, CVE-2026-23014, CVE-2026-23015, CVE-2026-23017, CVE-2026-23018, CVE-2026-23019, CVE-2026-23020, CVE-2026-23021, CVE-2026-23022, CVE-2026-23023, CVE-2026-23024, CVE-2026-23025, CVE-2026-23026, CVE-2026-23030, CVE-2026-23031, CVE-2026-23032, CVE-2026-23033, CVE-2026-23034, CVE-2026-23035, CVE-2026-23036, CVE-2026-23037, CVE-2026-23038, CVE-2026-23042, CVE-2026-23044, CVE-2026-23045, CVE-2026-23046, CVE-2026-23047, CVE-2026-23049, CVE-2026-23050, CVE-2026-23051, CVE-2026-23052, CVE-2026-23053, CVE-2026-23054, CVE-2026-23055, CVE-2026-23056, CVE-2026-23057, CVE-2026-23058, CVE-2026-23059, CVE-2026-23061, CVE-2026-23062, CVE-2026-23063, CVE-2026-23064, CVE-2026-23065, CVE-2026-23066, CVE-2026-23067, CVE-2026-23068, CVE-2026-23069, CVE-2026-23070, CVE-2026-23071, CVE-2026-23072, CVE-2026-23073, CVE-2026-23075, CVE-2026-23076, CVE-2026-23077, CVE-2026-23078, CVE-2026-23079,…
Record
USN-8594-1
Updated
2026-11-06
OSVUSN-8604-1No score

linux-azure-6.17 vulnerabilities

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

  • Foo-over-UDP (FOU);
  • ARM64 architecture;
  • x86 architecture;
  • Block layer subsystem;
  • Cryptographic API;
  • Drivers core;
  • Null block device driver;
  • Bluetooth drivers;
  • Counter interface drivers;
  • DMA engine subsystem;
  • DPLL subsystem;
  • GPIO subsystem;
  • GPU drivers;
  • I2C subsystem;
  • IIO ADC drivers;
  • IIO subsystem;
  • InfiniBand drivers;
  • On-Chip Interconnect management framework;
  • IOMMU subsystem;
  • IRQ chip drivers;
  • Modular ISDN driver;
  • LED subsystem;
  • Multiple devices driver;
  • UACCE accelerator framework;
  • MMC subsystem;
  • Ethernet bonding driver;
  • Network drivers;
  • Mellanox network drivers;
  • Microsoft Azure Network Adapter (MANA) driver;
  • STMicroelectronics network drivers;
  • NVME drivers;
  • Device tree and open firmware driver;
  • PHY drivers;
  • x86 platform drivers;
  • i.MX PM domains;
  • SCSI subsystem;
  • SLIMbus drivers;
  • SPI subsystem;
  • TTY drivers;
  • USB Host Controller drivers;
  • USB over IP driver;
  • W1 Dallas's 1-wire bus driver;
  • Xen hypervisor drivers;
  • BTRFS file system;
  • File systems infrastructure;
  • EFI Variable file system;
  • Ext4 file system;
  • FUSE (File system in Userspace);
  • Network file systems library;
  • Network file system (NFS) client;
  • Network file system (NFS) server daemon;
  • SMB network file system;
  • Memory Management;
  • Kernel thread helper (kthread);
  • Memory management;
  • Scheduler infrastructure;
  • Tracing infrastructure;
  • IPv6 networking;
  • Netfilter;
  • NFC subsystem;
  • io_uring subsystem;
  • Perf events;
  • Kernel exit() syscall;
  • Hibernation control;
  • Timer subsystem;
  • BPF subsystem;
  • Floating proportions library;
  • Scatterlist API;
  • B.A.T.M.A.N. meshing protocol;
  • Bluetooth subsystem;
  • Ethernet bridge;
  • CAN network layer;
  • Ceph Core library;
  • Networking core;
  • IPv4 networking;
  • L2TP protocol;
  • MAC80211 subsystem;
  • Multipath TCP;
  • NET/ROM layer;
  • RxRPC session sockets;
  • Network traffic control;
  • SCTP protocol;
  • SMC sockets;
  • VMware vSockets driver;
  • Wireless networking;
  • X.25 network layer;
  • ALSA AC97 driver;
  • Creative Sound Blaster X-Fi driver;
  • Texas InstrumentS Audio (ASoC/HDA) drivers;
  • USB sound devices; (CVE-2025-71158, CVE-2025-71160, CVE-2025-71161, CVE-2025-71162, CVE-2025-71163, CVE-2025-71180, CVE-2025-71182, CVE-2025-71183, CVE-2025-71184, CVE-2025-71185, CVE-2025-71186, CVE-2025-71187, CVE-2025-71188, CVE-2025-71189, CVE-2025-71190, CVE-2025-71191, CVE-2025-71192, CVE-2025-71193, CVE-2025-71194, CVE-2025-71195, CVE-2025-71196, CVE-2025-71197, CVE-2025-71198, CVE-2025-71199, CVE-2025-71200, CVE-2025-71201, CVE-2026-22976, CVE-2026-22977, CVE-2026-22978, CVE-2026-22979, CVE-2026-22980, CVE-2026-22981, CVE-2026-22982, CVE-2026-22984, CVE-2026-22985, CVE-2026-22986, CVE-2026-22987, CVE-2026-22989, CVE-2026-22990, CVE-2026-22991, CVE-2026-22992, CVE-2026-22993, CVE-2026-22994, CVE-2026-22996, CVE-2026-22997, CVE-2026-22998, CVE-2026-22999, CVE-2026-23000, CVE-2026-23001, CVE-2026-23002, CVE-2026-23003, CVE-2026-23004, CVE-2026-23005, CVE-2026-23006, CVE-2026-23007, CVE-2026-23008, CVE-2026-23009, CVE-2026-23010, CVE-2026-23011, CVE-2026-23012, CVE-2026-23013, CVE-2026-23014, CVE-2026-23015, CVE-2026-23017, CVE-2026-23018, CVE-2026-23019, CVE-2026-23020, CVE-2026-23021, CVE-2026-23022, CVE-2026-23023, CVE-2026-23024, CVE-2026-23025, CVE-2026-23026, CVE-2026-23030, CVE-2026-23031, CVE-2026-23032, CVE-2026-23033, CVE-2026-23034, CVE-2026-23035, CVE-2026-23036, CVE-2026-23037, CVE-2026-23038, CVE-2026-23042, CVE-2026-23044, CVE-2026-23045, CVE-2026-23046, CVE-2026-23047, CVE-2026-23049, CVE-2026-23050, CVE-2026-23051, CVE-2026-23052, CVE-2026-23053, CVE-2026-23054,…
Record
USN-8604-1
Updated
2026-11-07
OSVUSN-8605-1No score

linux-azure-fde-6.17 vulnerabilities

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

  • Foo-over-UDP (FOU);
  • ARM64 architecture;
  • x86 architecture;
  • Block layer subsystem;
  • Cryptographic API;
  • Drivers core;
  • Null block device driver;
  • Bluetooth drivers;
  • Counter interface drivers;
  • DMA engine subsystem;
  • DPLL subsystem;
  • GPIO subsystem;
  • GPU drivers;
  • I2C subsystem;
  • IIO ADC drivers;
  • IIO subsystem;
  • InfiniBand drivers;
  • On-Chip Interconnect management framework;
  • IOMMU subsystem;
  • IRQ chip drivers;
  • Modular ISDN driver;
  • LED subsystem;
  • Multiple devices driver;
  • UACCE accelerator framework;
  • MMC subsystem;
  • Ethernet bonding driver;
  • Network drivers;
  • Mellanox network drivers;
  • Microsoft Azure Network Adapter (MANA) driver;
  • STMicroelectronics network drivers;
  • NVME drivers;
  • Device tree and open firmware driver;
  • PHY drivers;
  • x86 platform drivers;
  • i.MX PM domains;
  • SCSI subsystem;
  • SLIMbus drivers;
  • SPI subsystem;
  • TTY drivers;
  • USB Host Controller drivers;
  • USB over IP driver;
  • W1 Dallas's 1-wire bus driver;
  • Xen hypervisor drivers;
  • BTRFS file system;
  • File systems infrastructure;
  • EFI Variable file system;
  • Ext4 file system;
  • FUSE (File system in Userspace);
  • Network file systems library;
  • Network file system (NFS) client;
  • Network file system (NFS) server daemon;
  • SMB network file system;
  • Memory Management;
  • Kernel thread helper (kthread);
  • Memory management;
  • Scheduler infrastructure;
  • Tracing infrastructure;
  • IPv6 networking;
  • Netfilter;
  • NFC subsystem;
  • io_uring subsystem;
  • Perf events;
  • Kernel exit() syscall;
  • Hibernation control;
  • Timer subsystem;
  • BPF subsystem;
  • Floating proportions library;
  • Scatterlist API;
  • B.A.T.M.A.N. meshing protocol;
  • Bluetooth subsystem;
  • Ethernet bridge;
  • CAN network layer;
  • Ceph Core library;
  • Networking core;
  • IPv4 networking;
  • L2TP protocol;
  • MAC80211 subsystem;
  • Multipath TCP;
  • NET/ROM layer;
  • RxRPC session sockets;
  • Network traffic control;
  • SCTP protocol;
  • SMC sockets;
  • VMware vSockets driver;
  • Wireless networking;
  • X.25 network layer;
  • ALSA AC97 driver;
  • Creative Sound Blaster X-Fi driver;
  • Texas InstrumentS Audio (ASoC/HDA) drivers;
  • USB sound devices; (CVE-2025-71158, CVE-2025-71160, CVE-2025-71161, CVE-2025-71162, CVE-2025-71163, CVE-2025-71180, CVE-2025-71182, CVE-2025-71183, CVE-2025-71184, CVE-2025-71185, CVE-2025-71186, CVE-2025-71187, CVE-2025-71188, CVE-2025-71189, CVE-2025-71190, CVE-2025-71191, CVE-2025-71192, CVE-2025-71193, CVE-2025-71194, CVE-2025-71195, CVE-2025-71196, CVE-2025-71197, CVE-2025-71198, CVE-2025-71199, CVE-2025-71200, CVE-2025-71201, CVE-2026-22976, CVE-2026-22977, CVE-2026-22978, CVE-2026-22979, CVE-2026-22980, CVE-2026-22981, CVE-2026-22982, CVE-2026-22984, CVE-2026-22985, CVE-2026-22986, CVE-2026-22987, CVE-2026-22989, CVE-2026-22990, CVE-2026-22991, CVE-2026-22992, CVE-2026-22993, CVE-2026-22994, CVE-2026-22996, CVE-2026-22997, CVE-2026-22998, CVE-2026-22999, CVE-2026-23000, CVE-2026-23001, CVE-2026-23002, CVE-2026-23003, CVE-2026-23004, CVE-2026-23005, CVE-2026-23006, CVE-2026-23007, CVE-2026-23008, CVE-2026-23009, CVE-2026-23010, CVE-2026-23011, CVE-2026-23012, CVE-2026-23013, CVE-2026-23014, CVE-2026-23015, CVE-2026-23017, CVE-2026-23018, CVE-2026-23019, CVE-2026-23020, CVE-2026-23021, CVE-2026-23022, CVE-2026-23023, CVE-2026-23024, CVE-2026-23025, CVE-2026-23026, CVE-2026-23030, CVE-2026-23031, CVE-2026-23032, CVE-2026-23033, CVE-2026-23034, CVE-2026-23035, CVE-2026-23036, CVE-2026-23037, CVE-2026-23038, CVE-2026-23042, CVE-2026-23044, CVE-2026-23045, CVE-2026-23046, CVE-2026-23047, CVE-2026-23049, CVE-2026-23050, CVE-2026-23051, CVE-2026-23052, CVE-2026-23053, CVE-2026-23054,…
Record
USN-8605-1
Updated
2026-11-02
OSVUSN-8669-1No score

linux-nvidia-6.17 vulnerabilities

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

  • Foo-over-UDP (FOU);
  • ARM64 architecture;
  • x86 architecture;
  • Block layer subsystem;
  • Drivers core;
  • Null block device driver;
  • Bluetooth drivers;
  • Counter interface drivers;
  • DMA engine subsystem;
  • DPLL subsystem;
  • GPIO subsystem;
  • GPU drivers;
  • I2C subsystem;
  • IIO ADC drivers;
  • IIO subsystem;
  • InfiniBand drivers;
  • On-Chip Interconnect management framework;
  • IOMMU subsystem;
  • IRQ chip drivers;
  • Modular ISDN driver;
  • LED subsystem;
  • Multiple devices driver;
  • Media drivers;
  • UACCE accelerator framework;
  • MMC subsystem;
  • Ethernet bonding driver;
  • Network drivers;
  • Mellanox network drivers;
  • Texas Instruments network drivers;
  • NVME drivers;
  • Device tree and open firmware driver;
  • PHY drivers;
  • x86 platform drivers;
  • i.MX PM domains;
  • SCSI subsystem;
  • SLIMbus drivers;
  • SPI subsystem;
  • TTY drivers;
  • USB Host Controller drivers;
  • W1 Dallas's 1-wire bus driver;
  • Xen hypervisor drivers;
  • BTRFS file system;
  • EFI Variable file system;
  • File systems infrastructure;
  • Ext4 file system;
  • FUSE (File system in Userspace);
  • Network file systems library;
  • Network file system (NFS) client;
  • Network file system (NFS) server daemon;
  • SMB network file system;
  • Memory Management;
  • Memory management;
  • Scheduler infrastructure;
  • Tracing infrastructure;
  • IPv4 networking;
  • Netfilter;
  • NFC subsystem;
  • Network traffic control;
  • TCP network protocol;
  • io_uring subsystem;
  • Perf events;
  • Locking primitives;
  • Hibernation control;
  • Timer subsystem;
  • BPF subsystem;
  • Floating proportions library;
  • Bluetooth subsystem;
  • CAN network layer;
  • Ceph Core library;
  • Networking core;
  • IPv6 networking;
  • L2TP protocol;
  • MAC80211 subsystem;
  • Multipath TCP;
  • NET/ROM layer;
  • RxRPC session sockets;
  • SCTP protocol;
  • SMC sockets;
  • VMware vSockets driver;
  • Wireless networking;
  • ALSA AC97 driver;
  • Creative Sound Blaster X-Fi driver;
  • Texas InstrumentS Audio (ASoC/HDA) drivers;
  • USB sound devices; (CVE-2025-71158, CVE-2025-71160, CVE-2025-71161, CVE-2025-71162, CVE-2025-71163, CVE-2025-71180, CVE-2025-71182, CVE-2025-71183, CVE-2025-71184, CVE-2025-71185, CVE-2025-71186, CVE-2025-71187, CVE-2025-71188, CVE-2025-71189, CVE-2025-71190, CVE-2025-71191, CVE-2025-71192, CVE-2025-71193, CVE-2025-71194, CVE-2025-71195, CVE-2025-71196, CVE-2025-71197, CVE-2025-71198, CVE-2025-71199, CVE-2025-71200, CVE-2025-71201, CVE-2026-22976, CVE-2026-22977, CVE-2026-22978, CVE-2026-22979, CVE-2026-22980, CVE-2026-22981, CVE-2026-22982, CVE-2026-22985, CVE-2026-22986, CVE-2026-22987, CVE-2026-22989, CVE-2026-22990, CVE-2026-22991, CVE-2026-22992, CVE-2026-22993, CVE-2026-22994, CVE-2026-22996, CVE-2026-22997, CVE-2026-22998, CVE-2026-22999, CVE-2026-23000, CVE-2026-23001, CVE-2026-23002, CVE-2026-23003, CVE-2026-23004, CVE-2026-23005, CVE-2026-23006, CVE-2026-23007, CVE-2026-23008, CVE-2026-23009, CVE-2026-23010, CVE-2026-23011, CVE-2026-23012, CVE-2026-23013, CVE-2026-23014, CVE-2026-23015, CVE-2026-23017, CVE-2026-23018, CVE-2026-23019, CVE-2026-23020, CVE-2026-23021, CVE-2026-23022, CVE-2026-23023, CVE-2026-23024, CVE-2026-23025, CVE-2026-23026, CVE-2026-23030, CVE-2026-23031, CVE-2026-23032, CVE-2026-23033, CVE-2026-23034, CVE-2026-23035, CVE-2026-23036, CVE-2026-23037, CVE-2026-23038, CVE-2026-23042, CVE-2026-23044, CVE-2026-23045, CVE-2026-23046, CVE-2026-23047, CVE-2026-23049, CVE-2026-23050, CVE-2026-23051, CVE-2026-23052, CVE-2026-23053, CVE-2026-23054, CVE-2026-23055, CVE-2026-23056, CVE-2026-23057, CVE-2026-23058, CVE-2026-23059, CVE-2026-23061, CVE-2026-23062, CVE-2026-23063, CVE-2026-23064, CVE-2026-23065, CVE-2026-23066, CVE-2026-23067, CVE-2026-23068,…
Record
USN-8669-1
Updated
2026-11-06

Affected products

Affected packages

Affected packages
PackageAffectedFixed
linux-lts
Alpaquita:stream
6.12.92-r1 up to 6.18.35-r1
6.18.35-r1
Kernel
Linux
6.16.0 up to 6.18.8
6.18.8
linux
Debian:14
before 6.18.8-1, plus listed versions
6.12.100-16.12.101-16.12.105-16.12.107-16.12.111-1
Show 45 moreShow less
6.12.38-16.12.41-16.12.43-16.12.43-1~bpo12+16.12.48-16.12.57-16.12.57-1~bpo12+16.12.63-16.12.63-1~bpo12+16.12.69-16.12.69-1~bpo12+16.12.73-16.12.73-1~bpo12+16.12.74-16.12.74-26.12.74-2~bpo12+16.12.85-16.12.85-1~bpo12+16.12.86-16.12.86-1~bpo12+16.12.88-16.12.88-1~bpo12+16.12.90-16.12.90-1~bpo12+16.12.90-26.12.90-2~bpo12+16.12.94-16.12.94-1~bpo12+16.12.95-16.12.95-1~bpo12+16.12.96-16.13.10-1~exp16.13.11-1~exp16.13.2-1~exp16.13.3-1~exp16.13.4-1~exp16.13.5-1~exp16.13.6-1~exp16.13.7-1~exp16.13.8-1~exp16.13.9-1~exp16.13~rc6-1~exp16.13~rc7-1~exp16.14.3-1~exp16.14.5-1~exp1
6.18.8-1
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
Show 109 moreShow less
Affected packages
PackageAffectedFixed
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-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-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-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-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-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-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-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-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-aws-6.17
Ubuntu:24.04:LTS
All versions, plus listed versions
6.17.0-1005.5~24.04.26.17.0-1007.7~24.04.16.17.0-1009.9~24.04.26.17.0-1010.10~24.04.16.17.0-1012.12~24.04.1
Show 5 moreShow less
6.17.0-1013.13~24.04.16.17.0-1015.15~24.04.16.17.0-1017.17~24.04.16.17.0-1019.19~24.04.16.17.0-1020.20~24.04.1
None known
linux-azure-6.11
Ubuntu:24.04:LTS
All versions, plus listed versions
6.11.0-1008.8~24.04.16.11.0-1012.12~24.04.16.11.0-1013.13~24.04.16.11.0-1014.14~24.04.16.11.0-1015.15~24.04.16.11.0-1017.17~24.04.16.11.0-1018.18~24.04.1
None known
linux-azure-6.17
Ubuntu:24.04:LTS
before 6.17.0-1021.21~24.04.1, plus listed versions
6.17.0-1008.8~24.04.16.17.0-1010.10~24.04.16.17.0-1011.11~24.04.26.17.0-1013.13~24.04.16.17.0-1015.15~24.04.16.17.0-1017.17~24.04.16.17.0-1018.18~24.04.16.17.0-1020.20~24.04.1
6.17.0-1021.21~24.04.1
linux-gcp-6.11
Ubuntu:24.04:LTS
All versions, plus listed versions
6.11.0-1006.6~24.04.26.11.0-1011.11~24.04.16.11.0-1013.13~24.04.16.11.0-1014.14~24.04.16.11.0-1015.15~24.04.16.11.0-1016.16~24.04.16.11.0-1017.17~24.04.1
None known
linux-gcp-6.17
Ubuntu:24.04:LTS
before 6.17.0-1021.24~24.04.1, plus listed versions
6.17.0-1004.4~24.04.36.17.0-1008.8~24.04.16.17.0-1009.9~24.04.36.17.0-1010.10~24.04.16.17.0-1012.12~24.04.1
Show 4 moreShow less
6.17.0-1013.13~24.04.16.17.0-1016.17~24.04.16.17.0-1018.19~24.04.16.17.0-1020.22~24.04.1
6.17.0-1021.24~24.04.1
linux-hwe-6.11
Ubuntu:24.04:LTS
All versions, plus listed versions
6.11.0-17.17~24.04.26.11.0-19.19~24.04.16.11.0-21.21~24.04.16.11.0-24.24~24.04.16.11.0-25.25~24.04.16.11.0-26.26~24.04.16.11.0-28.28~24.04.16.11.0-29.29~24.04.1
None known
linux-hwe-6.17
Ubuntu:24.04:LTS
before 6.17.0-41.41~24.04.1, plus listed versions
6.17.0-14.14~24.04.16.17.0-19.19~24.04.26.17.0-20.20~24.04.16.17.0-22.22~24.04.16.17.0-23.23~24.04.16.17.0-29.29~24.04.16.17.0-35.35~24.04.16.17.0-40.40~24.04.1
6.17.0-41.41~24.04.1
linux-lowlatency-hwe-6.11
Ubuntu:24.04:LTS
All versions, plus listed versions
6.11.0-1009.10~24.04.16.11.0-1011.12~24.04.16.11.0-1012.13~24.04.16.11.0-1013.14~24.04.16.11.0-1014.15~24.04.16.11.0-1015.16~24.04.26.11.0-1016.17~24.04.1
None known
linux-nvidia-6.11
Ubuntu:24.04:LTS
All versions, plus listed versions
6.11.0-1002.26.11.0-1003.36.11.0-1007.76.11.0-1010.106.11.0-1011.116.11.0-1012.126.11.0-1013.136.11.0-1016.16
None known
linux-nvidia-6.17
Ubuntu:24.04:LTS
before 6.17.0-1031.31, plus listed versions
6.17.0-1004.46.17.0-1008.86.17.0-1014.146.17.0-1018.186.17.0-1021.216.17.0-1026.266.17.0-1029.29
6.17.0-1031.31
linux-oem-6.11
Ubuntu:24.04:LTS
All versions, plus listed versions
6.11.0-1007.76.11.0-1008.86.11.0-1009.96.11.0-1010.106.11.0-1011.11
Show 13 moreShow less
6.11.0-1012.126.11.0-1013.136.11.0-1015.156.11.0-1016.166.11.0-1017.176.11.0-1018.186.11.0-1020.206.11.0-1021.216.11.0-1022.226.11.0-1023.236.11.0-1024.246.11.0-1025.256.11.0-1027.27
None known
linux-oem-6.17
Ubuntu:24.04:LTS
before 6.17.0-1030.30, plus listed versions
6.17.0-1005.56.17.0-1006.66.17.0-1007.76.17.0-1008.86.17.0-1009.9
Show 9 moreShow less
6.17.0-1010.106.17.0-1011.116.17.0-1012.126.17.0-1017.176.17.0-1020.206.17.0-1023.236.17.0-1024.246.17.0-1025.256.17.0-1028.28
6.17.0-1030.30
linux-oem-6.8
Ubuntu:24.04:LTS
All versions, 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 21 moreShow less
6.8.0-1008.86.8.0-1009.96.8.0-1010.106.8.0-1011.116.8.0-1012.126.8.0-1013.136.8.0-1014.146.8.0-1016.166.8.0-1017.176.8.0-1018.186.8.0-1019.196.8.0-1020.206.8.0-1024.246.8.0-1025.256.8.0-1026.266.8.0-1027.276.8.0-1028.286.8.0-1029.296.8.0-1030.306.8.0-1031.316.8.0-1032.32
None known
linux-oracle-6.14
Ubuntu:24.04:LTS
All versions, plus listed versions
6.14.0-1007.7~24.04.16.14.0-1009.9~24.04.16.14.0-1010.10~24.04.16.14.0-1011.11~24.04.16.14.0-1012.12~24.04.1
Show 6 moreShow less
6.14.0-1013.13~24.04.16.14.0-1014.14~24.04.16.14.0-1015.15~24.04.16.14.0-1016.16~24.04.16.14.0-1017.17~24.04.16.14.0-1018.18~24.04.1
None known
linux-oracle-6.17
Ubuntu:24.04:LTS
before 6.17.0-1019.19~24.04.3, plus listed versions
6.17.0-1004.4~24.04.26.17.0-1007.7~24.04.16.17.0-1009.9~24.04.16.17.0-1010.10~24.04.16.17.0-1011.11~24.04.16.17.0-1014.14~24.04.16.17.0-1016.16~24.04.16.17.0-1018.18~24.04.1
6.17.0-1019.19~24.04.3
linux-raspi-realtime
Ubuntu:24.04:LTS
All versions, plus listed versions
6.8.0-2019.20
None known
linux-realtime
Ubuntu:24.04:LTS
All versions, plus listed versions
6.8.1-1015.16
None known
linux-riscv
Ubuntu:24.04:LTS
All versions, 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 19 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.16.8.0-44.44.16.8.0-47.47.16.8.0-48.48.16.8.0-49.49.16.8.0-50.51.16.8.0-51.52.16.8.0-52.53.16.8.0-53.55.16.8.0-55.57.16.8.0-56.58.16.8.0-57.59.16.8.0-58.60.16.8.0-59.61.16.8.0-60.63.1
None known
linux-riscv-6.14
Ubuntu:24.04:LTS
All versions, plus listed versions
6.14.0-22.22.1~24.04.16.14.0-23.23.1~24.04.16.14.0-24.24.1~24.04.16.14.0-27.27.1~24.04.16.14.0-28.28.1~24.04.1
Show 7 moreShow less
6.14.0-29.29.1~24.04.16.14.0-32.32.1~24.04.16.14.0-33.33.1~24.04.16.14.0-34.34.1~24.04.16.14.0-35.35.1~24.04.16.14.0-36.36.1~24.04.16.14.0-37.37.1~24.04.1
None known
linux-riscv-6.17
Ubuntu:24.04:LTS
All versions, plus listed versions
6.17.0-14.14.1~24.04.16.17.0-19.19.1~24.04.16.17.0-20.20.1~24.04.16.17.0-22.22.1~24.04.16.17.0-23.23.1~24.04.16.17.0-29.29.1~24.04.16.17.0-35.35.1~24.04.16.17.0-38.38.1~24.04.1
None known
linux-realtime-6.14
Ubuntu:Pro:Realtime:24.04:LTS
All versions, plus listed versions
6.14.0-1003.3~24.04.36.14.0-1010.10~24.04.16.14.0-1011.11~24.04.16.14.0-1012.12~24.04.16.14.0-1013.13~24.04.1
Show 4 moreShow less
6.14.0-1014.14~24.04.16.14.0-1015.15~24.04.16.14.0-1016.16~24.04.16.14.0-1017.17~24.04.1
None known
linux-realtime-6.17
Ubuntu:Pro:Realtime:24.04:LTS
before 6.17.0-1018.20~24.04.1, plus listed versions
6.17.0-1004.5~24.04.26.17.0-1006.7~24.04.16.17.0-1008.9~24.04.16.17.0-1009.10~24.04.16.17.0-1010.11~24.04.1
Show 4 moreShow less
6.17.0-1011.12~24.04.16.17.0-1013.15~24.04.16.17.0-1014.16~24.04.16.17.0-1017.19~24.04.1
6.17.0-1018.20~24.04.1
linux
Ubuntu:25.10
All versions, plus listed versions
6.14.0-15.156.15.0-3.36.15.0-4.46.16.0-13.136.16.0-16.16
Show 15 moreShow less
6.17.0-3.36.17.0-4.46.17.0-5.56.17.0-6.66.17.0-7.76.17.0-8.86.17.0-12.126.17.0-14.146.17.0-19.196.17.0-20.206.17.0-22.226.17.0-23.236.17.0-29.296.17.0-35.356.17.0-40.40
None known
linux-aws
Ubuntu:25.10
All versions, plus listed versions
6.14.0-1005.56.14.0-1007.7+25.10.26.16.0-1001.16.17.0-1001.16.17.0-1002.2
Show 12 moreShow less
6.17.0-1003.36.17.0-1004.46.17.0-1005.56.17.0-1006.66.17.0-1007.76.17.0-1009.96.17.0-1010.106.17.0-1012.126.17.0-1013.136.17.0-1015.156.17.0-1017.176.17.0-1019.19
None known
linux-azure
Ubuntu:25.10
All versions, plus listed versions
6.14.0-1004.46.14.0-1007.7+25.10.16.16.0-1001.16.17.0-1002.26.17.0-1003.3
Show 11 moreShow less
6.17.0-1004.46.17.0-1006.66.17.0-1007.76.17.0-1008.86.17.0-1010.106.17.0-1011.116.17.0-1013.136.17.0-1015.156.17.0-1017.176.17.0-1018.186.17.0-1020.20
None known
linux-azure-fde
Ubuntu:25.10
All versions, plus listed versions
6.17.0-1003.36.17.0-1004.46.17.0-1005.56.17.0-1007.76.17.0-1008.8
Show 5 moreShow less
6.17.0-1010.106.17.0-1012.126.17.0-1014.146.17.0-1015.156.17.0-1017.17
None known
linux-gcp
Ubuntu:25.10
All versions, plus listed versions
6.14.0-1006.66.14.0-1009.9+25.10.16.16.0-1001.16.17.0-1001.16.17.0-1002.2
Show 12 moreShow less
6.17.0-1003.36.17.0-1004.46.17.0-1005.56.17.0-1006.66.17.0-1007.76.17.0-1009.96.17.0-1010.106.17.0-1012.126.17.0-1013.136.17.0-1016.176.17.0-1018.196.17.0-1020.22
None known
linux-oracle
Ubuntu:25.10
All versions, plus listed versions
6.14.0-1005.56.14.0-1007.7+25.10.16.16.0-1001.16.17.0-1001.16.17.0-1002.2
Show 11 moreShow less
6.17.0-1003.36.17.0-1005.56.17.0-1006.66.17.0-1007.76.17.0-1009.96.17.0-1010.106.17.0-1011.116.17.0-1012.126.17.0-1014.146.17.0-1016.166.17.0-1018.18
None known
linux-raspi
Ubuntu:25.10
All versions, plus listed versions
6.14.0-1005.56.17.0-1003.36.17.0-1004.46.17.0-1005.56.17.0-1006.6
Show 9 moreShow less
6.17.0-1007.76.17.0-1008.86.17.0-1010.106.17.0-1011.116.17.0-1013.136.17.0-1014.146.17.0-1017.176.17.0-1018.186.17.0-1021.21
None known
linux-realtime
Ubuntu:25.10
All versions, plus listed versions
6.14.0-1002.26.17.0-1001.26.17.0-1002.36.17.0-1003.46.17.0-1004.5
Show 9 moreShow less
6.17.0-1005.66.17.0-1006.76.17.0-1008.96.17.0-1009.106.17.0-1010.116.17.0-1011.126.17.0-1013.156.17.0-1014.166.17.0-1017.19
None known
linux-riscv
Ubuntu:25.10
All versions, plus listed versions
6.14.0-13.13.26.17.0-4.4.16.17.0-5.5.16.17.0-6.6.16.17.0-7.7.1
Show 10 moreShow less
6.17.0-8.8.16.17.0-12.12.16.17.0-14.14.16.17.0-19.19.16.17.0-20.20.16.17.0-22.22.16.17.0-23.23.16.17.0-29.29.16.17.0-35.35.16.17.0-40.40.1
None known
linux-gcp-6.17
Ubuntu:24.04:LTS
From an advisory covering 203 CVEs
before 6.17.0-1021.24~24.04.1, plus listed versions
6.17.0-1004.4~24.04.36.17.0-1008.8~24.04.16.17.0-1009.9~24.04.36.17.0-1010.10~24.04.16.17.0-1012.12~24.04.1
Show 4 moreShow less
6.17.0-1013.13~24.04.16.17.0-1016.17~24.04.16.17.0-1018.19~24.04.16.17.0-1020.22~24.04.1
6.17.0-1021.24~24.04.1
linux-realtime-6.17
Ubuntu:Pro:Realtime:24.04:LTS
From an advisory covering 203 CVEs
before 6.17.0-1018.20~24.04.1, plus listed versions
6.17.0-1004.5~24.04.26.17.0-1006.7~24.04.16.17.0-1008.9~24.04.16.17.0-1009.10~24.04.16.17.0-1010.11~24.04.1
Show 4 moreShow less
6.17.0-1011.12~24.04.16.17.0-1013.15~24.04.16.17.0-1014.16~24.04.16.17.0-1017.19~24.04.1
6.17.0-1018.20~24.04.1
linux-oracle-6.17
Ubuntu:24.04:LTS
From an advisory covering 203 CVEs
before 6.17.0-1019.19~24.04.3, plus listed versions
6.17.0-1004.4~24.04.26.17.0-1007.7~24.04.16.17.0-1009.9~24.04.16.17.0-1010.10~24.04.16.17.0-1011.11~24.04.16.17.0-1014.14~24.04.16.17.0-1016.16~24.04.16.17.0-1018.18~24.04.1
6.17.0-1019.19~24.04.3
linux-oem-6.17
Ubuntu:24.04:LTS
From an advisory covering 203 CVEs
before 6.17.0-1030.30, plus listed versions
6.17.0-1005.56.17.0-1006.66.17.0-1007.76.17.0-1008.86.17.0-1009.9
Show 9 moreShow less
6.17.0-1010.106.17.0-1011.116.17.0-1012.126.17.0-1017.176.17.0-1020.206.17.0-1023.236.17.0-1024.246.17.0-1025.256.17.0-1028.28
6.17.0-1030.30
linux-azure-6.17
Ubuntu:24.04:LTS
From an advisory covering 267 CVEs
before 6.17.0-1021.21~24.04.1, plus listed versions
6.17.0-1008.8~24.04.16.17.0-1010.10~24.04.16.17.0-1011.11~24.04.26.17.0-1013.13~24.04.16.17.0-1015.15~24.04.16.17.0-1017.17~24.04.16.17.0-1018.18~24.04.16.17.0-1020.20~24.04.1
6.17.0-1021.21~24.04.1
linux-azure-fde-6.17
Ubuntu:24.04:LTS
From an advisory covering 266 CVEs
before 6.17.0-1018.18~24.04.1, plus listed versions
6.17.0-1005.5~24.04.16.17.0-1010.10~24.04.16.17.0-1015.15~24.04.16.17.0-1017.17~24.04.1
6.17.0-1018.18~24.04.1
linux-nvidia-6.17
Ubuntu:24.04:LTS
From an advisory covering 227 CVEs
before 6.17.0-1031.31, plus listed versions
6.17.0-1004.46.17.0-1008.86.17.0-1014.146.17.0-1018.186.17.0-1021.216.17.0-1026.266.17.0-1029.29
6.17.0-1031.31

History

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

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

In short

CVE-2026-23077 is a high vulnerability (CVSS 7.8) in Linux, published February 4, 2026. No source lists public exploit code. EPSS puts the chance of exploitation in the next 30 days at 0.16%, the 5th percentile. Fixed in linux-lts 6.18.35-r1.

References

Show 194 moreShow less
This page doesn't list everything

Left out here: 76 versions, 109 references and the rest of 6 source descriptions. The JSON record has them.

MoveEnter Open