NVD / CVE Program· CNA Linux

CVE-2022-49179: block, bfq: don't move oom_bfqq

Noroxi assessment

Priority: Monitor (action score 31/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 0.27% (FIRST EPSS).
Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
Fixed version: Linux Linux 7507ead1e9d42957c2340f2c4a0e9d00034e3366, 8410f70977734f21b8ed45c37e925d311dfda2e7, 87fdfe8589d43e471dffb4c60f75eeb6f37afc4c.

Low priority for now. Upgrade to Linux Linux 7507ead1e9d42957c2340f2c4a0e9d00034e3366, 8410f70977734f21b8ed45c37e925d311dfda2e7, 87fdfe8589d43e471dffb4c60f75eeb6f37afc4c or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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---

HighCVSS 7.8 · v3.1—No exploit Fix available

Memory safety

Published: Feb 26, 2025
Updated: Aug 12, 2026
EPSS: 0.2% · 20th percentile
CWE: CWE-416

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 31 / 40 · 7.8 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.2%

CISA SSVC decision

Exploitation: none
Automatable: no
Technical impact: total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD: —
CNA · Linux: 7.8; NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

ProductVersion

Vendor	Product	CPE
linux	linux kernel	cpe:2.3:o:linux:linux_kernel

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

linux linux kernelbefore 5.4.189
linux linux kernel5.5 and later · before 5.10.110
linux linux kernel5.11 and later · before 5.15.33
linux linux kernel5.16 and later · before 5.16.19
linux linux kernel5.17 and later · before 5.17.2

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

Linux Linux
- 4.16affected
- 0d52af590552473666da5b6111e7182d6cd23f92 and later · before c4f5a678add58a8a0e7ee5e038496b376ea6d205affected · git
- 0d52af590552473666da5b6111e7182d6cd23f92 and later · before 7507ead1e9d42957c2340f2c4a0e9d00034e3366affected · git
- 0d52af590552473666da5b6111e7182d6cd23f92 and later · before 8f34dea99cd7761156a146a5258a67d045d862f7affected · git
- 0d52af590552473666da5b6111e7182d6cd23f92 and later · before 87fdfe8589d43e471dffb4c60f75eeb6f37afc4caffected · git
- 0d52af590552473666da5b6111e7182d6cd23f92 and later · before c01fced8d38fbccc82787065229578006f28e020affected · git
- 0d52af590552473666da5b6111e7182d6cd23f92 and later · before 8410f70977734f21b8ed45c37e925d311dfda2e7affected · git
- before 4.16not affected · semver
- 5.4.189 and later · up to and including 5.4.*not affected · semver
- 5.10.110 and later · up to and including 5.10.*not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

Ecosystem	Package	Affected range	Fix
Debian:12	linux	before 5.17.3-1	5.17.3-1
SUSE:Linux Enterprise Live Patching 12 SP5	kernel-default	before 4.12.14-122.258.1	4.12.14-122.258.1
SUSE:Linux Enterprise Live Patching 12 SP5	kgraft-patch-SLE12-SP5_Update_56	before 18-2.1	18-2.1
SUSE:Linux Enterprise Live Patching 12 SP5	kgraft-patch-SLE12-SP5_Update_58	before 13-2.1	13-2.1
SUSE:Linux Enterprise Live Patching 12 SP5	kgraft-patch-SLE12-SP5_Update_59	before 12-2.1	12-2.1
SUSE:Linux Enterprise Live Patching 12 SP5	kgraft-patch-SLE12-SP5_Update_60	before 11-2.1	11-2.1
SUSE:Linux Enterprise Live Patching 12 SP5	kgraft-patch-SLE12-SP5_Update_61	before 18-4.1	18-4.1
SUSE:Linux Enterprise Live Patching 12 SP5	kgraft-patch-SLE12-SP5_Update_61	before 10-2.1	10-2.1
SUSE:Linux Enterprise Live Patching 12 SP5	kgraft-patch-SLE12-SP5_Update_63	before 6-2.1	6-2.1
SUSE:Linux Enterprise Live Patching 12 SP5	kgraft-patch-SLE12-SP5_Update_64	before 5-2.1	5-2.1
SUSE:Linux Enterprise Live Patching 12 SP5	kgraft-patch-SLE12-SP5_Update_65	before 3-2.1	3-2.1
SUSE:Linux Enterprise Live Patching 12 SP5	kgraft-patch-SLE12-SP5_Update_66	before 3-2.1	3-2.1
SUSE:Linux Enterprise Live Patching 12 SP5	kgraft-patch-SLE12-SP5_Update_67	before 2-2.1	2-2.1
SUSE:Linux Enterprise Live Patching 12 SP5	kgraft-patch-SLE12-SP5_Update_68	before 1-8.3.1	1-8.3.1
SUSE:Linux Enterprise Server 12 SP5-LTSS	kernel-source	before 4.12.14-122.258.1	4.12.14-122.258.1
SUSE:Linux Enterprise Server 12 SP5-LTSS	kernel-syms	before 4.12.14-122.258.1	4.12.14-122.258.1

Same product

linux: all records

Other highest-scoring records for the same primary product.

CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
90Now
CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV
89Now
CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
85Now

Published before and after this one in the same product

← EarlierCVE-2022-49176Feb 26, 2025 · bfq: fix use-after-free in bfq_dispatch_request
31Monitor
← EarlierCVE-2022-49177Feb 26, 2025 · hwrng: cavium - fix NULL but dereferenced coccicheck error
22Monitor
Later →CVE-2022-49180Feb 26, 2025 · LSM: general protection fault in legacy_parse_param
22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / package	Fixed version	Source
Linux Linux	7507ead1e9d42957c2340f2c4a0e9d00034e3366	Vendor (CNA)
Linux Linux	8410f70977734f21b8ed45c37e925d311dfda2e7	Vendor (CNA)
Linux Linux	87fdfe8589d43e471dffb4c60f75eeb6f37afc4c	Vendor (CNA)
Linux Linux	8f34dea99cd7761156a146a5258a67d045d862f7	Vendor (CNA)
Linux Linux	c01fced8d38fbccc82787065229578006f28e020	Vendor (CNA)
Linux Linux	c4f5a678add58a8a0e7ee5e038496b376ea6d205	Vendor (CNA)
debian:linux	5.17.3-1 · Debian:12	Package registry (OSV)
suse:kernel-default	4.12.14-122.258.1 · SUSE:Linux Enterprise Live Patching 12 SP5	Package registry (OSV)
suse:kernel-source	4.12.14-122.258.1 · SUSE:Linux Enterprise Server 12 SP5-LTSS	Package registry (OSV)
suse:kernel-syms	4.12.14-122.258.1 · SUSE:Linux Enterprise Server 12 SP5-LTSS	Package registry (OSV)
suse:kgraft-patch-SLE12-SP5_Update_56	18-2.1 · SUSE:Linux Enterprise Live Patching 12 SP5	Package registry (OSV)
suse:kgraft-patch-SLE12-SP5_Update_58	13-2.1 · SUSE:Linux Enterprise Live Patching 12 SP5	Package registry (OSV)
suse:kgraft-patch-SLE12-SP5_Update_59	12-2.1 · SUSE:Linux Enterprise Live Patching 12 SP5	Package registry (OSV)
suse:kgraft-patch-SLE12-SP5_Update_60	11-2.1 · SUSE:Linux Enterprise Live Patching 12 SP5	Package registry (OSV)
suse:kgraft-patch-SLE12-SP5_Update_61	10-2.1 · SUSE:Linux Enterprise Live Patching 12 SP5	Package registry (OSV)
suse:kgraft-patch-SLE12-SP5_Update_63	6-2.1 · SUSE:Linux Enterprise Live Patching 12 SP5	Package registry (OSV)
suse:kgraft-patch-SLE12-SP5_Update_64	5-2.1 · SUSE:Linux Enterprise Live Patching 12 SP5	Package registry (OSV)
suse:kgraft-patch-SLE12-SP5_Update_65	3-2.1 · SUSE:Linux Enterprise Live Patching 12 SP5	Package registry (OSV)
suse:kgraft-patch-SLE12-SP5_Update_68	1-8.3.1 · SUSE:Linux Enterprise Live Patching 12 SP5	Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

Someone with local access to the system can trigger it.
A low-privileged account is enough.
No user action is required.
No special conditions are required; it is repeatable.

If successful

Confidentiality: high · data can be read
Integrity: high · data or configuration can be modified
Availability: high · the service can be disrupted

Attack vector: Local
Attack complexity: Low
Privileges required: Low
User interaction: None
Scope: Unchanged
Confidentiality impact: High
Integrity impact: High
Availability impact: High

Weakness class (CWE)

CWE-416 · Use After Free

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

nvd-secondary

Root cause

After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.

The bug in code

The whole CWE-416 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1free(dev->buf);
2/* ... another thread is still running ... */
3process(dev->buf);

Fixed

1lock(&dev->lock);
2free(dev->buf);
3dev->buf = NULL;
4unlock(&dev->lock);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

Fix✗ → ✓Sep 28, 2026, 10:11 PM UTC

For records you follow, these changes also arrive as notifications. →

References

git.kernel.org/stable/c/7507ead1e9d42957c2340f2c4a0e9d00034e3366

Show all references (5 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records