BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2025
CVE-2022-49179High confidence

block, bfq: don't move oom_bfqq

Linux · Linux

7.8HighCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 1 structured product or package state remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityHighOperational priority:Medium, lowered one band.downgradedsince 12 Aug 2026

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • Exploitation requires an existing local or physical foothold with privileges.
  • EPSS is 0.28% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict local access and enforce least privilege on affected hosts.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs Linux Linux and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: As exposure requiresRemediation target: Within 365 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 1 structured product or package state remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Distribution package intelligence

Release-specific package status

Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

5 package states
Package result overrides the generic status

BlackTree has verified remediation for at least one product or source, but the relevant distribution still reports no fixed package for 1 affected package state shown here. Treat those rows as affected with no fix until that distribution publishes a fixed version.

Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Distribution releaseSource packageVendor stateFixed versionEvidence
Debian trixietrixie · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.5.17.3-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.5.17.3-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.5.17.3-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.5.17.3-1Debian Security Tracker ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-raspi-realtimeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2022-55046

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionPatch only the product branches with a verified fix

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 1 structured product or package state remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
01

What, why and how

In the Linux kernel, the following vulnerability has been resolved: block, bfq: don't move oom_bfqq Our test report a UAF: [ 2073.019181] ================================================================== [ 2073.019188] BUG: KASAN: use-after-free in __bfq_put_async_bfqq+0xa0/0x168 [ 2073.019191] Write of size 8 at addr ffff8000ccf64128 by task rmmod/72584 [ 2073.019192] [ 2073.019196] CPU: 0 PID: 72584 Comm: rmmod Kdump: loaded Not tainted 4.19.90-yk #5 [ 2073.019198] Hardware name: QEMU KVM Virtual Machine, BIOS 0.0.0 02/06/2015 [ 2073.019200] Call trace: [ 2073.019203] dump_backtrace+0x0/0x310 [ 2073.019206] show_stack+0x28/0x38 [ 2073.019210] dump_stack+0xec/0x15c [ 2073.019216] print_address_description+0x68/0x2d0 [ 2073.019220] kasan_report+0x238/0x2f0 [ 2073.019224] __asan_store8+0x88/0xb0 [ 2073.019229] __bfq_put_async_bfqq+0xa0/0x168 [ 2073.019233] bfq_put_async_queues+0xbc/0x208 [ 2073.019236] bfq_pd_offline+0x178/0x238 [ 2073.019240] blkcg_deactivate_policy+0x1f0/0x420 [ 2073.019244] bfq_exit_queue+0x128/0x178 [ 2073.019249] blk_mq_exit_sched+0x12c/0x160 [ 2073.019252] elevator_exit+0xc8/0xd0 [ 2073.019256] blk_exit_queue+0x50/0x88 [ 2073.019259] blk_cleanup_queue+0x228/0x3d8 [ 2073.019267] null_del_dev+0xfc/0x1e0 [null_blk] [ 2073.019274] null_exit+0x90/0x114 [null_blk] [ 2073.019278] __arm64_sys_delete_module+0x358/0x5a0 [ 2073.019282] el0_svc_common+0xc8/0x320 [ 2073.019287] el0_svc_handler+0xf8/0x160 [ 2073.019290] el0_svc+0x10/0x218 [ 2073.019291] [ 2073.019294] Allocated by task 14163: [ 2073.019301] kasan_kmalloc+0xe0/0x190 [ 2073.019305] kmem_cache_alloc_node_trace+0x1cc/0x418 [ 2073.019308] bfq_pd_alloc+0x54/0x118 [ 2073.019313] blkcg_activate_policy+0x250/0x460 [ 2073.019317] bfq_create_group_hierarchy+0x38/0x110 [ 2073.019321] bfq_init_queue+0x6d0/0x948 [ 2073.019325] blk_mq_init_sched+0x1d8/0x390 [ 2073.019330] elevator_switch_mq+0x88/0x170 [ 2073.019334] elevator_switch+0x140/0x270 [ 2073.019338] elv_iosched_store+0x1a4/0x2a0 [ 2073.019342] queue_attr_store+0x90/0xe0 [ 2073.019348] sysfs_kf_write+0xa8/0xe8 [ 2073.019351] kernfs_fop_write+0x1f8/0x378 [ 2073.019359] __vfs_write+0xe0/0x360 [ 2073.019363] vfs_write+0xf0/0x270 [ 2073.019367] ksys_write+0xdc/0x1b8 [ 2073.019371] __arm64_sys_write+0x50/0x60 [ 2073.019375] el0_svc_common+0xc8/0x320 [ 2073.019380] el0_svc_handler+0xf8/0x160 [ 2073.019383] el0_svc+0x10/0x218 [ 2073.019385] [ 2073.019387] Freed by task 72584: [ 2073.019391] __kasan_slab_free+0x120/0x228 [ 2073.019394] kasan_slab_free+0x10/0x18 [ 2073.019397] kfree+0x94/0x368 [ 2073.019400] bfqg_put+0x64/0xb0 [ 2073.019404] bfqg_and_blkg_put+0x90/0xb0 [ 2073.019408] bfq_put_queue+0x220/0x228 [ 2073.019413] __bfq_put_async_bfqq+0x98/0x168 [ 2073.019416] bfq_put_async_queues+0xbc/0x208 [ 2073.019420] bfq_pd_offline+0x178/0x238 [ 2073.019424] blkcg_deactivate_policy+0x1f0/0x420 [ 2073.019429] bfq_exit_queue+0x128/0x178 [ 2073.019433] blk_mq_exit_sched+0x12c/0x160 [ 2073.019437] elevator_exit+0xc8/0xd0 [ 2073.019440] blk_exit_queue+0x50/0x88 [ 2073.019443] blk_cleanup_queue+0x228/0x3d8 [ 2073.019451] null_del_dev+0xfc/0x1e0 [null_blk] [ 2073.019459] null_exit+0x90/0x114 [null_blk] [ 2073.019462] __arm64_sys_delete_module+0x358/0x5a0 [ 2073.019467] el0_svc_common+0xc8/0x320 [ 2073.019471] el0_svc_handler+0xf8/0x160 [ 2073.019474] el0_svc+0x10/0x218 [ 2073.019475] [ 2073.019479] The buggy address belongs to the object at ffff8000ccf63f00 which belongs to the cache kmalloc-1024 of size 1024 [ 2073.019484] The buggy address is located 552 bytes inside of 1024-byte region [ffff8000ccf63f00, ffff8000ccf64300) [ 2073.019486] The buggy address belongs to the page: [ 2073.019492] page:ffff7e000333d800 count:1 mapcount:0 mapping:ffff8000c0003a00 index:0x0 compound_mapcount: 0 [ 2073.020123] flags: 0x7ffff0000008100(slab|head) [ 2073.020403] raw: 07ffff0000008100 ffff7e0003334c08 ffff7e00001f5a08 ffff8000c0003a00 [ 2073.020409] ra ---truncated---

What

In the Linux kernel, the following vulnerability has been resolved: block, bfq: don't move oom_bfqq Our test report a UAF: [ 2073.019181] ================================================================== [ 2073.019188] BUG: KASAN: use-after-free in __bfq_put_async_bfqq+0xa0/0x168 [ 2073.019191] Write of size 8 at addr ffff8000ccf64128 by task rmmod/72584 [ 2073.019192] [ 2073.019196] CPU: 0 PID: 72584 Comm: rmmod Kdump: loaded Not tainted 4.19.90-yk #5 [ 2073.019198] Hardware name: QEMU KVM Virtual Machine, BIOS 0.0.0 02/06/2015 [ 2073.019200] Call trace: [ 2073.019203] dump_backtrace+0x0/0x310 [ 2073.019206] show_stack+0x28/0x38 [ 2073.019210] dump_stack+0xec/0x15c [ 2073.019216] print_address_description+0x68/0x2d0 [ 2073.019220] kasan_report+0x238/0x2f0 [ 2073.019224] __asan_store8+0x88/0xb0 [ 2073.019229] __bfq_put_async_bfqq+0xa0/0x168 [ 2073.019233] bfq_put_async_queues+0xbc/0x208 [ 2073.019236] bfq_pd_offline+0x178/0x238 [ 2073.019240] blkcg_deactivate_policy+0x1f0/0x420 [ 2073.019244] bfq_exit_queue+0x128/0x178 [ 2073.019249] blk_mq_exit_sched+0x12c/0x160 [ 2073.019252] elevator_exit+0xc8/0xd0 [ 2073.019256] blk_exit_queue+0x50/0x88 [ 2073.019259] blk_cleanup_queue+0x228/0x3d8 [ 2073.019267] null_del_dev+0xfc/0x1e0 [null_blk] [ 2073.019274] null_exit+0x90/0x114 [null_blk] [ 2073.019278] __arm64_sys_delete_module+0x358/0x5a0 [ 2073.019282] el0_svc_common+0xc8/0x320 [ 2073.019287] el0_svc_handler+0xf8/0x160 [ 2073.019290] el0_svc+0x10/0x218 [ 2073.019291] [ 2073.019294] Allocated by task 14163: [ 2073.019301] kasan_kmalloc+0xe0/0x190 [ 2073.019305] kmem_cache_alloc_node_trace+0x1cc/0x418 [ 2073.019308] bfq_pd_alloc+0x54/0x118 [ 2073.019313] blkcg_activate_policy+0x250/0x460 [ 2073.019317] bfq_create_group_hierarchy+0x38/0x110 [ 2073.019321] bfq_init_queue+0x6d0/0x948 [ 2073.019325] blk_mq_init_sched+0x1d8/0x390 [ 2073.019330] elevator_switch_mq+0x88/0x170 [ 2073.019334] elevator_switch+0x140/0x270 [ 2073.019338] elv_iosched_store+0x1a4/0x2a0 [ 2073.019342] queue_attr_store+0x90/0xe0 [ 2073.019348] sysfs_kf_write+0xa8/0xe8 [ 2073.019351] kernfs_fop_write+0x1f8/0x378 [ 2073.019359] __vfs_write+0xe0/0x360 [ 2073.019363] vfs_write+0xf0/0x270 [ 2073.019367] ksys_write+0xdc/0x1b8 [ 2073.019371] __arm64_sys_write+0x50/0x60 [ 2073.019375] el0_svc_common+0xc8/0x320 [ 2073.019380] el0_svc_handler+0xf8/0x160 [ 2073.019383] el0_svc+0x10/0x218 [ 2073.019385] [ 2073.019387] Freed by task 72584: [ 2073.019391] __kasan_slab_free+0x120/0x228 [ 2073.019394] kasan_slab_free+0x10/0x18 [ 2073.019397] kfree+0x94/0x368 [ 2073.019400] bfqg_put+0x64/0xb0 [ 2073.019404] bfqg_and_blkg_put+0x90/0xb0 [ 2073.019408] bfq_put_queue+0x220/0x228 [ 2073.019413] __bfq_put_async_bfqq+0x98/0x168 [ 2073.019416] bfq_put_async_queues+0xbc/0x208 [ 2073.019420] bfq_pd_offline+0x178/0x238 [ 2073.019424] blkcg_deactivate_policy+0x1f0/0x420 [ 2073.019429] bfq_exit_queue+0x128/0x178 [ 2073.019433] blk_mq_exit_sched+0x12c/0x160 [ 2073.019437] elevator_exit+0xc8/0xd0 [ 2073.019440] blk_exit_queue+0x50/0x88 [ 2073.019443] blk_cleanup_queue+0x228/0x3d8 [ 2073.019451] null_del_dev+0xfc/0x1e0 [null_blk] [ 2073.019459] null_exit+0x90/0x114 [null_blk] [ 2073.019462] __arm64_sys_delete_module+0x358/0x5a0 [ 2073.019467] el0_svc_common+0xc8/0x320 [ 2073.019471] el0_svc_handler+0xf8/0x160 [ 2073.019474] el0_svc+0x10/0x218 [ 2073.019475] [ 2073.019479] The buggy address belongs to the object at ffff8000ccf63f00 which belongs to the cache kmalloc-1024 of size 1024 [ 2073.019484] The buggy address is located 552 bytes inside of 1024-byte region [ffff8000ccf63f00, ffff8000ccf64300) [ 2073.019486] The buggy address belongs to the page: [ 2073.019492] page:ffff7e000333d800 count:1 mapcount:0 mapping:ffff8000c0003a00 index:0x0 compound_mapcount: 0 [ 2073.020123] flags: 0x7ffff0000008100(slab|head) [ 2073.020403] raw: 07ffff0000008100 ffff7e0003334c08 ffff7e00001f5a08 ffff8000c0003a00 [ 2073.020409] ra ---truncated---

Why

The program can continue using memory after it has been released, producing unsafe and attacker-influenceable behaviour.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

In the Linux kernel, the following vulnerability has been resolved: block, bfq: don't move oom_bfqq Our test report a UAF: [ 2073.019181] ================================================================== [ 2073.019188] BUG: KASAN: use-after-free in __bfq_put_async_bfqq+0xa0/0x168 [ 2073.019191] Write of size 8 at addr ffff8000ccf64128 by task rmmod/72584 [ 2073.019192] [ 2073.019196] CPU: 0 PID: 72584 Comm: rmmod Kdump: loaded Not tainted 4.19.90-yk #5 [ 2073.019198] Hardware name: QEMU KVM Virtual Machine, BIOS 0.0.0 02/06/2015 [ 2073.019200] Call trace: [ 2073.019203] dump_backtrace+0x0/0x310 [ 2073.019206] show_stack+0x28/0x38 [ 2073.019210] dump_stack+0xec/0x15c [ 2073.019216] print_address_description+0x68/0x2d0 [ 2073.019220] kasan_report+0x238/0x2f0 [ 2073.019224] __asan_store8+0x88/0xb0 [ 2073.019229] __bfq_put_async_bfqq+0xa0/0x168 [ 2073.019233] bfq_put_async_queues+0xbc/0x208 [ 2073.019236] bfq_pd_offline+0x178/0x238 [ 2073.019240] blkcg_deactivate_policy+0x1f0/0x420 [ 2073.019244] bfq_exit_queue+0x128/0x178 [ 2073.019249] blk_mq_exit_sched+0x12c/0x160 [ 2073.019252] elevator_exit+0xc8/0xd0 [ 2073.019256] blk_exit_queue+0x50/0x88 [ 2073.019259] blk_cleanup_queue+0x228/0x3d8 [ 2073.019267] null_del_dev+0xfc/0x1e0 [null_blk] [ 2073.019274] null_exit+0x90/0x114 [null_blk] [ 2073.019278] __arm64_sys_delete_module+0x358/0x5a0 [ 2073.019282] el0_svc_common+0xc8/0x320 [ 2073.019287] el0_svc_handler+0xf8/0x160 [ 2073.019290] el0_svc+0x10/0x218 [ 2073.019291] [ 2073.019294] Allocated by task 14163: [ 2073.019301] kasan_kmalloc+0xe0/0x190 [ 2073.019305] kmem_cache_alloc_node_trace+0x1cc/0x418 [ 2073.019308] bfq_pd_alloc+0x54/0x118 [ 2073.019313] blkcg_activate_policy+0x250/0x460 [ 2073.019317] bfq_create_group_hierarchy+0x38/0x110 [ 2073.019321] bfq_init_queue+0x6d0/0x948 [ 2073.019325] blk_mq_init_sched+0x1d8/0x390 [ 2073.019330] elevator_switch_mq+0x88/0x170 [ 2073.019334] elevator_switch+0x140/0x270 [ 2073.019338] elv_iosched_store+0x1a4/0x2a0 [ 2073.019342] queue_attr_store+0x90/0xe0 [ 2073.019348] sysfs_kf_write+0xa8/0xe8 [ 2073.019351] kernfs_fop_write+0x1f8/0x378 [ 2073.019359] __vfs_write+0xe0/0x360 [ 2073.019363] vfs_write+0xf0/0x270 [ 2073.019367] ksys_write+0xdc/0x1b8 [ 2073.019371] __arm64_sys_write+0x50/0x60 [ 2073.019375] el0_svc_common+0xc8/0x320 [ 2073.019380] el0_svc_handler+0xf8/0x160 [ 2073.019383] el0_svc+0x10/0x218 [ 2073.019385] [ 2073.019387] Freed by task 72584: [ 2073.019391] __kasan_slab_free+0x120/0x228 [ 2073.019394] kasan_slab_free+0x10/0x18 [ 2073.019397] kfree+0x94/0x368 [ 2073.019400] bfqg_put+0x64/0xb0 [ 2073.019404] bfqg_and_blkg_put+0x90/0xb0 [ 2073.019408] bfq_put_queue+0x220/0x228 [ 2073.019413] __bfq_put_async_bfqq+0x98/0x168 [ 2073.019416] bfq_put_async_queues+0xbc/0x208 [ 2073.019420] bfq_pd_offline+0x178/0x238 [ 2073.019424] blkcg_deactivate_policy+0x1f0/0x420 [ 2073.019429] bfq_exit_queue+0x128/0x178 [ 2073.019433] blk_mq_exit_sched+0x12c/0x160 [ 2073.019437] elevator_exit+0xc8/0xd0 [ 2073.019440] blk_exit_queue+0x50/0x88 [ 2073.019443] blk_cleanup_queue+0x228/0x3d8 [ 2073.019451] null_del_dev+0xfc/0x1e0 [null_blk] [ 2073.019459] null_exit+0x90/0x114 [null_blk] [ 2073.019462] __arm64_sys_delete_module+0x358/0x5a0 [ 2073.019467] el0_svc_common+0xc8/0x320 [ 2073.019471] el0_svc_handler+0xf8/0x160 [ 2073.019474] el0_svc+0x10/0x218 [ 2073.019475] [ 2073.019479] The buggy address belongs to the object at ffff8000ccf63f00 which belongs to the cache kmalloc-1024 of size 1024 [ 2073.019484] The buggy address is located 552 bytes inside of 1024-byte region [ffff8000ccf63f00, ffff8000ccf64300) [ 2073.019486] The buggy address belongs to the page: [ 2073.019492] page:ffff7e000333d800 count:1 mapcount:0 mapping:ffff8000c0003a00 index:0x0 compound_mapcount: 0 [ 2073.020123] flags: 0x7ffff0000008100(slab|head) [ 2073.020403] raw: 07ffff0000008100 ffff7e0003334c08 ffff7e00001f5a08 ffff8000c0003a00 [ 2073.020409] ra ---truncated---

Why

The program can continue using memory after it has been released, producing unsafe and attacker-influenceable behaviour.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
local access → Use After Free → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Local
Privileges required
Low: a basic authenticated account is required
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-416 ↗

CWE-416: Use After Free. The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory belongs to the code that operates on the new pointer.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVLocalAttack vector: The attacker needs local access to the vulnerable system.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRLowPrivileges required: The attacker needs basic user-level privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CHighConfidentiality impact: A successful attack can cause a major loss.IHighIntegrity impact: A successful attack can cause a major loss.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
The issue can support a local privilege or sandbox boundary transition; normal system utilities may then be available in the gained context.
CWE-416
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

Cyber Security Agency of Singapore · English · CSA-SB-20250305Security Bulletin 5 March 2025

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 5 March 2025, published on 5 March 2025. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-1032Multiples vulnérabilités dans le noyau Linux de SUSE

USE-SU-2025:4141-1 du 19 novembre 2025 https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1 Bulletin de sécurité SUSE SUSE-SU-2025:4149-1 du 20 novembre 2025 https://www.suse.com/support/update/announcement/2025/suse-su-20254149-1 Référence CVE CVE-2022-43945 https://www.cve.org/CVERecord?id=CVE-2022-43945 Référence CVE CVE-2022-48956 https://www.cve.org/CVERecord?id=CVE-2022-48956 Référence CVE CVE-2022-49014 https://www.cve.org/CVERecord?id=CVE-2022-49014 Référence CVE CVE-2022-49053 https://www.cve.org/CVERecord?id=CVE-2022-49053 Référence CVE CVE-2022-49080 https://www.cve.org/CVERecord?id=CVE-2022-49080 Référence CVE CVE-2022-49179 https://www.cve.org/CVERecord?id=CVE-2022-49179 Référence CVE CVE-2022-49465 https://www.cve.org/CVERecord?id=CVE-2022-49465 Référence CVE CVE-2022-49545 https://www.cve.org/CVERecord?id=CVE-2022-49545 Référence CVE CVE-2022-49563 https://www.cve.org/CVERecord?id=CVE-2022-49563 Référence CVE CVE-2022-49564 https://www.cve.org/CVERecord?id=CVE-2022-49564 Référence CVE CVE-2022-50252 https://www.cve.org/CVERecord?id=CVE-2022-50252 Référence CVE CVE-2022-50327 https://www.cve.org/CVERecord?id=CVE-2022-50327 Référence CVE CVE-2022-50334 https://www.cve.org/CVERecord?id=CVE-2022-50334 Référence CVE CVE-2022-50386 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0589Multiples vulnérabilités dans le noyau Linux d'Ubuntu

s://ubuntu.com/security/notices/USN-7627-2 Bulletin de sécurité Ubuntu USN-7628-1 du 08 juillet 2025 https://ubuntu.com/security/notices/USN-7628-1 Bulletin de sécurité Ubuntu LSN-0113-1 du 10 juillet 2025 https://ubuntu.com/security/notices/LSN-0113-1 Référence CVE CVE-2021-47260 https://www.cve.org/CVERecord?id=CVE-2021-47260 Référence CVE CVE-2021-47379 https://www.cve.org/CVERecord?id=CVE-2021-47379 Référence CVE CVE-2021-47576 https://www.cve.org/CVERecord?id=CVE-2021-47576 Référence CVE CVE-2022-3640 https://www.cve.org/CVERecord?id=CVE-2022-3640 Référence CVE CVE-2022-49176 https://www.cve.org/CVERecord?id=CVE-2022-49176 Référence CVE CVE-2022-49179 https://www.cve.org/CVERecord?id=CVE-2022-49179 Référence CVE CVE-2022-49636 https://www.cve.org/CVERecord?id=CVE-2022-49636 Référence CVE CVE-2022-49728 https://www.cve.org/CVERecord?id=CVE-2022-49728 Référence CVE CVE-2022-49909 https://www.cve.org/CVERecord?id=CVE-2022-49909 Référence CVE CVE-2023-53034 https://www.cve.org/CVERecord?id=CVE-2023-53034 Référence CVE CVE-2024-36945 https://www.cve.org/CVERecord?id=CVE-2024-36945 Référence CVE CVE-2024-41070 https://www.cve.org/CVERecord?id=CVE-2024-41070 Référence CVE CVE-2024-42230 https://www.cve.org/CVERecord?id=CVE-2024-42230 Référence CVE CVE-2024-46753 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0547Multiples vulnérabilités dans le noyau Linux de SUSE

-202502140-1 Bulletin de sécurité SUSE SUSE-SU-2025:02142-1 du 26 juin 2025 https://www.suse.com/support/update/announcement/2025/suse-su-202502142-1 Bulletin de sécurité SUSE SUSE-SU-2025:02144-1 du 26 juin 2025 https://www.suse.com/support/update/announcement/2025/suse-su-202502144-1 Bulletin de sécurité SUSE SUSE-SU-2025:02145-1 du 27 juin 2025 https://www.suse.com/support/update/announcement/2025/suse-su-202502145-1 Bulletin de sécurité SUSE SUSE-SU-2025:02146-1 du 27 juin 2025 https://www.suse.com/support/update/announcement/2025/suse-su-202502146-1 Référence CVE CVE-2017-5753 https://www.cve.org/CVERecord?id=CVE-2017-5753 Référence CVE CVE-2022-49179 https://www.cve.org/CVERecord?id=CVE-2022-49179 Référence CVE CVE-2022-49545 https://www.cve.org/CVERecord?id=CVE-2022-49545 Référence CVE CVE-2023-2162 https://www.cve.org/CVERecord?id=CVE-2023-2162 Référence CVE CVE-2023-3567 https://www.cve.org/CVERecord?id=CVE-2023-3567 Référence CVE CVE-2023-52973 https://www.cve.org/CVERecord?id=CVE-2023-52973 Référence CVE CVE-2023-52974 https://www.cve.org/CVERecord?id=CVE-2023-52974 Référence CVE CVE-2023-53000 https://www.cve.org/CVERecord?id=CVE-2023-53000 Référence CVE CVE-2024-40937 https://www.cve.org/CVERecord?id=CVE-2024-40937 Référence CVE CVE-2024-50124 https://www.cve.org/CVERecord?id=CVE-

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0449Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2022-49110 Référence CVE CVE-2022-49111 https://www.cve.org/CVERecord?id=CVE-2022-49111 Référence CVE CVE-2022-49118 https://www.cve.org/CVERecord?id=CVE-2022-49118 Référence CVE CVE-2022-49121 https://www.cve.org/CVERecord?id=CVE-2022-49121 Référence CVE CVE-2022-49137 https://www.cve.org/CVERecord?id=CVE-2022-49137 Référence CVE CVE-2022-49139 https://www.cve.org/CVERecord?id=CVE-2022-49139 Référence CVE CVE-2022-49171 https://www.cve.org/CVERecord?id=CVE-2022-49171 Référence CVE CVE-2022-49175 https://www.cve.org/CVERecord?id=CVE-2022-49175 Référence CVE CVE-2022-49176 https://www.cve.org/CVERecord?id=CVE-2022-49176 Référence CVE CVE-2022-49179 https://www.cve.org/CVERecord?id=CVE-2022-49179 Référence CVE CVE-2022-49188 https://www.cve.org/CVERecord?id=CVE-2022-49188 Référence CVE CVE-2022-49197 https://www.cve.org/CVERecord?id=CVE-2022-49197 Référence CVE CVE-2022-49205 https://www.cve.org/CVERecord?id=CVE-2022-49205 Référence CVE CVE-2022-49232 https://www.cve.org/CVERecord?id=CVE-2022-49232 Référence CVE CVE-2022-49290 https://www.cve.org/CVERecord?id=CVE-2022-49290 Référence CVE CVE-2022-49305 https://www.cve.org/CVERecord?id=CVE-2022-49305 Référence CVE CVE-2022-49325 https://www.cve.org/CVERecord?id=CVE-2022-49325 Référence CVE CVE-2022-49335 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0336Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2022-49162 Référence CVE CVE-2022-49163 https://www.cve.org/CVERecord?id=CVE-2022-49163 Référence CVE CVE-2022-49164 https://www.cve.org/CVERecord?id=CVE-2022-49164 Référence CVE CVE-2022-49165 https://www.cve.org/CVERecord?id=CVE-2022-49165 Référence CVE CVE-2022-49174 https://www.cve.org/CVERecord?id=CVE-2022-49174 Référence CVE CVE-2022-49175 https://www.cve.org/CVERecord?id=CVE-2022-49175 Référence CVE CVE-2022-49176 https://www.cve.org/CVERecord?id=CVE-2022-49176 Référence CVE CVE-2022-49177 https://www.cve.org/CVERecord?id=CVE-2022-49177 Référence CVE CVE-2022-49178 https://www.cve.org/CVERecord?id=CVE-2022-49178 Référence CVE CVE-2022-49179 https://www.cve.org/CVERecord?id=CVE-2022-49179 Référence CVE CVE-2022-49180 https://www.cve.org/CVERecord?id=CVE-2022-49180 Référence CVE CVE-2022-49182 https://www.cve.org/CVERecord?id=CVE-2022-49182 Référence CVE CVE-2022-49183 https://www.cve.org/CVERecord?id=CVE-2022-49183 Référence CVE CVE-2022-49185 https://www.cve.org/CVERecord?id=CVE-2022-49185 Référence CVE CVE-2022-49187 https://www.cve.org/CVERecord?id=CVE-2022-49187 Référence CVE CVE-2022-49188 https://www.cve.org/CVERecord?id=CVE-2022-49188 Référence CVE CVE-2022-49189 https://www.cve.org/CVERecord?id=CVE-2022-49189 Référence CVE CVE-2022-49191 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0307Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2022-49162 Référence CVE CVE-2022-49163 https://www.cve.org/CVERecord?id=CVE-2022-49163 Référence CVE CVE-2022-49164 https://www.cve.org/CVERecord?id=CVE-2022-49164 Référence CVE CVE-2022-49165 https://www.cve.org/CVERecord?id=CVE-2022-49165 Référence CVE CVE-2022-49174 https://www.cve.org/CVERecord?id=CVE-2022-49174 Référence CVE CVE-2022-49175 https://www.cve.org/CVERecord?id=CVE-2022-49175 Référence CVE CVE-2022-49176 https://www.cve.org/CVERecord?id=CVE-2022-49176 Référence CVE CVE-2022-49177 https://www.cve.org/CVERecord?id=CVE-2022-49177 Référence CVE CVE-2022-49178 https://www.cve.org/CVERecord?id=CVE-2022-49178 Référence CVE CVE-2022-49179 https://www.cve.org/CVERecord?id=CVE-2022-49179 Référence CVE CVE-2022-49180 https://www.cve.org/CVERecord?id=CVE-2022-49180 Référence CVE CVE-2022-49182 https://www.cve.org/CVERecord?id=CVE-2022-49182 Référence CVE CVE-2022-49183 https://www.cve.org/CVERecord?id=CVE-2022-49183 Référence CVE CVE-2022-49185 https://www.cve.org/CVERecord?id=CVE-2022-49185 Référence CVE CVE-2022-49187 https://www.cve.org/CVERecord?id=CVE-2022-49187 Référence CVE CVE-2022-49188 https://www.cve.org/CVERecord?id=CVE-2022-49188 Référence CVE CVE-2022-49189 https://www.cve.org/CVERecord?id=CVE-2022-49189 Référence CVE CVE-2022-49192 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0252Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2022-49160 Référence CVE CVE-2022-49162 https://www.cve.org/CVERecord?id=CVE-2022-49162 Référence CVE CVE-2022-49163 https://www.cve.org/CVERecord?id=CVE-2022-49163 Référence CVE CVE-2022-49164 https://www.cve.org/CVERecord?id=CVE-2022-49164 Référence CVE CVE-2022-49165 https://www.cve.org/CVERecord?id=CVE-2022-49165 Référence CVE CVE-2022-49174 https://www.cve.org/CVERecord?id=CVE-2022-49174 Référence CVE CVE-2022-49175 https://www.cve.org/CVERecord?id=CVE-2022-49175 Référence CVE CVE-2022-49176 https://www.cve.org/CVERecord?id=CVE-2022-49176 Référence CVE CVE-2022-49177 https://www.cve.org/CVERecord?id=CVE-2022-49177 Référence CVE CVE-2022-49179 https://www.cve.org/CVERecord?id=CVE-2022-49179 Référence CVE CVE-2022-49180 https://www.cve.org/CVERecord?id=CVE-2022-49180 Référence CVE CVE-2022-49182 https://www.cve.org/CVERecord?id=CVE-2022-49182 Référence CVE CVE-2022-49185 https://www.cve.org/CVERecord?id=CVE-2022-49185 Référence CVE CVE-2022-49187 https://www.cve.org/CVERecord?id=CVE-2022-49187 Référence CVE CVE-2022-49188 https://www.cve.org/CVERecord?id=CVE-2022-49188 Référence CVE CVE-2022-49189 https://www.cve.org/CVERecord?id=CVE-2022-49189 Référence CVE CVE-2022-49193 https://www.cve.org/CVERecord?id=CVE-2022-49193 Référence CVE CVE-2022-49194 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2022-026000Linux の Linux Kernel における解放済みメモリの使用に関する脆弱性

Linux の Linux Kernel には、解放済みメモリの使用に関する脆弱性が存在します。

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Fix availability varies by product
Affected
Linux: 0d52af590552473666da5b6111e7182d6cd23f92 < c4f5a678add58a8a0e7ee5e038496b376ea6d205, 0d52af590552473666da5b6111e7182d6cd23f92 < 7507ead1e9d42957c2340f2c4a0e9d00034e3366, 0d52af590552473666da5b6111e7182d6cd23f92 < 8f34dea99cd7761156a146a5258a67d045d862f7, 0d52af590552473666da5b6111e7182d6cd23f92 < 87fdfe8589d43e471dffb4c60f75eeb6f37afc4c, 0d52af590552473666da5b6111e7182d6cd23f92 < c01fced8d38fbccc82787065229578006f28e020, 0d52af590552473666da5b6111e7182d6cd23f92 < 8410f70977734f21b8ed45c37e925d311dfda2e7, 4.16
Fixed
Linux: < 4.16, 5.4.189 ≤ 5.4.*, 5.10.110 ≤ 5.10.*, 5.15.33 ≤ 5.15.*, 5.16.19 ≤ 5.16.*, 5.17.2 ≤ 5.17.*, 5.18 ≤ *
Action
Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
Workaround
No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.
04

Evidence and provenance

Published 26 Feb 2025 · Last source change 12 Aug 2026, 23:58 UTC · CWE-416 · Use After Free

CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2022-55046
Product sourceCNA
Remediation sourceCVE/CNA references
CWE sourceCISA ADP
NVD statusNVD enriched

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗

No material field changes have been recorded since change tracking began. Routine source refreshes and cosmetic edits are intentionally excluded.

Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release or patch reference recorded
ENISA EUVD · EUVD-2022-55046↗CVE authority or vendor reference↗Patch or update reference↗Patch or update reference↗Patch or update reference↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2022-49179 · cve.blacktree.nl