CVE-2022-50356: net: sched: sfb: fix null pointer access issue when sfb_init() fails
Noroxi assessment
Priority: Monitor (action score 22/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.20% (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 2a3fc78210b9f0e85372a2435368962009f480fc, 723399af2795fb95687a531c9480464b5f489333, c2e1e59d59fafe297779ceae1fe0e6fbebc3e745.
Low priority for now. Upgrade to Linux Linux 2a3fc78210b9f0e85372a2435368962009f480fc, 723399af2795fb95687a531c9480464b5f489333, c2e1e59d59fafe297779ceae1fe0e6fbebc3e745 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: net: sched: sfb: fix null pointer access issue when sfb_init() fails When the default qdisc is sfb, if the qdisc of dev_queue fails to be inited during mqprio_init(), sfb_reset() is invoked to clear resources. In this case, the q->qdisc is NULL, and it will cause gpf issue. The process is as follows: qdisc_create_dflt() sfb_init() tcf_block_get() --->failed, q->qdisc is NULL ... qdisc_put() ... sfb_reset() qdisc_reset(q->qdisc) --->q->qdisc is NULL ops = qdisc->ops The following is the Call Trace information: general protection fault, probably for non-canonical address 0xdffffc0000000003: 0000 [#1] PREEMPT SMP KASAN KASAN: null-ptr-deref in range [0x0000000000000018-0x000000000000001f] RIP: 0010:qdisc_reset+0x2b/0x6f0 Call Trace: <TASK> sfb_reset+0x37/0xd0 qdisc_reset+0xed/0x6f0 qdisc_destroy+0x82/0x4c0 qdisc_put+0x9e/0xb0 qdisc_create_dflt+0x2c3/0x4a0 mqprio_init+0xa71/0x1760 qdisc_create+0x3eb/0x1000 tc_modify_qdisc+0x408/0x1720 rtnetlink_rcv_msg+0x38e/0xac0 netlink_rcv_skb+0x12d/0x3a0 netlink_unicast+0x4a2/0x740 netlink_sendmsg+0x826/0xcc0 sock_sendmsg+0xc5/0x100 ____sys_sendmsg+0x583/0x690 ___sys_sendmsg+0xe8/0x160 __sys_sendmsg+0xbf/0x160 do_syscall_64+0x35/0x80 entry_SYSCALL_64_after_hwframe+0x46/0xb0 RIP: 0033:0x7f2164122d04 </TASK>
- Published
- Sep 17, 2025
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 10th percentile
- CWE
- CWE-476
Report tools
Action score
22
Monitor
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
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
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 helpAffected 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.
| 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 kernel2.6.39 and later · before 5.10.152
- linux linux kernel5.11 and later · before 5.15.76
- linux linux kernel5.16 and later · before 6.0.6
- linux linux kernel6.1
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
- 2.6.39affected
- e13e02a3c68d899169c78d9a18689bd73491d59a and later · before ded86c4191a3c17f8200d17a7d8a6f63b74554aeaffected · git
- e13e02a3c68d899169c78d9a18689bd73491d59a and later · before c2e1e59d59fafe297779ceae1fe0e6fbebc3e745affected · git
- e13e02a3c68d899169c78d9a18689bd73491d59a and later · before 723399af2795fb95687a531c9480464b5f489333affected · git
- e13e02a3c68d899169c78d9a18689bd73491d59a and later · before 2a3fc78210b9f0e85372a2435368962009f480fcaffected · git
- before 2.6.39not affected · semver
- 5.10.152 and later · up to and including 5.10.*not affected · semver
- 5.15.76 and later · up to and including 5.15.*not affected · semver
- 6.0.6 and later · up to and including 6.0.*not affected · semver
- 6.1 and laternot affected · original_commit_for_fix
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 6.0.6-1 | 6.0.6-1 |
| Red Hat:rhel_aus:8.2::baseos | bpftool | before 0:4.18.0-193.178.1.el8_2 | 0:4.18.0-193.178.1.el8_2 |
| Red Hat:rhel_aus:8.2::baseos | bpftool-debuginfo | before 0:4.18.0-193.178.1.el8_2 | 0:4.18.0-193.178.1.el8_2 |
| Red Hat:rhel_aus:8.2::baseos | kernel | before 0:4.18.0-193.178.1.el8_2 | 0:4.18.0-193.178.1.el8_2 |
| Red Hat:rhel_aus:8.2::baseos | kernel-abi-whitelists | before 0:4.18.0-193.178.1.el8_2 | 0:4.18.0-193.178.1.el8_2 |
| Red Hat:rhel_aus:8.2::baseos | kernel-core | before 0:4.18.0-193.178.1.el8_2 | 0:4.18.0-193.178.1.el8_2 |
| Red Hat:rhel_aus:8.2::baseos | kernel-debug | before 0:4.18.0-193.178.1.el8_2 | 0:4.18.0-193.178.1.el8_2 |
| Red Hat:rhel_aus:8.2::baseos | kernel-debug-core | before 0:4.18.0-193.178.1.el8_2 | 0:4.18.0-193.178.1.el8_2 |
| Red Hat:rhel_aus:8.2::baseos | kernel-debug-debuginfo | before 0:4.18.0-193.178.1.el8_2 | 0:4.18.0-193.178.1.el8_2 |
| Red Hat:rhel_aus:8.2::baseos | kernel-debug-devel | before 0:4.18.0-193.178.1.el8_2 | 0:4.18.0-193.178.1.el8_2 |
| Red Hat:rhel_aus:8.2::baseos | kernel-debug-modules | before 0:4.18.0-193.178.1.el8_2 | 0:4.18.0-193.178.1.el8_2 |
| Red Hat:rhel_aus:8.2::baseos | kernel-debug-modules-extra | before 0:4.18.0-193.178.1.el8_2 | 0:4.18.0-193.178.1.el8_2 |
| Red Hat:rhel_aus:8.2::baseos | kernel-debuginfo | before 0:4.18.0-193.178.1.el8_2 | 0:4.18.0-193.178.1.el8_2 |
| Red Hat:rhel_aus:8.2::baseos | kernel-debuginfo-common-x86_64 | before 0:4.18.0-193.178.1.el8_2 | 0:4.18.0-193.178.1.el8_2 |
| Red Hat:rhel_aus:8.2::baseos | kernel-devel | before 0:4.18.0-193.178.1.el8_2 | 0:4.18.0-193.178.1.el8_2 |
| Red Hat:rhel_aus:8.2::baseos | kernel-doc | before 0:4.18.0-193.178.1.el8_2 | 0:4.18.0-193.178.1.el8_2 |
| Red Hat:rhel_aus:8.2::baseos | kernel-modules | before 0:4.18.0-193.178.1.el8_2 | 0:4.18.0-193.178.1.el8_2 |
| Red Hat:rhel_aus:8.2::baseos | kernel-modules-extra | before 0:4.18.0-193.178.1.el8_2 | 0:4.18.0-193.178.1.el8_2 |
| Red Hat:rhel_aus:8.2::baseos | kernel-tools | before 0:4.18.0-193.178.1.el8_2 | 0:4.18.0-193.178.1.el8_2 |
| Red Hat:rhel_aus:8.2::baseos | kernel-tools-debuginfo | before 0:4.18.0-193.178.1.el8_2 | 0:4.18.0-193.178.1.el8_2 |
| Red Hat:rhel_aus:8.2::baseos | kernel-tools-libs | before 0:4.18.0-193.178.1.el8_2 | 0:4.18.0-193.178.1.el8_2 |
| Red Hat:rhel_aus:8.2::baseos | perf | before 0:4.18.0-193.178.1.el8_2 | 0:4.18.0-193.178.1.el8_2 |
| Red Hat:rhel_aus:8.2::baseos | perf-debuginfo | before 0:4.18.0-193.178.1.el8_2 | 0:4.18.0-193.178.1.el8_2 |
| Red Hat:rhel_aus:8.2::baseos | python3-perf | before 0:4.18.0-193.178.1.el8_2 | 0:4.18.0-193.178.1.el8_2 |
+96
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- 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 KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2022-50354Sep 17, 2025 · drm/amdkfd: Fix kfd_process_device_init_vm error handling22Monitor
- ← EarlierCVE-2022-50355Sep 17, 2025 · staging: vt6655: fix some erroneous memory clean-up loops22Monitor
- Later →CVE-2022-50357Sep 17, 2025 · usb: dwc3: core: fix some leaks in probe22Monitor
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 | 2a3fc78210b9f0e85372a2435368962009f480fc | Vendor (CNA) |
| Linux Linux | 723399af2795fb95687a531c9480464b5f489333 | Vendor (CNA) |
| Linux Linux | c2e1e59d59fafe297779ceae1fe0e6fbebc3e745 | Vendor (CNA) |
| Linux Linux | ded86c4191a3c17f8200d17a7d8a6f63b74554ae | Vendor (CNA) |
| debian:linux | 6.0.6-1 · Debian:12 | Package registry (OSV) |
| red hat:bpftool-debuginfo | 0:7.0.0-284.146.1.el9_2 · Red Hat:rhel_e4s:9.2::appstream | Package registry (OSV) |
| red hat:kernel-64k-debug-debuginfo | 0:5.14.0-284.146.1.el9_2 · Red Hat:rhel_e4s:9.2::appstream | Package registry (OSV) |
| red hat:kernel-64k-debug-devel | 0:5.14.0-284.146.1.el9_2 · Red Hat:rhel_e4s:9.2::appstream | Package registry (OSV) |
| red hat:kernel-64k-debug-devel-matched | 0:5.14.0-284.146.1.el9_2 · Red Hat:rhel_e4s:9.2::appstream | Package registry (OSV) |
| red hat:kernel-64k-debuginfo | 0:5.14.0-284.146.1.el9_2 · Red Hat:rhel_e4s:9.2::appstream | Package registry (OSV) |
| red hat:kernel-64k-devel | 0:5.14.0-284.146.1.el9_2 · Red Hat:rhel_e4s:9.2::appstream | Package registry (OSV) |
| red hat:kernel-64k-devel-matched | 0:5.14.0-284.146.1.el9_2 · Red Hat:rhel_e4s:9.2::appstream | Package registry (OSV) |
| red hat:kernel-debug-debuginfo | 0:5.14.0-284.146.1.el9_2 · Red Hat:rhel_e4s:9.2::appstream | Package registry (OSV) |
| red hat:kernel-debug-devel | 0:5.14.0-284.146.1.el9_2 · Red Hat:rhel_e4s:9.2::appstream | Package registry (OSV) |
| red hat:kernel-debug-devel-matched | 0:5.14.0-284.146.1.el9_2 · Red Hat:rhel_e4s:9.2::appstream | Package registry (OSV) |
| red hat:kernel-debuginfo | 0:5.14.0-284.146.1.el9_2 · Red Hat:rhel_e4s:9.2::appstream | Package registry (OSV) |
| red hat:kernel-debuginfo-common-aarch64 | 0:5.14.0-284.146.1.el9_2 · Red Hat:rhel_e4s:9.2::appstream | Package registry (OSV) |
| suse:kernel-default | 4.12.14-122.280.1 · SUSE:Linux Enterprise Live Patching 12 SP5 | Package registry (OSV) |
| suse:kernel-source | 4.12.14-122.280.1 · SUSE:Linux Enterprise Server 12 SP5-LTSS | Package registry (OSV) |
| suse:kernel-syms | 4.12.14-122.280.1 · SUSE:Linux Enterprise Server 12 SP5-LTSS | Package registry (OSV) |
| suse:kgraft-patch-SLE12-SP5_Update_74 | 1-8.5.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 researchersFinders, 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
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-476 · NULL Pointer DereferenceCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
nvd-primary
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✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (3 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.