CVE-2022-49999
btrfs: fix space cache corruption and potential double allocations
In the Linux kernel, the following vulnerability has been resolved:
btrfs: fix space cache corruption and potential double allocations
When testing space_cache v2 on a large set of machines, we encountered a few symptoms:
- "unable to add free space :-17" (EEXIST) errors.
- Missing free space info items, sometimes caught with a "missing free space info for X" error.
- Double-accounted space: ranges that were allocated in the extent tree and also marked as free in the free space tree, ranges that were marked as allocated twice in the extent tree, or ranges that were marked as free twice in the free space tree. If the latter made it onto disk, the next reboot would hit the BUG_ON() in add_new_free_space().
- On some hosts with no on-disk corruption or error messages, the in-memory space cache (dumped with drgn) disagreed with the free space tree.
All of these symptoms have the same underlying cause: a race between caching the free space for a block group and returning free space to the in-memory space cache for pinned extents causes us to double-add a free range to the space cache. This race exists when free space is cached from the free space tree (space_cache=v2) or the extent tree (nospace_cache, or space_cache=v1 if the cache needs to be regenerated). struct btrfs_block_group::last_byte_to_unpin and struct btrfs_block_group::progress are supposed to protect against this race, but commit d0c2f4fa555e ("btrfs: make concurrent fsyncs wait less when waiting for a transaction commit") subtly broke this by allowing multiple transactions to be unpinning extents at the same time.
Specifically, the race is as follows:
- An extent is deleted from an uncached block group in transaction A.
- btrfs_commit_transaction() is called for transaction A.
- btrfs_run_delayed_refs() -> __btrfs_free_extent() runs the delayed ref for the deleted extent.
- __btrfs_free_extent() -> do_free_extent_accounting() -> add_to_free_space_tree() adds the deleted extent back to the free space tree.
- do_free_extent_accounting() -> btrfs_update_block_group() -> btrfs_cache_block_group() queues up the block group to get cached. block_group->progress is set to block_group->start.
- btrfs_commit_transaction() for transaction A calls switch_commit_roots(). It sets block_group->last_byte_to_unpin to block_group->progress, which is block_group->start because the block group hasn't been cached yet.
- The caching thread gets to our block group. Since the commit roots were already switched, load_free_space_tree() sees the deleted extent as free and adds it to the space cache. It finishes caching and sets block_group->progress to U64_MAX.
- btrfs_commit_transaction() advances transaction A to TRANS_STATE_SUPER_COMMITTED.
- fsync calls btrfs_commit_transaction() for transaction B. Since transaction A is already in TRANS_STATE_SUPER_COMMITTED and the commit is for fsync, it advances.
- btrfs_commit_transaction() for transaction B calls switch_commit_roots(). This time, the block group has already been cached, so it sets block_group->last_byte_to_unpin to U64_MAX.
- btrfs_commit_transaction() for transaction A calls btrfs_finish_extent_commit(), which calls unpin_extent_range() for the deleted extent. It sees last_byte_to_unpin set to U64_MAX (by transaction B!), so it adds the deleted extent to the space cache again!
This explains all of our symptoms above:
- If the sequence of events is exactly as described above, when the free space is re-added in step 11, it will fail with EEXIST.
- If another thread reallocates the deleted extent in between steps 7 and 11, then step 11 will silently re-add that space to the space cache as free even though it is actually allocated. Then, if that space is allocated again, the free space tree will be corrupted (namely, the wrong item will be deleted).
- If we don't catch this free space tree corr ---truncated---
Attack profile
How easy it is to exploit
- Attack vector
- Local
- Complexity
- Low
- Privileges needed
- Low
- User interaction
- None
What an attacker can affect
- Confidentiality
- High
- Integrity
- High
- Availability
- High
Exploit likelihood
What each source reports
CVE List Score used
7.8
btrfs: fix space cache corruption and potential double allocations
In the Linux kernel, the following vulnerability has been resolved:
btrfs: fix space cache corruption and potential double allocations
When testing space_cache v2 on a large set of machines, we encountered a few symptoms:
- "unable to add free space :-17" (EEXIST) errors.
- Missing free space info items, sometimes caught with a "missing free space info for X" error.
- Double-accounted space: ranges that were allocated in the extent tree and also marked as free in the free space tree, ranges that were marked as allocated twice in the extent tree, or ranges that were marked as free twice in the free space tree. If the latter made it onto disk, the next reboot would hit the BUG_ON() in add_new_free_space().
- On some hosts with no on-disk corruption or error messages, the in-memory space cache (dumped with drgn) disagreed with the free space tree.
All of these symptoms have the same underlying cause: a race between caching the free space for a block group and returning free space to the in-memory space cache for pinned extents causes us to double-add a free range to the space cache. This race exists when free space is cached from the free space tree (space_cache=v2) or the extent tree (nospace_cache, or space_cache=v1 if the cache needs to be regenerated). struct btrfs_block_group::last_byte_to_unpin and struct btrfs_block_group::progress are supposed to protect against this race, but commit d0c2f4fa555e ("btrfs: make concurrent fsyncs wait less when waiting for a transaction commit") subtly broke this by allowing multiple transactions to be unpinning extents at the same time.
Specifically, the race is as follows:
- An extent is deleted from an uncached block group in transaction A.
- btrfs_commit_transaction() is called for transaction A.
- btrfs_run_delayed_refs() -> __btrfs_free_extent() runs the delayed ref for the deleted extent.
- __btrfs_free_extent() -> do_free_extent_accounting() -> add_to_free_space_tree() adds the deleted extent back to the free space tree.
- do_free_extent_accounting() -> btrfs_update_block_group() -> btrfs_cache_block_group() queues up the block group to get cached. block_group->progress is set to block_group->start.
- btrfs_commit_transaction() for transaction A calls switch_commit_roots(). It sets block_group->last_byte_to_unpin to block_group->progress, which is block_group->start because the block group hasn't been cached yet.
- The caching thread gets to our block group. Since the commit roots were already switched, load_free_space_tree() sees the deleted extent as free and adds it to the space cache. It finishes caching and sets block_group->progress to U64_MAX.
- btrfs_commit_transaction() advances transaction A to TRANS_STATE_SUPER_COMMITTED.
- fsync calls btrfs_commit_transaction() for transaction B. Since transaction A is already in TRANS_STATE_SUPER_COMMITTED and the commit is for fsync, it advances.
- btrfs_commit_transaction() for transaction B calls switch_commit_roots(). This time, the block group has already been cached, so it sets block_group->last_byte_to_unpin to U64_MAX.
- btrfs_commit_transaction() for transaction A calls btrfs_finish_extent_commit(), which calls unpin_extent_range() for the deleted extent. It sees last_byte_to_unpin set to U64_MAX (by transaction B!), so it adds the deleted extent to the space cache again!
This explains all of our symptoms above:
- If the sequence of events is exactly as described above, when the free space is re-added in step 11, it will fail with EEXIST.
- If another thread reallocates the deleted extent in between steps 7 and 11, then step 11 will silently re-add that space to the space cache as free even though it is actually allocated. Then, if that space is allocated again, the free space tree will be corrupted (namely, the wrong item will be deleted).
- If we don't catch this free space tree corr ---truncated---
- Record
CVE-2022-49999- CVSS 3.1
- 7.8 High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H - Updated
- 2026-11-02
EUVDEUVD-2022-55278
7.8
In the Linux kernel, the following vulnerability has been resolved:
btrfs: fix space cache corruption and potential double allocations
When testing space_cache v2 on a large set of machines, we encountered a few symptoms:
- "unable to add free space :-17" (EEXIST) errors.
- Missing free space info items, sometimes caught with a "missing free space info for X" error.
- Double-accounted space: ranges that were allocated in the extent tree and also marked as free in the free space tree, ranges that were marked as allocated twice in the extent tree, or ranges that were marked as free twice in the free space tree. If the latter made it onto disk, the next reboot would hit the BUG_ON() in add_new_free_space().
- On some hosts with no on-disk corruption or error messages, the in-memory space cache (dumped with drgn) disagreed with the free space tree.
All of these symptoms have the same underlying cause: a race between caching the free space for a block group and returning free space to the in-memory space cache for pinned extents causes us to double-add a free range to the space cache. This race exists when free space is cached from the free space tree (space_cache=v2) or the extent tree (nospace_cache, or space_cache=v1 if the cache needs to be regenerated). struct btrfs_block_group::last_byte_to_unpin and struct btrfs_block_group::progress are supposed to protect against this race, but commit d0c2f4fa555e ("btrfs: make concurrent fsyncs wait less when waiting for a transaction commit") subtly broke this by allowing multiple transactions to be unpinning extents at the same time.
Specifically, the race is as follows:
- An extent is deleted from an uncached block group in transaction A.
- btrfs_commit_transaction() is called for transaction A.
- btrfs_run_delayed_refs() -> __btrfs_free_extent() runs the delayed ref for the deleted extent.
- __btrfs_free_extent() -> do_free_extent_accounting() -> add_to_free_space_tree() adds the deleted extent back to the free space tree.
- do_free_extent_accounting() -> btrfs_update_block_group() -> btrfs_cache_block_group() queues up the block group to get cached. block_group->progress is set to block_group->start.
- btrfs_commit_transaction() for transaction A calls switch_commit_roots(). It sets block_group->last_byte_to_unpin to block_group->progress, which is block_group->start because the block group hasn't been cached yet.
- The caching thread gets to our block group. Since the commit roots were already switched, load_free_space_tree() sees the deleted extent as free and adds it to the space cache. It finishes caching and sets block_group->progress to U64_MAX.
- btrfs_commit_transaction() advances transaction A to TRANS_STATE_SUPER_COMMITTED.
- fsync calls btrfs_commit_transaction() for transaction B. Since transaction A is already in TRANS_STATE_SUPER_COMMITTED and the commit is for fsync, it advances.
- btrfs_commit_transaction() for transaction B calls switch_commit_roots(). This time, the block group has already been cached, so it sets block_group->last_byte_to_unpin to U64_MAX.
- btrfs_commit_transaction() for transaction A calls btrfs_finish_extent_commit(), which calls unpin_extent_range() for the deleted extent. It sees last_byte_to_unpin set to U64_MAX (by transaction B!), so it adds the deleted extent to the space cache again!
This explains all of our symptoms above:
- If the sequence of events is exactly as described above, when the free space is re-added in step 11, it will fail with EEXIST.
- If another thread reallocates the deleted extent in between steps 7 and 11, then step 11 will silently re-add that space to the space cache as free even though it is actually allocated. Then, if that space is allocated again, the free space tree will be corrupted (namely, the wrong item will be deleted).
- If we don't catch this free space tree corr ---truncated---
- Record
EUVD-2022-55278- CVSS 3.1
- 7.8 High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H - Updated
- 2026-11-02
GitHub AdvisoriesGHSA-j8xg-f23q-2vmv
7.8
In the Linux kernel, the following vulnerability has been resolved: btrfs: fix space cache...
In the Linux kernel, the following vulnerability has been resolved:
btrfs: fix space cache corruption and potential double allocations
When testing space_cache v2 on a large set of machines, we encountered a few symptoms:
- "unable to add free space :-17" (EEXIST) errors.
- Missing free space info items, sometimes caught with a "missing free space info for X" error.
- Double-accounted space: ranges that were allocated in the extent tree and also marked as free in the free space tree, ranges that were marked as allocated twice in the extent tree, or ranges that were marked as free twice in the free space tree. If the latter made it onto disk, the next reboot would hit the BUG_ON() in add_new_free_space().
- On some hosts with no on-disk corruption or error messages, the in-memory space cache (dumped with drgn) disagreed with the free space tree.
All of these symptoms have the same underlying cause: a race between caching the free space for a block group and returning free space to the in-memory space cache for pinned extents causes us to double-add a free range to the space cache. This race exists when free space is cached from the free space tree (space_cache=v2) or the extent tree (nospace_cache, or space_cache=v1 if the cache needs to be regenerated). struct btrfs_block_group::last_byte_to_unpin and struct btrfs_block_group::progress are supposed to protect against this race, but commit d0c2f4fa555e ("btrfs: make concurrent fsyncs wait less when waiting for a transaction commit") subtly broke this by allowing multiple transactions to be unpinning extents at the same time.
Specifically, the race is as follows:
- An extent is deleted from an uncached block group in transaction A.
- btrfs_commit_transaction() is called for transaction A.
- btrfs_run_delayed_refs() -> __btrfs_free_extent() runs the delayed ref for the deleted extent.
- __btrfs_free_extent() -> do_free_extent_accounting() -> add_to_free_space_tree() adds the deleted extent back to the free space tree.
- do_free_extent_accounting() -> btrfs_update_block_group() -> btrfs_cache_block_group() queues up the block group to get cached. block_group->progress is set to block_group->start.
- btrfs_commit_transaction() for transaction A calls switch_commit_roots(). It sets block_group->last_byte_to_unpin to block_group->progress, which is block_group->start because the block group hasn't been cached yet.
- The caching thread gets to our block group. Since the commit roots were already switched, load_free_space_tree() sees the deleted extent as free and adds it to the space cache. It finishes caching and sets block_group->progress to U64_MAX.
- btrfs_commit_transaction() advances transaction A to TRANS_STATE_SUPER_COMMITTED.
- fsync calls btrfs_commit_transaction() for transaction B. Since transaction A is already in TRANS_STATE_SUPER_COMMITTED and the commit is for fsync, it advances.
- btrfs_commit_transaction() for transaction B calls switch_commit_roots(). This time, the block group has already been cached, so it sets block_group->last_byte_to_unpin to U64_MAX.
- btrfs_commit_transaction() for transaction A calls btrfs_finish_extent_commit(), which calls unpin_extent_range() for the deleted extent. It sees last_byte_to_unpin set to U64_MAX (by transaction B!), so it adds the deleted extent to the space cache again!
This explains all of our symptoms above:
- If the sequence of events is exactly as described above, when the free space is re-added in step 11, it will fail with EEXIST.
- If another thread reallocates the deleted extent in between steps 7 and 11, then step 11 will silently re-add that space to the space cache as free even though it is actually allocated. Then, if that space is allocated again, the free space tree will be corrupted (namely, the wrong item will be deleted).
- If we don't catch this free space tree corr ---truncated---
- Record
GHSA-j8xg-f23q-2vmv- CVSS 3.1
- 7.8 High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H - Weakness
- CWE-787
- Updated
- 2026-11-02
NVD
7.8
In the Linux kernel, the following vulnerability has been resolved:
btrfs: fix space cache corruption and potential double allocations
When testing space_cache v2 on a large set of machines, we encountered a few symptoms:
- "unable to add free space :-17" (EEXIST) errors.
- Missing free space info items, sometimes caught with a "missing free space info for X" error.
- Double-accounted space: ranges that were allocated in the extent tree and also marked as free in the free space tree, ranges that were marked as allocated twice in the extent tree, or ranges that were marked as free twice in the free space tree. If the latter made it onto disk, the next reboot would hit the BUG_ON() in add_new_free_space().
- On some hosts with no on-disk corruption or error messages, the in-memory space cache (dumped with drgn) disagreed with the free space tree.
All of these symptoms have the same underlying cause: a race between caching the free space for a block group and returning free space to the in-memory space cache for pinned extents causes us to double-add a free range to the space cache. This race exists when free space is cached from the free space tree (space_cache=v2) or the extent tree (nospace_cache, or space_cache=v1 if the cache needs to be regenerated). struct btrfs_block_group::last_byte_to_unpin and struct btrfs_block_group::progress are supposed to protect against this race, but commit d0c2f4fa555e ("btrfs: make concurrent fsyncs wait less when waiting for a transaction commit") subtly broke this by allowing multiple transactions to be unpinning extents at the same time.
Specifically, the race is as follows:
- An extent is deleted from an uncached block group in transaction A.
- btrfs_commit_transaction() is called for transaction A.
- btrfs_run_delayed_refs() -> __btrfs_free_extent() runs the delayed ref for the deleted extent.
- __btrfs_free_extent() -> do_free_extent_accounting() -> add_to_free_space_tree() adds the deleted extent back to the free space tree.
- do_free_extent_accounting() -> btrfs_update_block_group() -> btrfs_cache_block_group() queues up the block group to get cached. block_group->progress is set to block_group->start.
- btrfs_commit_transaction() for transaction A calls switch_commit_roots(). It sets block_group->last_byte_to_unpin to block_group->progress, which is block_group->start because the block group hasn't been cached yet.
- The caching thread gets to our block group. Since the commit roots were already switched, load_free_space_tree() sees the deleted extent as free and adds it to the space cache. It finishes caching and sets block_group->progress to U64_MAX.
- btrfs_commit_transaction() advances transaction A to TRANS_STATE_SUPER_COMMITTED.
- fsync calls btrfs_commit_transaction() for transaction B. Since transaction A is already in TRANS_STATE_SUPER_COMMITTED and the commit is for fsync, it advances.
- btrfs_commit_transaction() for transaction B calls switch_commit_roots(). This time, the block group has already been cached, so it sets block_group->last_byte_to_unpin to U64_MAX.
- btrfs_commit_transaction() for transaction A calls btrfs_finish_extent_commit(), which calls unpin_extent_range() for the deleted extent. It sees last_byte_to_unpin set to U64_MAX (by transaction B!), so it adds the deleted extent to the space cache again!
This explains all of our symptoms above:
- If the sequence of events is exactly as described above, when the free space is re-added in step 11, it will fail with EEXIST.
- If another thread reallocates the deleted extent in between steps 7 and 11, then step 11 will silently re-add that space to the space cache as free even though it is actually allocated. Then, if that space is allocated again, the free space tree will be corrupted (namely, the wrong item will be deleted).
- If we don't catch this free space tree corr ---truncated---
- Record
CVE-2022-49999- CVSS 3.1
- 7.8 High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H - Weakness
- CWE-787
- Updated
- 2026-11-02
OSV
7.8
btrfs: fix space cache corruption and potential double allocations
In the Linux kernel, the following vulnerability has been resolved:
btrfs: fix space cache corruption and potential double allocations
When testing space_cache v2 on a large set of machines, we encountered a few symptoms:
- "unable to add free space :-17" (EEXIST) errors.
- Missing free space info items, sometimes caught with a "missing free space info for X" error.
- Double-accounted space: ranges that were allocated in the extent tree and also marked as free in the free space tree, ranges that were marked as allocated twice in the extent tree, or ranges that were marked as free twice in the free space tree. If the latter made it onto disk, the next reboot would hit the BUG_ON() in add_new_free_space().
- On some hosts with no on-disk corruption or error messages, the in-memory space cache (dumped with drgn) disagreed with the free space tree.
All of these symptoms have the same underlying cause: a race between caching the free space for a block group and returning free space to the in-memory space cache for pinned extents causes us to double-add a free range to the space cache. This race exists when free space is cached from the free space tree (space_cache=v2) or the extent tree (nospace_cache, or space_cache=v1 if the cache needs to be regenerated). struct btrfs_block_group::last_byte_to_unpin and struct btrfs_block_group::progress are supposed to protect against this race, but commit d0c2f4fa555e ("btrfs: make concurrent fsyncs wait less when waiting for a transaction commit") subtly broke this by allowing multiple transactions to be unpinning extents at the same time.
Specifically, the race is as follows:
- An extent is deleted from an uncached block group in transaction A.
- btrfs_commit_transaction() is called for transaction A.
- btrfs_run_delayed_refs() -> __btrfs_free_extent() runs the delayed ref for the deleted extent.
- __btrfs_free_extent() -> do_free_extent_accounting() -> add_to_free_space_tree() adds the deleted extent back to the free space tree.
- do_free_extent_accounting() -> btrfs_update_block_group() -> btrfs_cache_block_group() queues up the block group to get cached. block_group->progress is set to block_group->start.
- btrfs_commit_transaction() for transaction A calls switch_commit_roots(). It sets block_group->last_byte_to_unpin to block_group->progress, which is block_group->start because the block group hasn't been cached yet.
- The caching thread gets to our block group. Since the commit roots were already switched, load_free_space_tree() sees the deleted extent as free and adds it to the space cache. It finishes caching and sets block_group->progress to U64_MAX.
- btrfs_commit_transaction() advances transaction A to TRANS_STATE_SUPER_COMMITTED.
- fsync calls btrfs_commit_transaction() for transaction B. Since transaction A is already in TRANS_STATE_SUPER_COMMITTED and the commit is for fsync, it advances.
- btrfs_commit_transaction() for transaction B calls switch_commit_roots(). This time, the block group has already been cached, so it sets block_group->last_byte_to_unpin to U64_MAX.
- btrfs_commit_transaction() for transaction A calls btrfs_finish_extent_commit(), which calls unpin_extent_range() for the deleted extent. It sees last_byte_to_unpin set to U64_MAX (by transaction B!), so it adds the deleted extent to the space cache again!
This explains all of our symptoms above:
- If the sequence of events is exactly as described above, when the free space is re-added in step 11, it will fail with EEXIST.
- If another thread reallocates the deleted extent in between steps 7 and 11, then step 11 will silently re-add that space to the space cache as free even though it is actually allocated. Then, if that space is allocated again, the free space tree will be corrupted (namely, the wrong item will be deleted).
- If we don't catch this free space tree corr ---truncated---
- Record
CVE-2022-49999- CVSS 3.1
- 7.8 High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H - Updated
- 2026-11-02
OSVDEBIAN-CVE-2022-49999
7.8
In the Linux kernel, the following vulnerability has been resolved: btrfs: fix space cache corruption and potential double allocations When testing space_cache v2 on a large set of machines, we encountered a few symptoms: 1. "unable to add free space :-17" (EEXIST) errors. 2. Missing free space info items, sometimes caught with a "missing free space info for X" error. 3. Double-accounted space: ranges that were allocated in the extent tree and also marked as free in the free space tree, ranges that were marked as allocated twice in the extent tree, or ranges that were marked as free twice in the free space tree. If the latter made it onto disk, the next reboot would hit the BUG_ON() in add_new_free_space(). 4. On some hosts with no on-disk corruption or error messages, the in-memory space cache (dumped with drgn) disagreed with the free space tree. All of these symptoms have the same underlying cause: a race between caching the free space for a block group and returning free space to the in-memory space cache for pinned extents causes us to double-add a free range to the space cache. This race exists when free space is cached from the free space tree (space_cache=v2) or the extent tree (nospace_cache, or space_cache=v1 if the cache needs to be regenerated). struct btrfs_block_group::last_byte_to_unpin and struct btrfs_block_group::progress are supposed to protect against this race, but commit d0c2f4fa555e ("btrfs: make concurrent fsyncs wait less when waiting for a transaction commit") subtly broke this by allowing multiple transactions to be unpinning extents at the same time. Specifically, the race is as follows: 1. An extent is deleted from an uncached block group in transaction A. 2. btrfs_commit_transaction() is called for transaction A. 3. btrfs_run_delayed_refs() -> __btrfs_free_extent() runs the delayed ref for the deleted extent. 4. __btrfs_free_extent() -> do_free_extent_accounting() -> add_to_free_space_tree() adds the deleted extent back to the free space tree. 5. do_free_extent_accounting() -> btrfs_update_block_group() -> btrfs_cache_block_group() queues up the block group to get cached. block_group->progress is set to block_group->start. 6. btrfs_commit_transaction() for transaction A calls switch_commit_roots(). It sets block_group->last_byte_to_unpin to block_group->progress, which is block_group->start because the block group hasn't been cached yet. 7. The caching thread gets to our block group. Since the commit roots were already switched, load_free_space_tree() sees the deleted extent as free and adds it to the space cache. It finishes caching and sets block_group->progress to U64_MAX. 8. btrfs_commit_transaction() advances transaction A to TRANS_STATE_SUPER_COMMITTED. 9. fsync calls btrfs_commit_transaction() for transaction B. Since transaction A is already in TRANS_STATE_SUPER_COMMITTED and the commit is for fsync, it advances. 10. btrfs_commit_transaction() for transaction B calls switch_commit_roots(). This time, the block group has already been cached, so it sets block_group->last_byte_to_unpin to U64_MAX. 11. btrfs_commit_transaction() for transaction A calls btrfs_finish_extent_commit(), which calls unpin_extent_range() for the deleted extent. It sees last_byte_to_unpin set to U64_MAX (by transaction B!), so it adds the deleted extent to the space cache again! This explains all of our symptoms above: * If the sequence of events is exactly as described above, when the free space is re-added in step 11, it will fail with EEXIST. * If another thread reallocates the deleted extent in between steps 7 and 11, then step 11 will silently re-add that space to the space cache as free even though it is actually allocated. Then, if that space is allocated again, the free space tree will be corrupted (namely, the wrong item will be deleted). * If we don't catch this free space tree corr ---truncated---
- Record
DEBIAN-CVE-2022-49999- CVSS 3.1
- 7.8 High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H - Updated
- 2026-11-03
Show 6 moreShow less
OSVUBUNTU-CVE-2022-49999
5.8
In the Linux kernel, the following vulnerability has been resolved: btrfs: fix space cache corruption and potential double allocations When testing space_cache v2 on a large set of machines, we encountered a few symptoms: 1. "unable to add free space :-17" (EEXIST) errors. 2. Missing free space info items, sometimes caught with a "missing free space info for X" error. 3. Double-accounted space: ranges that were allocated in the extent tree and also marked as free in the free space tree, ranges that were marked as allocated twice in the extent tree, or ranges that were marked as free twice in the free space tree. If the latter made it onto disk, the next reboot would hit the BUG_ON() in add_new_free_space(). 4. On some hosts with no on-disk corruption or error messages, the in-memory space cache (dumped with drgn) disagreed with the free space tree. All of these symptoms have the same underlying cause: a race between caching the free space for a block group and returning free space to the in-memory space cache for pinned extents causes us to double-add a free range to the space cache. This race exists when free space is cached from the free space tree (space_cache=v2) or the extent tree (nospace_cache, or space_cache=v1 if the cache needs to be regenerated). struct btrfs_block_group::last_byte_to_unpin and struct btrfs_block_group::progress are supposed to protect against this race, but commit d0c2f4fa555e ("btrfs: make concurrent fsyncs wait less when waiting for a transaction commit") subtly broke this by allowing multiple transactions to be unpinning extents at the same time. Specifically, the race is as follows: 1. An extent is deleted from an uncached block group in transaction A. 2. btrfs_commit_transaction() is called for transaction A. 3. btrfs_run_delayed_refs() -> __btrfs_free_extent() runs the delayed ref for the deleted extent. 4. __btrfs_free_extent() -> do_free_extent_accounting() -> add_to_free_space_tree() adds the deleted extent back to the free space tree. 5. do_free_extent_accounting() -> btrfs_update_block_group() -> btrfs_cache_block_group() queues up the block group to get cached. block_group->progress is set to block_group->start. 6. btrfs_commit_transaction() for transaction A calls switch_commit_roots(). It sets block_group->last_byte_to_unpin to block_group->progress, which is block_group->start because the block group hasn't been cached yet. 7. The caching thread gets to our block group. Since the commit roots were already switched, load_free_space_tree() sees the deleted extent as free and adds it to the space cache. It finishes caching and sets block_group->progress to U64_MAX. 8. btrfs_commit_transaction() advances transaction A to TRANS_STATE_SUPER_COMMITTED. 9. fsync calls btrfs_commit_transaction() for transaction B. Since transaction A is already in TRANS_STATE_SUPER_COMMITTED and the commit is for fsync, it advances. 10. btrfs_commit_transaction() for transaction B calls switch_commit_roots(). This time, the block group has already been cached, so it sets block_group->last_byte_to_unpin to U64_MAX. 11. btrfs_commit_transaction() for transaction A calls btrfs_finish_extent_commit(), which calls unpin_extent_range() for the deleted extent. It sees last_byte_to_unpin set to U64_MAX (by transaction B!), so it adds the deleted extent to the space cache again! This explains all of our symptoms above: * If the sequence of events is exactly as described above, when the free space is re-added in step 11, it will fail with EEXIST. * If another thread reallocates the deleted extent in between steps 7 and 11, then step 11 will silently re-add that space to the space cache as free even though it is actually allocated. Then, if that space is allocated again, the free space tree will be corrupted (namely, the wrong item will be deleted). * If we don't catch this free space tree corr ---truncated---
- Record
UBUNTU-CVE-2022-49999- CVSS 4.0
- 5.8 Medium
CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:N/VC:L/VI:L/VA:H/SC:N/SI:N/SA:N - CVSS 3.1
- 7.8 High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H - Updated
- 2026-11-06
OSVSUSE-SU-2025:02264-1 No score
Security update for the Linux Kernel
The SUSE Linux Enterprise 15 SP5 kernel was updated to receive various security bugfixes.
The following security bugs were fixed:
- CVE-2021-47557: net/sched: sch_ets: do not peek at classes beyond 'nbands' (bsc#1207361 bsc#1225468).
- CVE-2021-47595: net/sched: sch_ets: do not remove idle classes from the round-robin list (bsc#1207361 bsc#1226552).
- CVE-2023-52924: netfilter: nf_tables: do not skip expired elements during walk (bsc#1236821).
- CVE-2023-52925: netfilter: nf_tables: do not fail inserts if duplicate has expired (bsc#1236822).
- CVE-2024-26808: netfilter: nft_chain_filter: handle NETDEV_UNREGISTER for inet/ingress basechain (bsc#1222634).
- CVE-2024-26924: scsi: lpfc: Release hbalock before calling lpfc_worker_wake_up() (bsc#1225820).
- CVE-2024-27397: kabi: place tstamp needed for nftables set in a hole (bsc#1224095).
- CVE-2024-36978: net: sched: sch_multiq: fix possible OOB write in multiq_tune() (bsc#1226514).
- CVE-2024-46800: sch/netem: fix use after free in netem_dequeue (bsc#1230827).
- CVE-2024-53125: bpf: sync_linked_regs() must preserve subreg_def (bsc#1234156).
- CVE-2024-53141: netfilter: ipset: add missing range check in bitmap_ip_uadt (bsc#1234381).
- CVE-2024-53197: ALSA: usb-audio: Fix potential out-of-bound accesses for Extigy and Mbox devices (bsc#1235464).
- CVE-2024-56770: sch/netem: fix use after free in netem_dequeue (bsc#1235637).
- CVE-2025-21700: net: sched: Disallow replacing of child qdisc from one parent to another (bsc#1237159).
- CVE-2025-21702: pfifo_tail_enqueue: Drop new packet when sch->limit == 0 (bsc#1237312).
- CVE-2025-21703: netem: Update sch->q.qlen before qdisc_tree_reduce_backlog() (bsc#1237313).
- CVE-2025-21756: vsock: Orphan socket after transport release (bsc#1238876).
- CVE-2025-23141: KVM: x86: Acquire SRCU in KVM_GET_MP_STATE to protect guest memory accesses (bsc#1242782).
- CVE-2025-37752: net_sched: sch_sfq: move the limit validation (bsc#1242504).
- CVE-2025-37823: net_sched: hfsc: Fix a potential UAF in hfsc_dequeue() too (bsc#1242924).
- CVE-2025-37890: net_sched: hfsc: Fix a UAF vulnerability in class with netem as child qdisc (bsc#1243330).
- CVE-2025-37997: netfilter: ipset: fix region locking in hash types (bsc#1243832).
- CVE-2025-38000: sch_hfsc: Fix qlen accounting bug when using peek in hfsc_enqueue() (bsc#1244277).
- CVE-2025-38001: net_sched: hfsc: Address reentrant enqueue adding class to eltree twice (bsc#1244234).
- CVE-2025-38014: dmaengine: idxd: Refactor remove call with idxd_cleanup() helper (bsc#1244732).
- CVE-2025-38060: bpf: abort verification if env->cur_state->loop_entry != NULL (bsc#1245155).
- CVE-2025-38083: net_sched: prio: fix a race in prio_tune() (bsc#1245183).
The following non-security bugs were fixed:
- ALSA: usb-audio: Fix a DMA to stack memory bug (git-fixes).
- Fix reference in 'net_sched: sch_sfq: use a temporary work area for validating configuration' (bsc#1242504)
- MyBS: Correctly generate build flags for non-multibuild package limit (bsc# 1244241) Fixes: 0999112774fc ('MyBS: Use buildflags to set which package to build')
- MyBS: Do not build kernel-obs-qa with limit_packages Fixes: 58e3f8c34b2b ('bs-upload-kernel: Pass limit_packages also on multibuild')
- MyBS: Simplify qa_expr generation Start with a 0 which makes the expression valid even if there are no QA repositories (currently does not happen). Then separator is always needed.
- bs-upload-kernel: Pass limit_packages also on multibuild Fixes: 0999112774fc ('MyBS: Use buildflags to set which package to build') Fixes: 747f601d4156 ('bs-upload-kernel, MyBS, Buildresults: Support multibuild (JSC-SLE#5501, boo#1211226, bsc#1218184)')
- hugetlb: unshare some PMDs when splitting VMAs (bsc#1245431).
- kernel-source: Do not use multiple -r in sed parameters
- kernel-source: Remove log.sh from sources
- mkspec: Exclude rt flavor from kernel-syms dependencies (bsc#1244337).
- mm/hugetlb: fix huge_pmd_unshare() vs GUP-fast race (bsc#1245431).
- mm/hugetlb: unshare…
- Record
SUSE-SU-2025:02264-1- Updated
- 2026-11-02
OSVSUSE-SU-2025:02321-1 No score
Security update for the Linux Kernel
The SUSE Linux Enterprise 15 SP5 RT kernel was updated to receive various security bugfixes.
The following security bugs were fixed:
- CVE-2021-47557: net/sched: sch_ets: do not peek at classes beyond 'nbands' (bsc#1207361 bsc#1225468).
- CVE-2021-47595: net/sched: sch_ets: do not remove idle classes from the round-robin list (bsc#1207361 bsc#1226552).
- CVE-2023-52924: netfilter: nf_tables: do not skip expired elements during walk (bsc#1236821).
- CVE-2023-52925: netfilter: nf_tables: do not fail inserts if duplicate has expired (bsc#1236822).
- CVE-2024-26808: netfilter: nft_chain_filter: handle NETDEV_UNREGISTER for inet/ingress basechain (bsc#1222634).
- CVE-2024-26924: scsi: lpfc: Release hbalock before calling lpfc_worker_wake_up() (bsc#1225820).
- CVE-2024-27397: kabi: place tstamp needed for nftables set in a hole (bsc#1224095).
- CVE-2024-28956: x86/its: Add support for ITS-safe indirect thunk (bsc#1242006).
- CVE-2024-36978: net: sched: sch_multiq: fix possible OOB write in multiq_tune() (bsc#1226514).
- CVE-2024-46800: sch/netem: fix use after free in netem_dequeue (bsc#1230827).
- CVE-2024-53125: bpf: sync_linked_regs() must preserve subreg_def (bsc#1234156).
- CVE-2024-53141: netfilter: ipset: add missing range check in bitmap_ip_uadt (bsc#1234381).
- CVE-2024-53197: ALSA: usb-audio: Fix potential out-of-bound accesses for Extigy and Mbox devices (bsc#1235464).
- CVE-2024-56770: sch/netem: fix use after free in netem_dequeue (bsc#1235637).
- CVE-2025-21700: net: sched: Disallow replacing of child qdisc from one parent to another (bsc#1237159).
- CVE-2025-21702: pfifo_tail_enqueue: Drop new packet when sch->limit == 0 (bsc#1237312).
- CVE-2025-21703: netem: Update sch->q.qlen before qdisc_tree_reduce_backlog() (bsc#1237313).
- CVE-2025-21756: vsock: Orphan socket after transport release (bsc#1238876).
- CVE-2025-23141: KVM: x86: Acquire SRCU in KVM_GET_MP_STATE to protect guest memory accesses (bsc#1242782).
- CVE-2025-37752: net_sched: sch_sfq: move the limit validation (bsc#1242504).
- CVE-2025-37785: ext4: fix OOB read when checking dotdot dir (bsc#1241640).
- CVE-2025-37823: net_sched: hfsc: Fix a potential UAF in hfsc_dequeue() too (bsc#1242924).
- CVE-2025-37890: net_sched: hfsc: Fix a UAF vulnerability in class with netem as child qdisc (bsc#1243330).
- CVE-2025-37997: netfilter: ipset: fix region locking in hash types (bsc#1243832).
- CVE-2025-38000: sch_hfsc: Fix qlen accounting bug when using peek in hfsc_enqueue() (bsc#1244277).
- CVE-2025-38001: net_sched: hfsc: Address reentrant enqueue adding class to eltree twice (bsc#1244234).
- CVE-2025-38014: dmaengine: idxd: Refactor remove call with idxd_cleanup() helper (bsc#1244732).
- CVE-2025-38060: bpf: abort verification if env->cur_state->loop_entry != NULL (bsc#1245155).
- CVE-2025-38083: net_sched: prio: fix a race in prio_tune() (bsc#1245183).
The following non-security bugs were fixed:
- ALSA: usb-audio: Fix a DMA to stack memory bug (git-fixes).
- Fix conditional for selecting gcc-13 Fixes: 51dacec21eb1 ('Use gcc-13 for build on SLE16 (jsc#PED-10028).')
- Fix reference in 'net_sched: sch_sfq: use a temporary work area for validating configuration' (bsc#1242504)
- MyBS: Correctly generate build flags for non-multibuild package limit (bsc# 1244241) Fixes: 0999112774fc ('MyBS: Use buildflags to set which package to build')
- MyBS: Do not build kernel-obs-qa with limit_packages Fixes: 58e3f8c34b2b ('bs-upload-kernel: Pass limit_packages also on multibuild')
- MyBS: Simplify qa_expr generation Start with a 0 which makes the expression valid even if there are no QA repositories (currently does not happen). Then separator is always needed.
- Require zstd in kernel-default-devel when module compression is zstd To use ksym-provides tool modules need to be uncompressed. Without zstd at least kernel-default-base does not have provides. Link: https://github.com/openSUSE/rpm-config-SUSE/pull/82
- Use gcc-13 for build on SLE16 (jsc#PED-10028).
- add…
- Record
SUSE-SU-2025:02321-1- Updated
- 2026-11-02
OSVSUSE-SU-2025:02322-1 No score
Security update for the Linux Kernel
The SUSE Linux Enterprise 15 SP4 RT kernel was updated to receive various security bugfixes.
The following security bugs were fixed:
- CVE-2021-47557: net/sched: sch_ets: do not peek at classes beyond 'nbands' (bsc#1207361 bsc#1225468).
- CVE-2021-47595: net/sched: sch_ets: do not remove idle classes from the round-robin list (bsc#1207361 bsc#1226552).
- CVE-2023-52924: netfilter: nf_tables: do not skip expired elements during walk (bsc#1236821).
- CVE-2023-52925: netfilter: nf_tables: do not fail inserts if duplicate has expired (bsc#1236822).
- CVE-2024-26808: netfilter: nft_chain_filter: handle NETDEV_UNREGISTER for inet/ingress basechain (bsc#1222634).
- CVE-2024-26924: scsi: lpfc: Release hbalock before calling lpfc_worker_wake_up() (bsc#1225820).
- CVE-2024-27397: kabi: place tstamp needed for nftables set in a hole (bsc#1224095).
- CVE-2024-36978: net: sched: sch_multiq: fix possible OOB write in multiq_tune() (bsc#1226514).
- CVE-2024-46800: sch/netem: fix use after free in netem_dequeue (bsc#1230827).
- CVE-2024-53057: net/sched: stop qdisc_tree_reduce_backlog on TC_H_ROOT (bsc#1233551).
- CVE-2024-53125: bpf: sync_linked_regs() must preserve subreg_def (bsc#1234156).
- CVE-2024-53141: netfilter: ipset: add missing range check in bitmap_ip_uadt (bsc#1234381).
- CVE-2024-56770: sch/netem: fix use after free in netem_dequeue (bsc#1235637).
- CVE-2024-57947: netfilter: nf_set_pipapo: fix initial map fill (bsc#1236333).
- CVE-2025-21700: net: sched: Disallow replacing of child qdisc from one parent to another (bsc#1237159).
- CVE-2025-21702: pfifo_tail_enqueue: Drop new packet when sch->limit == 0 (bsc#1237312).
- CVE-2025-21703: netem: Update sch->q.qlen before qdisc_tree_reduce_backlog() (bsc#1237313).
- CVE-2025-21756: vsock: Orphan socket after transport release (bsc#1238876).
- CVE-2025-23141: KVM: x86: Acquire SRCU in KVM_GET_MP_STATE to protect guest memory accesses (bsc#1242782).
- CVE-2025-37752: net_sched: sch_sfq: move the limit validation (bsc#1242504).
- CVE-2025-37797: net_sched: hfsc: Fix a UAF vulnerability in class handling (bsc#1242417).
- CVE-2025-37823: net_sched: hfsc: Fix a potential UAF in hfsc_dequeue() too (bsc#1242924).
- CVE-2025-37890: net_sched: hfsc: Fix a UAF vulnerability in class with netem as child qdisc (bsc#1243330).
- CVE-2025-37997: netfilter: ipset: fix region locking in hash types (bsc#1243832).
- CVE-2025-38000: sch_hfsc: Fix qlen accounting bug when using peek in hfsc_enqueue() (bsc#1244277).
- CVE-2025-38001: net_sched: hfsc: Address reentrant enqueue adding class to eltree twice (bsc#1244234).
- CVE-2025-38014: dmaengine: idxd: Refactor remove call with idxd_cleanup() helper (bsc#1244732).
- CVE-2025-38083: net_sched: prio: fix a race in prio_tune() (bsc#1245183).
The following non-security bugs were fixed:
- Fix conditional for selecting gcc-13 Fixes: 51dacec21eb1 ('Use gcc-13 for build on SLE16 (jsc#PED-10028).')
- Fix reference in 'net_sched: sch_sfq: use a temporary work area for validating configuration' (bsc#1242504)
- MyBS: Correctly generate build flags for non-multibuild package limit (bsc# 1244241) Fixes: 0999112774fc ('MyBS: Use buildflags to set which package to build')
- MyBS: Do not build kernel-obs-qa with limit_packages Fixes: 58e3f8c34b2b ('bs-upload-kernel: Pass limit_packages also on multibuild')
- MyBS: Simplify qa_expr generation Start with a 0 which makes the expression valid even if there are no QA repositories (currently does not happen). Then separator is always needed.
- Require zstd in kernel-default-devel when module compression is zstd To use ksym-provides tool modules need to be uncompressed. Without zstd at least kernel-default-base does not have provides. Link: https://github.com/openSUSE/rpm-config-SUSE/pull/82
- Test the correct macro to detect RT kernel build Fixes: 470cd1a41502 ('kernel-binary: Support livepatch_rt with merged RT branch')
- Use gcc-13 for build on SLE16 (jsc#PED-10028).
- add nf_tables for iptables non-legacy network…
- Record
SUSE-SU-2025:02322-1- Updated
- 2026-11-02
OSVSUSE-SU-2025:02537-1 No score
Security update for the Linux Kernel
The SUSE Linux Enterprise 15 SP4 kernel was updated to receive various security bugfixes.
The following security bugs were fixed:
- CVE-2021-47557: net/sched: sch_ets: do not peek at classes beyond 'nbands' (bsc#1207361 bsc#1225468).
- CVE-2021-47595: net/sched: sch_ets: do not remove idle classes from the round-robin list (bsc#1207361 bsc#1226552).
- CVE-2023-52924: netfilter: nf_tables: do not skip expired elements during walk (bsc#1236821).
- CVE-2023-52925: netfilter: nf_tables: do not fail inserts if duplicate has expired (bsc#1236822).
- CVE-2024-26808: netfilter: nft_chain_filter: handle NETDEV_UNREGISTER for inet/ingress basechain (bsc#1222634).
- CVE-2024-26924: scsi: lpfc: Release hbalock before calling lpfc_worker_wake_up() (bsc#1225820).
- CVE-2024-27397: kabi: place tstamp needed for nftables set in a hole (bsc#1224095).
- CVE-2024-36978: net: sched: sch_multiq: fix possible OOB write in multiq_tune() (bsc#1226514).
- CVE-2024-46800: sch/netem: fix use after free in netem_dequeue (bsc#1230827).
- CVE-2024-53057: net/sched: stop qdisc_tree_reduce_backlog on TC_H_ROOT (bsc#1233551).
- CVE-2024-53125: bpf: sync_linked_regs() must preserve subreg_def (bsc#1234156).
- CVE-2024-53141: netfilter: ipset: add missing range check in bitmap_ip_uadt (bsc#1234381).
- CVE-2024-56770: sch/netem: fix use after free in netem_dequeue (bsc#1235637).
- CVE-2024-57947: netfilter: nf_set_pipapo: fix initial map fill (bsc#1236333).
- CVE-2025-21700: net: sched: Disallow replacing of child qdisc from one parent to another (bsc#1237159).
- CVE-2025-21702: pfifo_tail_enqueue: Drop new packet when sch->limit == 0 (bsc#1237312).
- CVE-2025-21703: netem: Update sch->q.qlen before qdisc_tree_reduce_backlog() (bsc#1237313).
- CVE-2025-21756: vsock: Orphan socket after transport release (bsc#1238876).
- CVE-2025-23141: KVM: x86: Acquire SRCU in KVM_GET_MP_STATE to protect guest memory accesses (bsc#1242782).
- CVE-2025-37752: net_sched: sch_sfq: move the limit validation (bsc#1242504).
- CVE-2025-37797: net_sched: hfsc: Fix a UAF vulnerability in class handling (bsc#1242417).
- CVE-2025-37823: net_sched: hfsc: Fix a potential UAF in hfsc_dequeue() too (bsc#1242924).
- CVE-2025-37890: net_sched: hfsc: Fix a UAF vulnerability in class with netem as child qdisc (bsc#1243330).
- CVE-2025-37997: netfilter: ipset: fix region locking in hash types (bsc#1243832).
- CVE-2025-38000: sch_hfsc: Fix qlen accounting bug when using peek in hfsc_enqueue() (bsc#1244277).
- CVE-2025-38001: net_sched: hfsc: Address reentrant enqueue adding class to eltree twice (bsc#1244234).
- CVE-2025-38014: dmaengine: idxd: Refactor remove call with idxd_cleanup() helper (bsc#1244732).
- CVE-2025-38083: net_sched: prio: fix a race in prio_tune() (bsc#1245183).
The following non-security bugs were fixed:
- Fix conditional for selecting gcc-13 Fixes: 51dacec21eb1 ('Use gcc-13 for build on SLE16 (jsc#PED-10028).')
- Fix reference in 'net_sched: sch_sfq: use a temporary work area for validating configuration' (bsc#1242504)
- MyBS: Correctly generate build flags for non-multibuild package limit (bsc# 1244241) Fixes: 0999112774fc ('MyBS: Use buildflags to set which package to build')
- MyBS: Do not build kernel-obs-qa with limit_packages Fixes: 58e3f8c34b2b ('bs-upload-kernel: Pass limit_packages also on multibuild')
- MyBS: Simplify qa_expr generation Start with a 0 which makes the expression valid even if there are no QA repositories (currently does not happen). Then separator is always needed.
- Require zstd in kernel-default-devel when module compression is zstd To use ksym-provides tool modules need to be uncompressed. Without zstd at least kernel-default-base does not have provides. Link: https://github.com/openSUSE/rpm-config-SUSE/pull/82
- Use gcc-13 for build on SLE16 (jsc#PED-10028).
- add nf_tables for iptables non-legacy network handling This is needed for example by docker on the Alpine Linux distribution, but can also be used on openSUSE.
- bs-upload-kernel: Pass…
- Record
SUSE-SU-2025:02537-1- Updated
- 2026-11-02
OSVSUSE-SU-2025:2264-1 No score
Security update for the Linux Kernel
The SUSE Linux Enterprise 15 SP5 kernel was updated to receive various security bugfixes.
The following security bugs were fixed:
- CVE-2021-47557: net/sched: sch_ets: do not peek at classes beyond 'nbands' (bsc#1207361 bsc#1225468).
- CVE-2021-47595: net/sched: sch_ets: do not remove idle classes from the round-robin list (bsc#1207361 bsc#1226552).
- CVE-2023-52924: netfilter: nf_tables: do not skip expired elements during walk (bsc#1236821).
- CVE-2023-52925: netfilter: nf_tables: do not fail inserts if duplicate has expired (bsc#1236822).
- CVE-2024-26808: netfilter: nft_chain_filter: handle NETDEV_UNREGISTER for inet/ingress basechain (bsc#1222634).
- CVE-2024-26924: scsi: lpfc: Release hbalock before calling lpfc_worker_wake_up() (bsc#1225820).
- CVE-2024-27397: kabi: place tstamp needed for nftables set in a hole (bsc#1224095).
- CVE-2024-36978: net: sched: sch_multiq: fix possible OOB write in multiq_tune() (bsc#1226514).
- CVE-2024-46800: sch/netem: fix use after free in netem_dequeue (bsc#1230827).
- CVE-2024-53125: bpf: sync_linked_regs() must preserve subreg_def (bsc#1234156).
- CVE-2024-53141: netfilter: ipset: add missing range check in bitmap_ip_uadt (bsc#1234381).
- CVE-2024-53197: ALSA: usb-audio: Fix potential out-of-bound accesses for Extigy and Mbox devices (bsc#1235464).
- CVE-2024-56770: sch/netem: fix use after free in netem_dequeue (bsc#1235637).
- CVE-2025-21700: net: sched: Disallow replacing of child qdisc from one parent to another (bsc#1237159).
- CVE-2025-21702: pfifo_tail_enqueue: Drop new packet when sch->limit == 0 (bsc#1237312).
- CVE-2025-21703: netem: Update sch->q.qlen before qdisc_tree_reduce_backlog() (bsc#1237313).
- CVE-2025-21756: vsock: Orphan socket after transport release (bsc#1238876).
- CVE-2025-23141: KVM: x86: Acquire SRCU in KVM_GET_MP_STATE to protect guest memory accesses (bsc#1242782).
- CVE-2025-37752: net_sched: sch_sfq: move the limit validation (bsc#1242504).
- CVE-2025-37823: net_sched: hfsc: Fix a potential UAF in hfsc_dequeue() too (bsc#1242924).
- CVE-2025-37890: net_sched: hfsc: Fix a UAF vulnerability in class with netem as child qdisc (bsc#1243330).
- CVE-2025-37997: netfilter: ipset: fix region locking in hash types (bsc#1243832).
- CVE-2025-38000: sch_hfsc: Fix qlen accounting bug when using peek in hfsc_enqueue() (bsc#1244277).
- CVE-2025-38001: net_sched: hfsc: Address reentrant enqueue adding class to eltree twice (bsc#1244234).
- CVE-2025-38014: dmaengine: idxd: Refactor remove call with idxd_cleanup() helper (bsc#1244732).
- CVE-2025-38060: bpf: abort verification if env->cur_state->loop_entry != NULL (bsc#1245155).
- CVE-2025-38083: net_sched: prio: fix a race in prio_tune() (bsc#1245183).
The following non-security bugs were fixed:
- ALSA: usb-audio: Fix a DMA to stack memory bug (git-fixes).
- Fix reference in 'net_sched: sch_sfq: use a temporary work area for validating configuration' (bsc#1242504)
- MyBS: Correctly generate build flags for non-multibuild package limit (bsc# 1244241) Fixes: 0999112774fc ('MyBS: Use buildflags to set which package to build')
- MyBS: Do not build kernel-obs-qa with limit_packages Fixes: 58e3f8c34b2b ('bs-upload-kernel: Pass limit_packages also on multibuild')
- MyBS: Simplify qa_expr generation Start with a 0 which makes the expression valid even if there are no QA repositories (currently does not happen). Then separator is always needed.
- bs-upload-kernel: Pass limit_packages also on multibuild Fixes: 0999112774fc ('MyBS: Use buildflags to set which package to build') Fixes: 747f601d4156 ('bs-upload-kernel, MyBS, Buildresults: Support multibuild (JSC-SLE#5501, boo#1211226, bsc#1218184)')
- hugetlb: unshare some PMDs when splitting VMAs (bsc#1245431).
- kernel-source: Do not use multiple -r in sed parameters
- kernel-source: Remove log.sh from sources
- mkspec: Exclude rt flavor from kernel-syms dependencies (bsc#1244337).
- mm/hugetlb: fix huge_pmd_unshare() vs GUP-fast race (bsc#1245431).
- mm/hugetlb: unshare…
- Record
SUSE-SU-2025:2264-1- Updated
- 2026-11-02
Affected products
Affected packages
| Package | Affected | Fixed |
|---|---|---|
KernelLinux |
5.12.0 up to 5.15.65, 5.16.0 up to 5.19.6 | 5.15.655.19.6 |
linuxDebian:12 |
before 6.0.2-1 | 6.0.2-1 |
linuxDebian:13 |
before 6.0.2-1 | 6.0.2-1 |
linuxDebian:14 |
before 6.0.2-1 | 6.0.2-1 |
kernel-defaultSUSE:Linux Enterprise Micro 5.5 From an advisory covering 258 CVEs |
before 5.14.21-150500.55.113.1 | 5.14.21-150500.55.113.1 |
kernel-default-baseSUSE:Linux Enterprise Micro 5.5 From an advisory covering 258 CVEs |
before 5.14.21-150500.55.113.1.150500.6.53.1 | 5.14.21-150500.55.113.1.150500.6.53.1 |
kernel-sourceSUSE:Linux Enterprise Micro 5.5 From an advisory covering 258 CVEs |
before 5.14.21-150500.55.113.1 | 5.14.21-150500.55.113.1 |
kernel-defaultSUSE:Linux Enterprise Live Patching 15 SP5 From an advisory covering 258 CVEs |
before 5.14.21-150500.55.113.1 | 5.14.21-150500.55.113.1 |
kernel-livepatch-SLE15-SP5_Update_28SUSE:Linux Enterprise Live Patching 15 SP5 From an advisory covering 258 CVEs |
before 1-150500.11.3.1 | 1-150500.11.3.1 |
kernel-64kbSUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOS From an advisory covering 258 CVEs |
before 5.14.21-150500.55.113.1 | 5.14.21-150500.55.113.1 |
Show 179 moreShow less
| Package | Affected | Fixed |
|---|---|---|
kernel-defaultSUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOS From an advisory covering 258 CVEs |
before 5.14.21-150500.55.113.1 | 5.14.21-150500.55.113.1 |
kernel-default-baseSUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOS From an advisory covering 258 CVEs |
before 5.14.21-150500.55.113.1.150500.6.53.1 | 5.14.21-150500.55.113.1.150500.6.53.1 |
kernel-docsSUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOS From an advisory covering 258 CVEs |
before 5.14.21-150500.55.113.1 | 5.14.21-150500.55.113.1 |
kernel-obs-buildSUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOS From an advisory covering 258 CVEs |
before 5.14.21-150500.55.113.1 | 5.14.21-150500.55.113.1 |
kernel-sourceSUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOS From an advisory covering 258 CVEs |
before 5.14.21-150500.55.113.1 | 5.14.21-150500.55.113.1 |
kernel-symsSUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOS From an advisory covering 258 CVEs |
before 5.14.21-150500.55.113.1 | 5.14.21-150500.55.113.1 |
kernel-64kbSUSE:Linux Enterprise High Performance Computing 15 SP5-LTSS From an advisory covering 258 CVEs |
before 5.14.21-150500.55.113.1 | 5.14.21-150500.55.113.1 |
kernel-defaultSUSE:Linux Enterprise High Performance Computing 15 SP5-LTSS From an advisory covering 258 CVEs |
before 5.14.21-150500.55.113.1 | 5.14.21-150500.55.113.1 |
kernel-default-baseSUSE:Linux Enterprise High Performance Computing 15 SP5-LTSS From an advisory covering 258 CVEs |
before 5.14.21-150500.55.113.1.150500.6.53.1 | 5.14.21-150500.55.113.1.150500.6.53.1 |
kernel-docsSUSE:Linux Enterprise High Performance Computing 15 SP5-LTSS From an advisory covering 258 CVEs |
before 5.14.21-150500.55.113.1 | 5.14.21-150500.55.113.1 |
kernel-obs-buildSUSE:Linux Enterprise High Performance Computing 15 SP5-LTSS From an advisory covering 258 CVEs |
before 5.14.21-150500.55.113.1 | 5.14.21-150500.55.113.1 |
kernel-sourceSUSE:Linux Enterprise High Performance Computing 15 SP5-LTSS From an advisory covering 258 CVEs |
before 5.14.21-150500.55.113.1 | 5.14.21-150500.55.113.1 |
kernel-symsSUSE:Linux Enterprise High Performance Computing 15 SP5-LTSS From an advisory covering 258 CVEs |
before 5.14.21-150500.55.113.1 | 5.14.21-150500.55.113.1 |
kernel-64kbSUSE:Linux Enterprise Server 15 SP5-LTSS From an advisory covering 258 CVEs |
before 5.14.21-150500.55.113.1 | 5.14.21-150500.55.113.1 |
kernel-defaultSUSE:Linux Enterprise Server 15 SP5-LTSS From an advisory covering 258 CVEs |
before 5.14.21-150500.55.113.1 | 5.14.21-150500.55.113.1 |
kernel-default-baseSUSE:Linux Enterprise Server 15 SP5-LTSS From an advisory covering 258 CVEs |
before 5.14.21-150500.55.113.1.150500.6.53.1 | 5.14.21-150500.55.113.1.150500.6.53.1 |
kernel-docsSUSE:Linux Enterprise Server 15 SP5-LTSS From an advisory covering 258 CVEs |
before 5.14.21-150500.55.113.1 | 5.14.21-150500.55.113.1 |
kernel-obs-buildSUSE:Linux Enterprise Server 15 SP5-LTSS From an advisory covering 258 CVEs |
before 5.14.21-150500.55.113.1 | 5.14.21-150500.55.113.1 |
kernel-sourceSUSE:Linux Enterprise Server 15 SP5-LTSS From an advisory covering 258 CVEs |
before 5.14.21-150500.55.113.1 | 5.14.21-150500.55.113.1 |
kernel-symsSUSE:Linux Enterprise Server 15 SP5-LTSS From an advisory covering 258 CVEs |
before 5.14.21-150500.55.113.1 | 5.14.21-150500.55.113.1 |
kernel-zfcpdumpSUSE:Linux Enterprise Server 15 SP5-LTSS From an advisory covering 258 CVEs |
before 5.14.21-150500.55.113.1 | 5.14.21-150500.55.113.1 |
kernel-defaultSUSE:Linux Enterprise Server for SAP Applications 15 SP5 From an advisory covering 258 CVEs |
before 5.14.21-150500.55.113.1 | 5.14.21-150500.55.113.1 |
kernel-default-baseSUSE:Linux Enterprise Server for SAP Applications 15 SP5 From an advisory covering 258 CVEs |
before 5.14.21-150500.55.113.1.150500.6.53.1 | 5.14.21-150500.55.113.1.150500.6.53.1 |
kernel-docsSUSE:Linux Enterprise Server for SAP Applications 15 SP5 From an advisory covering 258 CVEs |
before 5.14.21-150500.55.113.1 | 5.14.21-150500.55.113.1 |
kernel-obs-buildSUSE:Linux Enterprise Server for SAP Applications 15 SP5 From an advisory covering 258 CVEs |
before 5.14.21-150500.55.113.1 | 5.14.21-150500.55.113.1 |
kernel-sourceSUSE:Linux Enterprise Server for SAP Applications 15 SP5 From an advisory covering 258 CVEs |
before 5.14.21-150500.55.113.1 | 5.14.21-150500.55.113.1 |
kernel-symsSUSE:Linux Enterprise Server for SAP Applications 15 SP5 From an advisory covering 258 CVEs |
before 5.14.21-150500.55.113.1 | 5.14.21-150500.55.113.1 |
kernel-rtSUSE:Linux Enterprise Micro 5.5 From an advisory covering 260 CVEs |
before 5.14.21-150500.13.100.2 | 5.14.21-150500.13.100.2 |
kernel-source-rtSUSE:Linux Enterprise Micro 5.5 From an advisory covering 260 CVEs |
before 5.14.21-150500.13.100.1 | 5.14.21-150500.13.100.1 |
kernel-rtSUSE:Linux Enterprise Micro 5.3 From an advisory covering 221 CVEs |
before 5.14.21-150400.15.124.1 | 5.14.21-150400.15.124.1 |
kernel-source-rtSUSE:Linux Enterprise Micro 5.3 From an advisory covering 221 CVEs |
before 5.14.21-150400.15.124.1 | 5.14.21-150400.15.124.1 |
kernel-rtSUSE:Linux Enterprise Micro 5.4 From an advisory covering 221 CVEs |
before 5.14.21-150400.15.124.1 | 5.14.21-150400.15.124.1 |
kernel-source-rtSUSE:Linux Enterprise Micro 5.4 From an advisory covering 221 CVEs |
before 5.14.21-150400.15.124.1 | 5.14.21-150400.15.124.1 |
kernel-defaultSUSE:Linux Enterprise Micro 5.3 From an advisory covering 221 CVEs |
before 5.14.21-150400.24.170.2 | 5.14.21-150400.24.170.2 |
kernel-default-baseSUSE:Linux Enterprise Micro 5.3 From an advisory covering 221 CVEs |
before 5.14.21-150400.24.170.2.150400.24.86.2 | 5.14.21-150400.24.170.2.150400.24.86.2 |
kernel-defaultSUSE:Linux Enterprise Micro 5.4 From an advisory covering 221 CVEs |
before 5.14.21-150400.24.170.2 | 5.14.21-150400.24.170.2 |
kernel-default-baseSUSE:Linux Enterprise Micro 5.4 From an advisory covering 221 CVEs |
before 5.14.21-150400.24.170.2.150400.24.86.2 | 5.14.21-150400.24.170.2.150400.24.86.2 |
kernel-defaultSUSE:Linux Enterprise High Availability Extension 15 SP4 From an advisory covering 221 CVEs |
before 5.14.21-150400.24.170.2 | 5.14.21-150400.24.170.2 |
kernel-64kbSUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS From an advisory covering 221 CVEs |
before 5.14.21-150400.24.170.2 | 5.14.21-150400.24.170.2 |
kernel-defaultSUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS From an advisory covering 221 CVEs |
before 5.14.21-150400.24.170.2 | 5.14.21-150400.24.170.2 |
kernel-default-baseSUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS From an advisory covering 221 CVEs |
before 5.14.21-150400.24.170.2.150400.24.86.2 | 5.14.21-150400.24.170.2.150400.24.86.2 |
kernel-docsSUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS From an advisory covering 221 CVEs |
before 5.14.21-150400.24.170.1 | 5.14.21-150400.24.170.1 |
kernel-obs-buildSUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS From an advisory covering 221 CVEs |
before 5.14.21-150400.24.170.2 | 5.14.21-150400.24.170.2 |
kernel-sourceSUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS From an advisory covering 221 CVEs |
before 5.14.21-150400.24.170.1 | 5.14.21-150400.24.170.1 |
kernel-symsSUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS From an advisory covering 221 CVEs |
before 5.14.21-150400.24.170.1 | 5.14.21-150400.24.170.1 |
kernel-64kbSUSE:Linux Enterprise High Performance Computing 15 SP4-LTSS From an advisory covering 221 CVEs |
before 5.14.21-150400.24.170.2 | 5.14.21-150400.24.170.2 |
kernel-defaultSUSE:Linux Enterprise High Performance Computing 15 SP4-LTSS From an advisory covering 221 CVEs |
before 5.14.21-150400.24.170.2 | 5.14.21-150400.24.170.2 |
kernel-default-baseSUSE:Linux Enterprise High Performance Computing 15 SP4-LTSS From an advisory covering 221 CVEs |
before 5.14.21-150400.24.170.2.150400.24.86.2 | 5.14.21-150400.24.170.2.150400.24.86.2 |
kernel-docsSUSE:Linux Enterprise High Performance Computing 15 SP4-LTSS From an advisory covering 221 CVEs |
before 5.14.21-150400.24.170.1 | 5.14.21-150400.24.170.1 |
kernel-obs-buildSUSE:Linux Enterprise High Performance Computing 15 SP4-LTSS From an advisory covering 221 CVEs |
before 5.14.21-150400.24.170.2 | 5.14.21-150400.24.170.2 |
kernel-sourceSUSE:Linux Enterprise High Performance Computing 15 SP4-LTSS From an advisory covering 221 CVEs |
before 5.14.21-150400.24.170.1 | 5.14.21-150400.24.170.1 |
kernel-symsSUSE:Linux Enterprise High Performance Computing 15 SP4-LTSS From an advisory covering 221 CVEs |
before 5.14.21-150400.24.170.1 | 5.14.21-150400.24.170.1 |
kernel-64kbSUSE:Linux Enterprise Server 15 SP4-LTSS From an advisory covering 221 CVEs |
before 5.14.21-150400.24.170.2 | 5.14.21-150400.24.170.2 |
kernel-defaultSUSE:Linux Enterprise Server 15 SP4-LTSS From an advisory covering 221 CVEs |
before 5.14.21-150400.24.170.2 | 5.14.21-150400.24.170.2 |
kernel-default-baseSUSE:Linux Enterprise Server 15 SP4-LTSS From an advisory covering 221 CVEs |
before 5.14.21-150400.24.170.2.150400.24.86.2 | 5.14.21-150400.24.170.2.150400.24.86.2 |
kernel-docsSUSE:Linux Enterprise Server 15 SP4-LTSS From an advisory covering 221 CVEs |
before 5.14.21-150400.24.170.1 | 5.14.21-150400.24.170.1 |
kernel-obs-buildSUSE:Linux Enterprise Server 15 SP4-LTSS From an advisory covering 221 CVEs |
before 5.14.21-150400.24.170.2 | 5.14.21-150400.24.170.2 |
kernel-sourceSUSE:Linux Enterprise Server 15 SP4-LTSS From an advisory covering 221 CVEs |
before 5.14.21-150400.24.170.1 | 5.14.21-150400.24.170.1 |
kernel-symsSUSE:Linux Enterprise Server 15 SP4-LTSS From an advisory covering 221 CVEs |
before 5.14.21-150400.24.170.1 | 5.14.21-150400.24.170.1 |
kernel-zfcpdumpSUSE:Linux Enterprise Server 15 SP4-LTSS From an advisory covering 221 CVEs |
before 5.14.21-150400.24.170.2 | 5.14.21-150400.24.170.2 |
kernel-defaultSUSE:Linux Enterprise Server for SAP Applications 15 SP4 From an advisory covering 221 CVEs |
before 5.14.21-150400.24.170.2 | 5.14.21-150400.24.170.2 |
kernel-default-baseSUSE:Linux Enterprise Server for SAP Applications 15 SP4 From an advisory covering 221 CVEs |
before 5.14.21-150400.24.170.2.150400.24.86.2 | 5.14.21-150400.24.170.2.150400.24.86.2 |
kernel-docsSUSE:Linux Enterprise Server for SAP Applications 15 SP4 From an advisory covering 221 CVEs |
before 5.14.21-150400.24.170.1 | 5.14.21-150400.24.170.1 |
kernel-obs-buildSUSE:Linux Enterprise Server for SAP Applications 15 SP4 From an advisory covering 221 CVEs |
before 5.14.21-150400.24.170.2 | 5.14.21-150400.24.170.2 |
kernel-sourceSUSE:Linux Enterprise Server for SAP Applications 15 SP4 From an advisory covering 221 CVEs |
before 5.14.21-150400.24.170.1 | 5.14.21-150400.24.170.1 |
kernel-symsSUSE:Linux Enterprise Server for SAP Applications 15 SP4 From an advisory covering 221 CVEs |
before 5.14.21-150400.24.170.1 | 5.14.21-150400.24.170.1 |
kernel-defaultSUSE:Manager Proxy 4.3 From an advisory covering 221 CVEs |
before 5.14.21-150400.24.170.2 | 5.14.21-150400.24.170.2 |
kernel-default-baseSUSE:Manager Proxy 4.3 From an advisory covering 221 CVEs |
before 5.14.21-150400.24.170.2.150400.24.86.2 | 5.14.21-150400.24.170.2.150400.24.86.2 |
kernel-sourceSUSE:Manager Proxy 4.3 From an advisory covering 221 CVEs |
before 5.14.21-150400.24.170.1 | 5.14.21-150400.24.170.1 |
kernel-symsSUSE:Manager Proxy 4.3 From an advisory covering 221 CVEs |
before 5.14.21-150400.24.170.1 | 5.14.21-150400.24.170.1 |
kernel-defaultSUSE:Manager Server 4.3 From an advisory covering 221 CVEs |
before 5.14.21-150400.24.170.2 | 5.14.21-150400.24.170.2 |
kernel-default-baseSUSE:Manager Server 4.3 From an advisory covering 221 CVEs |
before 5.14.21-150400.24.170.2.150400.24.86.2 | 5.14.21-150400.24.170.2.150400.24.86.2 |
kernel-sourceSUSE:Manager Server 4.3 From an advisory covering 221 CVEs |
before 5.14.21-150400.24.170.1 | 5.14.21-150400.24.170.1 |
kernel-symsSUSE:Manager Server 4.3 From an advisory covering 221 CVEs |
before 5.14.21-150400.24.170.1 | 5.14.21-150400.24.170.1 |
kernel-zfcpdumpSUSE:Manager Server 4.3 From an advisory covering 221 CVEs |
before 5.14.21-150400.24.170.2 | 5.14.21-150400.24.170.2 |
linux-hwe-edgeUbuntu:16.04:LTS |
All versions, plus listed versions 4.8.0-28.30~16.04.14.8.0-30.32~16.04.14.8.0-32.34~16.04.14.8.0-34.36~16.04.14.10.0-14.16~16.04.1 Show 18 moreShow less4.10.0-19.21~16.04.14.10.0-20.22~16.04.14.10.0-21.23~16.04.14.10.0-22.24~16.04.14.10.0-24.28~16.04.14.10.0-26.30~16.04.14.11.0-13.19~16.04.14.11.0-14.20~16.04.14.13.0-16.19~16.04.34.13.0-17.20~16.04.14.13.0-19.22~16.04.14.13.0-21.24~16.04.14.13.0-25.29~16.04.24.15.0-13.14~16.04.14.15.0-15.16~16.04.14.15.0-20.21~16.04.14.15.0-22.24~16.04.14.15.0-23.25~16.04.1 |
None known |
linux-aws-5.0Ubuntu:18.04:LTS |
All versions, plus listed versions 5.0.0-1021.24~18.04.15.0.0-1022.25~18.04.15.0.0-1023.26~18.04.15.0.0-1024.27~18.04.15.0.0-1025.285.0.0-1027.30 |
None known |
linux-aws-5.3Ubuntu:18.04:LTS |
All versions, plus listed versions 5.3.0-1016.17~18.04.15.3.0-1017.18~18.04.15.3.0-1019.21~18.04.15.3.0-1023.25~18.04.15.3.0-1028.30~18.04.1 Show 5 moreShow less5.3.0-1030.32~18.04.15.3.0-1032.34~18.04.25.3.0-1033.355.3.0-1034.365.3.0-1035.37 |
None known |
linux-azureUbuntu:18.04:LTS |
All versions, plus listed versions 4.15.0-1002.24.15.0-1003.34.15.0-1004.44.15.0-1008.84.15.0-1009.9 Show 39 moreShow less4.15.0-1012.124.15.0-1013.134.15.0-1014.144.15.0-1018.184.15.0-1019.194.15.0-1021.214.15.0-1022.234.15.0-1023.244.15.0-1025.264.15.0-1028.294.15.0-1030.314.15.0-1031.324.15.0-1032.334.15.0-1035.364.15.0-1036.384.15.0-1037.394.18.0-1011.11~18.04.14.18.0-1013.13~18.04.14.18.0-1014.14~18.04.14.18.0-1018.18~18.04.14.18.0-1019.19~18.04.14.18.0-1020.20~18.04.14.18.0-1023.24~18.04.14.18.0-1024.25~18.04.14.18.0-1025.27~18.04.15.0.0-1014.14~18.04.15.0.0-1016.17~18.04.15.0.0-1018.19~18.04.15.0.0-1020.21~18.04.15.0.0-1022.23~18.04.15.0.0-1023.24~18.04.15.0.0-1025.27~18.04.15.0.0-1027.29~18.04.15.0.0-1028.30~18.04.15.0.0-1029.31~18.04.15.0.0-1031.335.0.0-1032.345.0.0-1035.375.0.0-1036.38 |
None known |
linux-azure-5.3Ubuntu:18.04:LTS |
All versions, plus listed versions 5.3.0-1007.8~18.04.15.3.0-1008.9~18.04.15.3.0-1009.10~18.04.15.3.0-1010.11~18.04.15.3.0-1012.13~18.04.1 Show 11 moreShow less5.3.0-1013.14~18.04.15.3.0-1016.17~18.04.15.3.0-1018.19~18.04.15.3.0-1019.20~18.04.15.3.0-1020.21~18.04.15.3.0-1022.23~18.04.15.3.0-1028.29~18.04.15.3.0-1031.32~18.04.15.3.0-1032.33~18.04.15.3.0-1034.35~18.04.15.3.0-1035.36 |
None known |
linux-azure-edgeUbuntu:18.04:LTS |
All versions, plus listed versions 4.18.0-1006.6~18.04.14.18.0-1007.7~18.04.14.18.0-1008.8~18.04.15.0.0-1012.12~18.04.2 |
None known |
linux-gcpUbuntu:18.04:LTS |
All versions, plus listed versions 4.15.0-1001.14.15.0-1003.34.15.0-1005.54.15.0-1006.64.15.0-1008.8 Show 33 moreShow less4.15.0-1009.94.15.0-1010.104.15.0-1014.144.15.0-1015.154.15.0-1017.184.15.0-1018.194.15.0-1019.204.15.0-1021.224.15.0-1023.244.15.0-1024.254.15.0-1025.264.15.0-1026.274.15.0-1027.284.15.0-1028.294.15.0-1029.314.15.0-1030.324.15.0-1032.344.15.0-1033.354.15.0-1034.364.15.0-1036.384.15.0-1037.394.15.0-1040.424.15.0-1042.454.15.0-1044.705.0.0-1020.20~18.04.15.0.0-1021.21~18.04.15.0.0-1025.26~18.04.15.0.0-1026.27~18.04.15.0.0-1028.29~18.04.15.0.0-1029.30~18.04.15.0.0-1031.325.0.0-1033.345.0.0-1034.35 |
None known |
linux-gcp-5.3Ubuntu:18.04:LTS |
All versions, plus listed versions 5.3.0-1008.9~18.04.15.3.0-1009.10~18.04.15.3.0-1010.11~18.04.15.3.0-1012.13~18.04.15.3.0-1014.15~18.04.1 Show 8 moreShow less5.3.0-1016.17~18.04.15.3.0-1017.18~18.04.15.3.0-1018.19~18.04.15.3.0-1020.22~18.04.15.3.0-1026.28~18.04.15.3.0-1029.31~18.04.15.3.0-1030.32~18.04.15.3.0-1032.34~18.04.1 |
None known |
linux-gke-4.15Ubuntu:18.04:LTS |
All versions, plus listed versions 4.15.0-1030.324.15.0-1032.344.15.0-1033.354.15.0-1034.364.15.0-1036.38 Show 28 moreShow less4.15.0-1037.394.15.0-1040.424.15.0-1041.434.15.0-1042.444.15.0-1044.464.15.0-1045.484.15.0-1046.494.15.0-1048.514.15.0-1049.524.15.0-1050.534.15.0-1052.554.15.0-1055.584.15.0-1057.604.15.0-1058.614.15.0-1059.624.15.0-1063.664.15.0-1064.674.15.0-1066.694.15.0-1067.704.15.0-1069.724.15.0-1070.734.15.0-1072.764.15.0-1073.784.15.0-1074.794.15.0-1076.814.15.0-1077.824.15.0-1078.834.15.0-1079.84 |
None known |
linux-gke-5.4Ubuntu:18.04:LTS |
All versions, plus listed versions 5.4.0-1025.25~18.04.15.4.0-1027.28~18.04.15.4.0-1029.31~18.04.15.4.0-1030.32~18.04.15.4.0-1032.34~18.04.1 Show 32 moreShow less5.4.0-1033.35~18.04.15.4.0-1035.37~18.04.15.4.0-1036.38~18.04.15.4.0-1037.39~18.04.15.4.0-1039.41~18.04.15.4.0-1040.42~18.04.15.4.0-1042.44~18.04.15.4.0-1043.45~18.04.15.4.0-1044.46~18.04.15.4.0-1046.48~18.04.15.4.0-1049.52~18.04.15.4.0-1051.54~18.04.15.4.0-1052.55~18.04.15.4.0-1053.56~18.04.15.4.0-1054.57~18.04.15.4.0-1055.58~18.04.15.4.0-1056.59~18.04.15.4.0-1057.60~18.04.15.4.0-1059.62~18.04.15.4.0-1061.64~18.04.15.4.0-1062.65~18.04.15.4.0-1063.66~18.04.15.4.0-1065.68~18.04.15.4.0-1066.69~18.04.15.4.0-1067.70~18.04.15.4.0-1068.71~18.04.15.4.0-1071.76~18.04.35.4.0-1072.77~18.04.15.4.0-1074.79~18.04.15.4.0-1076.82~18.04.15.4.0-1078.84~18.04.15.4.0-1080.86~18.04.1 |
None known |
linux-gkeop-5.4Ubuntu:18.04:LTS |
All versions, plus listed versions 5.4.0-1001.15.4.0-1003.35.4.0-1004.55.4.0-1005.65.4.0-1007.8~18.04.1 Show 32 moreShow less5.4.0-1008.9~18.04.15.4.0-1009.10~18.04.15.4.0-1010.11~18.04.15.4.0-1011.12~18.04.25.4.0-1012.13~18.04.15.4.0-1013.14~18.04.15.4.0-1014.15~18.04.15.4.0-1015.16~18.04.15.4.0-1016.17~18.04.15.4.0-1018.19~18.04.15.4.0-1021.22~18.04.15.4.0-1022.23~18.04.15.4.0-1023.24~18.04.15.4.0-1024.25~18.04.15.4.0-1025.26~18.04.15.4.0-1026.27~18.04.15.4.0-1027.28~18.04.15.4.0-1029.30~18.04.25.4.0-1031.32~18.04.15.4.0-1032.33~18.04.15.4.0-1033.34~18.04.15.4.0-1034.35~18.04.15.4.0-1036.37~18.04.15.4.0-1037.38~18.04.15.4.0-1038.39~18.04.15.4.0-1039.40~18.04.15.4.0-1040.41~18.04.15.4.0-1043.44~18.04.15.4.0-1046.48~18.04.15.4.0-1048.51~18.04.15.4.0-1049.52~18.04.15.4.0-1051.54~18.04.1 |
None known |
linux-hweUbuntu:18.04:LTS |
All versions, plus listed versions 4.18.0-13.14~18.04.14.18.0-14.15~18.04.14.18.0-15.16~18.04.14.18.0-16.17~18.04.14.18.0-17.18~18.04.1 Show 38 moreShow less4.18.0-18.19~18.04.14.18.0-20.21~18.04.14.18.0-21.22~18.04.14.18.0-22.23~18.04.14.18.0-24.25~18.04.14.18.0-25.26~18.04.15.0.0-23.24~18.04.15.0.0-25.26~18.04.15.0.0-27.28~18.04.15.0.0-29.31~18.04.15.0.0-31.33~18.04.15.0.0-32.34~18.04.25.0.0-35.38~18.04.15.0.0-36.39~18.04.15.0.0-37.40~18.04.15.3.0-26.28~18.04.15.3.0-28.30~18.04.15.3.0-40.32~18.04.15.3.0-42.34~18.04.15.3.0-45.37~18.04.15.3.0-46.38~18.04.15.3.0-51.44~18.04.25.3.0-53.47~18.04.15.3.0-59.53~18.04.15.3.0-61.55~18.04.15.3.0-62.56~18.04.15.3.0-64.58~18.04.15.3.0-65.595.3.0-66.605.3.0-67.615.3.0-68.635.3.0-69.655.3.0-70.665.3.0-72.685.3.0-73.695.3.0-74.705.3.0-75.715.3.0-76.72 |
None known |
linux-hwe-edgeUbuntu:18.04:LTS |
All versions, plus listed versions 5.0.0-15.16~18.04.15.0.0-16.17~18.04.15.0.0-17.18~18.04.15.0.0-19.20~18.04.15.0.0-20.21~18.04.1 Show 5 moreShow less5.3.0-19.20~18.04.25.3.0-22.24~18.04.15.3.0-23.25~18.04.15.3.0-23.25~18.04.25.3.0-24.26~18.04.2 |
None known |
linux-oemUbuntu:18.04:LTS |
All versions, plus listed versions 4.15.0-1002.34.15.0-1004.54.15.0-1006.94.15.0-1008.114.15.0-1009.12 Show 45 moreShow less4.15.0-1012.154.15.0-1013.164.15.0-1015.184.15.0-1017.204.15.0-1018.214.15.0-1021.244.15.0-1024.294.15.0-1026.314.15.0-1028.334.15.0-1030.354.15.0-1033.384.15.0-1034.394.15.0-1035.404.15.0-1036.414.15.0-1038.434.15.0-1039.444.15.0-1043.484.15.0-1045.504.15.0-1050.574.15.0-1056.654.15.0-1057.664.15.0-1059.684.15.0-1063.724.15.0-1064.734.15.0-1065.754.15.0-1066.764.15.0-1067.774.15.0-1069.794.15.0-1073.834.15.0-1076.864.15.0-1079.894.15.0-1080.904.15.0-1081.914.15.0-1087.974.15.0-1090.1004.15.0-1091.1014.15.0-1093.1034.15.0-1094.1044.15.0-1096.1064.15.0-1097.1074.15.0-1099.1094.15.0-1100.1104.15.0-1101.1124.15.0-1102.1134.15.0-1103.114 |
None known |
linux-oracle-5.0Ubuntu:18.04:LTS |
All versions, plus listed versions 5.0.0-1007.12~18.04.15.0.0-1008.13~18.04.15.0.0-1009.14~18.04.15.0.0-1010.15~18.04.15.0.0-1011.165.0.0-1013.185.0.0-1014.19 |
None known |
linux-oracle-5.3Ubuntu:18.04:LTS |
All versions, plus listed versions 5.3.0-1011.12~18.04.15.3.0-1013.14~18.04.15.3.0-1014.15~18.04.15.3.0-1016.18~18.04.15.3.0-1018.20~18.04.1 Show 4 moreShow less5.3.0-1024.26~18.04.15.3.0-1027.29~18.04.15.3.0-1028.30~18.04.15.3.0-1030.32~18.04.1 |
None known |
linux-aws-5.15Ubuntu:20.04:LTS |
before 5.15.0-1027.31~20.04.1, plus listed versions 5.15.0-1014.18~20.04.15.15.0-1015.19~20.04.15.15.0-1017.21~20.04.15.15.0-1019.23~20.04.15.15.0-1020.24~20.04.1 Show 4 moreShow less5.15.0-1021.25~20.04.15.15.0-1022.26~20.04.15.15.0-1023.27~20.04.15.15.0-1026.30~20.04.2 |
5.15.0-1027.31~20.04.1 |
linux-azure-5.15Ubuntu:20.04:LTS |
before 5.15.0-1030.37~20.04.1, plus listed versions 5.15.0-1007.8~20.04.15.15.0-1008.9~20.04.15.15.0-1013.16~20.04.15.15.0-1014.17~20.04.15.15.0-1017.20~20.04.1 Show 6 moreShow less5.15.0-1019.24~20.04.15.15.0-1020.25~20.04.15.15.0-1021.26~20.04.15.15.0-1022.27~20.04.15.15.0-1023.29~20.04.15.15.0-1029.36~20.04.1 |
5.15.0-1030.37~20.04.1 |
linux-gcp-5.15Ubuntu:20.04:LTS |
before 5.15.0-1027.34~20.04.1, plus listed versions 5.15.0-1006.9~20.04.15.15.0-1012.17~20.04.15.15.0-1013.18~20.04.15.15.0-1016.21~20.04.15.15.0-1017.23~20.04.2 Show 5 moreShow less5.15.0-1018.24~20.04.15.15.0-1021.28~20.04.15.15.0-1022.29~20.04.15.15.0-1025.32~20.04.25.15.0-1026.33~20.04.1 |
5.15.0-1027.34~20.04.1 |
linux-hwe-5.15Ubuntu:20.04:LTS |
before 5.15.0-57.63~20.04.1, plus listed versions 5.15.0-33.34~20.04.15.15.0-41.44~20.04.15.15.0-43.46~20.04.15.15.0-46.49~20.04.15.15.0-48.54~20.04.1 Show 4 moreShow less5.15.0-50.56~20.04.15.15.0-52.58~20.04.15.15.0-53.59~20.04.15.15.0-56.62~20.04.1 |
5.15.0-57.63~20.04.1 |
linux-intel-iotg-5.15Ubuntu:20.04:LTS |
before 5.15.0-1023.28~20.04.1, plus listed versions 5.15.0-1003.5~20.04.15.15.0-1008.11~20.04.15.15.0-1010.14~20.04.15.15.0-1015.20~20.04.25.15.0-1016.21~20.04.15.15.0-1017.22~20.04.15.15.0-1018.23~20.04.15.15.0-1021.26~20.04.1 |
5.15.0-1023.28~20.04.1 |
linux-lowlatency-hwe-5.15Ubuntu:20.04:LTS |
before 5.15.0-58.64~20.04.1, plus listed versions 5.15.0-33.34~20.04.15.15.0-42.45~20.04.15.15.0-43.46~20.04.15.15.0-46.49~20.04.15.15.0-48.54~20.04.1 Show 4 moreShow less5.15.0-50.56~20.04.15.15.0-52.58~20.04.15.15.0-53.59~20.04.15.15.0-56.62~20.04.1 |
5.15.0-58.64~20.04.1 |
linux-oracle-5.15Ubuntu:20.04:LTS |
before 5.15.0-1027.33~20.04.1, plus listed versions 5.15.0-1007.9~20.04.15.15.0-1013.17~20.04.15.15.0-1016.20~20.04.15.15.0-1017.22~20.04.15.15.0-1018.23~20.04.1 Show 4 moreShow less5.15.0-1019.24~20.04.15.15.0-1021.27~20.04.15.15.0-1022.28~20.04.15.15.0-1025.31~20.04.2 |
5.15.0-1027.33~20.04.1 |
linux-riscv-5.15Ubuntu:20.04:LTS |
before 5.15.0-1027.31~20.04.1, plus listed versions 5.15.0-1015.17~20.04.15.15.0-1017.19~20.04.15.15.0-1018.21~20.04.15.15.0-1019.22~20.04.15.15.0-1022.26~20.04.15.15.0-1023.27~20.04.15.15.0-1026.30~20.04.2 |
5.15.0-1027.31~20.04.1 |
linux-aws-5.11Ubuntu:20.04:LTS |
All versions, plus listed versions 5.11.0-1009.9~20.04.25.11.0-1014.15~20.04.15.11.0-1016.17~20.04.15.11.0-1017.18~20.04.15.11.0-1019.20~20.04.1 Show 7 moreShow less5.11.0-1020.21~20.04.25.11.0-1021.22~20.04.25.11.0-1022.23~20.04.15.11.0-1023.24~20.04.15.11.0-1025.27~20.04.15.11.0-1027.30~20.04.15.11.0-1028.31~20.04.1 |
None known |
linux-aws-5.13Ubuntu:20.04:LTS |
All versions, plus listed versions 5.13.0-1008.9~20.04.25.13.0-1011.12~20.04.15.13.0-1012.13~20.04.15.13.0-1014.15~20.04.15.13.0-1017.19~20.04.1 Show 8 moreShow less5.13.0-1019.21~20.04.15.13.0-1021.23~20.04.25.13.0-1022.24~20.04.15.13.0-1023.25~20.04.15.13.0-1025.27~20.04.15.13.0-1028.31~20.04.15.13.0-1029.32~20.04.15.13.0-1031.35~20.04.1 |
None known |
linux-aws-5.8Ubuntu:20.04:LTS |
All versions, plus listed versions 5.8.0-1035.37~20.04.15.8.0-1038.40~20.04.15.8.0-1041.43~20.04.15.8.0-1042.44~20.04.1 |
None known |
linux-azure-5.11Ubuntu:20.04:LTS |
All versions, plus listed versions 5.11.0-1007.7~20.04.25.11.0-1012.13~20.04.15.11.0-1013.14~20.04.15.11.0-1015.16~20.04.15.11.0-1017.18~20.04.1 Show 8 moreShow less5.11.0-1019.20~20.04.15.11.0-1020.21~20.04.15.11.0-1021.22~20.04.15.11.0-1022.23~20.04.15.11.0-1023.24~20.04.15.11.0-1025.27~20.04.15.11.0-1027.30~20.04.15.11.0-1028.31~20.04.2 |
None known |
linux-azure-5.13Ubuntu:20.04:LTS |
All versions, plus listed versions 5.13.0-1009.10~20.04.25.13.0-1012.14~20.04.15.13.0-1013.15~20.04.15.13.0-1014.16~20.04.15.13.0-1017.19~20.04.1 Show 7 moreShow less5.13.0-1021.24~20.04.15.13.0-1022.26~20.04.15.13.0-1023.27~20.04.15.13.0-1025.29~20.04.15.13.0-1028.33~20.04.15.13.0-1029.34~20.04.15.13.0-1031.37~20.04.1 |
None known |
linux-azure-5.8Ubuntu:20.04:LTS |
All versions, plus listed versions 5.8.0-1033.35~20.04.15.8.0-1036.38~20.04.15.8.0-1039.42~20.04.15.8.0-1040.43~20.04.15.8.0-1041.44~20.04.15.8.0-1042.45~20.04.15.8.0-1043.46~20.04.1 |
None known |
linux-azure-fdeUbuntu:20.04:LTS |
All versions, plus listed versions 5.4.0-1063.66+cvm2.25.4.0-1063.66+cvm3.25.4.0-1064.67+cvm1.15.4.0-1065.68+cvm2.15.4.0-1067.70+cvm1.1 Show 21 moreShow less5.4.0-1068.71+cvm1.15.4.0-1069.72+cvm1.15.4.0-1070.73+cvm1.15.4.0-1072.75+cvm1.15.4.0-1073.76+cvm1.15.4.0-1074.77+cvm1.15.4.0-1076.79+cvm1.15.4.0-1078.81+cvm1.15.4.0-1080.83+cvm1.15.4.0-1083.87+cvm1.15.4.0-1085.90+cvm1.15.4.0-1085.90+cvm2.15.4.0-1086.91+cvm1.15.4.0-1089.94+cvm1.25.4.0-1090.95+cvm1.15.4.0-1091.96+cvm1.15.4.0-1092.97+cvm1.15.4.0-1095.101+cvm1.15.4.0-1098.104+cvm1.15.4.0-1100.106+cvm1.15.4.0-1103.109+cvm1.1 |
None known |
linux-gcp-5.11Ubuntu:20.04:LTS |
All versions, plus listed versions 5.11.0-1009.10~20.04.15.11.0-1014.16~20.04.15.11.0-1017.19~20.04.15.11.0-1018.20~20.04.25.11.0-1020.22~20.04.1 Show 7 moreShow less5.11.0-1021.23~20.04.15.11.0-1022.24~20.04.15.11.0-1023.25~20.04.15.11.0-1024.26~20.04.15.11.0-1026.29~20.04.15.11.0-1028.32~20.04.15.11.0-1029.33~20.04.3 |
None known |
linux-gcp-5.13Ubuntu:20.04:LTS |
All versions, plus listed versions 5.13.0-1008.9~20.04.35.13.0-1012.15~20.04.15.13.0-1013.16~20.04.15.13.0-1015.18~20.04.15.13.0-1019.23~20.04.1 Show 8 moreShow less5.13.0-1021.25~20.04.15.13.0-1023.28~20.04.15.13.0-1024.29~20.04.15.13.0-1025.30~20.04.15.13.0-1027.32~20.04.15.13.0-1030.36~20.04.15.13.0-1031.37~20.04.15.13.0-1033.40~20.04.1 |
None known |
linux-gcp-5.8Ubuntu:20.04:LTS |
All versions, plus listed versions 5.8.0-1032.34~20.04.15.8.0-1035.37~20.04.15.8.0-1038.40~20.04.15.8.0-1039.41 |
None known |
linux-gkeUbuntu:20.04:LTS |
All versions, plus listed versions 5.4.0-1033.355.4.0-1035.375.4.0-1036.385.4.0-1037.395.4.0-1039.41 Show 45 moreShow less5.4.0-1041.435.4.0-1042.445.4.0-1043.455.4.0-1044.465.4.0-1046.485.4.0-1049.525.4.0-1051.545.4.0-1052.555.4.0-1053.565.4.0-1054.575.4.0-1055.585.4.0-1056.595.4.0-1057.605.4.0-1059.625.4.0-1061.645.4.0-1062.655.4.0-1063.665.4.0-1065.685.4.0-1066.695.4.0-1067.705.4.0-1068.715.4.0-1071.765.4.0-1072.775.4.0-1074.795.4.0-1076.825.4.0-1078.845.4.0-1080.865.4.0-1081.875.4.0-1083.895.4.0-1084.905.4.0-1086.935.4.0-1087.945.4.0-1090.975.4.0-1091.985.4.0-1094.1015.4.0-1095.1025.4.0-1096.1035.4.0-1097.1045.4.0-1098.1055.4.0-1099.1065.4.0-1100.1075.4.0-1101.1085.4.0-1102.1095.4.0-1103.1105.4.0-1104.111 |
None known |
linux-gke-5.15Ubuntu:20.04:LTS |
All versions, plus listed versions 5.15.0-1011.14~20.04.15.15.0-1014.17~20.04.15.15.0-1015.18~20.04.15.15.0-1016.19~20.04.15.15.0-1019.23~20.04.1 Show 13 moreShow less5.15.0-1020.25~20.04.15.15.0-1023.28~20.04.25.15.0-1027.32~20.04.15.15.0-1028.33~20.04.15.15.0-1029.34~20.04.15.15.0-1031.36~20.04.15.15.0-1032.37~20.04.15.15.0-1033.38~20.04.15.15.0-1034.39~20.04.15.15.0-1036.41~20.04.15.15.0-1037.42~20.04.15.15.0-1038.43~20.04.15.15.0-1039.44~20.04.1 |
None known |
linux-gkeopUbuntu: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 less5.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.15Ubuntu:20.04:LTS |
All versions, plus listed versions 5.15.0-1003.5~20.04.25.15.0-1005.7~20.04.15.15.0-1007.10~20.04.15.15.0-1008.12~20.04.15.15.0-1011.15~20.04.2 Show 40 moreShow less5.15.0-1012.16~20.04.15.15.0-1013.17~20.04.15.15.0-1015.19~20.04.15.15.0-1016.21~20.04.15.15.0-1017.22~20.04.15.15.0-1018.23~20.04.15.15.0-1019.24~20.04.15.15.0-1020.25~20.04.15.15.0-1021.26~20.04.15.15.0-1022.27~20.04.15.15.0-1023.28~20.04.15.15.0-1024.29~20.04.15.15.0-1025.30~20.04.15.15.0-1026.31~20.04.15.15.0-1027.32~20.04.15.15.0-1028.33~20.04.15.15.0-1030.35~20.04.15.15.0-1031.37~20.04.15.15.0-1032.38~20.04.15.15.0-1033.39~20.04.15.15.0-1034.40~20.04.15.15.0-1035.41~20.04.15.15.0-1036.42~20.04.15.15.0-1037.43~20.04.15.15.0-1038.44~20.04.15.15.0-1039.45~20.04.15.15.0-1040.46~20.04.15.15.0-1043.50~20.04.15.15.0-1044.51~20.04.15.15.0-1045.52~20.04.15.15.0-1046.53~20.04.15.15.0-1047.54~20.04.15.15.0-1048.55~20.04.15.15.0-1049.56~20.04.15.15.0-1050.57~20.04.15.15.0-1051.58~20.04.15.15.0-1052.59~20.04.15.15.0-1053.60~20.04.15.15.0-1054.61~20.04.15.15.0-1055.62~20.04.1 |
None known |
linux-hwe-5.11Ubuntu:20.04:LTS |
All versions, plus listed versions 5.11.0-22.23~20.04.15.11.0-25.27~20.04.15.11.0-27.29~20.04.15.11.0-34.36~20.04.15.11.0-36.40~20.04.1 Show 7 moreShow less5.11.0-37.41~20.04.25.11.0-38.42~20.04.15.11.0-40.44~20.04.25.11.0-41.45~20.04.15.11.0-43.47~20.04.25.11.0-44.48~20.04.25.11.0-46.51~20.04.1 |
None known |
linux-hwe-5.13Ubuntu:20.04:LTS |
All versions, plus listed versions 5.13.0-21.21~20.04.15.13.0-22.22~20.04.15.13.0-23.23~20.04.25.13.0-25.26~20.04.15.13.0-27.29~20.04.1 Show 11 moreShow less5.13.0-28.31~20.04.15.13.0-30.33~20.04.15.13.0-35.40~20.04.15.13.0-37.42~20.04.15.13.0-39.44~20.04.15.13.0-40.45~20.04.15.13.0-41.46~20.04.15.13.0-44.49~20.04.15.13.0-48.54~20.04.15.13.0-51.58~20.04.15.13.0-52.59~20.04.1 |
None known |
linux-hwe-5.8Ubuntu:20.04:LTS |
All versions, plus listed versions 5.8.0-23.24~20.04.15.8.0-25.26~20.04.15.8.0-28.30~20.04.15.8.0-29.31~20.04.15.8.0-31.33~20.04.1 Show 16 moreShow less5.8.0-33.36~20.04.15.8.0-34.37~20.04.25.8.0-36.40~20.04.15.8.0-38.43~20.04.15.8.0-40.45~20.04.15.8.0-41.46~20.04.15.8.0-43.49~20.04.15.8.0-44.50~20.04.15.8.0-45.51~20.04.15.8.0-48.54~20.04.15.8.0-49.55~20.04.15.8.0-50.56~20.04.15.8.0-53.60~20.04.15.8.0-55.62~20.04.15.8.0-59.66~20.04.15.8.0-63.71~20.04.1 |
None known |
linux-intel-5.13Ubuntu:20.04:LTS |
All versions, plus listed versions 5.13.0-1007.75.13.0-1008.85.13.0-1009.95.13.0-1010.105.13.0-1011.115.13.0-1014.155.13.0-1017.19 |
None known |
linux-oem-5.10Ubuntu:20.04:LTS |
All versions, plus listed versions 5.10.0-1008.95.10.0-1011.125.10.0-1013.145.10.0-1014.155.10.0-1016.17 Show 21 moreShow less5.10.0-1017.185.10.0-1019.205.10.0-1021.225.10.0-1022.235.10.0-1023.245.10.0-1025.265.10.0-1026.275.10.0-1029.305.10.0-1032.335.10.0-1033.345.10.0-1034.355.10.0-1038.405.10.0-1044.465.10.0-1045.475.10.0-1049.515.10.0-1050.525.10.0-1051.535.10.0-1052.545.10.0-1053.555.10.0-1055.585.10.0-1057.61 |
None known |
linux-oem-5.13Ubuntu:20.04:LTS |
All versions, plus listed versions 5.13.0-1009.105.13.0-1010.115.13.0-1012.165.13.0-1014.185.13.0-1017.21 Show 7 moreShow less5.13.0-1019.235.13.0-1020.245.13.0-1021.255.13.0-1022.265.13.0-1026.325.13.0-1028.355.13.0-1029.36 |
None known |
linux-oem-5.14Ubuntu:20.04:LTS |
All versions, plus listed versions 5.14.0-1004.45.14.0-1005.55.14.0-1007.75.14.0-1008.85.14.0-1010.10 Show 30 moreShow less5.14.0-1011.115.14.0-1013.135.14.0-1018.195.14.0-1020.225.14.0-1022.245.14.0-1024.265.14.0-1027.305.14.0-1029.325.14.0-1031.345.14.0-1032.355.14.0-1033.365.14.0-1034.375.14.0-1036.405.14.0-1038.425.14.0-1042.475.14.0-1044.495.14.0-1045.515.14.0-1046.535.14.0-1047.545.14.0-1048.555.14.0-1049.565.14.0-1050.575.14.0-1051.585.14.0-1052.595.14.0-1054.615.14.0-1055.625.14.0-1056.635.14.0-1057.645.14.0-1058.665.14.0-1059.67 |
None known |
linux-oem-5.6Ubuntu:20.04:LTS |
All versions, plus listed versions 5.6.0-1007.75.6.0-1008.85.6.0-1010.105.6.0-1011.115.6.0-1013.13 Show 24 moreShow less5.6.0-1017.175.6.0-1018.185.6.0-1020.205.6.0-1021.215.6.0-1023.235.6.0-1026.265.6.0-1027.275.6.0-1028.285.6.0-1031.325.6.0-1032.335.6.0-1033.355.6.0-1034.365.6.0-1035.375.6.0-1036.395.6.0-1039.435.6.0-1042.465.6.0-1047.515.6.0-1048.525.6.0-1050.545.6.0-1052.565.6.0-1053.575.6.0-1054.585.6.0-1055.595.6.0-1056.60 |
None known |
linux-oracle-5.11Ubuntu:20.04:LTS |
All versions, plus listed versions 5.11.0-1008.8~20.04.15.11.0-1013.14~20.04.15.11.0-1016.17~20.04.15.11.0-1017.18~20.04.15.11.0-1019.20~20.04.1 Show 7 moreShow less5.11.0-1020.21~20.04.15.11.0-1021.22~20.04.15.11.0-1022.23~20.04.15.11.0-1023.24~20.04.15.11.0-1025.27~20.04.15.11.0-1027.30~20.04.15.11.0-1028.31~20.04.1 |
None known |
linux-oracle-5.13Ubuntu:20.04:LTS |
All versions, plus listed versions 5.13.0-1011.13~20.04.25.13.0-1015.19~20.04.15.13.0-1016.20~20.04.15.13.0-1018.22~20.04.15.13.0-1021.26~20.04.1 Show 7 moreShow less5.13.0-1025.30~20.04.15.13.0-1027.32~20.04.15.13.0-1028.33~20.04.15.13.0-1030.35~20.04.15.13.0-1033.39~20.04.15.13.0-1034.40~20.04.15.13.0-1036.43~20.04.1 |
None known |
linux-oracle-5.8Ubuntu:20.04:LTS |
All versions, plus listed versions 5.8.0-1031.32~20.04.25.8.0-1033.34~20.04.15.8.0-1034.35~20.04.25.8.0-1037.38~20.04.15.8.0-1038.39~20.04.1 |
None known |
linux-raspi2Ubuntu:20.04:LTS |
All versions, plus listed versions 5.3.0-1007.85.3.0-1014.165.3.0-1015.175.3.0-1017.195.4.0-1004.45.4.0-1006.6 |
None known |
linux-riscvUbuntu:20.04:LTS |
All versions, plus listed versions 5.4.0-24.285.4.0-26.305.4.0-27.315.4.0-28.325.4.0-30.34 Show 7 moreShow less5.4.0-31.355.4.0-33.375.4.0-34.385.4.0-36.415.4.0-37.425.4.0-39.445.4.0-40.45 |
None known |
linux-riscv-5.11Ubuntu:20.04:LTS |
All versions, plus listed versions 5.11.0-1015.16~20.04.15.11.0-1017.18~20.04.15.11.0-1018.19~20.04.25.11.0-1020.21~20.04.15.11.0-1021.22~20.04.1 Show 8 moreShow less5.11.0-1022.23~20.04.15.11.0-1023.24~20.04.15.11.0-1024.25~20.04.15.11.0-1026.28~20.04.15.11.0-1028.31~20.04.15.11.0-1029.32~20.04.15.11.0-1030.345.11.0-1031.35 |
None known |
linux-riscv-5.8Ubuntu:20.04:LTS |
All versions, plus listed versions 5.8.0-14.16~20.04.15.8.0-14.16~20.04.35.8.0-16.18~20.04.15.8.0-17.19~20.04.15.8.0-18.20~20.04.1 Show 5 moreShow less5.8.0-20.22~20.04.15.8.0-22.24~20.04.15.8.0-25.27~20.04.15.8.0-26.28~20.04.15.8.0-29.31~20.04.1 |
None known |
linuxUbuntu:22.04:LTS |
before 5.15.0-57.63, plus listed versions 5.13.0-19.195.15.0-17.175.15.0-18.185.15.0-22.225.15.0-23.23 Show 17 moreShow less5.15.0-25.255.15.0-27.285.15.0-30.315.15.0-33.345.15.0-35.365.15.0-37.395.15.0-39.425.15.0-40.435.15.0-41.445.15.0-43.465.15.0-46.495.15.0-47.515.15.0-48.545.15.0-50.565.15.0-52.585.15.0-53.595.15.0-56.62 |
5.15.0-57.63 |
linux-allwinner-5.19Ubuntu:22.04:LTS |
All versions, plus listed versions 5.19.0-1007.7~22.04.15.19.0-1009.9~22.04.15.19.0-1010.10~22.04.15.19.0-1011.11~22.04.15.19.0-1012.12~22.04.15.19.0-1013.13~22.04.15.19.0-1014.14~22.04.15.19.0-1015.15~22.04.1 |
None known |
linux-awsUbuntu:22.04:LTS |
before 5.15.0-1027.31, plus listed versions 5.13.0-1005.65.15.0-1002.45.15.0-1003.55.15.0-1004.65.15.0-1005.7 Show 13 moreShow less5.15.0-1008.105.15.0-1009.115.15.0-1011.145.15.0-1013.175.15.0-1014.185.15.0-1015.195.15.0-1017.215.15.0-1019.235.15.0-1020.245.15.0-1021.255.15.0-1022.265.15.0-1023.275.15.0-1026.30 |
5.15.0-1027.31 |
linux-aws-5.19Ubuntu: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 less5.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.2Ubuntu: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 less6.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.5Ubuntu: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 less6.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-azureUbuntu:22.04:LTS |
before 5.15.0-1030.37, plus listed versions 5.13.0-1006.75.15.0-1001.25.15.0-1002.35.15.0-1003.45.15.0-1005.6 Show 14 moreShow less5.15.0-1007.85.15.0-1008.95.15.0-1010.125.15.0-1012.155.15.0-1013.165.15.0-1014.175.15.0-1017.205.15.0-1019.245.15.0-1020.255.15.0-1021.265.15.0-1022.275.15.0-1023.295.15.0-1024.305.15.0-1029.36 |
5.15.0-1030.37 |
linux-azure-5.19Ubuntu: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.2Ubuntu: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 less6.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.5Ubuntu: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 less6.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-fdeUbuntu:22.04:LTS |
before 5.15.0-1030.37.1, plus listed versions 5.15.0-1019.24.15.15.0-1024.30.15.15.0-1029.36.1 |
5.15.0-1030.37.1 |
linux-azure-fde-5.19Ubuntu: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.2Ubuntu: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 less6.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-gcpUbuntu:22.04:LTS |
before 5.15.0-1026.33, plus listed versions 5.13.0-1005.65.15.0-1001.35.15.0-1002.55.15.0-1003.65.15.0-1004.7 Show 12 moreShow less5.15.0-1005.85.15.0-1006.95.15.0-1008.125.15.0-1010.155.15.0-1013.185.15.0-1016.215.15.0-1017.235.15.0-1018.245.15.0-1019.255.15.0-1021.285.15.0-1022.295.15.0-1025.32 |
5.15.0-1026.33 |
linux-gcp-5.19Ubuntu: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.2Ubuntu: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 less6.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.5Ubuntu: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 less6.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-gkeUbuntu:22.04:LTS |
before 5.15.0-1024.29, plus listed versions 5.15.0-1002.25.15.0-1003.35.15.0-1004.55.15.0-1005.65.15.0-1006.7 Show 10 moreShow less5.15.0-1008.105.15.0-1010.135.15.0-1011.145.15.0-1014.175.15.0-1015.185.15.0-1016.195.15.0-1017.205.15.0-1019.235.15.0-1020.255.15.0-1023.28 |
5.15.0-1024.29 |
linux-gkeopUbuntu:22.04:LTS |
before 5.15.0-1012.16, plus listed versions 5.15.0-1001.25.15.0-1002.45.15.0-1003.55.15.0-1004.65.15.0-1005.75.15.0-1007.105.15.0-1008.125.15.0-1011.15 |
5.15.0-1012.16 |
linux-hwe-5.19Ubuntu: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 less5.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.2Ubuntu: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 less6.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.5Ubuntu: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 less6.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-ibmUbuntu:22.04:LTS |
before 5.15.0-1022.25, plus listed versions 5.15.0-1002.25.15.0-1003.35.15.0-1004.45.15.0-1005.55.15.0-1007.8 Show 8 moreShow less5.15.0-1009.115.15.0-1010.125.15.0-1012.145.15.0-1013.155.15.0-1015.175.15.0-1017.205.15.0-1018.215.15.0-1021.24 |
5.15.0-1022.25 |
linux-intel-iot-realtimeUbuntu:22.04:LTS |
All versions, plus listed versions 5.15.0-1073.75 |
None known |
linux-intel-iotgUbuntu:22.04:LTS |
before 5.15.0-1023.28, plus listed versions 5.15.0-1004.65.15.0-1008.115.15.0-1010.145.15.0-1013.175.15.0-1015.20 Show 4 moreShow less5.15.0-1016.215.15.0-1017.225.15.0-1018.235.15.0-1021.26 |
5.15.0-1023.28 |
linux-kvmUbuntu:22.04:LTS |
before 5.15.0-1025.30, 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-1002.2 Show 14 moreShow less5.15.0-1004.45.15.0-1005.55.15.0-1007.75.15.0-1008.85.15.0-1010.115.15.0-1012.145.15.0-1013.165.15.0-1016.195.15.0-1017.215.15.0-1018.225.15.0-1019.235.15.0-1020.245.15.0-1021.265.15.0-1024.29 |
5.15.0-1025.30 |
linux-lowlatencyUbuntu:22.04:LTS |
before 5.15.0-57.63, plus listed versions 5.15.0-22.225.15.0-23.235.15.0-24.245.15.0-27.285.15.0-30.31 Show 14 moreShow less5.15.0-33.345.15.0-35.365.15.0-37.395.15.0-39.425.15.0-40.435.15.0-41.445.15.0-43.465.15.0-46.495.15.0-47.535.15.0-48.545.15.0-50.565.15.0-52.585.15.0-53.595.15.0-56.62 |
5.15.0-57.63 |
linux-lowlatency-hwe-5.19Ubuntu: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 less5.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.2Ubuntu: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 less6.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.5Ubuntu: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 less6.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-nvidiaUbuntu:22.04:LTS |
before 5.15.0-1015.15, plus listed versions 5.15.0-1005.55.15.0-1007.75.15.0-1010.10 |
5.15.0-1015.15 |
linux-nvidia-6.2Ubuntu: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.5Ubuntu: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 less6.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.17Ubuntu: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 less5.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.0Ubuntu: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 less6.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.1Ubuntu: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 less6.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.5Ubuntu: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 less6.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-oracleUbuntu:22.04:LTS |
before 5.15.0-1026.32, plus listed versions 5.13.0-1008.105.15.0-1001.35.15.0-1002.45.15.0-1003.55.15.0-1006.8 Show 11 moreShow less5.15.0-1007.95.15.0-1009.125.15.0-1011.155.15.0-1013.175.15.0-1016.205.15.0-1017.225.15.0-1018.235.15.0-1019.245.15.0-1021.275.15.0-1022.285.15.0-1025.31 |
5.15.0-1026.32 |
linux-oracle-6.5Ubuntu: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 less6.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-raspiUbuntu:22.04:LTS |
before 5.15.0-1022.24, plus listed versions 5.13.0-1008.95.15.0-1002.25.15.0-1003.35.15.0-1004.45.15.0-1005.5 Show 11 moreShow less5.15.0-1006.65.15.0-1008.85.15.0-1011.135.15.0-1012.145.15.0-1013.155.15.0-1014.165.15.0-1015.175.15.0-1016.185.15.0-1017.195.15.0-1018.205.15.0-1021.23 |
5.15.0-1022.24 |
linux-realtimeUbuntu:22.04:LTS |
All versions, plus listed versions 5.15.0-1032.35 |
None known |
linux-riscvUbuntu: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 less5.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.19Ubuntu: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.5Ubuntu: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 less6.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.19Ubuntu: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.2Ubuntu: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.5Ubuntu: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 less6.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-realtimeUbuntu:Pro:Realtime:22.04:LTS |
before 5.15.0-1029.32, plus listed versions 5.15.0-1006.65.15.0-1007.75.15.0-1009.95.15.0-1011.115.15.0-1014.14 Show 9 moreShow less5.15.0-1015.155.15.0-1016.165.15.0-1019.195.15.0-1020.205.15.0-1021.215.15.0-1022.225.15.0-1024.255.15.0-1025.285.15.0-1028.31 |
5.15.0-1029.32 |
linux-raspi-realtimeUbuntu:24.04:LTS |
All versions, plus listed versions 6.8.0-2019.20 |
None known |
linux-realtimeUbuntu:24.04:LTS |
All versions, plus listed versions 6.8.1-1015.16 |
None known |
linux-riscvUbuntu: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 less6.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 |
History
| Recorded | Changed | Sources |
|---|---|---|
| affected, facts | OSV | |
| first indexed | CVE List, EUVD, GitHub Advisories, NVD, OSV |
Dates are when Every CVE recorded each change. Upstream dates may differ.
In short
CVE-2022-49999 is a high vulnerability (CVSS 7.8) in Linux, published June 18, 2025. No source lists public exploit code. EPSS puts the chance of exploitation in the next 30 days at 0.26%, the 17th percentile. Fixed in Kernel 5.15.65.
References
git.kernel.org/stable/c/92dc4c1a8e58bcc7a183a4c86b055c24cc88d967
git.kernel.org/stable/c/a2e54eb64229f07f917b05d0c323604fda9b89f7
git.kernel.org/stable/c/ced8ecf026fd8084cf175530ff85c76d6085d715
nvd.nist.gov/vuln/detail/CVE-2022-49999
github.com/advisories/GHSA-j8xg-f23q-2vmv
github.com/CVEProject/cvelistV5/tree/main/cves/2022/49xxx/CVE-2022-49999.json
Show 194 moreShow less
git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
security-tracker.debian.org/tracker/CVE-2022-49999
suse.com/support/update/announcement/2025/suse-su-202502264-1
bugzilla.suse.com/1065729
bugzilla.suse.com/1156395
bugzilla.suse.com/1193629
bugzilla.suse.com/1194869
bugzilla.suse.com/1198410
bugzilla.suse.com/1199356
bugzilla.suse.com/1199487
bugzilla.suse.com/1201160
bugzilla.suse.com/1201956
bugzilla.suse.com/1202094
bugzilla.suse.com/1202095
bugzilla.suse.com/1202564
bugzilla.suse.com/1202716
bugzilla.suse.com/1202823
bugzilla.suse.com/1202860
bugzilla.suse.com/1203197
bugzilla.suse.com/1203361
bugzilla.suse.com/1205220
bugzilla.suse.com/1205514
bugzilla.suse.com/1205701
bugzilla.suse.com/1206451
bugzilla.suse.com/1206664
bugzilla.suse.com/1206878
bugzilla.suse.com/1206880
bugzilla.suse.com/1207361
bugzilla.suse.com/1207638
bugzilla.suse.com/1211226
bugzilla.suse.com/1212051
bugzilla.suse.com/1213090
bugzilla.suse.com/1218184
bugzilla.suse.com/1218234
bugzilla.suse.com/1218470
bugzilla.suse.com/1222634
bugzilla.suse.com/1223675
bugzilla.suse.com/1224095
bugzilla.suse.com/1224597
bugzilla.suse.com/1225468
bugzilla.suse.com/1225820
bugzilla.suse.com/1226514
bugzilla.suse.com/1226552
bugzilla.suse.com/1230827
bugzilla.suse.com/1232504
bugzilla.suse.com/1234156
bugzilla.suse.com/1234381
bugzilla.suse.com/1235464
bugzilla.suse.com/1235637
bugzilla.suse.com/1236821
bugzilla.suse.com/1236822
bugzilla.suse.com/1237159
bugzilla.suse.com/1237312
bugzilla.suse.com/1237313
bugzilla.suse.com/1238526
bugzilla.suse.com/1238876
bugzilla.suse.com/1241900
bugzilla.suse.com/1242221
bugzilla.suse.com/1242414
bugzilla.suse.com/1242504
bugzilla.suse.com/1242596
bugzilla.suse.com/1242778
bugzilla.suse.com/1242782
bugzilla.suse.com/1242924
bugzilla.suse.com/1243330
bugzilla.suse.com/1243543
bugzilla.suse.com/1243627
bugzilla.suse.com/1243649
bugzilla.suse.com/1243660
bugzilla.suse.com/1243832
bugzilla.suse.com/1244114
bugzilla.suse.com/1244179
bugzilla.suse.com/1244180
bugzilla.suse.com/1244234
bugzilla.suse.com/1244241
bugzilla.suse.com/1244277
bugzilla.suse.com/1244309
bugzilla.suse.com/1244337
bugzilla.suse.com/1244732
bugzilla.suse.com/1244764
bugzilla.suse.com/1244765
bugzilla.suse.com/1244767
bugzilla.suse.com/1244770
bugzilla.suse.com/1244771
bugzilla.suse.com/1244772
bugzilla.suse.com/1244773
bugzilla.suse.com/1244774
bugzilla.suse.com/1244776
bugzilla.suse.com/1244779
bugzilla.suse.com/1244780
bugzilla.suse.com/1244781
bugzilla.suse.com/1244782
bugzilla.suse.com/1244783
bugzilla.suse.com/1244784
bugzilla.suse.com/1244786
bugzilla.suse.com/1244787
bugzilla.suse.com/1244788
bugzilla.suse.com/1244790
suse.com/security/cve/CVE-2021-47557
suse.com/security/cve/CVE-2021-47595
suse.com/security/cve/CVE-2022-1679
suse.com/security/cve/CVE-2022-2585
suse.com/security/cve/CVE-2022-2586
suse.com/security/cve/CVE-2022-2905
suse.com/security/cve/CVE-2022-3903
suse.com/security/cve/CVE-2022-4095
suse.com/security/cve/CVE-2022-4662
suse.com/security/cve/CVE-2022-49934
suse.com/security/cve/CVE-2022-49935
suse.com/security/cve/CVE-2022-49936
suse.com/security/cve/CVE-2022-49937
suse.com/security/cve/CVE-2022-49938
suse.com/security/cve/CVE-2022-49940
suse.com/security/cve/CVE-2022-49942
suse.com/security/cve/CVE-2022-49943
suse.com/security/cve/CVE-2022-49944
suse.com/security/cve/CVE-2022-49945
suse.com/security/cve/CVE-2022-49946
suse.com/security/cve/CVE-2022-49948
suse.com/security/cve/CVE-2022-49949
suse.com/security/cve/CVE-2022-49950
suse.com/security/cve/CVE-2022-49951
suse.com/security/cve/CVE-2022-49952
suse.com/security/cve/CVE-2022-49954
suse.com/security/cve/CVE-2022-49956
suse.com/security/cve/CVE-2022-49957
suse.com/security/cve/CVE-2022-49958
suse.com/security/cve/CVE-2022-49960
suse.com/security/cve/CVE-2022-49962
suse.com/security/cve/CVE-2022-49963
suse.com/security/cve/CVE-2022-49964
suse.com/security/cve/CVE-2022-49965
suse.com/security/cve/CVE-2022-49966
suse.com/security/cve/CVE-2022-49968
suse.com/security/cve/CVE-2022-49969
suse.com/security/cve/CVE-2022-49971
suse.com/security/cve/CVE-2022-49972
suse.com/security/cve/CVE-2022-49977
suse.com/security/cve/CVE-2022-49978
suse.com/security/cve/CVE-2022-49980
suse.com/security/cve/CVE-2022-49981
suse.com/security/cve/CVE-2022-49982
suse.com/security/cve/CVE-2022-49983
suse.com/security/cve/CVE-2022-49984
suse.com/security/cve/CVE-2022-49985
suse.com/security/cve/CVE-2022-49986
suse.com/security/cve/CVE-2022-49987
suse.com/security/cve/CVE-2022-49989
suse.com/security/cve/CVE-2022-49990
suse.com/security/cve/CVE-2022-49993
suse.com/security/cve/CVE-2022-49995
suse.com/security/cve/CVE-2022-49999
suse.com/security/cve/CVE-2022-50002
suse.com/security/cve/CVE-2022-50003
suse.com/security/cve/CVE-2022-50005
suse.com/security/cve/CVE-2022-50006
suse.com/security/cve/CVE-2022-50008
suse.com/security/cve/CVE-2022-50010
suse.com/security/cve/CVE-2022-50011
suse.com/security/cve/CVE-2022-50012
suse.com/security/cve/CVE-2022-50015
suse.com/security/cve/CVE-2022-50016
suse.com/security/cve/CVE-2022-50019
suse.com/security/cve/CVE-2022-50020
suse.com/security/cve/CVE-2022-50021
suse.com/security/cve/CVE-2022-50022
suse.com/security/cve/CVE-2022-50023
suse.com/security/cve/CVE-2022-50024
suse.com/security/cve/CVE-2022-50026
suse.com/security/cve/CVE-2022-50027
suse.com/security/cve/CVE-2022-50028
suse.com/security/cve/CVE-2022-50029
suse.com/security/cve/CVE-2022-50030
suse.com/security/cve/CVE-2022-50031
suse.com/security/cve/CVE-2022-50032
suse.com/security/cve/CVE-2022-50033
suse.com/security/cve/CVE-2022-50034
suse.com/security/cve/CVE-2022-50035
suse.com/security/cve/CVE-2022-50036
suse.com/security/cve/CVE-2022-50037
suse.com/security/cve/CVE-2022-50038
suse.com/security/cve/CVE-2022-50039
suse.com/security/cve/CVE-2022-50040
suse.com/security/cve/CVE-2022-50041
suse.com/security/cve/CVE-2022-50044
suse.com/security/cve/CVE-2022-50045
suse.com/security/cve/CVE-2022-50046
suse.com/security/cve/CVE-2022-50047
suse.com/security/cve/CVE-2022-50049
suse.com/security/cve/CVE-2022-50050
suse.com/security/cve/CVE-2022-50051
suse.com/security/cve/CVE-2022-50052
ubuntu.com/security/CVE-2022-49999
cve.org/CVERecord?id=CVE-2022-49999
Left out here: 29 versions, 381 references and the rest of 5 source descriptions. The JSON record has them.