UBUNTU-CVE-2022-49472

In the Linux kernel, the following vulnerability has been resolved: net: phy: micrel: Allow probing without .driverdata Currently, if the .probe element is present in the phydriver structure and the .driverdata is not, a NULL pointer dereference happens. Allow passing .probe without .driverdata b...

UBUNTU-CVE-2022-49308

In the Linux kernel, the following vulnerability has been resolved: extcon: Modify extcon device to be created after driver data is set Currently, someone can invoke the sysfs such as stateshow intermittently before devsetdrvdata is done. And it can be a cause of kernel Oops because of edev is Nu...

CVE-2022-49472 net: phy: micrel: Allow probing without .driver_data

In the Linux kernel, the following vulnerability has been resolved: net: phy: micrel: Allow probing without .driverdata Currently, if the .probe element is present in the phydriver structure and the .driverdata is not, a NULL pointer dereference happens. Allow passing .probe without .driverdata b...

CVE-2022-49472

CVE-2022-49472 affects the Linux kernel PHY Micrel driver: if a .probe is present and .driver_data is missing, a NULL pointer dereference can occur. The fix adds NULL checks for priv->type to allow probing without .driver_data. Connected advisories (Astra/Unity Linux) reference Linux kernel ve...

CVE-2022-49308

The CVE-2022-49308 entry describes a Linux kernel extcon overflow/NULL dereference vulnerability that could cause an Oops when sysfs state_show() runs before driver data is set. The root cause is extcon device creation occurring before drvdata is initialized, leading to an edev NULL dereference d...

CVE-2022-49308 extcon: Modify extcon device to be created after driver data is set

In the Linux kernel, the following vulnerability has been resolved: extcon: Modify extcon device to be created after driver data is set Currently, someone can invoke the sysfs such as stateshow intermittently before devsetdrvdata is done. And it can be a cause of kernel Oops because of edev is Nu...

CVE-2022-49308 extcon: Modify extcon device to be created after driver data is set

In the Linux kernel, the following vulnerability has been resolved: extcon: Modify extcon device to be created after driver data is set Currently, someone can invoke the sysfs such as stateshow intermittently before devsetdrvdata is done. And it can be a cause of kernel Oops because of edev is Nu...

Linux kernel 安全漏洞

Linux kernel is the kernel used by Linux, the open source operating system of the Linux Foundation in the United States. A security vulnerability exists in the Linux kernel that stems from the extcon device being created prior to setting the driver data, which could result in a null pointer...

Astra Linux – Vulnerability in Linux 6.1

In the Linux kernel, the following vulnerability has been resolved: media: amphion: Set video drvdata before registering the video device. video drvdata should be set before the video device is registered; otherwise, videodrvdata may return NULL in the open file operations, leading to errors...

Astra Linux – Vulnerability in Linux 6.1

In the Linux kernel, the following vulnerabilities have been resolved: HID: amdsfh: Free driverdata after destroying the hid device Driver callbacks for HID are no longer called after the hiddestroydevice function is called. Therefore, the driverdata should only be freed after the hiddestroydevic...

Astra Linux – Vulnerability in Linux 6.1

In the Linux kernel, the following vulnerability has been resolved: um: vector: Do not use drvdata in release The drvdata is not available in release. Let's just use containerof to get the vectordevice instance. Otherwise, removing a vector device will result in a crash: RIP:...

media: imx-jpeg: Set video drvdata before register video device

...

media: amphion: Set video drvdata before register video device

...

SUSE CVE-2024-57799

In the Linux kernel, the following vulnerability has been resolved: phy: rockchip: samsung-hdptx: Set drvdata before enabling runtime PM In some cases, rkhdptxphyruntimeresume may be invoked before platformsetdrvdata is executed in -probe, leading to a NULL pointer dereference when using the retu...

UBUNTU-CVE-2024-57799

In the Linux kernel, the following vulnerability has been resolved: phy: rockchip: samsung-hdptx: Set drvdata before enabling runtime PM In some cases, rkhdptxphyruntimeresume may be invoked before platformsetdrvdata is executed in -probe, leading to a NULL pointer dereference when using the retu...

The vulnerability of the dev_get_drvdata() function in the Cadence Quad SPI driver (drivers/spi/spi-cadence-quadspi.c) in the Linux operating system allows a hacker to cause a system failure.

The vulnerability of the devgetdrvdata function in the Cadence Quad SPI driver drivers/spi/spi-cadence-quadspi.c in Linux kernel is related to the use of an unreliable pointer. Exploiting this vulnerability could allow an attacker to cause a system failure...

PT-2026-5512

Name of the Vulnerable Software and Affected Versions Linux kernel affected versions not specified Description A device leak exists in the dmaengine subsystem, specifically within the stm32 dmamux component, during route allocation. The issue stems from failing to release a reference to the DMA m...

PT-2026-5993

Name of the Vulnerable Software and Affected Versions Linux kernel versions prior to 6.16.7+ 116 Description The Linux kernel contains a flaw related to power management in the Qualcomm USB2 PHY driver qcom-qusb2. Enabling runtime power management before the QPHY instance is attached as driver da...

AZL-55135 CVE-2024-56578 affecting package kernel for versions less than 6.6.64.2-1

In the Linux kernel, the following vulnerability has been resolved: media: imx-jpeg: Set video drvdata before register video device The video drvdata should be set before the video device is registered, otherwise videodrvdata may return NULL in the open file ops, and led to oops...

UBUNTU-CVE-2024-56579

In the Linux kernel, the following vulnerability has been resolved: media: amphion: Set video drvdata before register video device The video drvdata should be set before the video device is registered, otherwise videodrvdata may return NULL in the open file ops, and led to oops...