1. Home
  2. Vulnerabilities
  3. CVE-2023-53480
0.0
NA
CVE-2023-53480
kobject: Add sanity check for kset->kobj.ktype in kset_register()
Description

In the Linux kernel, the following vulnerability has been resolved: kobject: Add sanity check for kset->kobj.ktype in kset_register() When I register a kset in the following way: static struct kset my_kset; kobject_set_name(&my_kset.kobj, "my_kset"); ret = kset_register(&my_kset); A null pointer dereference exception is occurred: [ 4453.568337] Unable to handle kernel NULL pointer dereference at \ virtual address 0000000000000028 ... ... [ 4453.810361] Call trace: [ 4453.813062] kobject_get_ownership+0xc/0x34 [ 4453.817493] kobject_add_internal+0x98/0x274 [ 4453.822005] kset_register+0x5c/0xb4 [ 4453.825820] my_kobj_init+0x44/0x1000 [my_kset] ... ... Because I didn't initialize my_kset.kobj.ktype. According to the description in Documentation/core-api/kobject.rst: - A ktype is the type of object that embeds a kobject. Every structure that embeds a kobject needs a corresponding ktype. So add sanity check to make sure kset->kobj.ktype is not NULL.

INFO

Published Date :

Oct. 1, 2025, 12:15 p.m.

Last Modified :

Oct. 2, 2025, 7:12 p.m.

Remotely Exploit :

No

Source :

416baaa9-dc9f-4396-8d5f-8c081fb06d67
Affected Products

The following products are affected by CVE-2023-53480 vulnerability. Even if cvefeed.io is aware of the exact versions of the products that are affected, the information is not represented in the table below.

ID Vendor Product Action
1 Linux linux_kernel
: Total Affected Vendor : 1 | Products : 1
Solution
Ensure kobject ktype is initialized before registering a kset to prevent null pointer dereferences.
  • Initialize the kobject ktype for embedded structures.
  • Perform sanity checks for kset->kobj.ktype before kset registration.
  • Update the kernel with the provided patch.
References to Advisories, Solutions, and Tools

Here, you will find a curated list of external links that provide in-depth information, practical solutions, and valuable tools related to CVE-2023-53480.

URL Resource
https://git.kernel.org/stable/c/039ec9db2d30032eafa365f5f89b30eca5322b05
https://git.kernel.org/stable/c/1792eac72e27f676bf9ebde28a5afea627fb85f0
https://git.kernel.org/stable/c/1a772881bc059c596d8ca587cbd2a233edce3d3b
https://git.kernel.org/stable/c/48aebbe801e78a8932404c122ed0e880ccedc220
https://git.kernel.org/stable/c/4d0fe8c52bb3029d83e323c961221156ab98680b
https://git.kernel.org/stable/c/5df5829158513134ddcaf2184d9286eda7b0bb18
https://git.kernel.org/stable/c/964e025ceefdf75da46b0133d0c2790de451aeec
https://git.kernel.org/stable/c/f3f6bf22a4f5ba649cf26ae4670de5c7f861bdef
CWE - Common Weakness Enumeration

While CVE identifies specific instances of vulnerabilities, CWE categorizes the common flaws or weaknesses that can lead to vulnerabilities. CVE-2023-53480 is associated with the following CWEs:

Common Attack Pattern Enumeration and Classification (CAPEC)

Common Attack Pattern Enumeration and Classification (CAPEC) stores attack patterns, which are descriptions of the common attributes and approaches employed by adversaries to exploit the CVE-2023-53480 weaknesses.

We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).

Results are limited to the first 15 repositories due to potential performance issues.

The following list is the news that have been mention CVE-2023-53480 vulnerability anywhere in the article.

Results are limited to the first 20 news articles due to potential performance issues.

The following table lists the changes that have been made to the CVE-2023-53480 vulnerability over time.

Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.

  • New CVE Received by 416baaa9-dc9f-4396-8d5f-8c081fb06d67

    Oct. 01, 2025

    Action Type Old Value New Value
    Added Description In the Linux kernel, the following vulnerability has been resolved: kobject: Add sanity check for kset->kobj.ktype in kset_register() When I register a kset in the following way: static struct kset my_kset; kobject_set_name(&my_kset.kobj, "my_kset"); ret = kset_register(&my_kset); A null pointer dereference exception is occurred: [ 4453.568337] Unable to handle kernel NULL pointer dereference at \ virtual address 0000000000000028 ... ... [ 4453.810361] Call trace: [ 4453.813062] kobject_get_ownership+0xc/0x34 [ 4453.817493] kobject_add_internal+0x98/0x274 [ 4453.822005] kset_register+0x5c/0xb4 [ 4453.825820] my_kobj_init+0x44/0x1000 [my_kset] ... ... Because I didn't initialize my_kset.kobj.ktype. According to the description in Documentation/core-api/kobject.rst: - A ktype is the type of object that embeds a kobject. Every structure that embeds a kobject needs a corresponding ktype. So add sanity check to make sure kset->kobj.ktype is not NULL.
    Added Reference https://git.kernel.org/stable/c/039ec9db2d30032eafa365f5f89b30eca5322b05
    Added Reference https://git.kernel.org/stable/c/1792eac72e27f676bf9ebde28a5afea627fb85f0
    Added Reference https://git.kernel.org/stable/c/1a772881bc059c596d8ca587cbd2a233edce3d3b
    Added Reference https://git.kernel.org/stable/c/48aebbe801e78a8932404c122ed0e880ccedc220
    Added Reference https://git.kernel.org/stable/c/4d0fe8c52bb3029d83e323c961221156ab98680b
    Added Reference https://git.kernel.org/stable/c/5df5829158513134ddcaf2184d9286eda7b0bb18
    Added Reference https://git.kernel.org/stable/c/964e025ceefdf75da46b0133d0c2790de451aeec
    Added Reference https://git.kernel.org/stable/c/f3f6bf22a4f5ba649cf26ae4670de5c7f861bdef
EPSS is a daily estimate of the probability of exploitation activity being observed over the next 30 days. Following chart shows the EPSS score history of the vulnerability.
Vulnerability Scoring Details
No CVSS metrics available for this vulnerability.