Google Pixel suffers from an unspecified vulnerability (CNVD-2025-00977)

Google Pixel is a smartphone from the American company Google Google. Google Pixel suffers from a security vulnerability that stems from the presence of uninitialized data in gattsr.c's gattsprocessreadbytypereq, which can lead to information disclosure. No details of the vulnerability are...

PT-2025-36279

Name of the Vulnerable Software and Affected Versions Linux kernel affected versions not specified Description The Linux kernel contains a kernel-infoleak issue in the do insn ioctl and do insnlist ioctl functions. A kernel buffer allocated to hold insn-n samples may not be fully initialized befo...

PT-2025-30803

Name of the Vulnerable Software and Affected Versions Linux kernel affected versions not specified Description The Linux kernel contains an issue within the vsock/vmci subsystem. Specifically, the vmci transport packet structure was not properly initialized, potentially leaving uninitialized data...

PT-2025-30834

Name of the Vulnerable Software and Affected Versions Linux kernel affected versions not specified Description The Linux kernel contains a flaw within the mhi ep ring add element function where the read pointer rd offset is updated before the buffer is written. This can lead to race conditions,...

CVE-2024-56739

A vulnerability was found in the Linux kernel's RTC driver in the rtctimerdowork function, where the rtcreadtime call may fail. This issue results in uninitialized data in the rtctime struct. It can lead to the generation of extremely large values, causing periodic timer failures and potentially...

SUSE CVE-2024-56739

In the Linux kernel, the following vulnerability has been resolved: rtc: check if rtcreadtime was successful in rtctimerdowork If the rtcreadtime call fails,, the struct rtctime tm; may contain uninitialized data, or an illegal date/time read from the RTC hardware. When calling rtctmtoktime later...

CVE-2024-56739

In the Linux kernel, the following vulnerability has been resolved: rtc: check if rtcreadtime was successful in rtctimerdowork If the rtcreadtime call fails,, the struct rtctime tm; may contain uninitialized data, or an illegal date/time read from the RTC hardware. When calling rtctmtoktime later...

DEBIAN-CVE-2024-56739

In the Linux kernel, the following vulnerability has been resolved: rtc: check if rtcreadtime was successful in rtctimerdowork If the rtcreadtime call fails,, the struct rtctime tm; may contain uninitialized data, or an illegal date/time read from the RTC hardware. When calling rtctmtoktime later...

AZL-55041 CVE-2024-56739 affecting package kernel for versions less than 6.6.64.2-1

In the Linux kernel, the following vulnerability has been resolved: rtc: check if rtcreadtime was successful in rtctimerdowork If the rtcreadtime call fails,, the struct rtctime tm; may contain uninitialized data, or an illegal date/time read from the RTC hardware. When calling rtctmtoktime later...

UBUNTU-CVE-2024-56739

In the Linux kernel, the following vulnerability has been resolved: rtc: check if rtcreadtime was successful in rtctimerdowork If the rtcreadtime call fails,, the struct rtctime tm; may contain uninitialized data, or an illegal date/time read from the RTC hardware. When calling rtctmtoktime later...

CVE-2024-56739

CVE-2024-56739 affects the Linux kernel where a failed __rtc_read_time in rtc_timer_do_work() can leave struct rtc_time tm with uninitialized data, causing rtc_tm_to_ktime to yield a very large value and potentially trigger kernel softlockup via periodic timers. The published fix adds a check on ...

CVE-2024-56739 rtc: check if __rtc_read_time was successful in rtc_timer_do_work()

In the Linux kernel, the following vulnerability has been resolved: rtc: check if rtcreadtime was successful in rtctimerdowork If the rtcreadtime call fails,, the struct rtctime tm; may contain uninitialized data, or an illegal date/time read from the RTC hardware. When calling rtctmtoktime later...

CVE-2024-56739 rtc: check if __rtc_read_time was successful in rtc_timer_do_work()

In the Linux kernel, the following vulnerability has been resolved: rtc: check if rtcreadtime was successful in rtctimerdowork If the rtcreadtime call fails,, the struct rtctime tm; may contain uninitialized data, or an illegal date/time read from the RTC hardware. When calling rtctmtoktime later...

CVE-2024-56739 rtc: check if __rtc_read_time was successful in rtc_timer_do_work()

In the Linux kernel, the following vulnerability has been resolved: rtc: check if rtcreadtime was successful in rtctimerdowork If the rtcreadtime call fails,, the struct rtctime tm; may contain uninitialized data, or an illegal date/time read from the RTC hardware. When calling rtctmtoktime later...

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 an rtctime structure that may contain uninitialized data or an illegal date/time when the rtcreadtime functi...

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 originates from a failure of the rtcreadtime function in the rtc module in the rtctime structure may contain...

PT-2025-3668 · Linux +1 · Linux Kernel +1

Name of the Vulnerable Software and Affected Versions: Linux kernel affected versions not specified Description: The issue concerns the exfat component of the Linux kernel, where a new buffer was not zeroed before writing. This could lead to uninitialized data in the page cache being written. The...

CVE-2018-9429

In buildImageItemsIfPossible of ItemTable.cpp there is a possible out of bound read due to uninitialized data. This could lead to information disclosure with no additional execution privileges needed. User interaction is needed for exploitation...

CVE-2018-9429

In buildImageItemsIfPossible of ItemTable.cpp there is a possible out of bound read due to uninitialized data. This could lead to information disclosure with no additional execution privileges needed. User interaction is needed for exploitation...

CVE-2018-9381

In gattsprocessreadbytypereq of gattsr.c, there is a possible information disclosure due to uninitialized data. This could lead to remote information disclosure with no additional execution privileges needed. User interaction is not needed for exploitation...