Every CVE Search/ Get API key

CVE-2024-26939

drm/i915/vma: Fix UAF on destroy against retire race

7.8 HighFix available

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

drm/i915/vma: Fix UAF on destroy against retire race

Object debugging tools were sporadically reporting illegal attempts to free a still active i915 VMA object when parking a GT believed to be idle.

[161.359441] ODEBUG: free active (active state 0) object: ffff88811643b958 object type: i915_active hint: __i915_vma_active+0x0/0x50 [i915] [161.360082] WARNING: CPU: 5 PID: 276 at lib/debugobjects.c:514 debug_print_object+0x80/0xb0 ... [161.360304] CPU: 5 PID: 276 Comm: kworker/5:2 Not tainted 6.5.0-rc1-CI_DRM_13375-g003f860e5577+ #1 [161.360314] Hardware name: Intel Corporation Rocket Lake Client Platform/RocketLake S UDIMM 6L RVP, BIOS RKLSFWI1.R00.3173.A03.2204210138 04/21/2022 [161.360322] Workqueue: i915-unordered __intel_wakeref_put_work [i915] [161.360592] RIP: 0010:debug_print_object+0x80/0xb0 ... [161.361347] debug_object_free+0xeb/0x110 [161.361362] i915_active_fini+0x14/0x130 [i915] [161.361866] release_references+0xfe/0x1f0 [i915] [161.362543] i915_vma_parked+0x1db/0x380 [i915] [161.363129] __gt_park+0x121/0x230 [i915] [161.363515] ____intel_wakeref_put_last+0x1f/0x70 [i915]

That has been tracked down to be happening when another thread is deactivating the VMA inside __active_retire() helper, after the VMA's active counter has been already decremented to 0, but before deactivation of the VMA's object is reported to the object debugging tool.

We could prevent from that race by serializing i915_active_fini() with __active_retire() via ref->tree_lock, but that wouldn't stop the VMA from being used, e.g. from __i915_vma_retire() called at the end of __active_retire(), after that VMA has been already freed by a concurrent i915_vma_destroy() on return from the i915_active_fini(). Then, we should rather fix the issue at the VMA level, not in i915_active.

Since __i915_vma_parked() is called from __gt_park() on last put of the GT's wakeref, the issue could be addressed by holding the GT wakeref long enough for __active_retire() to complete before that wakeref is released and the GT parked.

I believe the issue was introduced by commit d93939730347 ("drm/i915: Remove the vma refcount") which moved a call to i915_active_fini() from a dropped i915_vma_release(), called on last put of the removed VMA kref, to i915_vma_parked() processing path called on last put of a GT wakeref. However, its visibility to the object debugging tool was suppressed by a bug in i915_active that was fixed two weeks later with commit e92eb246feb9 ("drm/i915/active: Fix missing debug object activation").

A VMA associated with a request doesn't acquire a GT wakeref by itself. Instead, it depends on a wakeref held directly by the request's active intel_context for a GT associated with its VM, and indirectly on that intel_context's engine wakeref if the engine belongs to the same GT as the VMA's VM. Those wakerefs are released asynchronously to VMA deactivation.

Fix the issue by getting a wakeref for the VMA's GT when activating it, and putting that wakeref only after the VMA is deactivated. However, exclude global GTT from that processing path, otherwise the GPU never goes idle. Since __i915_vma_retire() may be called from atomic contexts, use async variant of wakeref put. Also, to avoid circular locking dependency, take care of acquiring the wakeref before VM mutex when both are needed.

v7: Add inline comments with justifications for: - using untracked variants of intel_gt_pm_get/put() (Nirmoy), - using async variant of _put(), - not getting the wakeref in case of a global GTT, - always getting the first wakeref outside vm->mutex. v6: Since __i915_vma_active/retire() callbacks are not serialized, storing a wakeref tracking handle inside struct i915_vma is not safe, and there is no other good place for that. Use untracked variants of intel_gt_pm_get/put_async(). v5: Replace "tile" with "GT" across commit description (Rodrigo),

---truncated---

Attack profile

How easy it is to exploit

Attack vector
Local
Complexity
Low
Privileges needed
Low
User interaction
None

What an attacker can affect

Confidentiality
High
Integrity
High
Availability
High

Exploit likelihood

0.25%Up 0.2 points since May 1, 2024
90%50%10%1%

What each source reports

CVE List Score used 7.8

drm/i915/vma: Fix UAF on destroy against retire race

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

drm/i915/vma: Fix UAF on destroy against retire race

Object debugging tools were sporadically reporting illegal attempts to free a still active i915 VMA object when parking a GT believed to be idle.

[161.359441] ODEBUG: free active (active state 0) object: ffff88811643b958 object type: i915_active hint: __i915_vma_active+0x0/0x50 [i915] [161.360082] WARNING: CPU: 5 PID: 276 at lib/debugobjects.c:514 debug_print_object+0x80/0xb0 ... [161.360304] CPU: 5 PID: 276 Comm: kworker/5:2 Not tainted 6.5.0-rc1-CI_DRM_13375-g003f860e5577+ #1 [161.360314] Hardware name: Intel Corporation Rocket Lake Client Platform/RocketLake S UDIMM 6L RVP, BIOS RKLSFWI1.R00.3173.A03.2204210138 04/21/2022 [161.360322] Workqueue: i915-unordered __intel_wakeref_put_work [i915] [161.360592] RIP: 0010:debug_print_object+0x80/0xb0 ... [161.361347] debug_object_free+0xeb/0x110 [161.361362] i915_active_fini+0x14/0x130 [i915] [161.361866] release_references+0xfe/0x1f0 [i915] [161.362543] i915_vma_parked+0x1db/0x380 [i915] [161.363129] __gt_park+0x121/0x230 [i915] [161.363515] ____intel_wakeref_put_last+0x1f/0x70 [i915]

That has been tracked down to be happening when another thread is deactivating the VMA inside __active_retire() helper, after the VMA's active counter has been already decremented to 0, but before deactivation of the VMA's object is reported to the object debugging tool.

We could prevent from that race by serializing i915_active_fini() with __active_retire() via ref->tree_lock, but that wouldn't stop the VMA from being used, e.g. from __i915_vma_retire() called at the end of __active_retire(), after that VMA has been already freed by a concurrent i915_vma_destroy() on return from the i915_active_fini(). Then, we should rather fix the issue at the VMA level, not in i915_active.

Since __i915_vma_parked() is called from __gt_park() on last put of the GT's wakeref, the issue could be addressed by holding the GT wakeref long enough for __active_retire() to complete before that wakeref is released and the GT parked.

I believe the issue was introduced by commit d93939730347 ("drm/i915: Remove the vma refcount") which moved a call to i915_active_fini() from a dropped i915_vma_release(), called on last put of the removed VMA kref, to i915_vma_parked() processing path called on last put of a GT wakeref. However, its visibility to the object debugging tool was suppressed by a bug in i915_active that was fixed two weeks later with commit e92eb246feb9 ("drm/i915/active: Fix missing debug object activation").

A VMA associated with a request doesn't acquire a GT wakeref by itself. Instead, it depends on a wakeref held directly by the request's active intel_context for a GT associated with its VM, and indirectly on that intel_context's engine wakeref if the engine belongs to the same GT as the VMA's VM. Those wakerefs are released asynchronously to VMA deactivation.

Fix the issue by getting a wakeref for the VMA's GT when activating it, and putting that wakeref only after the VMA is deactivated. However, exclude global GTT from that processing path, otherwise the GPU never goes idle. Since __i915_vma_retire() may be called from atomic contexts, use async variant of wakeref put. Also, to avoid circular locking dependency, take care of acquiring the wakeref before VM mutex when both are needed.

v7: Add inline comments with justifications for: - using untracked variants of intel_gt_pm_get/put() (Nirmoy), - using async variant of _put(), - not getting the wakeref in case of a global GTT, - always getting the first wakeref outside vm->mutex. v6: Since __i915_vma_active/retire() callbacks are not serialized, storing a wakeref tracking handle inside struct i915_vma is not safe, and there is no other good place for that. Use untracked variants of intel_gt_pm_get/put_async(). v5: Replace "tile" with "GT" across commit description (Rodrigo),

---truncated---

Record
CVE-2024-26939
CVSS 3.1
7.8 HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Weakness
CWE-416
Updated
2026-11-02
EUVDEUVD-2024-24201 7.8

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

drm/i915/vma: Fix UAF on destroy against retire race

Object debugging tools were sporadically reporting illegal attempts to free a still active i915 VMA object when parking a GT believed to be idle.

[161.359441] ODEBUG: free active (active state 0) object: ffff88811643b958 object type: i915_active hint: __i915_vma_active+0x0/0x50 [i915] [161.360082] WARNING: CPU: 5 PID: 276 at lib/debugobjects.c:514 debug_print_object+0x80/0xb0 ... [161.360304] CPU: 5 PID: 276 Comm: kworker/5:2 Not tainted 6.5.0-rc1-CI_DRM_13375-g003f860e5577+ #1 [161.360314] Hardware name: Intel Corporation Rocket Lake Client Platform/RocketLake S UDIMM 6L RVP, BIOS RKLSFWI1.R00.3173.A03.2204210138 04/21/2022 [161.360322] Workqueue: i915-unordered __intel_wakeref_put_work [i915] [161.360592] RIP: 0010:debug_print_object+0x80/0xb0 ... [161.361347] debug_object_free+0xeb/0x110 [161.361362] i915_active_fini+0x14/0x130 [i915] [161.361866] release_references+0xfe/0x1f0 [i915] [161.362543] i915_vma_parked+0x1db/0x380 [i915] [161.363129] __gt_park+0x121/0x230 [i915] [161.363515] ____intel_wakeref_put_last+0x1f/0x70 [i915]

That has been tracked down to be happening when another thread is deactivating the VMA inside __active_retire() helper, after the VMA's active counter has been already decremented to 0, but before deactivation of the VMA's object is reported to the object debugging tool.

We could prevent from that race by serializing i915_active_fini() with __active_retire() via ref->tree_lock, but that wouldn't stop the VMA from being used, e.g. from __i915_vma_retire() called at the end of __active_retire(), after that VMA has been already freed by a concurrent i915_vma_destroy() on return from the i915_active_fini(). Then, we should rather fix the issue at the VMA level, not in i915_active.

Since __i915_vma_parked() is called from __gt_park() on last put of the GT's wakeref, the issue could be addressed by holding the GT wakeref long enough for __active_retire() to complete before that wakeref is released and the GT parked.

I believe the issue was introduced by commit d93939730347 ("drm/i915: Remove the vma refcount") which moved a call to i915_active_fini() from a dropped i915_vma_release(), called on last put of the removed VMA kref, to i915_vma_parked() processing path called on last put of a GT wakeref. However, its visibility to the object debugging tool was suppressed by a bug in i915_active that was fixed two weeks later with commit e92eb246feb9 ("drm/i915/active: Fix missing debug object activation").

A VMA associated with a request doesn't acquire a GT wakeref by itself. Instead, it depends on a wakeref held directly by the request's active intel_context for a GT associated with its VM, and indirectly on that intel_context's engine wakeref if the engine belongs to the same GT as the VMA's VM. Those wakerefs are released asynchronously to VMA deactivation.

Fix the issue by getting a wakeref for the VMA's GT when activating it, and putting that wakeref only after the VMA is deactivated. However, exclude global GTT from that processing path, otherwise the GPU never goes idle. Since __i915_vma_retire() may be called from atomic contexts, use async variant of wakeref put. Also, to avoid circular locking dependency, take care of acquiring the wakeref before VM mutex when both are needed.

v7: Add inline comments with justifications for: - using untracked variants of intel_gt_pm_get/put() (Nirmoy), - using async variant of _put(), - not getting the wakeref in case of a global GTT, - always getting the first wakeref outside vm->mutex. v6: Since __i915_vma_active/retire() callbacks are not serialized, storing a wakeref tracking handle inside struct i915_vma is not safe, and there is no other good place for that. Use untracked variants of intel_gt_pm_get/put_async(). v5: Replace "tile" with "GT" across commit description (Rodrigo),

---truncated---

Record
EUVD-2024-24201
CVSS 3.1
7.8 HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Updated
2026-11-02
GitHub AdvisoriesGHSA-gghh-gpx3-pmx6 7.0

In the Linux kernel, the following vulnerability has been resolved: drm/i915/vma: Fix UAF on...

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

drm/i915/vma: Fix UAF on destroy against retire race

Object debugging tools were sporadically reporting illegal attempts to free a still active i915 VMA object when parking a GT believed to be idle.

[161.359441] ODEBUG: free active (active state 0) object: ffff88811643b958 object type: i915_active hint: __i915_vma_active+0x0/0x50 [i915] [161.360082] WARNING: CPU: 5 PID: 276 at lib/debugobjects.c:514 debug_print_object+0x80/0xb0 ... [161.360304] CPU: 5 PID: 276 Comm: kworker/5:2 Not tainted 6.5.0-rc1-CI_DRM_13375-g003f860e5577+ #1 [161.360314] Hardware name: Intel Corporation Rocket Lake Client Platform/RocketLake S UDIMM 6L RVP, BIOS RKLSFWI1.R00.3173.A03.2204210138 04/21/2022 [161.360322] Workqueue: i915-unordered __intel_wakeref_put_work [i915] [161.360592] RIP: 0010:debug_print_object+0x80/0xb0 ... [161.361347] debug_object_free+0xeb/0x110 [161.361362] i915_active_fini+0x14/0x130 [i915] [161.361866] release_references+0xfe/0x1f0 [i915] [161.362543] i915_vma_parked+0x1db/0x380 [i915] [161.363129] __gt_park+0x121/0x230 [i915] [161.363515] ____intel_wakeref_put_last+0x1f/0x70 [i915]

That has been tracked down to be happening when another thread is deactivating the VMA inside __active_retire() helper, after the VMA's active counter has been already decremented to 0, but before deactivation of the VMA's object is reported to the object debugging tool.

We could prevent from that race by serializing i915_active_fini() with __active_retire() via ref->tree_lock, but that wouldn't stop the VMA from being used, e.g. from __i915_vma_retire() called at the end of __active_retire(), after that VMA has been already freed by a concurrent i915_vma_destroy() on return from the i915_active_fini(). Then, we should rather fix the issue at the VMA level, not in i915_active.

Since __i915_vma_parked() is called from __gt_park() on last put of the GT's wakeref, the issue could be addressed by holding the GT wakeref long enough for __active_retire() to complete before that wakeref is released and the GT parked.

I believe the issue was introduced by commit d93939730347 ("drm/i915: Remove the vma refcount") which moved a call to i915_active_fini() from a dropped i915_vma_release(), called on last put of the removed VMA kref, to i915_vma_parked() processing path called on last put of a GT wakeref. However, its visibility to the object debugging tool was suppressed by a bug in i915_active that was fixed two weeks later with commit e92eb246feb9 ("drm/i915/active: Fix missing debug object activation").

A VMA associated with a request doesn't acquire a GT wakeref by itself. Instead, it depends on a wakeref held directly by the request's active intel_context for a GT associated with its VM, and indirectly on that intel_context's engine wakeref if the engine belongs to the same GT as the VMA's VM. Those wakerefs are released asynchronously to VMA deactivation.

Fix the issue by getting a wakeref for the VMA's GT when activating it, and putting that wakeref only after the VMA is deactivated. However, exclude global GTT from that processing path, otherwise the GPU never goes idle. Since __i915_vma_retire() may be called from atomic contexts, use async variant of wakeref put. Also, to avoid circular locking dependency, take care of acquiring the wakeref before VM mutex when both are needed.

v7: Add inline comments with justifications for: - using untracked variants of intel_gt_pm_get/put() (Nirmoy), - using async variant of _put(), - not getting the wakeref in case of a global GTT, - always getting the first wakeref outside vm->mutex. v6: Since __i915_vma_active/retire() callbacks are not serialized, storing a wakeref tracking handle inside struct i915_vma is not safe, and there is no other good place for that. Use untracked variants of intel_gt_pm_get/put_async(). v5: Replace "tile" with "GT" across commit description (Rodrigo),

---truncated---

Record
GHSA-gghh-gpx3-pmx6
CVSS 3.1
7.0 HighCVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
Weakness
CWE-416
Updated
2026-11-02
NVD 7.8

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

drm/i915/vma: Fix UAF on destroy against retire race

Object debugging tools were sporadically reporting illegal attempts to free a still active i915 VMA object when parking a GT believed to be idle.

[161.359441] ODEBUG: free active (active state 0) object: ffff88811643b958 object type: i915_active hint: __i915_vma_active+0x0/0x50 [i915] [161.360082] WARNING: CPU: 5 PID: 276 at lib/debugobjects.c:514 debug_print_object+0x80/0xb0 ... [161.360304] CPU: 5 PID: 276 Comm: kworker/5:2 Not tainted 6.5.0-rc1-CI_DRM_13375-g003f860e5577+ #1 [161.360314] Hardware name: Intel Corporation Rocket Lake Client Platform/RocketLake S UDIMM 6L RVP, BIOS RKLSFWI1.R00.3173.A03.2204210138 04/21/2022 [161.360322] Workqueue: i915-unordered __intel_wakeref_put_work [i915] [161.360592] RIP: 0010:debug_print_object+0x80/0xb0 ... [161.361347] debug_object_free+0xeb/0x110 [161.361362] i915_active_fini+0x14/0x130 [i915] [161.361866] release_references+0xfe/0x1f0 [i915] [161.362543] i915_vma_parked+0x1db/0x380 [i915] [161.363129] __gt_park+0x121/0x230 [i915] [161.363515] ____intel_wakeref_put_last+0x1f/0x70 [i915]

That has been tracked down to be happening when another thread is deactivating the VMA inside __active_retire() helper, after the VMA's active counter has been already decremented to 0, but before deactivation of the VMA's object is reported to the object debugging tool.

We could prevent from that race by serializing i915_active_fini() with __active_retire() via ref->tree_lock, but that wouldn't stop the VMA from being used, e.g. from __i915_vma_retire() called at the end of __active_retire(), after that VMA has been already freed by a concurrent i915_vma_destroy() on return from the i915_active_fini(). Then, we should rather fix the issue at the VMA level, not in i915_active.

Since __i915_vma_parked() is called from __gt_park() on last put of the GT's wakeref, the issue could be addressed by holding the GT wakeref long enough for __active_retire() to complete before that wakeref is released and the GT parked.

I believe the issue was introduced by commit d93939730347 ("drm/i915: Remove the vma refcount") which moved a call to i915_active_fini() from a dropped i915_vma_release(), called on last put of the removed VMA kref, to i915_vma_parked() processing path called on last put of a GT wakeref. However, its visibility to the object debugging tool was suppressed by a bug in i915_active that was fixed two weeks later with commit e92eb246feb9 ("drm/i915/active: Fix missing debug object activation").

A VMA associated with a request doesn't acquire a GT wakeref by itself. Instead, it depends on a wakeref held directly by the request's active intel_context for a GT associated with its VM, and indirectly on that intel_context's engine wakeref if the engine belongs to the same GT as the VMA's VM. Those wakerefs are released asynchronously to VMA deactivation.

Fix the issue by getting a wakeref for the VMA's GT when activating it, and putting that wakeref only after the VMA is deactivated. However, exclude global GTT from that processing path, otherwise the GPU never goes idle. Since __i915_vma_retire() may be called from atomic contexts, use async variant of wakeref put. Also, to avoid circular locking dependency, take care of acquiring the wakeref before VM mutex when both are needed.

v7: Add inline comments with justifications for: - using untracked variants of intel_gt_pm_get/put() (Nirmoy), - using async variant of _put(), - not getting the wakeref in case of a global GTT, - always getting the first wakeref outside vm->mutex. v6: Since __i915_vma_active/retire() callbacks are not serialized, storing a wakeref tracking handle inside struct i915_vma is not safe, and there is no other good place for that. Use untracked variants of intel_gt_pm_get/put_async(). v5: Replace "tile" with "GT" across commit description (Rodrigo),

---truncated---

Record
CVE-2024-26939
CVSS 3.1
7.8 HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CVSS 3.1
7.0 HighCVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
Weakness
CWE-416
Updated
2026-11-02
OSVBELL-CVE-2024-26939 7.0
Record
BELL-CVE-2024-26939
CVSS 3.1
7.0 HighCVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
Updated
2026-11-02
OSV 7.8

drm/i915/vma: Fix UAF on destroy against retire race

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

drm/i915/vma: Fix UAF on destroy against retire race

Object debugging tools were sporadically reporting illegal attempts to free a still active i915 VMA object when parking a GT believed to be idle.

[161.359441] ODEBUG: free active (active state 0) object: ffff88811643b958 object type: i915_active hint: __i915_vma_active+0x0/0x50 [i915] [161.360082] WARNING: CPU: 5 PID: 276 at lib/debugobjects.c:514 debug_print_object+0x80/0xb0 ... [161.360304] CPU: 5 PID: 276 Comm: kworker/5:2 Not tainted 6.5.0-rc1-CI_DRM_13375-g003f860e5577+ #1 [161.360314] Hardware name: Intel Corporation Rocket Lake Client Platform/RocketLake S UDIMM 6L RVP, BIOS RKLSFWI1.R00.3173.A03.2204210138 04/21/2022 [161.360322] Workqueue: i915-unordered __intel_wakeref_put_work [i915] [161.360592] RIP: 0010:debug_print_object+0x80/0xb0 ... [161.361347] debug_object_free+0xeb/0x110 [161.361362] i915_active_fini+0x14/0x130 [i915] [161.361866] release_references+0xfe/0x1f0 [i915] [161.362543] i915_vma_parked+0x1db/0x380 [i915] [161.363129] __gt_park+0x121/0x230 [i915] [161.363515] ____intel_wakeref_put_last+0x1f/0x70 [i915]

That has been tracked down to be happening when another thread is deactivating the VMA inside __active_retire() helper, after the VMA's active counter has been already decremented to 0, but before deactivation of the VMA's object is reported to the object debugging tool.

We could prevent from that race by serializing i915_active_fini() with __active_retire() via ref->tree_lock, but that wouldn't stop the VMA from being used, e.g. from __i915_vma_retire() called at the end of __active_retire(), after that VMA has been already freed by a concurrent i915_vma_destroy() on return from the i915_active_fini(). Then, we should rather fix the issue at the VMA level, not in i915_active.

Since __i915_vma_parked() is called from __gt_park() on last put of the GT's wakeref, the issue could be addressed by holding the GT wakeref long enough for __active_retire() to complete before that wakeref is released and the GT parked.

I believe the issue was introduced by commit d93939730347 ("drm/i915: Remove the vma refcount") which moved a call to i915_active_fini() from a dropped i915_vma_release(), called on last put of the removed VMA kref, to i915_vma_parked() processing path called on last put of a GT wakeref. However, its visibility to the object debugging tool was suppressed by a bug in i915_active that was fixed two weeks later with commit e92eb246feb9 ("drm/i915/active: Fix missing debug object activation").

A VMA associated with a request doesn't acquire a GT wakeref by itself. Instead, it depends on a wakeref held directly by the request's active intel_context for a GT associated with its VM, and indirectly on that intel_context's engine wakeref if the engine belongs to the same GT as the VMA's VM. Those wakerefs are released asynchronously to VMA deactivation.

Fix the issue by getting a wakeref for the VMA's GT when activating it, and putting that wakeref only after the VMA is deactivated. However, exclude global GTT from that processing path, otherwise the GPU never goes idle. Since __i915_vma_retire() may be called from atomic contexts, use async variant of wakeref put. Also, to avoid circular locking dependency, take care of acquiring the wakeref before VM mutex when both are needed.

v7: Add inline comments with justifications for: - using untracked variants of intel_gt_pm_get/put() (Nirmoy), - using async variant of _put(), - not getting the wakeref in case of a global GTT, - always getting the first wakeref outside vm->mutex. v6: Since __i915_vma_active/retire() callbacks are not serialized, storing a wakeref tracking handle inside struct i915_vma is not safe, and there is no other good place for that. Use untracked variants of intel_gt_pm_get/put_async(). v5: Replace "tile" with "GT" across commit description (Rodrigo),

---truncated---

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

In the Linux kernel, the following vulnerability has been resolved: drm/i915/vma: Fix UAF on destroy against retire race Object debugging tools were sporadically reporting illegal attempts to free a still active i915 VMA object when parking a GT believed to be idle. [161.359441] ODEBUG: free active (active state 0) object: ffff88811643b958 object type: i915_active hint: __i915_vma_active+0x0/0x50 [i915] [161.360082] WARNING: CPU: 5 PID: 276 at lib/debugobjects.c:514 debug_print_object+0x80/0xb0 ... [161.360304] CPU: 5 PID: 276 Comm: kworker/5:2 Not tainted 6.5.0-rc1-CI_DRM_13375-g003f860e5577+ #1 [161.360314] Hardware name: Intel Corporation Rocket Lake Client Platform/RocketLake S UDIMM 6L RVP, BIOS RKLSFWI1.R00.3173.A03.2204210138 04/21/2022 [161.360322] Workqueue: i915-unordered __intel_wakeref_put_work [i915] [161.360592] RIP: 0010:debug_print_object+0x80/0xb0 ... [161.361347] debug_object_free+0xeb/0x110 [161.361362] i915_active_fini+0x14/0x130 [i915] [161.361866] release_references+0xfe/0x1f0 [i915] [161.362543] i915_vma_parked+0x1db/0x380 [i915] [161.363129] __gt_park+0x121/0x230 [i915] [161.363515] ____intel_wakeref_put_last+0x1f/0x70 [i915] That has been tracked down to be happening when another thread is deactivating the VMA inside __active_retire() helper, after the VMA's active counter has been already decremented to 0, but before deactivation of the VMA's object is reported to the object debugging tool. We could prevent from that race by serializing i915_active_fini() with __active_retire() via ref->tree_lock, but that wouldn't stop the VMA from being used, e.g. from __i915_vma_retire() called at the end of __active_retire(), after that VMA has been already freed by a concurrent i915_vma_destroy() on return from the i915_active_fini(). Then, we should rather fix the issue at the VMA level, not in i915_active. Since __i915_vma_parked() is called from __gt_park() on last put of the GT's wakeref, the issue could be addressed by holding the GT wakeref long enough for __active_retire() to complete before that wakeref is released and the GT parked. I believe the issue was introduced by commit d93939730347 ("drm/i915: Remove the vma refcount") which moved a call to i915_active_fini() from a dropped i915_vma_release(), called on last put of the removed VMA kref, to i915_vma_parked() processing path called on last put of a GT wakeref. However, its visibility to the object debugging tool was suppressed by a bug in i915_active that was fixed two weeks later with commit e92eb246feb9 ("drm/i915/active: Fix missing debug object activation"). A VMA associated with a request doesn't acquire a GT wakeref by itself. Instead, it depends on a wakeref held directly by the request's active intel_context for a GT associated with its VM, and indirectly on that intel_context's engine wakeref if the engine belongs to the same GT as the VMA's VM. Those wakerefs are released asynchronously to VMA deactivation. Fix the issue by getting a wakeref for the VMA's GT when activating it, and putting that wakeref only after the VMA is deactivated. However, exclude global GTT from that processing path, otherwise the GPU never goes idle. Since __i915_vma_retire() may be called from atomic contexts, use async variant of wakeref put. Also, to avoid circular locking dependency, take care of acquiring the wakeref before VM mutex when both are needed. v7: Add inline comments with justifications for: - using untracked variants of intel_gt_pm_get/put() (Nirmoy), - using async variant of _put(), - not getting the wakeref in case of a global GTT, - always getting the first wakeref outside vm->mutex. v6: Since __i915_vma_active/retire() callbacks are not serialized, storing a wakeref tracking handle inside struct i915_vma is not safe, and there is no other good place for that. Use untracked variants of intel_gt_pm_get/put_async(). v5: Replace "tile" with "GT" across commit description (Rodrigo), - ---truncated---

Record
DEBIAN-CVE-2024-26939
CVSS 3.1
7.0 HighCVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
Updated
2026-11-02
OSVRHSA-2024:7000 7.8

Red Hat Security Advisory: kernel security update

Record
RHSA-2024:7000
CVSS 3.1
7.8 HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Updated
2026-11-02
OSVRHSA-2024:7001 7.8

Red Hat Security Advisory: kernel-rt security update

Record
RHSA-2024:7001
CVSS 3.1
7.8 HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Updated
2026-11-02
OSVRHSA-2024:9315 7.8

Red Hat Security Advisory: kernel security update

Record
RHSA-2024:9315
CVSS 3.1
7.8 HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Updated
2026-11-02
OSVRHSA-2025:9584 7.1

Red Hat Security Advisory: kernel security update

Record
RHSA-2025:9584
CVSS 3.1
7.1 HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
Updated
2026-11-02
OSVRLSA-2024:7000 7.8

Important: kernel security update

The kernel packages contain the Linux kernel, the core of any Linux operating system.
Security Fix(es):

CVE-2023-6040 CVE-2024-26595 CVE-2024-26600 CVE-2021-46984 CVE-2023-52478 CVE-2023-52476 CVE-2023-52522 CVE-2021-47101 CVE-2021-47097 CVE-2023-52605 CVE-2024-26638 CVE-2024-26645 CVE-2024-26665 CVE-2024-26720 CVE-2024-26717 CVE-2024-26769 CVE-2024-26846 CVE-2024-26894 CVE-2024-26880 CVE-2024-26855 CVE-2024-26923 CVE-2024-26939 CVE-2024-27013 CVE-2024-27042 CVE-2024-35809 CVE-2023-52683 CVE-2024-35884 CVE-2024-35877 CVE-2024-35944 CVE-2024-35989 CVE-2021-47412 CVE-2021-47393 CVE-2021-47386 CVE-2021-47385 CVE-2021-47384 CVE-2021-47383 CVE-2021-47432 CVE-2021-47352 CVE-2021-47338 CVE-2021-47321 CVE-2021-47289 CVE-2021-47287 CVE-2023-52798 CVE-2023-52809 CVE-2023-52817 CVE-2023-52840 CVE-2023-52800 CVE-2021-47441 CVE-2021-47466 CVE-2021-47455 CVE-2021-47497 CVE-2021-47560 CVE-2021-47527 CVE-2024-36883 CVE-2024-36922 CVE-2024-36920 CVE-2024-36902 CVE-2024-36953 CVE-2024-36939 CVE-2024-36919 CVE-2024-36901 CVE-2021-47582 CVE-2021-47609 CVE-2024-38619 CVE-2022-48754 CVE-2022-48760 CVE-2024-38581 CVE-2024-38579 CVE-2024-38570 CVE-2024-38559 CVE-2024-38558 CVE-2024-37356 CVE-2024-39471 CVE-2024-39499 CVE-2024-39501 CVE-2024-39506 CVE-2024-40904 CVE-2024-40911 CVE-2024-40912 CVE-2024-40929 CVE-2024-40931 CVE-2024-40941 CVE-2024-40954 CVE-2024-40958 CVE-2024-40959 CVE-2024-40960 CVE-2024-40972 CVE-2024-40977 CVE-2024-40978 CVE-2024-40988 CVE-2024-40989 CVE-2024-40995 CVE-2024-40997 CVE-2024-40998 CVE-2024-41005 CVE-2024-40901 CVE-2024-41007 CVE-2024-41008 CVE-2022-48804 CVE-2022-48836 CVE-2022-48866 CVE-2024-41090 CVE-2024-41091 CVE-2024-41012 CVE-2024-41013 CVE-2024-41014 CVE-2024-41023 CVE-2024-41035 CVE-2024-41038 CVE-2024-41039 CVE-2024-41040 CVE-2024-41041 CVE-2024-41044 CVE-2024-41055 CVE-2024-41056 CVE-2024-41060 CVE-2024-41064 CVE-2024-41065 CVE-2024-41071 CVE-2024-41076 CVE-2024-41097 CVE-2024-42084 CVE-2024-42090 CVE-2024-42094 CVE-2024-42096 CVE-2024-42114 CVE-2024-42124 CVE-2024-42131 CVE-2024-42152 CVE-2024-42154 CVE-2024-42225 CVE-2024-42226 CVE-2024-42228 CVE-2024-42237 CVE-2024-42238 CVE-2024-42240 CVE-2024-42246 CVE-2024-42322 CVE-2024-43830 CVE-2024-43871 For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.

Record
RLSA-2024:7000
CVSS 3.1
7.8 HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Updated
2026-11-02
OSVUBUNTU-CVE-2024-26939 7.0

In the Linux kernel, the following vulnerability has been resolved: drm/i915/vma: Fix UAF on destroy against retire race Object debugging tools were sporadically reporting illegal attempts to free a still active i915 VMA object when parking a GT believed to be idle. [161.359441] ODEBUG: free active (active state 0) object: ffff88811643b958 object type: i915_active hint: __i915_vma_active+0x0/0x50 [i915] [161.360082] WARNING: CPU: 5 PID: 276 at lib/debugobjects.c:514 debug_print_object+0x80/0xb0 ... [161.360304] CPU: 5 PID: 276 Comm: kworker/5:2 Not tainted 6.5.0-rc1-CI_DRM_13375-g003f860e5577+ #1 [161.360314] Hardware name: Intel Corporation Rocket Lake Client Platform/RocketLake S UDIMM 6L RVP, BIOS RKLSFWI1.R00.3173.A03.2204210138 04/21/2022 [161.360322] Workqueue: i915-unordered __intel_wakeref_put_work [i915] [161.360592] RIP: 0010:debug_print_object+0x80/0xb0 ... [161.361347] debug_object_free+0xeb/0x110 [161.361362] i915_active_fini+0x14/0x130 [i915] [161.361866] release_references+0xfe/0x1f0 [i915] [161.362543] i915_vma_parked+0x1db/0x380 [i915] [161.363129] __gt_park+0x121/0x230 [i915] [161.363515] ____intel_wakeref_put_last+0x1f/0x70 [i915] That has been tracked down to be happening when another thread is deactivating the VMA inside __active_retire() helper, after the VMA's active counter has been already decremented to 0, but before deactivation of the VMA's object is reported to the object debugging tool. We could prevent from that race by serializing i915_active_fini() with __active_retire() via ref->tree_lock, but that wouldn't stop the VMA from being used, e.g. from __i915_vma_retire() called at the end of __active_retire(), after that VMA has been already freed by a concurrent i915_vma_destroy() on return from the i915_active_fini(). Then, we should rather fix the issue at the VMA level, not in i915_active. Since __i915_vma_parked() is called from __gt_park() on last put of the GT's wakeref, the issue could be addressed by holding the GT wakeref long enough for __active_retire() to complete before that wakeref is released and the GT parked. I believe the issue was introduced by commit d93939730347 ("drm/i915: Remove the vma refcount") which moved a call to i915_active_fini() from a dropped i915_vma_release(), called on last put of the removed VMA kref, to i915_vma_parked() processing path called on last put of a GT wakeref. However, its visibility to the object debugging tool was suppressed by a bug in i915_active that was fixed two weeks later with commit e92eb246feb9 ("drm/i915/active: Fix missing debug object activation"). A VMA associated with a request doesn't acquire a GT wakeref by itself. Instead, it depends on a wakeref held directly by the request's active intel_context for a GT associated with its VM, and indirectly on that intel_context's engine wakeref if the engine belongs to the same GT as the VMA's VM. Those wakerefs are released asynchronously to VMA deactivation. Fix the issue by getting a wakeref for the VMA's GT when activating it, and putting that wakeref only after the VMA is deactivated. However, exclude global GTT from that processing path, otherwise the GPU never goes idle. Since __i915_vma_retire() may be called from atomic contexts, use async variant of wakeref put. Also, to avoid circular locking dependency, take care of acquiring the wakeref before VM mutex when both are needed. v7: Add inline comments with justifications for: - using untracked variants of intel_gt_pm_get/put() (Nirmoy), - using async variant of _put(), - not getting the wakeref in case of a global GTT, - always getting the first wakeref outside vm->mutex. v6: Since __i915_vma_active/retire() callbacks are not serialized, storing a wakeref tracking handle inside struct i915_vma is not safe, and there is no other good place for that. Use untracked variants of intel_gt_pm_get/put_async(). v5: Replace "tile" with "GT" across commit description (Rodrigo), - ---truncated---

Record
UBUNTU-CVE-2024-26939
CVSS 3.1
7.0 HighCVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
CVSS 3.1
7.8 HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Updated
2026-11-02
OSVALSA-2024:7000 No score

Important: kernel security update

The kernel packages contain the Linux kernel, the core of any Linux operating system.
Security Fix(es):

CVE-2023-6040 CVE-2024-26595 CVE-2024-26600 CVE-2021-46984 CVE-2023-52478 CVE-2023-52476 CVE-2023-52522 CVE-2021-47101 CVE-2021-47097 CVE-2023-52605 CVE-2024-26638 CVE-2024-26645 CVE-2024-26665 CVE-2024-26720 CVE-2024-26717 CVE-2024-26769 CVE-2024-26846 CVE-2024-26894 CVE-2024-26880 CVE-2024-26855 CVE-2024-26923 CVE-2024-26939 CVE-2024-27013 CVE-2024-27042 CVE-2024-35809 CVE-2023-52683 CVE-2024-35884 CVE-2024-35877 CVE-2024-35944 CVE-2024-35989 CVE-2021-47412 CVE-2021-47393 CVE-2021-47386 CVE-2021-47385 CVE-2021-47384 CVE-2021-47383 CVE-2021-47432 CVE-2021-47352 CVE-2021-47338 CVE-2021-47321 CVE-2021-47289 CVE-2021-47287 CVE-2023-52798 CVE-2023-52809 CVE-2023-52817 CVE-2023-52840 CVE-2023-52800 CVE-2021-47441 CVE-2021-47466 CVE-2021-47455 CVE-2021-47497 CVE-2021-47560 CVE-2021-47527 CVE-2024-36883 CVE-2024-36922 CVE-2024-36920 CVE-2024-36902 CVE-2024-36953 CVE-2024-36939 CVE-2024-36919 CVE-2024-36901 CVE-2021-47582 CVE-2021-47609 CVE-2024-38619 CVE-2022-48754 CVE-2022-48760 CVE-2024-38581 CVE-2024-38579 CVE-2024-38570 CVE-2024-38559 CVE-2024-38558 CVE-2024-37356 CVE-2024-39471 CVE-2024-39499 CVE-2024-39501 CVE-2024-39506 CVE-2024-40904 CVE-2024-40911 CVE-2024-40912 CVE-2024-40929 CVE-2024-40931 CVE-2024-40941 CVE-2024-40954 CVE-2024-40958 CVE-2024-40959 CVE-2024-40960 CVE-2024-40972 CVE-2024-40977 CVE-2024-40978 CVE-2024-40988 CVE-2024-40989 CVE-2024-40995 CVE-2024-40997 CVE-2024-40998 CVE-2024-41005 CVE-2024-40901 CVE-2024-41007 CVE-2024-41008 CVE-2022-48804 CVE-2022-48836 CVE-2022-48866 CVE-2024-41090 CVE-2024-41091 CVE-2024-41012 CVE-2024-41013 CVE-2024-41014 CVE-2024-41023 CVE-2024-41035 CVE-2024-41038 CVE-2024-41039 CVE-2024-41040 CVE-2024-41041 CVE-2024-41044 CVE-2024-41055 CVE-2024-41056 CVE-2024-41060 CVE-2024-41064 CVE-2024-41065 CVE-2024-41071 CVE-2024-41076 CVE-2024-41097 CVE-2024-42084 CVE-2024-42090 CVE-2024-42094 CVE-2024-42096 CVE-2024-42114 CVE-2024-42124 CVE-2024-42131 CVE-2024-42152 CVE-2024-42154 CVE-2024-42225 CVE-2024-42226 CVE-2024-42228 CVE-2024-42237 CVE-2024-42238 CVE-2024-42240 CVE-2024-42246 CVE-2024-42322 CVE-2024-43830 CVE-2024-43871 For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.

Record
ALSA-2024:7000
Updated
2026-11-02
OSVALSA-2024:7001 No score

Important: kernel-rt security update

The kernel-rt packages provide the Real Time Linux Kernel, which enables fine-tuning for systems with extremely high determinism requirements.
Security Fix(es):

CVE-2023-6040 CVE-2024-26595 CVE-2021-46984 CVE-2023-52478 CVE-2023-52476 CVE-2023-52522 CVE-2021-47101 CVE-2021-47097 CVE-2023-52605 CVE-2024-26645 CVE-2024-26665 CVE-2024-26720 CVE-2024-26717 CVE-2024-26769 CVE-2024-26894 CVE-2024-26880 CVE-2024-26855 CVE-2024-26923 CVE-2024-26939 CVE-2024-27013 CVE-2024-27042 CVE-2024-35809 CVE-2023-52683 CVE-2024-35884 CVE-2024-35877 CVE-2024-35944 CVE-2024-35989 CVE-2021-47412 CVE-2021-47393 CVE-2021-47386 CVE-2021-47385 CVE-2021-47384 CVE-2021-47383 CVE-2021-47432 CVE-2021-47352 CVE-2021-47338 CVE-2021-47321 CVE-2021-47289 CVE-2021-47287 CVE-2023-52817 CVE-2023-52840 CVE-2021-47441 CVE-2021-47466 CVE-2021-47455 CVE-2021-47497 CVE-2021-47560 CVE-2021-47527 CVE-2024-36883 CVE-2024-36920 CVE-2024-36902 CVE-2024-36953 CVE-2024-36939 CVE-2024-36901 CVE-2021-47582 CVE-2021-47609 CVE-2024-38619 CVE-2022-48754 CVE-2022-48760 CVE-2024-38581 CVE-2024-38570 CVE-2024-38559 CVE-2024-38558 CVE-2024-37356 CVE-2024-39471 CVE-2024-39499 CVE-2024-39501 CVE-2024-39506 CVE-2024-40904 CVE-2024-40911 CVE-2024-40912 CVE-2024-40929 CVE-2024-40931 CVE-2024-40941 CVE-2024-40954 CVE-2024-40958 CVE-2024-40959 CVE-2024-40960 CVE-2024-40972 CVE-2024-40977 CVE-2024-40978 CVE-2024-40988 CVE-2024-40989 CVE-2024-40995 CVE-2024-40997 CVE-2024-40998 CVE-2024-41005 CVE-2024-40901 CVE-2024-41007 CVE-2024-41008 CVE-2022-48804 CVE-2022-48836 CVE-2022-48866 CVE-2024-41090 CVE-2024-41091 CVE-2024-41012 CVE-2024-41013 CVE-2024-41014 CVE-2024-41035 CVE-2024-41038 CVE-2024-41039 CVE-2024-41040 CVE-2024-41041 CVE-2024-41044 CVE-2024-41055 CVE-2024-41056 CVE-2024-41060 CVE-2024-41071 CVE-2024-41076 CVE-2024-41097 CVE-2024-42084 CVE-2024-42090 CVE-2024-42096 CVE-2024-42114 CVE-2024-42124 CVE-2024-42131 CVE-2024-42152 CVE-2024-42154 CVE-2024-42226 CVE-2024-42228 CVE-2024-42237 CVE-2024-42238 CVE-2024-42240 CVE-2024-42246 CVE-2024-42322 CVE-2024-43871 For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.

Record
ALSA-2024:7001
Updated
2026-11-02
OSVCLSA-2025-1758796886 No score

kernel: Fix of 23 CVEs

  • drm/amd/amdgpu: introduce gc_*_mes_2.bin v2
  • proc: fix a dentry lock race between release_task and lookup
  • scsi: aacraid: Stop using PCI_IRQ_AFFINITY
  • scsi: aacraid: Remove useless code
  • scsi: aacraid: Remove unused aac_check_health()
  • scsi: aacraid: struct {user,}sgmap{,64,raw}: Replace 1-element arrays with flexible arrays
  • scsi: aacraid: Rearrange order of struct aac_srb_unit
  • scsi: aacraid: struct aac_ciss_phys_luns_resp: Replace 1-element array with flexible array
  • scsi: aacraid: union aac_init: Replace 1-element array with flexible array
  • scsi: aacraid: aachba: Replace snprintf() with the safer scnprintf() variant
  • Revert "scsi: aacraid: Reply queue mapping to CPUs based on IRQ affinity"
  • scsi: aacraid: Avoid -Warray-bounds warning
  • scsi: aacraid: Reply queue mapping to CPUs based on IRQ affinity
  • scsi: aacraid: Replace all non-returning strlcpy with strscpy
  • scsi: aacraid: Declare SCSI host template const
  • scsi: aacraid: Drop redundant pci_enable_pcie_error_reporting()
  • scsi: aacraid: Allocate cmd_priv with scsicmd
  • scsi: aacraid: Remove redundant "the"
  • scsi: aacraid: Fix undefined behavior due to shift overflowing the constant
  • scsi: aacraid: Clean up some inconsistent indenting
  • scsi: aacraid: Move the SCSI pointer to private command data
  • scsi: aacraid: Fix spelling of "its"
  • scsi: aacraid: Call scsi_done() directly
  • scsi: aacraid: Introduce aac_scsi_done()
  • scsi: aacraid: Use scsi_cmd_to_rq() instead of scsi_cmnd.request
  • scsi: aacraid: Remove an unused include
  • x86/sev: Check for MWAITX and MONITORX opcodes in the #VC handler {CVE-2024-25743}
  • net: sched: sfb: fix null pointer access issue when sfb_init() fails {CVE-2022-50356}
  • ipv6: mcast: Delay put pmc->idev in mld_del_delrec() {CVE-2025-38550}
  • scsi: lpfc: Use memcpy() for BIOS version {CVE-2025-38332}
  • PM: hibernate: defer device probing when resuming from hibernation {CVE-2022-50202}
  • net: fix UaF in netns ops registration error path {CVE-2023-52999}
  • net: fix UAF issue in nfqnl_nf_hook_drop() when ops_init() failed {CVE-2023-52999}
  • usb: typec: fix potential array underflow in ucsi_ccg_sync_control() {CVE-2024-53203}
  • soundwire: cadence: fix invalid PDI offset {CVE-2024-38635}
  • drm/i915/vma: Fix UAF on destroy against retire race {CVE-2024-26939}
  • netns: Make get_net_ns() handle zero refcount net {CVE-2024-40958}
  • bonding: Fix out-of-bounds read in bond_option_arp_ip_targets_set() {CVE-2024-39487}
  • wifi: iwlwifi: mvm: guard against invalid STA ID on removal {CVE-2024-36921}
  • wifi: ath11k: fix gtk offload status event locking {CVE-2023-52777}
  • wifi: mac80211: fix potential key use-after-free {CVE-2023-52530}
  • i2c: mlxbf: prevent stack overflow in mlxbf_i2c_smbus_start_transaction() {CVE-2022-48632}
  • net/sched: act_mirred: don't override retval if we already lost the skb {CVE-2024-26739}
  • can: j1939: j1939_netdev_start(): fix UAF for rx_kref of j1939_priv {CVE-2021-47459}
  • net: hns3: fix use-after-free bug in hclgevf_send_mbx_msg {CVE-2021-47596}
  • Squashfs: check the inode number is not the invalid value of zero {CVE-2024-26982}
  • crypto: qat - resolve race condition during AER recovery {CVE-2024-26974}
  • crypto: qat - fix double free during reset
  • media: pvrusb2: fix use after free on context disconnection {CVE-2023-52445}
  • fs/smb/client: Reset password pointer to NULL {CVE-2023-5345}
Record
CLSA-2025-1758796886
Updated
2026-11-02
OSVCLSA-2026-1770032032 No score

kernel: Fix of 63 CVEs

  • mm/memory-failure: fix VM_BUG_ON_PAGE(PagePoisoned(page)) when unpoison memory {CVE-2025-39883}
  • comedi: aio_iiro_16: Fix bit shift out of bounds {CVE-2025-38529}
  • comedi: das6402: Fix bit shift out of bounds {CVE-2025-38482}
  • comedi: pcl812: Fix bit shift out of bounds {CVE-2025-38530}
  • comedi: das16m1: Fix bit shift out of bounds {CVE-2025-38483}
  • tcp: Don't call reqsk_fastopen_remove() in tcp_conn_request(). {CVE-2025-40186}
  • wifi: brcmfmac: fix use-after-free when rescheduling brcmf_btcoex_info work {CVE-2025-39863}
  • smb: client: Fix use-after-free in cifs_fill_dirent {CVE-2025-38051}
  • libceph: fix potential use-after-free in have_mon_and_osd_map() {CVE-2025-68285}
  • sctp: avoid NULL dereference when chunk data buffer is missing {CVE-2025-40240}
  • smb: client: let recv_done verify data_offset, data_length and remaining_data_length {CVE-2025-39933}
  • vsock: Ignore signal/timeout on connect() if already established {CVE-2025-40248}
  • ASoC: Intel: bytcr_rt5640: Fix invalid quirk input mapping {CVE-2025-40154}
  • Bluetooth: hci_event: call disconnect callback before deleting conn {CVE-2023-53673}
  • net: fix information leakage in /proc/net/ptype {CVE-2022-48757}
  • net/mlx5e: fix a potential double-free in fs_any_create_groups {CVE-2023-52667}
  • mlxsw: spectrum_acl_tcam: Fix possible use-after-free during activity update {CVE-2024-35855}
  • Squashfs: check the inode number is not the invalid value of zero {CVE-2024-26982}
  • crypto: qat - resolve race condition during AER recovery {CVE-2024-26974}
  • perf/core: Bail out early if the request AUX area is out of bound {CVE-2023-52835}
  • ext4: fix double-free of blocks due to wrong extents moved_len {CVE-2024-26704}
  • stm class: Fix a double free in stm_register_device() {CVE-2024-38627}
  • pinctrl: core: delete incorrect free in pinctrl_enable() {CVE-2024-36940}
  • ipvlan: add ipvlan_route_v6_outbound() helper {CVE-2023-52796}
  • wifi: ath11k: fix gtk offload status event locking {CVE-2023-52777}
  • ice: fix memory corruption bug with suspend and rebuild {CVE-2024-35911}
  • drm/amdgpu: Fix potential out-of-bounds access in 'amdgpu_discovery_reg_base_init()' {CVE-2024-27042}
  • drm/i915/vma: Fix UAF on destroy against retire race {CVE-2024-26939}
  • netfilter: nf_tables: prefer nft_chain_validate {CVE-2024-41042}
  • Bluetooth: Fix potential use-after-free when clear keys {CVE-2023-53386}
  • drm/amd/display: Check num_valid_sets before accessing reader_wm_sets[] {CVE-2024-46815}
  • drm/amd/display: Check pipe offset before setting vblank {CVE-2024-42120}
  • nbd: fix incomplete validation of ioctl arg {CVE-2023-53513}
  • RDMA/rxe: Fix incomplete state save in rxe_requester {CVE-2023-53539}
  • netfilter: nftables: exthdr: fix 4-byte stack OOB write
  • net: ppp: Add bound checking for skb data on ppp_sync_txmung {CVE-2025-37749}
  • net_sched: hfsc: Fix a potential UAF in hfsc_dequeue() too {CVE-2025-37823}
  • iommu/amd: Fix potential buffer overflow in parse_ivrs_acpihid {CVE-2025-37927}
  • drm/vmwgfx: Validate command header size against SVGA_CMD_MAX_DATASIZE {CVE-2025-40277}
  • nfsd: handle get_client_locked() failure in nfsd4_setclientid_confirm() {CVE-2025-38724}
  • RDMA/rxe: Fix mr->map double free {CVE-2022-50543}
  • ipc: fix to protect IPCS lookups using RCU {CVE-2025-38212}
  • vsock/vmci: Clear the vmci transport packet properly when initializing it {CVE-2025-38403}
  • RDMA/rxe: Fix slab-use-after-free Read in rxe_queue_cleanup bug {CVE-2025-38024}
  • drm/sched: Fix potential double free in drm_sched_job_add_resv_dependencies {CVE-2025-40096}
  • HID: usbhid: Eliminate recurrent out-of-bounds bug in usbhid_parse() {CVE-2025-38103}
  • drm/i915: mark requests for GuC virtual engines to avoid use-after-free {CVE-2023-53552}
  • net: atlantic: fix fragment overflow handling in RX path {CVE-2025-68301}
  • net: atm: add lec_mutex {CVE-2025-38323}
  • net: openvswitch: fix nested key length validation in the set() action {CVE-2025-37789}
  • scsi: lpfc: Fix buffer free/clear order in deferred receive path…
Record
CLSA-2026-1770032032
Updated
2026-11-02
OSVMGASA-2024-0263 No score

Updated kernel kmod-xtables-addons kmod-virtualbox dwarves packages fix security vulnerabilities

Upstream kernel version 6.6.37 fix bugs and vulnerabilities. The dwarves, kmod-virtualbox and kmod-xtables-addons packages have been updated to work with this new kernel. For information about the vulnerabilities see the links.

Record
MGASA-2024-0263
Updated
2026-11-02
OSVMGASA-2024-0266 No score

Updated kernel-linus packages fix security vulnerabilities

Vanilla upstream kernel version 6.6.37 fix bugs and vulnerabilities. For information about the vulnerabilities see the links.

Record
MGASA-2024-0266
Updated
2026-11-02
OSVRLSA-2024:7001 No score

Important: kernel-rt security update

The kernel-rt packages provide the Real Time Linux Kernel, which enables fine-tuning for systems with extremely high determinism requirements.
Security Fix(es):

CVE-2023-6040 CVE-2024-26595 CVE-2021-46984 CVE-2023-52478 CVE-2023-52476 CVE-2023-52522 CVE-2021-47101 CVE-2021-47097 CVE-2023-52605 CVE-2024-26645 CVE-2024-26665 CVE-2024-26720 CVE-2024-26717 CVE-2024-26769 CVE-2024-26894 CVE-2024-26880 CVE-2024-26855 CVE-2024-26923 CVE-2024-26939 CVE-2024-27013 CVE-2024-27042 CVE-2024-35809 CVE-2023-52683 CVE-2024-35884 CVE-2024-35877 CVE-2024-35944 CVE-2024-35989 CVE-2021-47412 CVE-2021-47393 CVE-2021-47386 CVE-2021-47385 CVE-2021-47384 CVE-2021-47383 CVE-2021-47432 CVE-2021-47352 CVE-2021-47338 CVE-2021-47321 CVE-2021-47289 CVE-2021-47287 CVE-2023-52817 CVE-2023-52840 CVE-2021-47441 CVE-2021-47466 CVE-2021-47455 CVE-2021-47497 CVE-2021-47560 CVE-2021-47527 CVE-2024-36883 CVE-2024-36920 CVE-2024-36902 CVE-2024-36953 CVE-2024-36939 CVE-2024-36901 CVE-2021-47582 CVE-2021-47609 CVE-2024-38619 CVE-2022-48754 CVE-2022-48760 CVE-2024-38581 CVE-2024-38570 CVE-2024-38559 CVE-2024-38558 CVE-2024-37356 CVE-2024-39471 CVE-2024-39499 CVE-2024-39501 CVE-2024-39506 CVE-2024-40904 CVE-2024-40911 CVE-2024-40912 CVE-2024-40929 CVE-2024-40931 CVE-2024-40941 CVE-2024-40954 CVE-2024-40958 CVE-2024-40959 CVE-2024-40960 CVE-2024-40972 CVE-2024-40977 CVE-2024-40978 CVE-2024-40988 CVE-2024-40989 CVE-2024-40995 CVE-2024-40997 CVE-2024-40998 CVE-2024-41005 CVE-2024-40901 CVE-2024-41007 CVE-2024-41008 CVE-2022-48804 CVE-2022-48836 CVE-2022-48866 CVE-2024-41090 CVE-2024-41091 CVE-2024-41012 CVE-2024-41013 CVE-2024-41014 CVE-2024-41035 CVE-2024-41038 CVE-2024-41039 CVE-2024-41040 CVE-2024-41041 CVE-2024-41044 CVE-2024-41055 CVE-2024-41056 CVE-2024-41060 CVE-2024-41071 CVE-2024-41076 CVE-2024-41097 CVE-2024-42084 CVE-2024-42090 CVE-2024-42096 CVE-2024-42114 CVE-2024-42124 CVE-2024-42131 CVE-2024-42152 CVE-2024-42154 CVE-2024-42226 CVE-2024-42228 CVE-2024-42237 CVE-2024-42238 CVE-2024-42240 CVE-2024-42246 CVE-2024-42322 CVE-2024-43871 For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.

Record
RLSA-2024:7001
Updated
2026-11-02
OSVSUSE-SU-2024:1644-1 No score

Security update for the Linux Kernel

The SUSE Linux Enterprise 15 SP5 Azure kernel was updated to receive various security bugfixes.

The following security bugs were fixed:

  • CVE-2024-27389: Fixed pstore inode handling with d_invalidate() (bsc#1223705).
  • CVE-2024-27062: Fixed nouveau lock inside client object tree (bsc#1223834).
  • CVE-2024-27056: Fixed wifi/iwlwifi/mvm to ensure offloading TID queue exists (bsc#1223822).
  • CVE-2024-27046: Fixed nfp/flower handling acti_netdevs allocation failure (bsc#1223827).
  • CVE-2024-27043: Fixed a use-after-free in edia/dvbdev in different places (bsc#1223824).
  • CVE-2024-27042: Fixed drm/amdgpu for potential out-of-bounds access in amdgpu_discovery_reg_base_init() (bsc#1223823).
  • CVE-2024-27041: Fixed drm/amd/display NULL checks for adev->dm.dc in amdgpu_dm_fini() (bsc#1223714).
  • CVE-2024-27039: Fixed clk/hisilicon/hi3559a an erroneous devm_kfree() (bsc#1223821).
  • CVE-2024-27038: Fixed clk_core_get NULL pointer dereference (bsc#1223816).
  • CVE-2024-27030: Fixed octeontx2-af to use separate handlers for interrupts (bsc#1223790).
  • CVE-2024-27014: Fixed net/mlx5e to prevent deadlock while disabling aRFS (bsc#1223735).
  • CVE-2024-27013: Fixed tun limit printing rate when illegal packet received by tun device (bsc#1223745).
  • CVE-2024-26993: Fixed fs/sysfs reference leak in sysfs_break_active_protection() (bsc#1223693).
  • CVE-2024-26982: Fixed Squashfs inode number check not to be an invalid value of zero (bsc#1223634).
  • CVE-2024-26970: Fixed clk/qcom/gcc-ipq6018 termination of frequency table arrays (bsc#1223644).
  • CVE-2024-26969: Fixed clk/qcom/gcc-ipq8074 termination of frequency table arrays (bsc#1223645).
  • CVE-2024-26966: Fixed clk/qcom/mmcc-apq8084 termination of frequency table arrays (bsc#1223646).
  • CVE-2024-26965: Fixed clk/qcom/mmcc-msm8974 termination of frequency table arrays (bsc#1223648).
  • CVE-2024-26960: Fixed mm/swap race between free_swap_and_cache() and swapoff() (bsc#1223655).
  • CVE-2024-26951: Fixed wireguard/netlink check for dangling peer via is_dead instead of empty list (bsc#1223660).
  • CVE-2024-26950: Fixed wireguard/netlink to access device through ctx instead of peer (bsc#1223661).
  • CVE-2024-26948: Fixed drm/amd/display by adding dc_state NULL check in dc_state_release (bsc#1223664).
  • CVE-2024-26939: Fixed drm/i915/vma UAF on destroy against retire race (bsc#1223679).
  • CVE-2024-26927: Fixed ASoC/SOF bounds checking to firmware data Smatch (bsc#1223525).
  • CVE-2024-26915: Fixed drm/amdgpu reset IH OVERFLOW_CLEAR bit (bsc#1223207).
  • CVE-2024-26901: Fixed do_sys_name_to_handle() to use kzalloc() to prevent kernel-infoleak (bsc#1223198).
  • CVE-2024-26898: Fixed aoe potential use-after-free problem in aoecmd_cfg_pkts (bsc#1223016).
  • CVE-2024-26896: Fixed wifi/wfx memory leak when starting AP (bsc#1223042).
  • CVE-2024-26893: Fixed firmware/arm_scmi for possible double free in SMC transport cleanup path (bsc#1223196).
  • CVE-2024-26885: Fixed bpf DEVMAP_HASH overflow check on 32-bit arches (bsc#1223190).
  • CVE-2024-26884: Fixed bpf hashtab overflow check on 32-bit arches (bsc#1223189).
  • CVE-2024-26883: Fixed bpf stackmap overflow check on 32-bit arches (bsc#1223035).
  • CVE-2024-26882: Fixed net/ip_tunnel to make sure to pull inner header in ip_tunnel_rcv() (bsc#1223034).
  • CVE-2024-26881: Fixed net/hns3 kernel crash when 1588 is received on HIP08 devices (bsc#1223041).
  • CVE-2024-26879: Fixed clk/meson by adding missing clocks to axg_clk_regmaps (bsc#1223066).
  • CVE-2024-26878: Fixed quota for potential NULL pointer dereference (bsc#1223060).
  • CVE-2024-26876: Fixed drm/bridge/adv7511 crash on irq during probe (bsc#1223119).
  • CVE-2024-26866: Fixed spi/spi-fsl-lpspi by removing redundant spi_controller_put call (bsc#1223024).
  • CVE-2024-26862: Fixed packet annotate data-races around ignore_outgoing (bsc#1223111).
  • CVE-2024-26861: Fixed wireguard/receive annotate data-race around receiving_counter.counter (bsc#1223076).
  • CVE-2024-26857: Fixed geneve to make sure to pull inner header in…
Record
SUSE-SU-2024:1644-1
Updated
2026-11-02
OSVSUSE-SU-2024:2008-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-47548: Fixed a possible array out-of=bounds (bsc#1225506)
  • CVE-2022-48689: Fixed data-race in lru_add_fn (bsc#1223959)
  • CVE-2022-48691: Fixed memory leak in netfilter (bsc#1223961)
  • CVE-2023-1829: Fixed a use-after-free vulnerability in the control index filter (tcindex) (bsc#1210335).
  • CVE-2023-42755: Check user supplied offsets (bsc#1215702).
  • CVE-2023-52586: Fixed mutex lock in control vblank irq (bsc#1221081).
  • CVE-2023-52618: Fixed string overflow in block/rnbd-srv (bsc#1221615).
  • CVE-2023-52656: Dropped any code related to SCM_RIGHTS (bsc#1224187).
  • CVE-2023-52660: Fiedx IRQ handling due to shared interrupts (bsc#1224443).
  • CVE-2023-52664: Eliminate double free in error handling logic (bsc#1224747).
  • CVE-2023-52671: Fixed hang/underflow when transitioning to ODM4:1 (bsc#1224729).
  • CVE-2023-52674: Add clamp() in scarlett2_mixer_ctl_put() (bsc#1224727).
  • CVE-2023-52680: Fixed missing error checks to *_ctl_get() (bsc#1224608).
  • CVE-2023-52692: Fixed missing error check to scarlett2_usb_set_config() (bsc#1224628).
  • CVE-2023-52698: Fixed memory leak in netlbl_calipso_add_pass() (CVE-2023-52698 bsc#1224621)
  • CVE-2023-52746: Prevent potential spectre v1 gadget in xfrm_xlate32_attr() (bsc#1225114)
  • CVE-2023-52757: Fixed potential deadlock when releasing mids (bsc#1225548).
  • CVE-2023-52795: Fixed use after free in vhost_vdpa_probe() (bsc#1225085).
  • CVE-2023-52796: Add ipvlan_route_v6_outbound() helper (bsc#1224930).
  • CVE-2023-52807: Fixed out-of-bounds access may occur when coalesce info is read via debugfs (bsc#1225097).
  • CVE-2023-52860: Fixed null pointer dereference in hisi_hns3 (bsc#1224936).
  • CVE-2024-2201: Fixed information leak in x86/BHI (bsc#1217339).
  • CVE-2024-26643: Fixed mark set as dead when unbinding anonymous set with timeout (bsc#1221829).
  • CVE-2024-26679: Fixed read sk->sk_family once in inet_recv_error() (bsc#1222385).
  • CVE-2024-26692: Fixed regression in writes when non-standard maximum write size negotiated (bsc#1222464).
  • CVE-2024-26715: Fixed NULL pointer dereference in dwc3_gadget_suspend (bsc#1222561).
  • CVE-2024-26742: Fixed disable_managed_interrupts (git-fixes bsc#1222608).
  • CVE-2024-26775: Fixed potential deadlock at set_capacity (bsc#1222627).
  • CVE-2024-26791: Fixed properly validate device names in btrfs (bsc#1222793)
  • CVE-2024-26822: Set correct id, uid and cruid for multiuser automounts (bsc#1223011).
  • CVE-2024-26828: Fixed underflow in parse_server_interfaces() (bsc#1223084).
  • CVE-2024-26876: Fixed crash on irq during probe (bsc#1223119).
  • CVE-2024-26900: Fixed kmemleak of rdev->serial (bsc#1223046).
  • CVE-2024-26915: Reset IH OVERFLOW_CLEAR bit (bsc#1223207)
  • CVE-2024-26919: Fixed debugfs directory leak (bsc#1223847).
  • CVE-2024-26921: Preserve kabi for sk_buff (bsc#1223138).
  • CVE-2024-26925: Release mutex after nft_gc_seq_end from abort path (bsc#1223390).
  • CVE-2024-26928: Fixed potential UAF in cifs_debug_files_proc_show() (bsc#1223532).
  • CVE-2024-26939: Fixed UAF on destroy against retire race (bsc#1223679).
  • CVE-2024-26958: Fixed UAF in direct writes (bsc#1223653).
  • CVE-2024-27042: Fixed potential out-of-bounds access in 'amdgpu_discovery_reg_base_init()' (bsc#1223823).
  • CVE-2024-27395: Fixed Use-After-Free in ovs_ct_exit (bsc#1224098).
  • CVE-2024-27396: Fixed Use-After-Free in gtp_dellink (bsc#1224096).
  • CVE-2024-27398: Fixed use-after-free bugs caused by sco_sock_timeout (bsc#1224174).
  • CVE-2024-27401: Fixed user_length taken into account when fetching packet contents (bsc#1224181).
  • CVE-2024-27417: Fixed potential 'struct net' leak in inet6_rtm_getaddr() (bsc#1224721)
  • CVE-2024-27419: Fixed data-races around sysctl_net_busy_read (bsc#1224759)
  • CVE-2024-27431: Fixed Zero-initialise xdp_rxq_info struct before running XDP program (bsc#1224718).
  • CVE-2024-35791: Flush pages under…
Record
SUSE-SU-2024:2008-1
Updated
2026-11-02
OSVSUSE-SU-2024:2190-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-47548: Fixed a possible array out-of=bounds (bsc#1225506)
  • CVE-2022-48689: Fixed data-race in lru_add_fn (bsc#1223959)
  • CVE-2022-48691: Fixed memory leak in netfilter (bsc#1223961)
  • CVE-2023-1829: Fixed a use-after-free vulnerability in the control index filter (tcindex) (bsc#1210335).
  • CVE-2023-42755: Check user supplied offsets (bsc#1215702).
  • CVE-2023-52586: Fixed mutex lock in control vblank irq (bsc#1221081).
  • CVE-2023-52618: Fixed string overflow in block/rnbd-srv (bsc#1221615).
  • CVE-2023-52655: Check packet for fixup for true limit (bsc#1217169).
  • CVE-2023-52656: Dropped any code related to SCM_RIGHTS (bsc#1224187).
  • CVE-2023-52660: Fiedx IRQ handling due to shared interrupts (bsc#1224443).
  • CVE-2023-52664: Eliminate double free in error handling logic (bsc#1224747).
  • CVE-2023-52671: Fixed hang/underflow when transitioning to ODM4:1 (bsc#1224729).
  • CVE-2023-52674: Add clamp() in scarlett2_mixer_ctl_put() (bsc#1224727).
  • CVE-2023-52680: Fixed missing error checks to *_ctl_get() (bsc#1224608).
  • CVE-2023-52692: Fixed missing error check to scarlett2_usb_set_config() (bsc#1224628).
  • CVE-2023-52698: Fixed memory leak in netlbl_calipso_add_pass() (bsc#1224621)
  • CVE-2023-52746: Prevent potential spectre v1 gadget in xfrm_xlate32_attr() (bsc#1225114)
  • CVE-2023-52757: Fixed potential deadlock when releasing mids (bsc#1225548).
  • CVE-2023-52795: Fixed use after free in vhost_vdpa_probe() (bsc#1225085).
  • CVE-2023-52796: Add ipvlan_route_v6_outbound() helper (bsc#1224930).
  • CVE-2023-52807: Fixed out-of-bounds access may occur when coalesce info is read via debugfs (bsc#1225097).
  • CVE-2023-52860: Fixed null pointer dereference in hisi_hns3 (bsc#1224936).
  • CVE-2023-6531: Fixed a use-after-free flaw due to a race problem in the unix garbage collector's deletion of SKB races with unix_stream_read_generic()on the socket that the SKB is queued on (bsc#1218447).
  • CVE-2024-2201: Fixed information leak in x86/BHI (bsc#1217339).
  • CVE-2024-26643: Fixed mark set as dead when unbinding anonymous set with timeout (bsc#1221829).
  • CVE-2024-26679: Fixed read sk->sk_family once in inet_recv_error() (bsc#1222385).
  • CVE-2024-26692: Fixed regression in writes when non-standard maximum write size negotiated (bsc#1222464).
  • CVE-2024-26700: Fixed drm/amd/display: Fix MST Null Ptr for RV (bsc#1222870)
  • CVE-2024-26715: Fixed NULL pointer dereference in dwc3_gadget_suspend (bsc#1222561).
  • CVE-2024-26742: Fixed disable_managed_interrupts (git-fixes bsc#1222608).
  • CVE-2024-26775: Fixed potential deadlock at set_capacity (bsc#1222627).
  • CVE-2024-26777: Error out if pixclock equals zero in fbdev/sis (bsc#1222765)
  • CVE-2024-26778: Error out if pixclock equals zero in fbdev/savage (bsc#1222770)
  • CVE-2024-26791: Fixed properly validate device names in btrfs (bsc#1222793)
  • CVE-2024-26822: Set correct id, uid and cruid for multiuser automounts (bsc#1223011).
  • CVE-2024-26828: Fixed underflow in parse_server_interfaces() (bsc#1223084).
  • CVE-2024-26839: Fixed a memleak in init_credit_return() (bsc#1222975)
  • CVE-2024-26876: Fixed crash on irq during probe (bsc#1223119).
  • CVE-2024-26900: Fixed kmemleak of rdev->serial (bsc#1223046).
  • CVE-2024-26907: Fixed a fortify source warning while accessing Eth segment in mlx5 (bsc#1223203).
  • CVE-2024-26915: Reset IH OVERFLOW_CLEAR bit (bsc#1223207)
  • CVE-2024-26919: Fixed debugfs directory leak (bsc#1223847).
  • CVE-2024-26921: Preserve kabi for sk_buff (bsc#1223138).
  • CVE-2024-26925: Release mutex after nft_gc_seq_end from abort path (bsc#1223390).
  • CVE-2024-26928: Fixed potential UAF in cifs_debug_files_proc_show() (bsc#1223532).
  • CVE-2024-26939: Fixed UAF on destroy against retire race (bsc#1223679).
  • CVE-2024-26958: Fixed UAF in direct writes (bsc#1223653).
  • CVE-2024-27042: Fixed potential out-of-bounds access in…
Record
SUSE-SU-2024:2190-1
Updated
2026-11-02
OSVSUSE-SU-2025:20008-1 No score

Security update for the Linux Kernel

The SUSE Linux Enterprise Micro 6.0 kernel was updated to receive various security bugfixes.

The following security bugs were fixed:

  • CVE-2024-41014: xfs: add bounds checking to xlog_recover_process_data (bsc#1228408).
  • CVE-2024-41013: xfs: do not walk off the end of a directory data block (bsc#1228405).
  • CVE-2024-41017: jfs: do not walk off the end of ealist (bsc#1228403).
  • CVE-2024-40972: ext4: fold quota accounting into ext4_xattr_inode_lookup_create() (bsc#1227910).
  • CVE-2024-39276: ext4: fix mb_cache_entry's e_refcnt leak in ext4_xattr_block_cache_find() (bsc#1226993).
  • CVE-2024-40925: block: fix request.queuelist usage in flush (bsc#1227789).
  • CVE-2024-40998: ext4: fix uninitialized ratelimit_state->lock access in __ext4_fill_super() (bsc#1227866).
  • CVE-2024-39494: ima: Fix use-after-free on a dentry's dname.name (bsc#1227716).
  • CVE-2024-39496: btrfs: zoned: fix use-after-free due to race with dev replace (bsc#1227719).
  • CVE-2024-41091: tun: add missing verification for short frame (bsc#1228327).
  • CVE-2024-41090: tap: add missing verification for short frame (bsc#1228328).
  • CVE-2024-40999: net: ena: Add validation for completion descriptors consistency (bsc#1227913).
  • CVE-2024-40966: kABI: tty: add the option to have a tty reject a new ldisc (bsc#1227886).
  • CVE-2024-40975: platform/x86: x86-android-tablets: Unregister devices in reverse order (bsc#1227926).
  • CVE-2024-40970: Avoid hw_desc array overrun in dw-axi-dmac (bsc#1227899).
  • CVE-2024-40947: ima: Avoid blocking in RCU read-side critical section (bsc#1227803).
  • CVE-2024-40908: bpf: Set run context for rawtp test_run callback (bsc#1227783).
  • CVE-2024-40960: ipv6: prevent possible NULL dereference in rt6_probe() (bsc#1227813).
  • CVE-2024-40935: cachefiles: flush all requests after setting CACHEFILES_DEAD (bsc#1227797).
  • CVE-2024-40961: ipv6: prevent possible NULL deref in fib6_nh_init() (bsc#1227814).
  • CVE-2024-39504: netfilter: nft_inner: validate mandatory meta and payload (bsc#1227757).
  • CVE-2024-41006: netrom: Fix a memory leak in nr_heartbeat_expiry() (bsc#1227862).
  • CVE-2024-40937: gve: Clear napi->skb before dev_kfree_skb_any() (bsc#1227836).
  • CVE-2024-39507: net: hns3: fix kernel crash problem in concurrent scenario (bsc#1227730).
  • CVE-2024-40940: net/mlx5: Fix tainted pointer delete is case of flow rules creation fail (bsc#1227800).
  • CVE-2024-40928: net: ethtool: fix the error condition in ethtool_get_phy_stats_ethtool() (bsc#1227788).
  • CVE-2024-26944: btrfs: zoned: fix lock ordering in btrfs_zone_activate() (bsc#1223731).
  • CVE-2024-40923: vmxnet3: disable rx data ring on dma allocation failure (bsc#1227786).
  • CVE-2024-40931: mptcp: ensure snd_una is properly initialized on connect (bsc#1227780).
  • CVE-2024-40919: bnxt_en: Adjust logging of firmware messages in case of released token in __hwrm_send() (bsc#1227779).
  • CVE-2024-39487: bonding: Fix out-of-bounds read in bond_option_arp_ip_targets_set() (bsc#1227573)
  • CVE-2024-35908: tls: get psock ref after taking rxlock to avoid leak (bsc#1224490)
  • CVE-2024-35899: netfilter: nf_tables: flush pending destroy work before exit_net release (bsc#1224499)
  • CVE-2024-35934: net/smc: reduce rtnl pressure in smc_pnet_create_pnetids_list() (bsc#1224641)
  • CVE-2024-35893: net/sched: act_skbmod: prevent kernel-infoleak (bsc#1224512)
  • CVE-2024-40901: scsi: mpt3sas: Avoid test/set_bit() operating in non-allocated memory (bsc#1227762).
  • CVE-2024-39472: xfs: fix log recovery buffer allocation for the legacy h_size fixup (bsc#1227432).
  • CVE-2024-40953: KVM: Fix a data race on last_boosted_vcpu in kvm_vcpu_on_spin() (bsc#1227806).
  • CVE-2024-27404: mptcp: fix data races on remote_id (bsc#1224422)
  • CVE-2024-27020: netfilter: nf_tables: Fix potential data-race in __nft_expr_type_get() (bsc#1223815)
  • CVE-2024-27019: netfilter: nf_tables: Fix potential data-race in __nft_obj_type_get() (bsc#1223813)
  • CVE-2024-40948: mm/page_table_check: fix crash on ZONE_DEVICE (bsc#1227801).
  • CVE-2024-35890:…
Record
SUSE-SU-2025:20008-1
Updated
2026-11-02
OSVSUSE-SU-2025:20028-1 No score

Security update for the Linux Kernel

The SUSE Linux Enterprise Micro 6.0 RT kernel was updated to receive various security bugfixes.

The following security bugs were fixed:

  • CVE-2024-41014: xfs: add bounds checking to xlog_recover_process_data (bsc#1228408).
  • CVE-2024-41013: xfs: do not walk off the end of a directory data block (bsc#1228405).
  • CVE-2024-41017: jfs: do not walk off the end of ealist (bsc#1228403).
  • CVE-2024-40972: ext4: fold quota accounting into ext4_xattr_inode_lookup_create() (bsc#1227910).
  • CVE-2024-39276: ext4: fix mb_cache_entry's e_refcnt leak in ext4_xattr_block_cache_find() (bsc#1226993).
  • CVE-2024-40925: block: fix request.queuelist usage in flush (bsc#1227789).
  • CVE-2024-40998: ext4: fix uninitialized ratelimit_state->lock access in __ext4_fill_super() (bsc#1227866).
  • CVE-2024-41011: drm/amdkfd: do not allow mapping the MMIO HDP page with large pages (bsc#1228114).
  • CVE-2024-39494: ima: Fix use-after-free on a dentry's dname.name (bsc#1227716).
  • CVE-2024-39496: btrfs: zoned: fix use-after-free due to race with dev replace (bsc#1227719).
  • CVE-2024-41091: tun: add missing verification for short frame (bsc#1228327).
  • CVE-2024-41090: tap: add missing verification for short frame (bsc#1228328).
  • CVE-2024-40999: net: ena: Add validation for completion descriptors consistency (bsc#1227913).
  • CVE-2024-40966: kABI: tty: add the option to have a tty reject a new ldisc (bsc#1227886).
  • CVE-2024-40975: platform/x86: x86-android-tablets: Unregister devices in reverse order (bsc#1227926).
  • CVE-2024-40970: Avoid hw_desc array overrun in dw-axi-dmac (bsc#1227899).
  • CVE-2024-40947: ima: Avoid blocking in RCU read-side critical section (bsc#1227803).
  • CVE-2024-40908: bpf: Set run context for rawtp test_run callback (bsc#1227783).
  • CVE-2024-40960: ipv6: prevent possible NULL dereference in rt6_probe() (bsc#1227813).
  • CVE-2024-40935: cachefiles: flush all requests after setting CACHEFILES_DEAD (bsc#1227797).
  • CVE-2024-40961: ipv6: prevent possible NULL deref in fib6_nh_init() (bsc#1227814).
  • CVE-2024-39504: netfilter: nft_inner: validate mandatory meta and payload (bsc#1227757).
  • CVE-2024-41006: netrom: Fix a memory leak in nr_heartbeat_expiry() (bsc#1227862).
  • CVE-2024-40937: gve: Clear napi->skb before dev_kfree_skb_any() (bsc#1227836).
  • CVE-2024-39507: net: hns3: fix kernel crash problem in concurrent scenario (bsc#1227730).
  • CVE-2024-40940: net/mlx5: Fix tainted pointer delete is case of flow rules creation fail (bsc#1227800).
  • CVE-2024-40928: net: ethtool: fix the error condition in ethtool_get_phy_stats_ethtool() (bsc#1227788).
  • CVE-2024-26944: btrfs: zoned: fix lock ordering in btrfs_zone_activate() (bsc#1223731).
  • CVE-2024-40923: vmxnet3: disable rx data ring on dma allocation failure (bsc#1227786).
  • CVE-2024-40931: mptcp: ensure snd_una is properly initialized on connect (bsc#1227780).
  • CVE-2024-40919: bnxt_en: Adjust logging of firmware messages in case of released token in __hwrm_send() (bsc#1227779).
  • CVE-2024-39487: bonding: Fix out-of-bounds read in bond_option_arp_ip_targets_set() (bsc#1227573)
  • CVE-2024-35908: tls: get psock ref after taking rxlock to avoid leak (bsc#1224490)
  • CVE-2024-35899: netfilter: nf_tables: flush pending destroy work before exit_net release (bsc#1224499)
  • CVE-2024-35934: net/smc: reduce rtnl pressure in smc_pnet_create_pnetids_list() (bsc#1224641)
  • CVE-2024-35893: net/sched: act_skbmod: prevent kernel-infoleak (bsc#1224512)
  • CVE-2024-40901: scsi: mpt3sas: Avoid test/set_bit() operating in non-allocated memory (bsc#1227762).
  • CVE-2024-39472: xfs: fix log recovery buffer allocation for the legacy h_size fixup (bsc#1227432).
  • CVE-2024-40953: KVM: Fix a data race on last_boosted_vcpu in kvm_vcpu_on_spin() (bsc#1227806).
  • CVE-2024-27404: mptcp: fix data races on remote_id (bsc#1224422)
  • CVE-2024-27020: netfilter: nf_tables: Fix potential data-race in __nft_expr_type_get() (bsc#1223815)
  • CVE-2024-27019: netfilter: nf_tables: Fix potential data-race in __nft_obj_type_get()…
Record
SUSE-SU-2025:20028-1
Updated
2026-11-02
OSVUSN-6816-1 No score

linux, linux-ibm, linux-lowlatency, linux-raspi vulnerabilities

Ziming Zhang discovered that the DRM driver for VMware Virtual GPU did not properly handle certain error conditions, leading to a NULL pointer dereference. A local attacker could possibly trigger this vulnerability to cause a denial of service. (CVE-2022-38096)

Zheng Wang discovered that the Broadcom FullMAC WLAN driver in the Linux kernel contained a race condition during device removal, leading to a use- after-free vulnerability. A physically proximate attacker could possibly use this to cause a denial of service (system crash). (CVE-2023-47233)

It was discovered that the ATA over Ethernet (AoE) driver in the Linux kernel contained a race condition, leading to a use-after-free vulnerability. An attacker could use this to cause a denial of service or possibly execute arbitrary code. (CVE-2023-6270)

It was discovered that the Atheros 802.11ac wireless driver did not properly validate certain data structures, leading to a NULL pointer dereference. An attacker could possibly use this to cause a denial of service. (CVE-2023-7042)

It was discovered that the Intel Data Streaming and Intel Analytics Accelerator drivers in the Linux kernel allowed direct access to the devices for unprivileged users and virtual machines. A local attacker could use this to cause a denial of service. (CVE-2024-21823)

Gui-Dong Han discovered that the software RAID driver in the Linux kernel contained a race condition, leading to an integer overflow vulnerability. A privileged attacker could possibly use this to cause a denial of service (system crash). (CVE-2024-23307)

Bai Jiaju discovered that the Xceive XC4000 silicon tuner device driver in the Linux kernel contained a race condition, leading to an integer overflow vulnerability. An attacker could possibly use this to cause a denial of service (system crash). (CVE-2024-24861)

Chenyuan Yang discovered that the Unsorted Block Images (UBI) flash device volume management subsystem did not properly validate logical eraseblock sizes in certain situations. An attacker could possibly use this to cause a denial of service (system crash). (CVE-2024-25739)

It was discovered that the MediaTek SoC Gigabit Ethernet driver in the Linux kernel contained a race condition when stopping the device. A local attacker could possibly use this to cause a denial of service (device unavailability). (CVE-2024-27432)

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

  • ARM32 architecture;
  • PowerPC architecture;
  • x86 architecture;
  • Block layer subsystem;
  • ACPI drivers;
  • Bluetooth drivers;
  • Clock framework and drivers;
  • CPU frequency scaling framework;
  • Cryptographic API;
  • DPLL subsystem;
  • ARM SCMI message protocol;
  • EFI core;
  • GPU drivers;
  • InfiniBand drivers;
  • IOMMU subsystem;
  • LED subsystem;
  • Multiple devices driver;
  • Media drivers;
  • MMC subsystem;
  • Network drivers;
  • NTB driver;
  • NVME drivers;
  • PCI subsystem;
  • Powercap sysfs driver;
  • SCSI drivers;
  • Freescale SoC drivers;
  • SPI subsystem;
  • Media staging drivers;
  • Thermal drivers;
  • TTY drivers;
  • USB subsystem;
  • DesignWare USB3 driver;
  • VFIO drivers;
  • Backlight driver;
  • Virtio drivers;
  • Xen hypervisor drivers;
  • AFS file system;
  • File systems infrastructure;
  • BTRFS file system;
  • debug file system;
  • Ext4 file system;
  • F2FS file system;
  • FAT file system;
  • Network file system client;
  • NILFS2 file system;
  • Overlay file system;
  • Pstore file system;
  • Diskquota system;
  • SMB network file system;
  • UBI file system;
  • io_uring subsystem;
  • BPF subsystem;
  • Core kernel;
  • Memory management;
  • Bluetooth subsystem;
  • Networking core;
  • HSR network protocol;
  • IPv4 networking;
  • IPv6 networking;
  • MAC80211 subsystem;
  • IEEE 802.15.4 subsystem;
  • Netfilter;
  • Packet sockets;
  • Network…
Record
USN-6816-1
Updated
2026-11-02
OSVUSN-6817-1 No score

linux-aws, linux-gcp vulnerabilities

Ziming Zhang discovered that the DRM driver for VMware Virtual GPU did not properly handle certain error conditions, leading to a NULL pointer dereference. A local attacker could possibly trigger this vulnerability to cause a denial of service. (CVE-2022-38096)

Zheng Wang discovered that the Broadcom FullMAC WLAN driver in the Linux kernel contained a race condition during device removal, leading to a use- after-free vulnerability. A physically proximate attacker could possibly use this to cause a denial of service (system crash). (CVE-2023-47233)

It was discovered that the ATA over Ethernet (AoE) driver in the Linux kernel contained a race condition, leading to a use-after-free vulnerability. An attacker could use this to cause a denial of service or possibly execute arbitrary code. (CVE-2023-6270)

It was discovered that the Atheros 802.11ac wireless driver did not properly validate certain data structures, leading to a NULL pointer dereference. An attacker could possibly use this to cause a denial of service. (CVE-2023-7042)

Gui-Dong Han discovered that the software RAID driver in the Linux kernel contained a race condition, leading to an integer overflow vulnerability. A privileged attacker could possibly use this to cause a denial of service (system crash). (CVE-2024-23307)

Bai Jiaju discovered that the Xceive XC4000 silicon tuner device driver in the Linux kernel contained a race condition, leading to an integer overflow vulnerability. An attacker could possibly use this to cause a denial of service (system crash). (CVE-2024-24861)

Chenyuan Yang discovered that the Unsorted Block Images (UBI) flash device volume management subsystem did not properly validate logical eraseblock sizes in certain situations. An attacker could possibly use this to cause a denial of service (system crash). (CVE-2024-25739)

It was discovered that the MediaTek SoC Gigabit Ethernet driver in the Linux kernel contained a race condition when stopping the device. A local attacker could possibly use this to cause a denial of service (device unavailability). (CVE-2024-27432)

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

  • ARM32 architecture;
  • PowerPC architecture;
  • x86 architecture;
  • Block layer subsystem;
  • ACPI drivers;
  • Bluetooth drivers;
  • Clock framework and drivers;
  • CPU frequency scaling framework;
  • Cryptographic API;
  • DPLL subsystem;
  • ARM SCMI message protocol;
  • EFI core;
  • GPU drivers;
  • InfiniBand drivers;
  • IOMMU subsystem;
  • LED subsystem;
  • Multiple devices driver;
  • Media drivers;
  • MMC subsystem;
  • Network drivers;
  • NTB driver;
  • NVME drivers;
  • PCI subsystem;
  • Powercap sysfs driver;
  • SCSI drivers;
  • Freescale SoC drivers;
  • SPI subsystem;
  • Media staging drivers;
  • Thermal drivers;
  • TTY drivers;
  • USB subsystem;
  • DesignWare USB3 driver;
  • VFIO drivers;
  • Backlight driver;
  • Virtio drivers;
  • Xen hypervisor drivers;
  • AFS file system;
  • File systems infrastructure;
  • BTRFS file system;
  • debug file system;
  • Ext4 file system;
  • F2FS file system;
  • FAT file system;
  • Network file system client;
  • NILFS2 file system;
  • Overlay file system;
  • Pstore file system;
  • Diskquota system;
  • SMB network file system;
  • UBI file system;
  • io_uring subsystem;
  • BPF subsystem;
  • Core kernel;
  • Memory management;
  • Bluetooth subsystem;
  • Networking core;
  • HSR network protocol;
  • IPv4 networking;
  • IPv6 networking;
  • MAC80211 subsystem;
  • IEEE 802.15.4 subsystem;
  • Netfilter;
  • Packet sockets;
  • Network traffic control;
  • Sun RPC protocol;
  • ALSA SH drivers;
  • SOF drivers;
  • USB sound devices;
  • KVM core; (CVE-2024-26859, CVE-2024-26944, CVE-2024-27049, CVE-2024-26868, CVE-2024-26932, CVE-2024-35843, CVE-2024-35814, CVE-2024-26866, CVE-2024-26941, CVE-2024-27080,…
Record
USN-6817-1
Updated
2026-11-02
OSVUSN-6817-2 No score

linux-oem-6.8 vulnerabilities

Ziming Zhang discovered that the DRM driver for VMware Virtual GPU did not properly handle certain error conditions, leading to a NULL pointer dereference. A local attacker could possibly trigger this vulnerability to cause a denial of service. (CVE-2022-38096)

Zheng Wang discovered that the Broadcom FullMAC WLAN driver in the Linux kernel contained a race condition during device removal, leading to a use- after-free vulnerability. A physically proximate attacker could possibly use this to cause a denial of service (system crash). (CVE-2023-47233)

It was discovered that the ATA over Ethernet (AoE) driver in the Linux kernel contained a race condition, leading to a use-after-free vulnerability. An attacker could use this to cause a denial of service or possibly execute arbitrary code. (CVE-2023-6270)

It was discovered that the Atheros 802.11ac wireless driver did not properly validate certain data structures, leading to a NULL pointer dereference. An attacker could possibly use this to cause a denial of service. (CVE-2023-7042)

Gui-Dong Han discovered that the software RAID driver in the Linux kernel contained a race condition, leading to an integer overflow vulnerability. A privileged attacker could possibly use this to cause a denial of service (system crash). (CVE-2024-23307)

Bai Jiaju discovered that the Xceive XC4000 silicon tuner device driver in the Linux kernel contained a race condition, leading to an integer overflow vulnerability. An attacker could possibly use this to cause a denial of service (system crash). (CVE-2024-24861)

Chenyuan Yang discovered that the Unsorted Block Images (UBI) flash device volume management subsystem did not properly validate logical eraseblock sizes in certain situations. An attacker could possibly use this to cause a denial of service (system crash). (CVE-2024-25739)

It was discovered that the MediaTek SoC Gigabit Ethernet driver in the Linux kernel contained a race condition when stopping the device. A local attacker could possibly use this to cause a denial of service (device unavailability). (CVE-2024-27432)

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

  • ARM32 architecture;
  • PowerPC architecture;
  • x86 architecture;
  • Block layer subsystem;
  • ACPI drivers;
  • Bluetooth drivers;
  • Clock framework and drivers;
  • CPU frequency scaling framework;
  • Cryptographic API;
  • DPLL subsystem;
  • ARM SCMI message protocol;
  • EFI core;
  • GPU drivers;
  • InfiniBand drivers;
  • IOMMU subsystem;
  • LED subsystem;
  • Multiple devices driver;
  • Media drivers;
  • MMC subsystem;
  • Network drivers;
  • NTB driver;
  • NVME drivers;
  • PCI subsystem;
  • Powercap sysfs driver;
  • SCSI drivers;
  • Freescale SoC drivers;
  • SPI subsystem;
  • Media staging drivers;
  • Thermal drivers;
  • TTY drivers;
  • USB subsystem;
  • DesignWare USB3 driver;
  • VFIO drivers;
  • Backlight driver;
  • Virtio drivers;
  • Xen hypervisor drivers;
  • AFS file system;
  • File systems infrastructure;
  • BTRFS file system;
  • debug file system;
  • Ext4 file system;
  • F2FS file system;
  • FAT file system;
  • Network file system client;
  • NILFS2 file system;
  • Overlay file system;
  • Pstore file system;
  • Diskquota system;
  • SMB network file system;
  • UBI file system;
  • io_uring subsystem;
  • BPF subsystem;
  • Core kernel;
  • Memory management;
  • Bluetooth subsystem;
  • Networking core;
  • HSR network protocol;
  • IPv4 networking;
  • IPv6 networking;
  • MAC80211 subsystem;
  • IEEE 802.15.4 subsystem;
  • Netfilter;
  • Packet sockets;
  • Network traffic control;
  • Sun RPC protocol;
  • ALSA SH drivers;
  • SOF drivers;
  • USB sound devices;
  • KVM core; (CVE-2024-26859, CVE-2024-26944, CVE-2024-27049, CVE-2024-26868, CVE-2024-26932, CVE-2024-35843, CVE-2024-35814, CVE-2024-26866, CVE-2024-26941, CVE-2024-27080,…
Record
USN-6817-2
Updated
2026-11-02
OSVUSN-6817-3 No score

linux-azure, linux-gke vulnerabilities

Ziming Zhang discovered that the DRM driver for VMware Virtual GPU did not properly handle certain error conditions, leading to a NULL pointer dereference. A local attacker could possibly trigger this vulnerability to cause a denial of service. (CVE-2022-38096)

Zheng Wang discovered that the Broadcom FullMAC WLAN driver in the Linux kernel contained a race condition during device removal, leading to a use- after-free vulnerability. A physically proximate attacker could possibly use this to cause a denial of service (system crash). (CVE-2023-47233)

It was discovered that the ATA over Ethernet (AoE) driver in the Linux kernel contained a race condition, leading to a use-after-free vulnerability. An attacker could use this to cause a denial of service or possibly execute arbitrary code. (CVE-2023-6270)

It was discovered that the Atheros 802.11ac wireless driver did not properly validate certain data structures, leading to a NULL pointer dereference. An attacker could possibly use this to cause a denial of service. (CVE-2023-7042)

Gui-Dong Han discovered that the software RAID driver in the Linux kernel contained a race condition, leading to an integer overflow vulnerability. A privileged attacker could possibly use this to cause a denial of service (system crash). (CVE-2024-23307)

Bai Jiaju discovered that the Xceive XC4000 silicon tuner device driver in the Linux kernel contained a race condition, leading to an integer overflow vulnerability. An attacker could possibly use this to cause a denial of service (system crash). (CVE-2024-24861)

Chenyuan Yang discovered that the Unsorted Block Images (UBI) flash device volume management subsystem did not properly validate logical eraseblock sizes in certain situations. An attacker could possibly use this to cause a denial of service (system crash). (CVE-2024-25739)

It was discovered that the MediaTek SoC Gigabit Ethernet driver in the Linux kernel contained a race condition when stopping the device. A local attacker could possibly use this to cause a denial of service (device unavailability). (CVE-2024-27432)

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

  • ARM32 architecture;
  • PowerPC architecture;
  • x86 architecture;
  • Block layer subsystem;
  • ACPI drivers;
  • Bluetooth drivers;
  • Clock framework and drivers;
  • CPU frequency scaling framework;
  • Cryptographic API;
  • DPLL subsystem;
  • ARM SCMI message protocol;
  • EFI core;
  • GPU drivers;
  • InfiniBand drivers;
  • IOMMU subsystem;
  • LED subsystem;
  • Multiple devices driver;
  • Media drivers;
  • MMC subsystem;
  • Network drivers;
  • NTB driver;
  • NVME drivers;
  • PCI subsystem;
  • Powercap sysfs driver;
  • SCSI drivers;
  • Freescale SoC drivers;
  • SPI subsystem;
  • Media staging drivers;
  • Thermal drivers;
  • TTY drivers;
  • USB subsystem;
  • DesignWare USB3 driver;
  • VFIO drivers;
  • Backlight driver;
  • Virtio drivers;
  • Xen hypervisor drivers;
  • AFS file system;
  • File systems infrastructure;
  • BTRFS file system;
  • debug file system;
  • Ext4 file system;
  • F2FS file system;
  • FAT file system;
  • Network file system client;
  • NILFS2 file system;
  • Overlay file system;
  • Pstore file system;
  • Diskquota system;
  • SMB network file system;
  • UBI file system;
  • io_uring subsystem;
  • BPF subsystem;
  • Core kernel;
  • Memory management;
  • Bluetooth subsystem;
  • Networking core;
  • HSR network protocol;
  • IPv4 networking;
  • IPv6 networking;
  • MAC80211 subsystem;
  • IEEE 802.15.4 subsystem;
  • Netfilter;
  • Packet sockets;
  • Network traffic control;
  • Sun RPC protocol;
  • ALSA SH drivers;
  • SOF drivers;
  • USB sound devices;
  • KVM core; (CVE-2024-26859, CVE-2024-26944, CVE-2024-27049, CVE-2024-26868, CVE-2024-26932, CVE-2024-35843, CVE-2024-35814, CVE-2024-26866, CVE-2024-26941, CVE-2024-27080,…
Record
USN-6817-3
Updated
2026-11-02
OSVUSN-6878-1 No score

linux-oracle vulnerabilities

Ziming Zhang discovered that the DRM driver for VMware Virtual GPU did not properly handle certain error conditions, leading to a NULL pointer dereference. A local attacker could possibly trigger this vulnerability to cause a denial of service. (CVE-2022-38096)

Zheng Wang discovered that the Broadcom FullMAC WLAN driver in the Linux kernel contained a race condition during device removal, leading to a use- after-free vulnerability. A physically proximate attacker could possibly use this to cause a denial of service (system crash). (CVE-2023-47233)

It was discovered that the ATA over Ethernet (AoE) driver in the Linux kernel contained a race condition, leading to a use-after-free vulnerability. An attacker could use this to cause a denial of service or possibly execute arbitrary code. (CVE-2023-6270)

It was discovered that the Atheros 802.11ac wireless driver did not properly validate certain data structures, leading to a NULL pointer dereference. An attacker could possibly use this to cause a denial of service. (CVE-2023-7042)

It was discovered that the Intel Data Streaming and Intel Analytics Accelerator drivers in the Linux kernel allowed direct access to the devices for unprivileged users and virtual machines. A local attacker could use this to cause a denial of service. (CVE-2024-21823)

Gui-Dong Han discovered that the software RAID driver in the Linux kernel contained a race condition, leading to an integer overflow vulnerability. A privileged attacker could possibly use this to cause a denial of service (system crash). (CVE-2024-23307)

Bai Jiaju discovered that the Xceive XC4000 silicon tuner device driver in the Linux kernel contained a race condition, leading to an integer overflow vulnerability. An attacker could possibly use this to cause a denial of service (system crash). (CVE-2024-24861)

Chenyuan Yang discovered that the Unsorted Block Images (UBI) flash device volume management subsystem did not properly validate logical eraseblock sizes in certain situations. An attacker could possibly use this to cause a denial of service (system crash). (CVE-2024-25739)

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

  • ARM32 architecture;
  • PowerPC architecture;
  • x86 architecture;
  • Block layer subsystem;
  • ACPI drivers;
  • Bluetooth drivers;
  • Clock framework and drivers;
  • CPU frequency scaling framework;
  • Cryptographic API;
  • DPLL subsystem;
  • ARM SCMI message protocol;
  • EFI core;
  • GPU drivers;
  • InfiniBand drivers;
  • IOMMU subsystem;
  • LED subsystem;
  • Multiple devices driver;
  • Media drivers;
  • MMC subsystem;
  • Network drivers;
  • NTB driver;
  • NVME drivers;
  • PCI subsystem;
  • Powercap sysfs driver;
  • SCSI drivers;
  • Freescale SoC drivers;
  • SPI subsystem;
  • Media staging drivers;
  • Thermal drivers;
  • TTY drivers;
  • USB subsystem;
  • DesignWare USB3 driver;
  • VFIO drivers;
  • Backlight driver;
  • Virtio drivers;
  • Xen hypervisor drivers;
  • File systems infrastructure;
  • BTRFS file system;
  • debug file system;
  • Ext4 file system;
  • F2FS file system;
  • FAT file system;
  • Network file system client;
  • NILFS2 file system;
  • Overlay file system;
  • Pstore file system;
  • Diskquota system;
  • SMB network file system;
  • UBI file system;
  • io_uring subsystem;
  • BPF subsystem;
  • Core kernel;
  • PCI iomap interfaces;
  • Memory management;
  • Bluetooth subsystem;
  • Networking core;
  • HSR network protocol;
  • IPv4 networking;
  • IPv6 networking;
  • MAC80211 subsystem;
  • IEEE 802.15.4 subsystem;
  • Netfilter;
  • Packet sockets;
  • Network traffic control;
  • Sun RPC protocol;
  • ALSA SH drivers;
  • SOF drivers;
  • USB sound devices;
  • KVM core; (CVE-2024-27032, CVE-2024-26868, CVE-2024-26879, CVE-2024-27033, CVE-2024-26943, CVE-2024-27040, CVE-2024-26950, CVE-2023-52650,…
Record
USN-6878-1
Updated
2026-11-02

Affected products

Affected packages

Affected packages
PackageAffectedFixed
bpftool
AlmaLinux:8
From an advisory covering 145 CVEs
 before 4.18.0-553.22.1.el8_10
4.18.0-553.22.1.el8_10
kernel
AlmaLinux:8
From an advisory covering 145 CVEs
 before 4.18.0-553.22.1.el8_10
4.18.0-553.22.1.el8_10
kernel-abi-stablelists
AlmaLinux:8
From an advisory covering 145 CVEs
 before 4.18.0-553.22.1.el8_10
4.18.0-553.22.1.el8_10
kernel-core
AlmaLinux:8
From an advisory covering 145 CVEs
 before 4.18.0-553.22.1.el8_10
4.18.0-553.22.1.el8_10
kernel-cross-headers
AlmaLinux:8
From an advisory covering 145 CVEs
 before 4.18.0-553.22.1.el8_10
4.18.0-553.22.1.el8_10
kernel-debug
AlmaLinux:8
From an advisory covering 145 CVEs
 before 4.18.0-553.22.1.el8_10
4.18.0-553.22.1.el8_10
kernel-debug-core
AlmaLinux:8
From an advisory covering 145 CVEs
 before 4.18.0-553.22.1.el8_10
4.18.0-553.22.1.el8_10
kernel-debug-devel
AlmaLinux:8
From an advisory covering 145 CVEs
 before 4.18.0-553.22.1.el8_10
4.18.0-553.22.1.el8_10
kernel-debug-modules
AlmaLinux:8
From an advisory covering 145 CVEs
 before 4.18.0-553.22.1.el8_10
4.18.0-553.22.1.el8_10
kernel-debug-modules-extra
AlmaLinux:8
From an advisory covering 145 CVEs
 before 4.18.0-553.22.1.el8_10
4.18.0-553.22.1.el8_10
Show 290 moreShow less
Affected packages
PackageAffectedFixed
kernel-devel
AlmaLinux:8
From an advisory covering 145 CVEs
 before 4.18.0-553.22.1.el8_10
4.18.0-553.22.1.el8_10
kernel-doc
AlmaLinux:8
From an advisory covering 145 CVEs
 before 4.18.0-553.22.1.el8_10
4.18.0-553.22.1.el8_10
kernel-headers
AlmaLinux:8
From an advisory covering 145 CVEs
 before 4.18.0-553.22.1.el8_10
4.18.0-553.22.1.el8_10
kernel-modules
AlmaLinux:8
From an advisory covering 145 CVEs
 before 4.18.0-553.22.1.el8_10
4.18.0-553.22.1.el8_10
kernel-modules-extra
AlmaLinux:8
From an advisory covering 145 CVEs
 before 4.18.0-553.22.1.el8_10
4.18.0-553.22.1.el8_10
kernel-tools
AlmaLinux:8
From an advisory covering 145 CVEs
 before 4.18.0-553.22.1.el8_10
4.18.0-553.22.1.el8_10
kernel-tools-libs
AlmaLinux:8
From an advisory covering 145 CVEs
 before 4.18.0-553.22.1.el8_10
4.18.0-553.22.1.el8_10
kernel-tools-libs-devel
AlmaLinux:8
From an advisory covering 145 CVEs
 before 4.18.0-553.22.1.el8_10
4.18.0-553.22.1.el8_10
kernel-zfcpdump
AlmaLinux:8
From an advisory covering 145 CVEs
 before 4.18.0-553.22.1.el8_10
4.18.0-553.22.1.el8_10
kernel-zfcpdump-core
AlmaLinux:8
From an advisory covering 145 CVEs
 before 4.18.0-553.22.1.el8_10
4.18.0-553.22.1.el8_10
kernel-zfcpdump-devel
AlmaLinux:8
From an advisory covering 145 CVEs
 before 4.18.0-553.22.1.el8_10
4.18.0-553.22.1.el8_10
kernel-zfcpdump-modules
AlmaLinux:8
From an advisory covering 145 CVEs
 before 4.18.0-553.22.1.el8_10
4.18.0-553.22.1.el8_10
kernel-zfcpdump-modules-extra
AlmaLinux:8
From an advisory covering 145 CVEs
 before 4.18.0-553.22.1.el8_10
4.18.0-553.22.1.el8_10
perf
AlmaLinux:8
From an advisory covering 145 CVEs
 before 4.18.0-553.22.1.el8_10
4.18.0-553.22.1.el8_10
python3-perf
AlmaLinux:8
From an advisory covering 145 CVEs
 before 4.18.0-553.22.1.el8_10
4.18.0-553.22.1.el8_10
kernel-rt
AlmaLinux:8
From an advisory covering 129 CVEs
 before 4.18.0-553.22.1.rt7.363.el8_10
4.18.0-553.22.1.rt7.363.el8_10
kernel-rt-core
AlmaLinux:8
From an advisory covering 129 CVEs
 before 4.18.0-553.22.1.rt7.363.el8_10
4.18.0-553.22.1.rt7.363.el8_10
kernel-rt-debug
AlmaLinux:8
From an advisory covering 129 CVEs
 before 4.18.0-553.22.1.rt7.363.el8_10
4.18.0-553.22.1.rt7.363.el8_10
kernel-rt-debug-core
AlmaLinux:8
From an advisory covering 129 CVEs
 before 4.18.0-553.22.1.rt7.363.el8_10
4.18.0-553.22.1.rt7.363.el8_10
kernel-rt-debug-devel
AlmaLinux:8
From an advisory covering 129 CVEs
 before 4.18.0-553.22.1.rt7.363.el8_10
4.18.0-553.22.1.rt7.363.el8_10
kernel-rt-debug-kvm
AlmaLinux:8
From an advisory covering 129 CVEs
 before 4.18.0-553.22.1.rt7.363.el8_10
4.18.0-553.22.1.rt7.363.el8_10
kernel-rt-debug-modules
AlmaLinux:8
From an advisory covering 129 CVEs
 before 4.18.0-553.22.1.rt7.363.el8_10
4.18.0-553.22.1.rt7.363.el8_10
kernel-rt-debug-modules-extra
AlmaLinux:8
From an advisory covering 129 CVEs
 before 4.18.0-553.22.1.rt7.363.el8_10
4.18.0-553.22.1.rt7.363.el8_10
kernel-rt-devel
AlmaLinux:8
From an advisory covering 129 CVEs
 before 4.18.0-553.22.1.rt7.363.el8_10
4.18.0-553.22.1.rt7.363.el8_10
kernel-rt-kvm
AlmaLinux:8
From an advisory covering 129 CVEs
 before 4.18.0-553.22.1.rt7.363.el8_10
4.18.0-553.22.1.rt7.363.el8_10
kernel-rt-modules
AlmaLinux:8
From an advisory covering 129 CVEs
 before 4.18.0-553.22.1.rt7.363.el8_10
4.18.0-553.22.1.rt7.363.el8_10
kernel-rt-modules-extra
AlmaLinux:8
From an advisory covering 129 CVEs
 before 4.18.0-553.22.1.rt7.363.el8_10
4.18.0-553.22.1.rt7.363.el8_10
linux-lts
Alpaquita:23
 6.1.82-r0 up to 6.1.89-r0
6.1.89-r0
linux-lts
Alpaquita:25
 6.6.89-r0 up to 6.12.41-r0
6.12.41-r0
linux-lts
Alpaquita:stream
 6.6.100-r0 up to 6.12.41-r0
6.12.41-r0
bpftool
TuxCare:AlmaLinux:9.2
From an advisory covering 22 CVEs
 before 7.0.0-284.1101.el9_2.tuxcare.7.els20
7.0.0-284.1101.el9_2.tuxcare.7.els20
kernel
TuxCare:AlmaLinux:9.2
From an advisory covering 22 CVEs
 before 5.14.0-284.1101.el9_2.tuxcare.7.els20
5.14.0-284.1101.el9_2.tuxcare.7.els20
kernel-64k
TuxCare:AlmaLinux:9.2
From an advisory covering 22 CVEs
 before 5.14.0-284.1101.el9_2.tuxcare.7.els20
5.14.0-284.1101.el9_2.tuxcare.7.els20
kernel-64k-core
TuxCare:AlmaLinux:9.2
From an advisory covering 22 CVEs
 before 5.14.0-284.1101.el9_2.tuxcare.7.els20
5.14.0-284.1101.el9_2.tuxcare.7.els20
kernel-64k-debug
TuxCare:AlmaLinux:9.2
From an advisory covering 22 CVEs
 before 5.14.0-284.1101.el9_2.tuxcare.7.els20
5.14.0-284.1101.el9_2.tuxcare.7.els20
kernel-64k-debug-core
TuxCare:AlmaLinux:9.2
From an advisory covering 22 CVEs
 before 5.14.0-284.1101.el9_2.tuxcare.7.els20
5.14.0-284.1101.el9_2.tuxcare.7.els20
kernel-64k-debug-devel
TuxCare:AlmaLinux:9.2
From an advisory covering 22 CVEs
 before 5.14.0-284.1101.el9_2.tuxcare.7.els20
5.14.0-284.1101.el9_2.tuxcare.7.els20
kernel-64k-debug-devel-matched
TuxCare:AlmaLinux:9.2
From an advisory covering 22 CVEs
 before 5.14.0-284.1101.el9_2.tuxcare.7.els20
5.14.0-284.1101.el9_2.tuxcare.7.els20
kernel-64k-debug-modules
TuxCare:AlmaLinux:9.2
From an advisory covering 22 CVEs
 before 5.14.0-284.1101.el9_2.tuxcare.7.els20
5.14.0-284.1101.el9_2.tuxcare.7.els20
kernel-64k-debug-modules-core
TuxCare:AlmaLinux:9.2
From an advisory covering 22 CVEs
 before 5.14.0-284.1101.el9_2.tuxcare.7.els20
5.14.0-284.1101.el9_2.tuxcare.7.els20
kernel-64k-debug-modules-extra
TuxCare:AlmaLinux:9.2
From an advisory covering 22 CVEs
 before 5.14.0-284.1101.el9_2.tuxcare.7.els20
5.14.0-284.1101.el9_2.tuxcare.7.els20
kernel-64k-debug-modules-internal
TuxCare:AlmaLinux:9.2
From an advisory covering 22 CVEs
 before 5.14.0-284.1101.el9_2.tuxcare.7.els20
5.14.0-284.1101.el9_2.tuxcare.7.els20
kernel-64k-debug-modules-partner
TuxCare:AlmaLinux:9.2
From an advisory covering 22 CVEs
 before 5.14.0-284.1101.el9_2.tuxcare.7.els20
5.14.0-284.1101.el9_2.tuxcare.7.els20
kernel-64k-devel
TuxCare:AlmaLinux:9.2
From an advisory covering 22 CVEs
 before 5.14.0-284.1101.el9_2.tuxcare.7.els20
5.14.0-284.1101.el9_2.tuxcare.7.els20
kernel-64k-devel-matched
TuxCare:AlmaLinux:9.2
From an advisory covering 22 CVEs
 before 5.14.0-284.1101.el9_2.tuxcare.7.els20
5.14.0-284.1101.el9_2.tuxcare.7.els20
kernel-64k-modules
TuxCare:AlmaLinux:9.2
From an advisory covering 22 CVEs
 before 5.14.0-284.1101.el9_2.tuxcare.7.els20
5.14.0-284.1101.el9_2.tuxcare.7.els20
kernel-64k-modules-core
TuxCare:AlmaLinux:9.2
From an advisory covering 22 CVEs
 before 5.14.0-284.1101.el9_2.tuxcare.7.els20
5.14.0-284.1101.el9_2.tuxcare.7.els20
kernel-64k-modules-extra
TuxCare:AlmaLinux:9.2
From an advisory covering 22 CVEs
 before 5.14.0-284.1101.el9_2.tuxcare.7.els20
5.14.0-284.1101.el9_2.tuxcare.7.els20
kernel-64k-modules-internal
TuxCare:AlmaLinux:9.2
From an advisory covering 22 CVEs
 before 5.14.0-284.1101.el9_2.tuxcare.7.els20
5.14.0-284.1101.el9_2.tuxcare.7.els20
kernel-64k-modules-partner
TuxCare:AlmaLinux:9.2
From an advisory covering 22 CVEs
 before 5.14.0-284.1101.el9_2.tuxcare.7.els20
5.14.0-284.1101.el9_2.tuxcare.7.els20
kernel-abi-stablelists
TuxCare:AlmaLinux:9.2
From an advisory covering 22 CVEs
 before 5.14.0-284.1101.el9_2.tuxcare.7.els20
5.14.0-284.1101.el9_2.tuxcare.7.els20
kernel-core
TuxCare:AlmaLinux:9.2
From an advisory covering 22 CVEs
 before 5.14.0-284.1101.el9_2.tuxcare.7.els20
5.14.0-284.1101.el9_2.tuxcare.7.els20
kernel-cross-headers
TuxCare:AlmaLinux:9.2
From an advisory covering 22 CVEs
 before 5.14.0-284.1101.el9_2.tuxcare.7.els20
5.14.0-284.1101.el9_2.tuxcare.7.els20
kernel-debug
TuxCare:AlmaLinux:9.2
From an advisory covering 22 CVEs
 before 5.14.0-284.1101.el9_2.tuxcare.7.els20
5.14.0-284.1101.el9_2.tuxcare.7.els20
kernel-debug-core
TuxCare:AlmaLinux:9.2
From an advisory covering 22 CVEs
 before 5.14.0-284.1101.el9_2.tuxcare.7.els20
5.14.0-284.1101.el9_2.tuxcare.7.els20
kernel-debug-devel
TuxCare:AlmaLinux:9.2
From an advisory covering 22 CVEs
 before 5.14.0-284.1101.el9_2.tuxcare.7.els20
5.14.0-284.1101.el9_2.tuxcare.7.els20
kernel-debug-devel-matched
TuxCare:AlmaLinux:9.2
From an advisory covering 22 CVEs
 before 5.14.0-284.1101.el9_2.tuxcare.7.els20
5.14.0-284.1101.el9_2.tuxcare.7.els20
kernel-debug-modules
TuxCare:AlmaLinux:9.2
From an advisory covering 22 CVEs
 before 5.14.0-284.1101.el9_2.tuxcare.7.els20
5.14.0-284.1101.el9_2.tuxcare.7.els20
kernel-debug-modules-core
TuxCare:AlmaLinux:9.2
From an advisory covering 22 CVEs
 before 5.14.0-284.1101.el9_2.tuxcare.7.els20
5.14.0-284.1101.el9_2.tuxcare.7.els20
kernel-debug-modules-extra
TuxCare:AlmaLinux:9.2
From an advisory covering 22 CVEs
 before 5.14.0-284.1101.el9_2.tuxcare.7.els20
5.14.0-284.1101.el9_2.tuxcare.7.els20
kernel-debug-modules-internal
TuxCare:AlmaLinux:9.2
From an advisory covering 22 CVEs
 before 5.14.0-284.1101.el9_2.tuxcare.7.els20
5.14.0-284.1101.el9_2.tuxcare.7.els20
kernel-debug-modules-partner
TuxCare:AlmaLinux:9.2
From an advisory covering 22 CVEs
 before 5.14.0-284.1101.el9_2.tuxcare.7.els20
5.14.0-284.1101.el9_2.tuxcare.7.els20
kernel-debug-uki-virt
TuxCare:AlmaLinux:9.2
From an advisory covering 22 CVEs
 before 5.14.0-284.1101.el9_2.tuxcare.7.els20
5.14.0-284.1101.el9_2.tuxcare.7.els20
kernel-devel
TuxCare:AlmaLinux:9.2
From an advisory covering 22 CVEs
 before 5.14.0-284.1101.el9_2.tuxcare.7.els20
5.14.0-284.1101.el9_2.tuxcare.7.els20
kernel-devel-matched
TuxCare:AlmaLinux:9.2
From an advisory covering 22 CVEs
 before 5.14.0-284.1101.el9_2.tuxcare.7.els20
5.14.0-284.1101.el9_2.tuxcare.7.els20
kernel-doc
TuxCare:AlmaLinux:9.2
From an advisory covering 22 CVEs
 before 5.14.0-284.1101.el9_2.tuxcare.7.els20
5.14.0-284.1101.el9_2.tuxcare.7.els20
kernel-headers
TuxCare:AlmaLinux:9.2
From an advisory covering 22 CVEs
 before 5.14.0-284.1101.el9_2.tuxcare.7.els20
5.14.0-284.1101.el9_2.tuxcare.7.els20
kernel-ipaclones-internal
TuxCare:AlmaLinux:9.2
From an advisory covering 22 CVEs
 before 5.14.0-284.1101.el9_2.tuxcare.7.els20
5.14.0-284.1101.el9_2.tuxcare.7.els20
kernel-modules
TuxCare:AlmaLinux:9.2
From an advisory covering 22 CVEs
 before 5.14.0-284.1101.el9_2.tuxcare.7.els20
5.14.0-284.1101.el9_2.tuxcare.7.els20
kernel-modules-core
TuxCare:AlmaLinux:9.2
From an advisory covering 22 CVEs
 before 5.14.0-284.1101.el9_2.tuxcare.7.els20
5.14.0-284.1101.el9_2.tuxcare.7.els20
kernel-modules-extra
TuxCare:AlmaLinux:9.2
From an advisory covering 22 CVEs
 before 5.14.0-284.1101.el9_2.tuxcare.7.els20
5.14.0-284.1101.el9_2.tuxcare.7.els20
kernel-modules-internal
TuxCare:AlmaLinux:9.2
From an advisory covering 22 CVEs
 before 5.14.0-284.1101.el9_2.tuxcare.7.els20
5.14.0-284.1101.el9_2.tuxcare.7.els20
kernel-modules-partner
TuxCare:AlmaLinux:9.2
From an advisory covering 22 CVEs
 before 5.14.0-284.1101.el9_2.tuxcare.7.els20
5.14.0-284.1101.el9_2.tuxcare.7.els20
kernel-selftests-internal
TuxCare:AlmaLinux:9.2
From an advisory covering 22 CVEs
 before 5.14.0-284.1101.el9_2.tuxcare.7.els20
5.14.0-284.1101.el9_2.tuxcare.7.els20
kernel-tools
TuxCare:AlmaLinux:9.2
From an advisory covering 22 CVEs
 before 5.14.0-284.1101.el9_2.tuxcare.7.els20
5.14.0-284.1101.el9_2.tuxcare.7.els20
kernel-tools-libs
TuxCare:AlmaLinux:9.2
From an advisory covering 22 CVEs
 before 5.14.0-284.1101.el9_2.tuxcare.7.els20
5.14.0-284.1101.el9_2.tuxcare.7.els20
kernel-tools-libs-devel
TuxCare:AlmaLinux:9.2
From an advisory covering 22 CVEs
 before 5.14.0-284.1101.el9_2.tuxcare.7.els20
5.14.0-284.1101.el9_2.tuxcare.7.els20
kernel-uki-virt
TuxCare:AlmaLinux:9.2
From an advisory covering 22 CVEs
 before 5.14.0-284.1101.el9_2.tuxcare.7.els20
5.14.0-284.1101.el9_2.tuxcare.7.els20
libbpf
TuxCare:AlmaLinux:9.2
From an advisory covering 22 CVEs
 before 2:1.0.0-2.el9_2.tuxcare.7.els20
2:1.0.0-2.el9_2.tuxcare.7.els20
libbpf-devel
TuxCare:AlmaLinux:9.2
From an advisory covering 22 CVEs
 before 2:1.0.0-2.el9_2.tuxcare.7.els20
2:1.0.0-2.el9_2.tuxcare.7.els20
libbpf-static
TuxCare:AlmaLinux:9.2
From an advisory covering 22 CVEs
 before 2:1.0.0-2.el9_2.tuxcare.7.els20
2:1.0.0-2.el9_2.tuxcare.7.els20
perf
TuxCare:AlmaLinux:9.2
From an advisory covering 22 CVEs
 before 5.14.0-284.1101.el9_2.tuxcare.7.els20
5.14.0-284.1101.el9_2.tuxcare.7.els20
python3-perf
TuxCare:AlmaLinux:9.2
From an advisory covering 22 CVEs
 before 5.14.0-284.1101.el9_2.tuxcare.7.els20
5.14.0-284.1101.el9_2.tuxcare.7.els20
rtla
TuxCare:AlmaLinux:9.2
From an advisory covering 22 CVEs
 before 5.14.0-284.1101.el9_2.tuxcare.7.els20
5.14.0-284.1101.el9_2.tuxcare.7.els20
bpftool
TuxCare:CentOS-Stream:8
From an advisory covering 63 CVEs
 before 4.18.0-553.6.1.el8_10.tuxcare.els15
4.18.0-553.6.1.el8_10.tuxcare.els15
kernel
TuxCare:CentOS-Stream:8
From an advisory covering 63 CVEs
 before 4.18.0-553.6.1.el8_10.tuxcare.els15
4.18.0-553.6.1.el8_10.tuxcare.els15
kernel-core
TuxCare:CentOS-Stream:8
From an advisory covering 63 CVEs
 before 4.18.0-553.6.1.el8_10.tuxcare.els15
4.18.0-553.6.1.el8_10.tuxcare.els15
kernel-cross-headers
TuxCare:CentOS-Stream:8
From an advisory covering 63 CVEs
 before 4.18.0-553.6.1.el8_10.tuxcare.els15
4.18.0-553.6.1.el8_10.tuxcare.els15
kernel-debug
TuxCare:CentOS-Stream:8
From an advisory covering 63 CVEs
 before 4.18.0-553.6.1.el8_10.tuxcare.els15
4.18.0-553.6.1.el8_10.tuxcare.els15
kernel-debug-core
TuxCare:CentOS-Stream:8
From an advisory covering 63 CVEs
 before 4.18.0-553.6.1.el8_10.tuxcare.els15
4.18.0-553.6.1.el8_10.tuxcare.els15
kernel-debug-devel
TuxCare:CentOS-Stream:8
From an advisory covering 63 CVEs
 before 4.18.0-553.6.1.el8_10.tuxcare.els15
4.18.0-553.6.1.el8_10.tuxcare.els15
kernel-debug-modules
TuxCare:CentOS-Stream:8
From an advisory covering 63 CVEs
 before 4.18.0-553.6.1.el8_10.tuxcare.els15
4.18.0-553.6.1.el8_10.tuxcare.els15
kernel-debug-modules-extra
TuxCare:CentOS-Stream:8
From an advisory covering 63 CVEs
 before 4.18.0-553.6.1.el8_10.tuxcare.els15
4.18.0-553.6.1.el8_10.tuxcare.els15
kernel-debug-modules-internal
TuxCare:CentOS-Stream:8
From an advisory covering 63 CVEs
 before 4.18.0-553.6.1.el8_10.tuxcare.els15
4.18.0-553.6.1.el8_10.tuxcare.els15
kernel-devel
TuxCare:CentOS-Stream:8
From an advisory covering 63 CVEs
 before 4.18.0-553.6.1.el8_10.tuxcare.els15
4.18.0-553.6.1.el8_10.tuxcare.els15
kernel-headers
TuxCare:CentOS-Stream:8
From an advisory covering 63 CVEs
 before 4.18.0-553.6.1.el8_10.tuxcare.els15
4.18.0-553.6.1.el8_10.tuxcare.els15
Kernel
Linux
 5.19.0 up to 6.1.88, 6.2.0 up to 6.6.29, 6.7.0 up to 6.8.3
6.1.886.6.296.8.3
linux
Debian:12
 before 6.1.90-1, plus listed versions
6.1.27-16.1.37-16.1.38-16.1.38-26.1.38-2~bpo11+1
Show 16 moreShow less
6.1.38-36.1.38-46.1.38-4~bpo11+16.1.52-16.1.55-16.1.55-1~bpo11+16.1.64-16.1.66-16.1.67-16.1.69-16.1.69-1~bpo11+16.1.76-16.1.76-1~bpo11+16.1.82-16.1.85-16.1.90-1~bpo11+1
6.1.90-1
linux
Debian:13
 before 6.8.9-1
6.8.9-1
linux
Debian:14
 before 6.8.9-1
6.8.9-1
linux
Debian:12
From an advisory covering 37 CVEs
 before 6.1.90-1, plus listed versions
6.1.27-16.1.37-16.1.38-16.1.38-26.1.38-2~bpo11+1
Show 16 moreShow less
6.1.38-36.1.38-46.1.38-4~bpo11+16.1.52-16.1.55-16.1.55-1~bpo11+16.1.64-16.1.66-16.1.67-16.1.69-16.1.69-1~bpo11+16.1.76-16.1.76-1~bpo11+16.1.82-16.1.85-16.1.90-1~bpo11+1
6.1.90-1
kernel
Mageia:9
From an advisory covering 320 CVEs
 before 6.6.37-1.mga9
6.6.37-1.mga9
kmod-xtables-addons
Mageia:9
From an advisory covering 320 CVEs
 before 3.24-59.mga9
3.24-59.mga9
kmod-virtualbox
Mageia:9
From an advisory covering 320 CVEs
 before 7.0.18-50.mga9
7.0.18-50.mga9
dwarves
Mageia:9
From an advisory covering 320 CVEs
 before 1.27-1.mga9
1.27-1.mga9
kernel-linus
Mageia:9
From an advisory covering 320 CVEs
 before 6.6.37-1.mga9
6.6.37-1.mga9
bpftool
Red Hat:enterprise_linux:8::baseos
From an advisory covering 151 CVEs
 before 0:4.18.0-553.22.1.el8_10
0:4.18.0-553.22.1.el8_10
bpftool-debuginfo
Red Hat:enterprise_linux:8::baseos
From an advisory covering 151 CVEs
 before 0:4.18.0-553.22.1.el8_10
0:4.18.0-553.22.1.el8_10
kernel
Red Hat:enterprise_linux:8::baseos
From an advisory covering 151 CVEs
 before 0:4.18.0-553.22.1.el8_10
0:4.18.0-553.22.1.el8_10
kernel-abi-stablelists
Red Hat:enterprise_linux:8::baseos
From an advisory covering 151 CVEs
 before 0:4.18.0-553.22.1.el8_10
0:4.18.0-553.22.1.el8_10
kernel-core
Red Hat:enterprise_linux:8::baseos
From an advisory covering 151 CVEs
 before 0:4.18.0-553.22.1.el8_10
0:4.18.0-553.22.1.el8_10
kernel-debug
Red Hat:enterprise_linux:8::baseos
From an advisory covering 151 CVEs
 before 0:4.18.0-553.22.1.el8_10
0:4.18.0-553.22.1.el8_10
kernel-debug-core
Red Hat:enterprise_linux:8::baseos
From an advisory covering 151 CVEs
 before 0:4.18.0-553.22.1.el8_10
0:4.18.0-553.22.1.el8_10
kernel-debug-debuginfo
Red Hat:enterprise_linux:8::baseos
From an advisory covering 151 CVEs
 before 0:4.18.0-553.22.1.el8_10
0:4.18.0-553.22.1.el8_10
kernel-debug-devel
Red Hat:enterprise_linux:8::baseos
From an advisory covering 151 CVEs
 before 0:4.18.0-553.22.1.el8_10
0:4.18.0-553.22.1.el8_10
kernel-debug-modules
Red Hat:enterprise_linux:8::baseos
From an advisory covering 151 CVEs
 before 0:4.18.0-553.22.1.el8_10
0:4.18.0-553.22.1.el8_10
kernel-debug-modules-extra
Red Hat:enterprise_linux:8::baseos
From an advisory covering 151 CVEs
 before 0:4.18.0-553.22.1.el8_10
0:4.18.0-553.22.1.el8_10
kernel-debuginfo
Red Hat:enterprise_linux:8::baseos
From an advisory covering 151 CVEs
 before 0:4.18.0-553.22.1.el8_10
0:4.18.0-553.22.1.el8_10
kernel-debuginfo-common-aarch64
Red Hat:enterprise_linux:8::baseos
From an advisory covering 151 CVEs
 before 0:4.18.0-553.22.1.el8_10
0:4.18.0-553.22.1.el8_10
kernel-debuginfo-common-ppc64le
Red Hat:enterprise_linux:8::baseos
From an advisory covering 151 CVEs
 before 0:4.18.0-553.22.1.el8_10
0:4.18.0-553.22.1.el8_10
kernel-debuginfo-common-s390x
Red Hat:enterprise_linux:8::baseos
From an advisory covering 151 CVEs
 before 0:4.18.0-553.22.1.el8_10
0:4.18.0-553.22.1.el8_10
kernel-debuginfo-common-x86_64
Red Hat:enterprise_linux:8::baseos
From an advisory covering 151 CVEs
 before 0:4.18.0-553.22.1.el8_10
0:4.18.0-553.22.1.el8_10
kernel-devel
Red Hat:enterprise_linux:8::baseos
From an advisory covering 151 CVEs
 before 0:4.18.0-553.22.1.el8_10
0:4.18.0-553.22.1.el8_10
kernel-doc
Red Hat:enterprise_linux:8::baseos
From an advisory covering 151 CVEs
 before 0:4.18.0-553.22.1.el8_10
0:4.18.0-553.22.1.el8_10
kernel-modules
Red Hat:enterprise_linux:8::baseos
From an advisory covering 151 CVEs
 before 0:4.18.0-553.22.1.el8_10
0:4.18.0-553.22.1.el8_10
kernel-modules-extra
Red Hat:enterprise_linux:8::baseos
From an advisory covering 151 CVEs
 before 0:4.18.0-553.22.1.el8_10
0:4.18.0-553.22.1.el8_10
kernel-tools
Red Hat:enterprise_linux:8::baseos
From an advisory covering 151 CVEs
 before 0:4.18.0-553.22.1.el8_10
0:4.18.0-553.22.1.el8_10
kernel-tools-debuginfo
Red Hat:enterprise_linux:8::baseos
From an advisory covering 151 CVEs
 before 0:4.18.0-553.22.1.el8_10
0:4.18.0-553.22.1.el8_10
kernel-tools-libs
Red Hat:enterprise_linux:8::baseos
From an advisory covering 151 CVEs
 before 0:4.18.0-553.22.1.el8_10
0:4.18.0-553.22.1.el8_10
kernel-zfcpdump
Red Hat:enterprise_linux:8::baseos
From an advisory covering 151 CVEs
 before 0:4.18.0-553.22.1.el8_10
0:4.18.0-553.22.1.el8_10
kernel-zfcpdump-core
Red Hat:enterprise_linux:8::baseos
From an advisory covering 151 CVEs
 before 0:4.18.0-553.22.1.el8_10
0:4.18.0-553.22.1.el8_10
kernel-zfcpdump-debuginfo
Red Hat:enterprise_linux:8::baseos
From an advisory covering 151 CVEs
 before 0:4.18.0-553.22.1.el8_10
0:4.18.0-553.22.1.el8_10
kernel-zfcpdump-devel
Red Hat:enterprise_linux:8::baseos
From an advisory covering 151 CVEs
 before 0:4.18.0-553.22.1.el8_10
0:4.18.0-553.22.1.el8_10
kernel-zfcpdump-modules
Red Hat:enterprise_linux:8::baseos
From an advisory covering 151 CVEs
 before 0:4.18.0-553.22.1.el8_10
0:4.18.0-553.22.1.el8_10
kernel-zfcpdump-modules-extra
Red Hat:enterprise_linux:8::baseos
From an advisory covering 151 CVEs
 before 0:4.18.0-553.22.1.el8_10
0:4.18.0-553.22.1.el8_10
perf
Red Hat:enterprise_linux:8::baseos
From an advisory covering 151 CVEs
 before 0:4.18.0-553.22.1.el8_10
0:4.18.0-553.22.1.el8_10
perf-debuginfo
Red Hat:enterprise_linux:8::baseos
From an advisory covering 151 CVEs
 before 0:4.18.0-553.22.1.el8_10
0:4.18.0-553.22.1.el8_10
python3-perf
Red Hat:enterprise_linux:8::baseos
From an advisory covering 151 CVEs
 before 0:4.18.0-553.22.1.el8_10
0:4.18.0-553.22.1.el8_10
python3-perf-debuginfo
Red Hat:enterprise_linux:8::baseos
From an advisory covering 151 CVEs
 before 0:4.18.0-553.22.1.el8_10
0:4.18.0-553.22.1.el8_10
bpftool-debuginfo
Red Hat:enterprise_linux:8::crb
From an advisory covering 151 CVEs
 before 0:4.18.0-553.22.1.el8_10
0:4.18.0-553.22.1.el8_10
kernel-debug-debuginfo
Red Hat:enterprise_linux:8::crb
From an advisory covering 151 CVEs
 before 0:4.18.0-553.22.1.el8_10
0:4.18.0-553.22.1.el8_10
kernel-debuginfo
Red Hat:enterprise_linux:8::crb
From an advisory covering 151 CVEs
 before 0:4.18.0-553.22.1.el8_10
0:4.18.0-553.22.1.el8_10
kernel-debuginfo-common-aarch64
Red Hat:enterprise_linux:8::crb
From an advisory covering 151 CVEs
 before 0:4.18.0-553.22.1.el8_10
0:4.18.0-553.22.1.el8_10
kernel-debuginfo-common-ppc64le
Red Hat:enterprise_linux:8::crb
From an advisory covering 151 CVEs
 before 0:4.18.0-553.22.1.el8_10
0:4.18.0-553.22.1.el8_10
kernel-debuginfo-common-x86_64
Red Hat:enterprise_linux:8::crb
From an advisory covering 151 CVEs
 before 0:4.18.0-553.22.1.el8_10
0:4.18.0-553.22.1.el8_10
kernel-tools-debuginfo
Red Hat:enterprise_linux:8::crb
From an advisory covering 151 CVEs
 before 0:4.18.0-553.22.1.el8_10
0:4.18.0-553.22.1.el8_10
kernel-tools-libs-devel
Red Hat:enterprise_linux:8::crb
From an advisory covering 151 CVEs
 before 0:4.18.0-553.22.1.el8_10
0:4.18.0-553.22.1.el8_10
perf-debuginfo
Red Hat:enterprise_linux:8::crb
From an advisory covering 151 CVEs
 before 0:4.18.0-553.22.1.el8_10
0:4.18.0-553.22.1.el8_10
python3-perf-debuginfo
Red Hat:enterprise_linux:8::crb
From an advisory covering 151 CVEs
 before 0:4.18.0-553.22.1.el8_10
0:4.18.0-553.22.1.el8_10
kernel-rt
Red Hat:enterprise_linux:8::nfv
From an advisory covering 129 CVEs
 before 0:4.18.0-553.22.1.rt7.363.el8_10
0:4.18.0-553.22.1.rt7.363.el8_10
kernel-rt-core
Red Hat:enterprise_linux:8::nfv
From an advisory covering 129 CVEs
 before 0:4.18.0-553.22.1.rt7.363.el8_10
0:4.18.0-553.22.1.rt7.363.el8_10
kernel-rt-debug
Red Hat:enterprise_linux:8::nfv
From an advisory covering 129 CVEs
 before 0:4.18.0-553.22.1.rt7.363.el8_10
0:4.18.0-553.22.1.rt7.363.el8_10
kernel-rt-debug-core
Red Hat:enterprise_linux:8::nfv
From an advisory covering 129 CVEs
 before 0:4.18.0-553.22.1.rt7.363.el8_10
0:4.18.0-553.22.1.rt7.363.el8_10
kernel-rt-debug-debuginfo
Red Hat:enterprise_linux:8::nfv
From an advisory covering 129 CVEs
 before 0:4.18.0-553.22.1.rt7.363.el8_10
0:4.18.0-553.22.1.rt7.363.el8_10
kernel-rt-debug-devel
Red Hat:enterprise_linux:8::nfv
From an advisory covering 129 CVEs
 before 0:4.18.0-553.22.1.rt7.363.el8_10
0:4.18.0-553.22.1.rt7.363.el8_10
kernel-rt-debug-kvm
Red Hat:enterprise_linux:8::nfv
From an advisory covering 129 CVEs
 before 0:4.18.0-553.22.1.rt7.363.el8_10
0:4.18.0-553.22.1.rt7.363.el8_10
kernel-rt-debug-modules
Red Hat:enterprise_linux:8::nfv
From an advisory covering 129 CVEs
 before 0:4.18.0-553.22.1.rt7.363.el8_10
0:4.18.0-553.22.1.rt7.363.el8_10
kernel-rt-debug-modules-extra
Red Hat:enterprise_linux:8::nfv
From an advisory covering 129 CVEs
 before 0:4.18.0-553.22.1.rt7.363.el8_10
0:4.18.0-553.22.1.rt7.363.el8_10
kernel-rt-debuginfo
Red Hat:enterprise_linux:8::nfv
From an advisory covering 129 CVEs
 before 0:4.18.0-553.22.1.rt7.363.el8_10
0:4.18.0-553.22.1.rt7.363.el8_10
kernel-rt-debuginfo-common-x86_64
Red Hat:enterprise_linux:8::nfv
From an advisory covering 129 CVEs
 before 0:4.18.0-553.22.1.rt7.363.el8_10
0:4.18.0-553.22.1.rt7.363.el8_10
kernel-rt-devel
Red Hat:enterprise_linux:8::nfv
From an advisory covering 129 CVEs
 before 0:4.18.0-553.22.1.rt7.363.el8_10
0:4.18.0-553.22.1.rt7.363.el8_10
kernel-rt-kvm
Red Hat:enterprise_linux:8::nfv
From an advisory covering 129 CVEs
 before 0:4.18.0-553.22.1.rt7.363.el8_10
0:4.18.0-553.22.1.rt7.363.el8_10
kernel-rt-modules
Red Hat:enterprise_linux:8::nfv
From an advisory covering 129 CVEs
 before 0:4.18.0-553.22.1.rt7.363.el8_10
0:4.18.0-553.22.1.rt7.363.el8_10
kernel-rt-modules-extra
Red Hat:enterprise_linux:8::nfv
From an advisory covering 129 CVEs
 before 0:4.18.0-553.22.1.rt7.363.el8_10
0:4.18.0-553.22.1.rt7.363.el8_10
kernel-rt
Red Hat:enterprise_linux:8::realtime
From an advisory covering 129 CVEs
 before 0:4.18.0-553.22.1.rt7.363.el8_10
0:4.18.0-553.22.1.rt7.363.el8_10
kernel-rt-core
Red Hat:enterprise_linux:8::realtime
From an advisory covering 129 CVEs
 before 0:4.18.0-553.22.1.rt7.363.el8_10
0:4.18.0-553.22.1.rt7.363.el8_10
kernel-rt-debug
Red Hat:enterprise_linux:8::realtime
From an advisory covering 129 CVEs
 before 0:4.18.0-553.22.1.rt7.363.el8_10
0:4.18.0-553.22.1.rt7.363.el8_10
kernel-rt-debug-core
Red Hat:enterprise_linux:8::realtime
From an advisory covering 129 CVEs
 before 0:4.18.0-553.22.1.rt7.363.el8_10
0:4.18.0-553.22.1.rt7.363.el8_10
kernel-rt-debug-debuginfo
Red Hat:enterprise_linux:8::realtime
From an advisory covering 129 CVEs
 before 0:4.18.0-553.22.1.rt7.363.el8_10
0:4.18.0-553.22.1.rt7.363.el8_10
kernel-rt-debug-devel
Red Hat:enterprise_linux:8::realtime
From an advisory covering 129 CVEs
 before 0:4.18.0-553.22.1.rt7.363.el8_10
0:4.18.0-553.22.1.rt7.363.el8_10
kernel-rt-debug-modules
Red Hat:enterprise_linux:8::realtime
From an advisory covering 129 CVEs
 before 0:4.18.0-553.22.1.rt7.363.el8_10
0:4.18.0-553.22.1.rt7.363.el8_10
kernel-rt-debug-modules-extra
Red Hat:enterprise_linux:8::realtime
From an advisory covering 129 CVEs
 before 0:4.18.0-553.22.1.rt7.363.el8_10
0:4.18.0-553.22.1.rt7.363.el8_10
kernel
Rocky Linux:8
From an advisory covering 147 CVEs
 before 0:4.18.0-553.22.1.el8_10
0:4.18.0-553.22.1.el8_10
kernel-rt
Rocky Linux:8
From an advisory covering 129 CVEs
 before 0:4.18.0-553.22.1.rt7.363.el8_10
0:4.18.0-553.22.1.rt7.363.el8_10
kernel-azure
SUSE:Linux Enterprise Module for Public Cloud 15 SP5
From an advisory covering 190 CVEs
 before 5.14.21-150500.33.51.1
5.14.21-150500.33.51.1
kernel-source-azure
SUSE:Linux Enterprise Module for Public Cloud 15 SP5
From an advisory covering 190 CVEs
 before 5.14.21-150500.33.51.1
5.14.21-150500.33.51.1
kernel-syms-azure
SUSE:Linux Enterprise Module for Public Cloud 15 SP5
From an advisory covering 190 CVEs
 before 5.14.21-150500.33.51.1
5.14.21-150500.33.51.1
kernel-azure
openSUSE:Leap 15.5
From an advisory covering 190 CVEs
 before 5.14.21-150500.33.51.1
5.14.21-150500.33.51.1
kernel-source-azure
openSUSE:Leap 15.5
From an advisory covering 190 CVEs
 before 5.14.21-150500.33.51.1
5.14.21-150500.33.51.1
kernel-syms-azure
openSUSE:Leap 15.5
From an advisory covering 190 CVEs
 before 5.14.21-150500.33.51.1
5.14.21-150500.33.51.1
kernel-rt
SUSE:Linux Enterprise Micro 5.5
From an advisory covering 561 CVEs
 before 5.14.21-150500.13.58.1
5.14.21-150500.13.58.1
kernel-source-rt
SUSE:Linux Enterprise Micro 5.5
From an advisory covering 561 CVEs
 before 5.14.21-150500.13.58.1
5.14.21-150500.13.58.1
kernel-livepatch-SLE15-SP5-RT_Update_16
SUSE:Linux Enterprise Live Patching 15 SP5
From an advisory covering 561 CVEs
 before 1-150500.11.3.1
1-150500.11.3.1
kernel-rt
SUSE:Real Time Module 15 SP5
From an advisory covering 561 CVEs
 before 5.14.21-150500.13.58.1
5.14.21-150500.13.58.1
kernel-rt_debug
SUSE:Real Time Module 15 SP5
From an advisory covering 561 CVEs
 before 5.14.21-150500.13.58.1
5.14.21-150500.13.58.1
kernel-source-rt
SUSE:Real Time Module 15 SP5
From an advisory covering 561 CVEs
 before 5.14.21-150500.13.58.1
5.14.21-150500.13.58.1
kernel-syms-rt
SUSE:Real Time Module 15 SP5
From an advisory covering 561 CVEs
 before 5.14.21-150500.13.58.1
5.14.21-150500.13.58.1
kernel-rt
openSUSE:Leap 15.5
From an advisory covering 561 CVEs
 before 5.14.21-150500.13.58.1
5.14.21-150500.13.58.1
kernel-rt_debug
openSUSE:Leap 15.5
From an advisory covering 561 CVEs
 before 5.14.21-150500.13.58.1
5.14.21-150500.13.58.1
kernel-source-rt
openSUSE:Leap 15.5
From an advisory covering 561 CVEs
 before 5.14.21-150500.13.58.1
5.14.21-150500.13.58.1
kernel-syms-rt
openSUSE:Leap 15.5
From an advisory covering 561 CVEs
 before 5.14.21-150500.13.58.1
5.14.21-150500.13.58.1
kernel-default
SUSE:Linux Enterprise Micro 5.5
From an advisory covering 557 CVEs
 before 5.14.21-150500.55.68.1
5.14.21-150500.55.68.1
kernel-default-base
SUSE:Linux Enterprise Micro 5.5
From an advisory covering 557 CVEs
 before 5.14.21-150500.55.68.1.150500.6.31.1
5.14.21-150500.55.68.1.150500.6.31.1
kernel-64kb
SUSE:Linux Enterprise Module for Basesystem 15 SP5
From an advisory covering 557 CVEs
 before 5.14.21-150500.55.68.1
5.14.21-150500.55.68.1
kernel-default
SUSE:Linux Enterprise Module for Basesystem 15 SP5
From an advisory covering 557 CVEs
 before 5.14.21-150500.55.68.1
5.14.21-150500.55.68.1
kernel-default-base
SUSE:Linux Enterprise Module for Basesystem 15 SP5
From an advisory covering 557 CVEs
 before 5.14.21-150500.55.68.1.150500.6.31.1
5.14.21-150500.55.68.1.150500.6.31.1
kernel-source
SUSE:Linux Enterprise Module for Basesystem 15 SP5
From an advisory covering 557 CVEs
 before 5.14.21-150500.55.68.1
5.14.21-150500.55.68.1
kernel-zfcpdump
SUSE:Linux Enterprise Module for Basesystem 15 SP5
From an advisory covering 557 CVEs
 before 5.14.21-150500.55.68.1
5.14.21-150500.55.68.1
kernel-docs
SUSE:Linux Enterprise Module for Development Tools 15 SP5
From an advisory covering 557 CVEs
 before 5.14.21-150500.55.68.1
5.14.21-150500.55.68.1
kernel-obs-build
SUSE:Linux Enterprise Module for Development Tools 15 SP5
From an advisory covering 557 CVEs
 before 5.14.21-150500.55.68.1
5.14.21-150500.55.68.1
kernel-source
SUSE:Linux Enterprise Module for Development Tools 15 SP5
From an advisory covering 557 CVEs
 before 5.14.21-150500.55.68.1
5.14.21-150500.55.68.1
kernel-syms
SUSE:Linux Enterprise Module for Development Tools 15 SP5
From an advisory covering 557 CVEs
 before 5.14.21-150500.55.68.1
5.14.21-150500.55.68.1
kernel-default
SUSE:Linux Enterprise Module for Legacy 15 SP5
From an advisory covering 557 CVEs
 before 5.14.21-150500.55.68.1
5.14.21-150500.55.68.1
kernel-default
SUSE:Linux Enterprise Live Patching 15 SP5
From an advisory covering 557 CVEs
 before 5.14.21-150500.55.68.1
5.14.21-150500.55.68.1
kernel-livepatch-SLE15-SP5_Update_15
SUSE:Linux Enterprise Live Patching 15 SP5
From an advisory covering 557 CVEs
 before 1-150500.11.3.1
1-150500.11.3.1
kernel-default
SUSE:Linux Enterprise High Availability Extension 15 SP5
From an advisory covering 557 CVEs
 before 5.14.21-150500.55.68.1
5.14.21-150500.55.68.1
kernel-default
SUSE:Linux Enterprise Workstation Extension 15 SP5
From an advisory covering 557 CVEs
 before 5.14.21-150500.55.68.1
5.14.21-150500.55.68.1
dtb-aarch64
openSUSE:Leap 15.5
From an advisory covering 557 CVEs
 before 5.14.21-150500.55.68.1
5.14.21-150500.55.68.1
kernel-64kb
openSUSE:Leap 15.5
From an advisory covering 557 CVEs
 before 5.14.21-150500.55.68.1
5.14.21-150500.55.68.1
kernel-debug
openSUSE:Leap 15.5
From an advisory covering 557 CVEs
 before 5.14.21-150500.55.68.1
5.14.21-150500.55.68.1
kernel-default
openSUSE:Leap 15.5
From an advisory covering 557 CVEs
 before 5.14.21-150500.55.68.1
5.14.21-150500.55.68.1
kernel-default-base
openSUSE:Leap 15.5
From an advisory covering 557 CVEs
 before 5.14.21-150500.55.68.1.150500.6.31.1
5.14.21-150500.55.68.1.150500.6.31.1
kernel-docs
openSUSE:Leap 15.5
From an advisory covering 557 CVEs
 before 5.14.21-150500.55.68.1
5.14.21-150500.55.68.1
kernel-kvmsmall
openSUSE:Leap 15.5
From an advisory covering 557 CVEs
 before 5.14.21-150500.55.68.1
5.14.21-150500.55.68.1
kernel-obs-build
openSUSE:Leap 15.5
From an advisory covering 557 CVEs
 before 5.14.21-150500.55.68.1
5.14.21-150500.55.68.1
kernel-obs-qa
openSUSE:Leap 15.5
From an advisory covering 557 CVEs
 before 5.14.21-150500.55.68.1
5.14.21-150500.55.68.1
kernel-source
openSUSE:Leap 15.5
From an advisory covering 557 CVEs
 before 5.14.21-150500.55.68.1
5.14.21-150500.55.68.1
kernel-syms
openSUSE:Leap 15.5
From an advisory covering 557 CVEs
 before 5.14.21-150500.55.68.1
5.14.21-150500.55.68.1
kernel-zfcpdump
openSUSE:Leap 15.5
From an advisory covering 557 CVEs
 before 5.14.21-150500.55.68.1
5.14.21-150500.55.68.1
kernel-default
SUSE:Linux Micro 6.0
From an advisory covering 848 CVEs
 before 6.4.0-18.1
6.4.0-18.1
kernel-default-base
SUSE:Linux Micro 6.0
From an advisory covering 848 CVEs
 before 6.4.0-17.1.1.51
6.4.0-17.1.1.51
kernel-kvmsmall
SUSE:Linux Micro 6.0
From an advisory covering 848 CVEs
 before 6.4.0-18.1
6.4.0-18.1
kernel-source
SUSE:Linux Micro 6.0
From an advisory covering 848 CVEs
 before 6.4.0-18.1
6.4.0-18.1
kernel-rt
SUSE:Linux Micro 6.0
From an advisory covering 826 CVEs
 before 6.4.0-9.1
6.4.0-9.1
kernel-source-rt
SUSE:Linux Micro 6.0
From an advisory covering 826 CVEs
 before 6.4.0-9.1
6.4.0-9.1
linux-hwe-edge
Ubuntu:16.04:LTS
 All versions, plus listed versions
4.8.0-28.30~16.04.14.8.0-30.32~16.04.14.8.0-32.34~16.04.14.8.0-34.36~16.04.14.10.0-14.16~16.04.1
Show 18 moreShow less
4.10.0-19.21~16.04.14.10.0-20.22~16.04.14.10.0-21.23~16.04.14.10.0-22.24~16.04.14.10.0-24.28~16.04.14.10.0-26.30~16.04.14.11.0-13.19~16.04.14.11.0-14.20~16.04.14.13.0-16.19~16.04.34.13.0-17.20~16.04.14.13.0-19.22~16.04.14.13.0-21.24~16.04.14.13.0-25.29~16.04.24.15.0-13.14~16.04.14.15.0-15.16~16.04.14.15.0-20.21~16.04.14.15.0-22.24~16.04.14.15.0-23.25~16.04.1
 None known
linux-aws-5.0
Ubuntu:18.04:LTS
 All versions, plus listed versions
5.0.0-1021.24~18.04.15.0.0-1022.25~18.04.15.0.0-1023.26~18.04.15.0.0-1024.27~18.04.15.0.0-1025.285.0.0-1027.30
 None known
linux-aws-5.3
Ubuntu:18.04:LTS
 All versions, plus listed versions
5.3.0-1016.17~18.04.15.3.0-1017.18~18.04.15.3.0-1019.21~18.04.15.3.0-1023.25~18.04.15.3.0-1028.30~18.04.1
Show 5 moreShow less
5.3.0-1030.32~18.04.15.3.0-1032.34~18.04.25.3.0-1033.355.3.0-1034.365.3.0-1035.37
 None known
linux-azure
Ubuntu:18.04:LTS
 All versions, plus listed versions
4.15.0-1002.24.15.0-1003.34.15.0-1004.44.15.0-1008.84.15.0-1009.9
Show 39 moreShow less
4.15.0-1012.124.15.0-1013.134.15.0-1014.144.15.0-1018.184.15.0-1019.194.15.0-1021.214.15.0-1022.234.15.0-1023.244.15.0-1025.264.15.0-1028.294.15.0-1030.314.15.0-1031.324.15.0-1032.334.15.0-1035.364.15.0-1036.384.15.0-1037.394.18.0-1011.11~18.04.14.18.0-1013.13~18.04.14.18.0-1014.14~18.04.14.18.0-1018.18~18.04.14.18.0-1019.19~18.04.14.18.0-1020.20~18.04.14.18.0-1023.24~18.04.14.18.0-1024.25~18.04.14.18.0-1025.27~18.04.15.0.0-1014.14~18.04.15.0.0-1016.17~18.04.15.0.0-1018.19~18.04.15.0.0-1020.21~18.04.15.0.0-1022.23~18.04.15.0.0-1023.24~18.04.15.0.0-1025.27~18.04.15.0.0-1027.29~18.04.15.0.0-1028.30~18.04.15.0.0-1029.31~18.04.15.0.0-1031.335.0.0-1032.345.0.0-1035.375.0.0-1036.38
 None known
linux-azure-5.3
Ubuntu:18.04:LTS
 All versions, plus listed versions
5.3.0-1007.8~18.04.15.3.0-1008.9~18.04.15.3.0-1009.10~18.04.15.3.0-1010.11~18.04.15.3.0-1012.13~18.04.1
Show 11 moreShow less
5.3.0-1013.14~18.04.15.3.0-1016.17~18.04.15.3.0-1018.19~18.04.15.3.0-1019.20~18.04.15.3.0-1020.21~18.04.15.3.0-1022.23~18.04.15.3.0-1028.29~18.04.15.3.0-1031.32~18.04.15.3.0-1032.33~18.04.15.3.0-1034.35~18.04.15.3.0-1035.36
 None known
linux-azure-edge
Ubuntu:18.04:LTS
 All versions, plus listed versions
4.18.0-1006.6~18.04.14.18.0-1007.7~18.04.14.18.0-1008.8~18.04.15.0.0-1012.12~18.04.2
 None known
linux-gcp
Ubuntu:18.04:LTS
 All versions, plus listed versions
4.15.0-1001.14.15.0-1003.34.15.0-1005.54.15.0-1006.64.15.0-1008.8
Show 33 moreShow less
4.15.0-1009.94.15.0-1010.104.15.0-1014.144.15.0-1015.154.15.0-1017.184.15.0-1018.194.15.0-1019.204.15.0-1021.224.15.0-1023.244.15.0-1024.254.15.0-1025.264.15.0-1026.274.15.0-1027.284.15.0-1028.294.15.0-1029.314.15.0-1030.324.15.0-1032.344.15.0-1033.354.15.0-1034.364.15.0-1036.384.15.0-1037.394.15.0-1040.424.15.0-1042.454.15.0-1044.705.0.0-1020.20~18.04.15.0.0-1021.21~18.04.15.0.0-1025.26~18.04.15.0.0-1026.27~18.04.15.0.0-1028.29~18.04.15.0.0-1029.30~18.04.15.0.0-1031.325.0.0-1033.345.0.0-1034.35
 None known
linux-gcp-5.3
Ubuntu:18.04:LTS
 All versions, plus listed versions
5.3.0-1008.9~18.04.15.3.0-1009.10~18.04.15.3.0-1010.11~18.04.15.3.0-1012.13~18.04.15.3.0-1014.15~18.04.1
Show 8 moreShow less
5.3.0-1016.17~18.04.15.3.0-1017.18~18.04.15.3.0-1018.19~18.04.15.3.0-1020.22~18.04.15.3.0-1026.28~18.04.15.3.0-1029.31~18.04.15.3.0-1030.32~18.04.15.3.0-1032.34~18.04.1
 None known
linux-gke-4.15
Ubuntu:18.04:LTS
 All versions, plus listed versions
4.15.0-1030.324.15.0-1032.344.15.0-1033.354.15.0-1034.364.15.0-1036.38
Show 28 moreShow less
4.15.0-1037.394.15.0-1040.424.15.0-1041.434.15.0-1042.444.15.0-1044.464.15.0-1045.484.15.0-1046.494.15.0-1048.514.15.0-1049.524.15.0-1050.534.15.0-1052.554.15.0-1055.584.15.0-1057.604.15.0-1058.614.15.0-1059.624.15.0-1063.664.15.0-1064.674.15.0-1066.694.15.0-1067.704.15.0-1069.724.15.0-1070.734.15.0-1072.764.15.0-1073.784.15.0-1074.794.15.0-1076.814.15.0-1077.824.15.0-1078.834.15.0-1079.84
 None known
linux-gke-5.4
Ubuntu:18.04:LTS
 All versions, plus listed versions
5.4.0-1025.25~18.04.15.4.0-1027.28~18.04.15.4.0-1029.31~18.04.15.4.0-1030.32~18.04.15.4.0-1032.34~18.04.1
Show 32 moreShow less
5.4.0-1033.35~18.04.15.4.0-1035.37~18.04.15.4.0-1036.38~18.04.15.4.0-1037.39~18.04.15.4.0-1039.41~18.04.15.4.0-1040.42~18.04.15.4.0-1042.44~18.04.15.4.0-1043.45~18.04.15.4.0-1044.46~18.04.15.4.0-1046.48~18.04.15.4.0-1049.52~18.04.15.4.0-1051.54~18.04.15.4.0-1052.55~18.04.15.4.0-1053.56~18.04.15.4.0-1054.57~18.04.15.4.0-1055.58~18.04.15.4.0-1056.59~18.04.15.4.0-1057.60~18.04.15.4.0-1059.62~18.04.15.4.0-1061.64~18.04.15.4.0-1062.65~18.04.15.4.0-1063.66~18.04.15.4.0-1065.68~18.04.15.4.0-1066.69~18.04.15.4.0-1067.70~18.04.15.4.0-1068.71~18.04.15.4.0-1071.76~18.04.35.4.0-1072.77~18.04.15.4.0-1074.79~18.04.15.4.0-1076.82~18.04.15.4.0-1078.84~18.04.15.4.0-1080.86~18.04.1
 None known
linux-gkeop-5.4
Ubuntu:18.04:LTS
 All versions, plus listed versions
5.4.0-1001.15.4.0-1003.35.4.0-1004.55.4.0-1005.65.4.0-1007.8~18.04.1
Show 32 moreShow less
5.4.0-1008.9~18.04.15.4.0-1009.10~18.04.15.4.0-1010.11~18.04.15.4.0-1011.12~18.04.25.4.0-1012.13~18.04.15.4.0-1013.14~18.04.15.4.0-1014.15~18.04.15.4.0-1015.16~18.04.15.4.0-1016.17~18.04.15.4.0-1018.19~18.04.15.4.0-1021.22~18.04.15.4.0-1022.23~18.04.15.4.0-1023.24~18.04.15.4.0-1024.25~18.04.15.4.0-1025.26~18.04.15.4.0-1026.27~18.04.15.4.0-1027.28~18.04.15.4.0-1029.30~18.04.25.4.0-1031.32~18.04.15.4.0-1032.33~18.04.15.4.0-1033.34~18.04.15.4.0-1034.35~18.04.15.4.0-1036.37~18.04.15.4.0-1037.38~18.04.15.4.0-1038.39~18.04.15.4.0-1039.40~18.04.15.4.0-1040.41~18.04.15.4.0-1043.44~18.04.15.4.0-1046.48~18.04.15.4.0-1048.51~18.04.15.4.0-1049.52~18.04.15.4.0-1051.54~18.04.1
 None known
linux-hwe
Ubuntu:18.04:LTS
 All versions, plus listed versions
4.18.0-13.14~18.04.14.18.0-14.15~18.04.14.18.0-15.16~18.04.14.18.0-16.17~18.04.14.18.0-17.18~18.04.1
Show 38 moreShow less
4.18.0-18.19~18.04.14.18.0-20.21~18.04.14.18.0-21.22~18.04.14.18.0-22.23~18.04.14.18.0-24.25~18.04.14.18.0-25.26~18.04.15.0.0-23.24~18.04.15.0.0-25.26~18.04.15.0.0-27.28~18.04.15.0.0-29.31~18.04.15.0.0-31.33~18.04.15.0.0-32.34~18.04.25.0.0-35.38~18.04.15.0.0-36.39~18.04.15.0.0-37.40~18.04.15.3.0-26.28~18.04.15.3.0-28.30~18.04.15.3.0-40.32~18.04.15.3.0-42.34~18.04.15.3.0-45.37~18.04.15.3.0-46.38~18.04.15.3.0-51.44~18.04.25.3.0-53.47~18.04.15.3.0-59.53~18.04.15.3.0-61.55~18.04.15.3.0-62.56~18.04.15.3.0-64.58~18.04.15.3.0-65.595.3.0-66.605.3.0-67.615.3.0-68.635.3.0-69.655.3.0-70.665.3.0-72.685.3.0-73.695.3.0-74.705.3.0-75.715.3.0-76.72
 None known
linux-oem
Ubuntu:18.04:LTS
 All versions, plus listed versions
4.15.0-1002.34.15.0-1004.54.15.0-1006.94.15.0-1008.114.15.0-1009.12
Show 45 moreShow less
4.15.0-1012.154.15.0-1013.164.15.0-1015.184.15.0-1017.204.15.0-1018.214.15.0-1021.244.15.0-1024.294.15.0-1026.314.15.0-1028.334.15.0-1030.354.15.0-1033.384.15.0-1034.394.15.0-1035.404.15.0-1036.414.15.0-1038.434.15.0-1039.444.15.0-1043.484.15.0-1045.504.15.0-1050.574.15.0-1056.654.15.0-1057.664.15.0-1059.684.15.0-1063.724.15.0-1064.734.15.0-1065.754.15.0-1066.764.15.0-1067.774.15.0-1069.794.15.0-1073.834.15.0-1076.864.15.0-1079.894.15.0-1080.904.15.0-1081.914.15.0-1087.974.15.0-1090.1004.15.0-1091.1014.15.0-1093.1034.15.0-1094.1044.15.0-1096.1064.15.0-1097.1074.15.0-1099.1094.15.0-1100.1104.15.0-1101.1124.15.0-1102.1134.15.0-1103.114
 None known
linux-oracle-5.0
Ubuntu:18.04:LTS
 All versions, plus listed versions
5.0.0-1007.12~18.04.15.0.0-1008.13~18.04.15.0.0-1009.14~18.04.15.0.0-1010.15~18.04.15.0.0-1011.165.0.0-1013.185.0.0-1014.19
 None known
linux-oracle-5.3
Ubuntu:18.04:LTS
 All versions, plus listed versions
5.3.0-1011.12~18.04.15.3.0-1013.14~18.04.15.3.0-1014.15~18.04.15.3.0-1016.18~18.04.15.3.0-1018.20~18.04.1
Show 4 moreShow less
5.3.0-1024.26~18.04.15.3.0-1027.29~18.04.15.3.0-1028.30~18.04.15.3.0-1030.32~18.04.1
 None known
linux-aws-5.11
Ubuntu:20.04:LTS
 All versions, plus listed versions
5.11.0-1009.9~20.04.25.11.0-1014.15~20.04.15.11.0-1016.17~20.04.15.11.0-1017.18~20.04.15.11.0-1019.20~20.04.1
Show 7 moreShow less
5.11.0-1020.21~20.04.25.11.0-1021.22~20.04.25.11.0-1022.23~20.04.15.11.0-1023.24~20.04.15.11.0-1025.27~20.04.15.11.0-1027.30~20.04.15.11.0-1028.31~20.04.1
 None known
linux-aws-5.13
Ubuntu:20.04:LTS
 All versions, plus listed versions
5.13.0-1008.9~20.04.25.13.0-1011.12~20.04.15.13.0-1012.13~20.04.15.13.0-1014.15~20.04.15.13.0-1017.19~20.04.1
Show 8 moreShow less
5.13.0-1019.21~20.04.15.13.0-1021.23~20.04.25.13.0-1022.24~20.04.15.13.0-1023.25~20.04.15.13.0-1025.27~20.04.15.13.0-1028.31~20.04.15.13.0-1029.32~20.04.15.13.0-1031.35~20.04.1
 None known
linux-aws-5.8
Ubuntu:20.04:LTS
 All versions, plus listed versions
5.8.0-1035.37~20.04.15.8.0-1038.40~20.04.15.8.0-1041.43~20.04.15.8.0-1042.44~20.04.1
 None known
linux-azure-5.11
Ubuntu:20.04:LTS
 All versions, plus listed versions
5.11.0-1007.7~20.04.25.11.0-1012.13~20.04.15.11.0-1013.14~20.04.15.11.0-1015.16~20.04.15.11.0-1017.18~20.04.1
Show 8 moreShow less
5.11.0-1019.20~20.04.15.11.0-1020.21~20.04.15.11.0-1021.22~20.04.15.11.0-1022.23~20.04.15.11.0-1023.24~20.04.15.11.0-1025.27~20.04.15.11.0-1027.30~20.04.15.11.0-1028.31~20.04.2
 None known
linux-azure-5.13
Ubuntu:20.04:LTS
 All versions, plus listed versions
5.13.0-1009.10~20.04.25.13.0-1012.14~20.04.15.13.0-1013.15~20.04.15.13.0-1014.16~20.04.15.13.0-1017.19~20.04.1
Show 7 moreShow less
5.13.0-1021.24~20.04.15.13.0-1022.26~20.04.15.13.0-1023.27~20.04.15.13.0-1025.29~20.04.15.13.0-1028.33~20.04.15.13.0-1029.34~20.04.15.13.0-1031.37~20.04.1
 None known
linux-azure-5.8
Ubuntu:20.04:LTS
 All versions, plus listed versions
5.8.0-1033.35~20.04.15.8.0-1036.38~20.04.15.8.0-1039.42~20.04.15.8.0-1040.43~20.04.15.8.0-1041.44~20.04.15.8.0-1042.45~20.04.15.8.0-1043.46~20.04.1
 None known
linux-azure-fde
Ubuntu:20.04:LTS
 All versions, plus listed versions
5.4.0-1063.66+cvm2.25.4.0-1063.66+cvm3.25.4.0-1064.67+cvm1.15.4.0-1065.68+cvm2.15.4.0-1067.70+cvm1.1
Show 21 moreShow less
5.4.0-1068.71+cvm1.15.4.0-1069.72+cvm1.15.4.0-1070.73+cvm1.15.4.0-1072.75+cvm1.15.4.0-1073.76+cvm1.15.4.0-1074.77+cvm1.15.4.0-1076.79+cvm1.15.4.0-1078.81+cvm1.15.4.0-1080.83+cvm1.15.4.0-1083.87+cvm1.15.4.0-1085.90+cvm1.15.4.0-1085.90+cvm2.15.4.0-1086.91+cvm1.15.4.0-1089.94+cvm1.25.4.0-1090.95+cvm1.15.4.0-1091.96+cvm1.15.4.0-1092.97+cvm1.15.4.0-1095.101+cvm1.15.4.0-1098.104+cvm1.15.4.0-1100.106+cvm1.15.4.0-1103.109+cvm1.1
 None known
linux-gcp-5.11
Ubuntu:20.04:LTS
 All versions, plus listed versions
5.11.0-1009.10~20.04.15.11.0-1014.16~20.04.15.11.0-1017.19~20.04.15.11.0-1018.20~20.04.25.11.0-1020.22~20.04.1
Show 7 moreShow less
5.11.0-1021.23~20.04.15.11.0-1022.24~20.04.15.11.0-1023.25~20.04.15.11.0-1024.26~20.04.15.11.0-1026.29~20.04.15.11.0-1028.32~20.04.15.11.0-1029.33~20.04.3
 None known
linux-gcp-5.13
Ubuntu:20.04:LTS
 All versions, plus listed versions
5.13.0-1008.9~20.04.35.13.0-1012.15~20.04.15.13.0-1013.16~20.04.15.13.0-1015.18~20.04.15.13.0-1019.23~20.04.1
Show 8 moreShow less
5.13.0-1021.25~20.04.15.13.0-1023.28~20.04.15.13.0-1024.29~20.04.15.13.0-1025.30~20.04.15.13.0-1027.32~20.04.15.13.0-1030.36~20.04.15.13.0-1031.37~20.04.15.13.0-1033.40~20.04.1
 None known
linux-gcp-5.8
Ubuntu:20.04:LTS
 All versions, plus listed versions
5.8.0-1032.34~20.04.15.8.0-1035.37~20.04.15.8.0-1038.40~20.04.15.8.0-1039.41
 None known
linux-gke
Ubuntu:20.04:LTS
 All versions, plus listed versions
5.4.0-1033.355.4.0-1035.375.4.0-1036.385.4.0-1037.395.4.0-1039.41
Show 45 moreShow less
5.4.0-1041.435.4.0-1042.445.4.0-1043.455.4.0-1044.465.4.0-1046.485.4.0-1049.525.4.0-1051.545.4.0-1052.555.4.0-1053.565.4.0-1054.575.4.0-1055.585.4.0-1056.595.4.0-1057.605.4.0-1059.625.4.0-1061.645.4.0-1062.655.4.0-1063.665.4.0-1065.685.4.0-1066.695.4.0-1067.705.4.0-1068.715.4.0-1071.765.4.0-1072.775.4.0-1074.795.4.0-1076.825.4.0-1078.845.4.0-1080.865.4.0-1081.875.4.0-1083.895.4.0-1084.905.4.0-1086.935.4.0-1087.945.4.0-1090.975.4.0-1091.985.4.0-1094.1015.4.0-1095.1025.4.0-1096.1035.4.0-1097.1045.4.0-1098.1055.4.0-1099.1065.4.0-1100.1075.4.0-1101.1085.4.0-1102.1095.4.0-1103.1105.4.0-1104.111
 None known
linux-gke-5.15
Ubuntu:20.04:LTS
 All versions, plus listed versions
5.15.0-1011.14~20.04.15.15.0-1014.17~20.04.15.15.0-1015.18~20.04.15.15.0-1016.19~20.04.15.15.0-1019.23~20.04.1
Show 13 moreShow less
5.15.0-1020.25~20.04.15.15.0-1023.28~20.04.25.15.0-1027.32~20.04.15.15.0-1028.33~20.04.15.15.0-1029.34~20.04.15.15.0-1031.36~20.04.15.15.0-1032.37~20.04.15.15.0-1033.38~20.04.15.15.0-1034.39~20.04.15.15.0-1036.41~20.04.15.15.0-1037.42~20.04.15.15.0-1038.43~20.04.15.15.0-1039.44~20.04.1
 None known
linux-hwe-5.11
Ubuntu:20.04:LTS
 All versions, plus listed versions
5.11.0-22.23~20.04.15.11.0-25.27~20.04.15.11.0-27.29~20.04.15.11.0-34.36~20.04.15.11.0-36.40~20.04.1
Show 7 moreShow less
5.11.0-37.41~20.04.25.11.0-38.42~20.04.15.11.0-40.44~20.04.25.11.0-41.45~20.04.15.11.0-43.47~20.04.25.11.0-44.48~20.04.25.11.0-46.51~20.04.1
 None known
linux-hwe-5.13
Ubuntu:20.04:LTS
 All versions, plus listed versions
5.13.0-21.21~20.04.15.13.0-22.22~20.04.15.13.0-23.23~20.04.25.13.0-25.26~20.04.15.13.0-27.29~20.04.1
Show 11 moreShow less
5.13.0-28.31~20.04.15.13.0-30.33~20.04.15.13.0-35.40~20.04.15.13.0-37.42~20.04.15.13.0-39.44~20.04.15.13.0-40.45~20.04.15.13.0-41.46~20.04.15.13.0-44.49~20.04.15.13.0-48.54~20.04.15.13.0-51.58~20.04.15.13.0-52.59~20.04.1
 None known
linux-hwe-5.8
Ubuntu:20.04:LTS
 All versions, plus listed versions
5.8.0-23.24~20.04.15.8.0-25.26~20.04.15.8.0-28.30~20.04.15.8.0-29.31~20.04.15.8.0-31.33~20.04.1
Show 16 moreShow less
5.8.0-33.36~20.04.15.8.0-34.37~20.04.25.8.0-36.40~20.04.15.8.0-38.43~20.04.15.8.0-40.45~20.04.15.8.0-41.46~20.04.15.8.0-43.49~20.04.15.8.0-44.50~20.04.15.8.0-45.51~20.04.15.8.0-48.54~20.04.15.8.0-49.55~20.04.15.8.0-50.56~20.04.15.8.0-53.60~20.04.15.8.0-55.62~20.04.15.8.0-59.66~20.04.15.8.0-63.71~20.04.1
 None known
linux-intel-5.13
Ubuntu:20.04:LTS
 All versions, plus listed versions
5.13.0-1007.75.13.0-1008.85.13.0-1009.95.13.0-1010.105.13.0-1011.115.13.0-1014.155.13.0-1017.19
 None known
linux-oem-5.10
Ubuntu:20.04:LTS
 All versions, plus listed versions
5.10.0-1008.95.10.0-1011.125.10.0-1013.145.10.0-1014.155.10.0-1016.17
Show 21 moreShow less
5.10.0-1017.185.10.0-1019.205.10.0-1021.225.10.0-1022.235.10.0-1023.245.10.0-1025.265.10.0-1026.275.10.0-1029.305.10.0-1032.335.10.0-1033.345.10.0-1034.355.10.0-1038.405.10.0-1044.465.10.0-1045.475.10.0-1049.515.10.0-1050.525.10.0-1051.535.10.0-1052.545.10.0-1053.555.10.0-1055.585.10.0-1057.61
 None known
linux-oem-5.13
Ubuntu:20.04:LTS
 All versions, plus listed versions
5.13.0-1009.105.13.0-1010.115.13.0-1012.165.13.0-1014.185.13.0-1017.21
Show 7 moreShow less
5.13.0-1019.235.13.0-1020.245.13.0-1021.255.13.0-1022.265.13.0-1026.325.13.0-1028.355.13.0-1029.36
 None known
linux-oem-5.14
Ubuntu:20.04:LTS
 All versions, plus listed versions
5.14.0-1004.45.14.0-1005.55.14.0-1007.75.14.0-1008.85.14.0-1010.10
Show 30 moreShow less
5.14.0-1011.115.14.0-1013.135.14.0-1018.195.14.0-1020.225.14.0-1022.245.14.0-1024.265.14.0-1027.305.14.0-1029.325.14.0-1031.345.14.0-1032.355.14.0-1033.365.14.0-1034.375.14.0-1036.405.14.0-1038.425.14.0-1042.475.14.0-1044.495.14.0-1045.515.14.0-1046.535.14.0-1047.545.14.0-1048.555.14.0-1049.565.14.0-1050.575.14.0-1051.585.14.0-1052.595.14.0-1054.615.14.0-1055.625.14.0-1056.635.14.0-1057.645.14.0-1058.665.14.0-1059.67
 None known
linux-oem-5.6
Ubuntu:20.04:LTS
 All versions, plus listed versions
5.6.0-1007.75.6.0-1008.85.6.0-1010.105.6.0-1011.115.6.0-1013.13
Show 24 moreShow less
5.6.0-1017.175.6.0-1018.185.6.0-1020.205.6.0-1021.215.6.0-1023.235.6.0-1026.265.6.0-1027.275.6.0-1028.285.6.0-1031.325.6.0-1032.335.6.0-1033.355.6.0-1034.365.6.0-1035.375.6.0-1036.395.6.0-1039.435.6.0-1042.465.6.0-1047.515.6.0-1048.525.6.0-1050.545.6.0-1052.565.6.0-1053.575.6.0-1054.585.6.0-1055.595.6.0-1056.60
 None known
linux-oracle-5.11
Ubuntu:20.04:LTS
 All versions, plus listed versions
5.11.0-1008.8~20.04.15.11.0-1013.14~20.04.15.11.0-1016.17~20.04.15.11.0-1017.18~20.04.15.11.0-1019.20~20.04.1
Show 7 moreShow less
5.11.0-1020.21~20.04.15.11.0-1021.22~20.04.15.11.0-1022.23~20.04.15.11.0-1023.24~20.04.15.11.0-1025.27~20.04.15.11.0-1027.30~20.04.15.11.0-1028.31~20.04.1
 None known
linux-oracle-5.13
Ubuntu:20.04:LTS
 All versions, plus listed versions
5.13.0-1011.13~20.04.25.13.0-1015.19~20.04.15.13.0-1016.20~20.04.15.13.0-1018.22~20.04.15.13.0-1021.26~20.04.1
Show 7 moreShow less
5.13.0-1025.30~20.04.15.13.0-1027.32~20.04.15.13.0-1028.33~20.04.15.13.0-1030.35~20.04.15.13.0-1033.39~20.04.15.13.0-1034.40~20.04.15.13.0-1036.43~20.04.1
 None known
linux-oracle-5.8
Ubuntu:20.04:LTS
 All versions, plus listed versions
5.8.0-1031.32~20.04.25.8.0-1033.34~20.04.15.8.0-1034.35~20.04.25.8.0-1037.38~20.04.15.8.0-1038.39~20.04.1
 None known
linux-raspi2
Ubuntu:20.04:LTS
 All versions, plus listed versions
5.3.0-1007.85.3.0-1014.165.3.0-1015.175.3.0-1017.195.4.0-1004.45.4.0-1006.6
 None known
linux-riscv
Ubuntu:20.04:LTS
 All versions, plus listed versions
5.4.0-24.285.4.0-26.305.4.0-27.315.4.0-28.325.4.0-30.34
Show 7 moreShow less
5.4.0-31.355.4.0-33.375.4.0-34.385.4.0-36.415.4.0-37.425.4.0-39.445.4.0-40.45
 None known
linux-riscv-5.11
Ubuntu:20.04:LTS
 All versions, plus listed versions
5.11.0-1015.16~20.04.15.11.0-1017.18~20.04.15.11.0-1018.19~20.04.25.11.0-1020.21~20.04.15.11.0-1021.22~20.04.1
Show 8 moreShow less
5.11.0-1022.23~20.04.15.11.0-1023.24~20.04.15.11.0-1024.25~20.04.15.11.0-1026.28~20.04.15.11.0-1028.31~20.04.15.11.0-1029.32~20.04.15.11.0-1030.345.11.0-1031.35
 None known
linux-riscv-5.8
Ubuntu:20.04:LTS
 All versions, plus listed versions
5.8.0-14.16~20.04.15.8.0-14.16~20.04.35.8.0-16.18~20.04.15.8.0-17.19~20.04.15.8.0-18.20~20.04.1
Show 5 moreShow less
5.8.0-20.22~20.04.15.8.0-22.24~20.04.15.8.0-25.27~20.04.15.8.0-26.28~20.04.15.8.0-29.31~20.04.1
 None known
linux-allwinner-5.19
Ubuntu:22.04:LTS
 All versions, plus listed versions
5.19.0-1007.7~22.04.15.19.0-1009.9~22.04.15.19.0-1010.10~22.04.15.19.0-1011.11~22.04.15.19.0-1012.12~22.04.15.19.0-1013.13~22.04.15.19.0-1014.14~22.04.15.19.0-1015.15~22.04.1
 None known
linux-aws-5.19
Ubuntu:22.04:LTS
 All versions, plus listed versions
5.19.0-1019.20~22.04.15.19.0-1020.21~22.04.15.19.0-1022.23~22.04.15.19.0-1023.24~22.04.15.19.0-1024.25~22.04.1
Show 5 moreShow less
5.19.0-1025.26~22.04.15.19.0-1026.27~22.04.15.19.0-1027.28~22.04.15.19.0-1028.29~22.04.15.19.0-1029.30~22.04.1
 None known
linux-aws-6.2
Ubuntu:22.04:LTS
 All versions, plus listed versions
6.2.0-1005.5~22.04.16.2.0-1006.6~22.04.16.2.0-1007.7~22.04.16.2.0-1008.8~22.04.16.2.0-1009.9~22.04.3
Show 9 moreShow less
6.2.0-1010.10~22.04.16.2.0-1011.11~22.04.16.2.0-1012.12~22.04.16.2.0-1013.13~22.04.16.2.0-1014.14~22.04.16.2.0-1015.15~22.04.16.2.0-1016.16~22.04.16.2.0-1017.17~22.04.16.2.0-1018.18~22.04.1
 None known
linux-aws-6.5
Ubuntu:22.04:LTS
 All versions, plus listed versions
6.5.0-1008.8~22.04.16.5.0-1010.10~22.04.16.5.0-1011.11~22.04.16.5.0-1012.12~22.04.16.5.0-1014.14~22.04.1
Show 9 moreShow less
6.5.0-1015.15~22.04.16.5.0-1016.16~22.04.16.5.0-1017.17~22.04.26.5.0-1018.18~22.04.16.5.0-1020.20~22.04.16.5.0-1021.21~22.04.16.5.0-1022.22~22.04.16.5.0-1023.23~22.04.16.5.0-1024.24~22.04.1
 None known
linux-azure-5.19
Ubuntu:22.04:LTS
 All versions, plus listed versions
5.19.0-1020.21~22.04.15.19.0-1021.22~22.04.15.19.0-1022.23~22.04.15.19.0-1023.24~22.04.15.19.0-1025.28~22.04.15.19.0-1026.29~22.04.15.19.0-1027.30~22.04.2
 None known
linux-azure-6.2
Ubuntu:22.04:LTS
 All versions, plus listed versions
6.2.0-1005.5~22.04.16.2.0-1006.6~22.04.16.2.0-1007.7~22.04.16.2.0-1008.8~22.04.16.2.0-1009.9~22.04.3
Show 8 moreShow less
6.2.0-1011.11~22.04.16.2.0-1012.12~22.04.16.2.0-1014.14~22.04.16.2.0-1015.15~22.04.16.2.0-1016.16~22.04.16.2.0-1017.17~22.04.16.2.0-1018.18~22.04.16.2.0-1019.19~22.04.1
 None known
linux-azure-6.5
Ubuntu:22.04:LTS
 All versions, plus listed versions
6.5.0-1007.7~22.04.16.5.0-1009.9~22.04.16.5.0-1010.10~22.04.16.5.0-1011.11~22.04.16.5.0-1015.15~22.04.1
Show 9 moreShow less
6.5.0-1016.16~22.04.16.5.0-1017.17~22.04.16.5.0-1018.19~22.04.26.5.0-1019.20~22.04.16.5.0-1021.22~22.04.16.5.0-1022.23~22.04.16.5.0-1023.24~22.04.16.5.0-1024.25~22.04.16.5.0-1025.26~22.04.1
 None known
linux-azure-fde-5.19
Ubuntu:22.04:LTS
 All versions, plus listed versions
5.19.0-1025.28~22.04.1.15.19.0-1026.29~22.04.1.15.19.0-1027.30~22.04.2.1
 None known
linux-azure-fde-6.2
Ubuntu:22.04:LTS
 All versions, plus listed versions
6.2.0-1008.8~22.04.1.16.2.0-1009.9~22.04.3.16.2.0-1011.11~22.04.1.16.2.0-1012.12~22.04.1.16.2.0-1014.14~22.04.1.1
Show 5 moreShow less
6.2.0-1015.15~22.04.1.16.2.0-1016.16~22.04.1.16.2.0-1017.17~22.04.1.16.2.0-1018.18~22.04.1.16.2.0-1019.19~22.04.1.1
 None known
linux-gcp-5.19
Ubuntu:22.04:LTS
 All versions, plus listed versions
5.19.0-1020.22~22.04.25.19.0-1021.23~22.04.15.19.0-1022.24~22.04.15.19.0-1024.26~22.04.15.19.0-1025.27~22.04.15.19.0-1026.28~22.04.15.19.0-1027.29~22.04.15.19.0-1030.32~22.04.1
 None known
linux-gcp-6.2
Ubuntu:22.04:LTS
 All versions, plus listed versions
6.2.0-1009.9~22.04.36.2.0-1010.10~22.04.16.2.0-1011.11~22.04.16.2.0-1011.11~22.04.36.2.0-1012.12~22.04.1
Show 7 moreShow less
6.2.0-1013.13~22.04.16.2.0-1014.14~22.04.16.2.0-1016.18~22.04.16.2.0-1017.19~22.04.16.2.0-1018.20~22.04.16.2.0-1019.21~22.04.16.2.0-1021.23~22.04.1
 None known
linux-gcp-6.5
Ubuntu:22.04:LTS
 All versions, plus listed versions
6.5.0-1010.10~22.04.36.5.0-1011.11~22.04.16.5.0-1013.13~22.04.16.5.0-1014.14~22.04.16.5.0-1015.15~22.04.1
Show 8 moreShow less
6.5.0-1016.16~22.04.16.5.0-1017.17~22.04.16.5.0-1018.18~22.04.16.5.0-1020.20~22.04.16.5.0-1022.24~22.04.16.5.0-1023.25~22.04.16.5.0-1024.26~22.04.16.5.0-1025.27~22.04.1
 None known
linux-hwe-5.19
Ubuntu:22.04:LTS
 All versions, plus listed versions
5.19.0-28.29~22.04.15.19.0-32.33~22.04.15.19.0-35.36~22.04.15.19.0-38.39~22.04.15.19.0-40.41~22.04.1
Show 6 moreShow less
5.19.0-41.42~22.04.15.19.0-42.43~22.04.15.19.0-43.44~22.04.15.19.0-45.46~22.04.15.19.0-46.47~22.04.15.19.0-50.50
 None known
linux-hwe-6.2
Ubuntu:22.04:LTS
 All versions, plus listed versions
6.2.0-25.25~22.04.26.2.0-26.26~22.04.16.2.0-31.31~22.04.16.2.0-32.32~22.04.16.2.0-33.33~22.04.1
Show 5 moreShow less
6.2.0-34.34~22.04.16.2.0-35.35~22.04.16.2.0-36.37~22.04.16.2.0-37.38~22.04.16.2.0-39.40~22.04.1
 None known
linux-hwe-6.5
Ubuntu:22.04:LTS
 All versions, plus listed versions
6.5.0-14.14~22.04.16.5.0-15.15~22.04.16.5.0-17.17~22.04.16.5.0-18.18~22.04.16.5.0-21.21~22.04.1
Show 8 moreShow less
6.5.0-25.25~22.04.16.5.0-26.26~22.04.16.5.0-27.28~22.04.16.5.0-28.29~22.04.16.5.0-35.35~22.04.16.5.0-41.41~22.04.26.5.0-44.44~22.04.16.5.0-45.45~22.04.1
 None known
linux-intel-iot-realtime
Ubuntu:22.04:LTS
 All versions, plus listed versions
5.15.0-1073.75
 None known
linux-lowlatency-hwe-5.19
Ubuntu:22.04:LTS
 All versions, plus listed versions
5.19.0-1017.18~22.04.15.19.0-1018.19~22.04.15.19.0-1021.22~22.04.15.19.0-1022.23~22.04.15.19.0-1023.24~22.04.1
Show 5 moreShow less
5.19.0-1024.25~22.04.15.19.0-1025.26~22.04.15.19.0-1027.28~22.04.15.19.0-1028.29~22.04.15.19.0-1030.30
 None known
linux-lowlatency-hwe-6.2
Ubuntu:22.04:LTS
 All versions, plus listed versions
6.2.0-1008.8~22.04.16.2.0-1009.9~22.04.16.2.0-1011.11~22.04.16.2.0-1012.12~22.04.16.2.0-1013.13~22.04.1
Show 5 moreShow less
6.2.0-1014.14~22.04.16.2.0-1015.15~22.04.16.2.0-1016.16~22.04.16.2.0-1017.17~22.04.16.2.0-1018.18~22.04.1
 None known
linux-lowlatency-hwe-6.5
Ubuntu:22.04:LTS
 All versions, plus listed versions
6.5.0-14.14.1~22.04.16.5.0-15.15.1.1~22.04.16.5.0-17.17.1.1.1~22.04.16.5.0-21.21.1~22.04.16.5.0-25.25.1~22.04.1
Show 8 moreShow less
6.5.0-26.26.1~22.04.16.5.0-27.28.1~22.04.16.5.0-28.29.1~22.04.16.5.0-35.35.1~22.04.16.5.0-41.41.1~22.04.16.5.0-42.42.1~22.04.16.5.0-44.44.1~22.04.16.5.0-45.45.1~22.04.1
 None known
linux-nvidia-6.2
Ubuntu:22.04:LTS
 All versions, plus listed versions
6.2.0-1003.3~22.04.16.2.0-1009.96.2.0-1010.106.2.0-1011.116.2.0-1012.126.2.0-1013.136.2.0-1015.15
 None known
linux-nvidia-6.5
Ubuntu:22.04:LTS
 All versions, plus listed versions
6.5.0-1004.46.5.0-1007.76.5.0-1013.136.5.0-1014.146.5.0-1015.15
Show 6 moreShow less
6.5.0-1018.186.5.0-1019.196.5.0-1021.226.5.0-1022.236.5.0-1023.246.5.0-1024.25
 None known
linux-oem-5.17
Ubuntu:22.04:LTS
 All versions, plus listed versions
5.17.0-1003.35.17.0-1004.45.17.0-1006.65.17.0-1011.125.17.0-1012.13
Show 21 moreShow less
5.17.0-1013.145.17.0-1014.155.17.0-1015.165.17.0-1016.175.17.0-1017.185.17.0-1018.195.17.0-1019.205.17.0-1020.215.17.0-1021.225.17.0-1024.255.17.0-1025.265.17.0-1026.275.17.0-1027.285.17.0-1028.295.17.0-1029.305.17.0-1030.315.17.0-1031.325.17.0-1032.335.17.0-1033.345.17.0-1034.355.17.0-1035.36
 None known
linux-oem-6.0
Ubuntu:22.04:LTS
 All versions, plus listed versions
6.0.0-1006.66.0.0-1007.76.0.0-1008.86.0.0-1009.96.0.0-1010.10
Show 11 moreShow less
6.0.0-1011.116.0.0-1012.126.0.0-1013.136.0.0-1014.146.0.0-1015.156.0.0-1016.166.0.0-1017.176.0.0-1018.186.0.0-1019.196.0.0-1020.206.0.0-1021.21
 None known

History

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

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

In short

CVE-2024-26939 is a high vulnerability (CVSS 7.8) in Linux, published May 1, 2024. No source lists public exploit code. EPSS puts the chance of exploitation in the next 30 days at 0.25%, the 16th percentile. Fixed in linux-lts 6.1.89-r0.

References

Show 194 moreShow less
This page doesn't list everything

Left out here: 335 package rows, 1 version, 6,461 references and the rest of 11 source descriptions. The JSON record has them.

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