CVE-2022-48753: block: fix memory leak in disk_register_independent_access_ranges
In the Linux kernel, the following vulnerability has been resolved:
block: fix memory leak in disk_register_independent_access_ranges
kobject_init_and_add() takes reference even when it fails.
According to the doc of kobject_init_and_add()
If this function returns an error, kobject_put() must be called to
properly clean up the memory associated with the object.
Fix this issue by adding kobject_put().
Callback function blk_ia_ranges_sysfs_release() in kobject_put()
can handle the pointer "iars" properly.
Security readout for executives and security teams
Plain-English summary
This is a Linux kernel memory-management bug in block-device registration. If a specific setup path fails, the kernel did not release an object reference correctly, causing a memory leak. The business risk is moderate and mainly applies to systems where local users or workloads can exercise affected kernel paths.
Executive priority
Treat as routine but necessary kernel maintenance. It does not justify emergency response from the provided evidence, but shared Linux infrastructure should receive timely patched kernels through normal change windows.
Technical view
The flaw is in disk_register_independent_access_ranges(). kobject_init_and_add() keeps a reference even on failure, and the vulnerable code missed the required kobject_put() cleanup. The fix adds kobject_put(), letting blk_ia_ranges_sysfs_release() free the affected iars object correctly.
Likely exposure
Exposure is limited to affected Linux kernel builds, including 5.16-era versions or kernels derived from the listed vulnerable commit. CVSS marks attack vector as local with low privileges required. Downstream distribution backports may change exposure.
Exploitation context
The bundle does not indicate CISA KEV listing or active exploitation. The CVSS vector suggests local, low-complexity exploitation with low confidentiality, integrity, and availability impact. No remote attack path is supported by the provided sources.
Researcher notes
Evidence supports a missing cleanup on a kobject initialization failure path. The source bundle does not include CWE mapping, exploit details, affected CPEs, or distribution-specific package status, so validation should rely on kernel lineage and vendor backport records.
Mitigation direction
Upgrade to a Linux kernel containing the referenced stable fixes.
Check your Linux distribution advisory for backported kernel packages.
Prioritize multi-user hosts, shared compute, and container platforms first.
Avoid assuming version strings alone prove vulnerability or safety.
Validation and detection
Inventory running kernel versions and distribution package revisions.
Check vendor changelogs for the two referenced stable commits.
Confirm whether kernels descend from commit a2247f19ee1c.
Review asset classes with local untrusted user or workload access.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2022-48753 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.