Go to homepageCyberStrike

Menu

Star on GitHub · 3.2k
Sign inDownload

CVE-2024-38633

5.5 · MEDIUM

In the Linux kernel, the following vulnerability has been resolved: serial: max3100: Update uart_driver_registered on driver removal The removal of the last MAX3100 device triggers the removal of…

Published Jun 21, 2024CWE-476EPSS 0.24%

Overview

CVE-2024-38633 is a medium-severity vulnerability. It was published on June 21, 2024 and has a CVSS 3.1 base score of 5.5 (MEDIUM).

This vulnerability has a CVSS 3.1 base score of 5.5, rated MEDIUM. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

Technical description

In the Linux kernel, the following vulnerability has been resolved:

serial: max3100: Update uart_driver_registered on driver removal

The removal of the last MAX3100 device triggers the removal of

the driver. However, code doesn't update the respective global

variable and after insmod — rmmod — insmod cycle the kernel

oopses:

max3100 spi-PRP0001:01: max3100_probe: adding port 0

BUG: kernel NULL pointer dereference, address: 0000000000000408

...

RIP: 0010:serial_core_register_port+0xa0/0x840

...

max3100_probe+0x1b6/0x280 [max3100]

spi_probe+0x8d/0xb0

Update the actual state so next time UART driver will be registered

again.

Hugo also noticed, that the error path in the probe also affected

by having the variable set, and not cleared. Instead of clearing it

move the assignment after the successfull uart_register_driver() call.

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

References

Refgit.kernel.org/stable/c/21a61a7fbcfdd3493cede43ebc7c4dfae2147a8bRefgit.kernel.org/stable/c/361a92c9038e8c8c3996f8eeaa14522a8ad90752Refgit.kernel.org/stable/c/712a1fcb38dc7cac6da63ee79a88708fbf9c45ecRefgit.kernel.org/stable/c/9db4222ed8cd3e50b81c8b910ae74c26427a4003Refgit.kernel.org/stable/c/b6eb7aff23e05f362e8c9b560f6ac5e727b70e00Refgit.kernel.org/stable/c/e8a10089eddba40d4b2080c9d3fc2d2b2488f762Refgit.kernel.org/stable/c/e8e2a4339decad7e59425b594a98613402652d72Refgit.kernel.org/stable/c/fa84ca78b048dfb00df0ef446f5c35e0a98ca6a0Refgit.kernel.org/stable/c/21a61a7fbcfdd3493cede43ebc7c4dfae2147a8bRefgit.kernel.org/stable/c/361a92c9038e8c8c3996f8eeaa14522a8ad90752

How CyberStrike helps

Frequently asked questions

What is CVE-2024-38633?

CVE-2024-38633 is a medium-severity vulnerability. It was published on June 21, 2024 and has a CVSS 3.1 base score of 5.5 (MEDIUM).

How severe is CVE-2024-38633?

This vulnerability has a CVSS 3.1 base score of 5.5, rated MEDIUM. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

How do I fix or remediate CVE-2024-38633?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2024-38633?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2024-38633 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related MEDIUM CVEs from 2024

View all
Browse by year2026202520242023202220212020201920182017201620152014201320122011201020092008200720062005200420032002200120001999