4912 matches found
CVE-2025-14308
creationtimestamp| type| source ---|---|--- 2025-12-09 09:04:14+00:00| seen| https://infosec.exchange/users/offseq/statuses/115688803731142569 2025-12-09 09:04:20+00:00| seen| https://bsky.app/profile/offseq.bsky.social/post/3m7k6talumn24 2025-12-09 18:55:58+00:00| seen|...
CVE-2025-13071
creationtimestamp| type| source ---|---|--- 2025-12-09 08:01:41+00:00| seen| https://gist.github.com/Darkcrai86/6218b103e76a646c545b484268694727 2025-12-09 09:26:19+00:00| seen| https://gist.github.com/Darkcrai86/d23c5f5b0f14fcae4068a588b849d8af...
EUVD-2023-60109
In the Linux kernel, the following vulnerability has been resolved: HID: wacom: Use ktimet rather than int when dealing with timestamps Code which interacts with timestamps needs to use the ktimet type returned by functions like ktimeget. The int type does not offer enough space to store these...
CVE-2023-53797
In the Linux kernel, the following vulnerability has been resolved: HID: wacom: Use ktimet rather than int when dealing with timestamps Code which interacts with timestamps needs to use the ktimet type returned by functions like ktimeget. The int type does not offer enough space to store these...
UBUNTU-CVE-2023-53797
In the Linux kernel, the following vulnerability has been resolved: HID: wacom: Use ktimet rather than int when dealing with timestamps Code which interacts with timestamps needs to use the ktimet type returned by functions like ktimeget. The int type does not offer enough space to store these...
CVE-2023-53797 HID: wacom: Use ktime_t rather than int when dealing with timestamps
In the Linux kernel, the following vulnerability has been resolved: HID: wacom: Use ktimet rather than int when dealing with timestamps Code which interacts with timestamps needs to use the ktimet type returned by functions like ktimeget. The int type does not offer enough space to store these...
CVE-2023-53797
CVE-2023-53797 : In the Linux kernel, HID wacom timestamp handling used int instead of ktime_t, risking overflow and incorrect values reported to userspace, potentially causing input handling to appear hung. The fix is to switch to ktime_t (via ktime_get) for timestamp values to prevent overflow....
CVE-2023-53797 HID: wacom: Use ktime_t rather than int when dealing with timestamps
In the Linux kernel, the following vulnerability has been resolved: HID: wacom: Use ktimet rather than int when dealing with timestamps Code which interacts with timestamps needs to use the ktimet type returned by functions like ktimeget. The int type does not offer enough space to store these...
CVE-2023-53797
In the Linux kernel, the following vulnerability has been resolved: HID: wacom: Use ktimet rather than int when dealing with timestamps Code which interacts with timestamps needs to use the ktimet type returned by functions like ktimeget. The int type does not offer enough space to store these...
PT-2025-49657
Name of the Vulnerable Software and Affected Versions Linux kernel affected versions not specified Description An issue exists in the Linux kernel’s Wacom HID driver related to timestamp handling. Code interacting with timestamps was incorrectly using the int data type instead of ktime t, which...
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 a problem with the use of the int type to handle timestamps...
UBUNTU-CVE-2025-66564
Sigstore Timestamp Authority is a service for issuing RFC 3161 timestamps. Prior to 2.0.3, Function api.ParseJSONRequest currently splits via a call to strings.Split an optionally-provided OID which is untrusted data on periods. Similarly, function api.getContentType splits the Content-Type heade...
CVE-2025-55182
creationtimestamp| type| source ---|---|--- 2025-12-03 15:45:15+00:00| seen| https://bsky.app/profile/react.dev/post/3m73sgkikuc2h 2025-12-03 15:55:55+00:00| seen| https://mstdn.social/users/jschauma/statuses/115656448649390437 2025-12-03 15:56:22+00:00| seen|...
CVE-2025-60912
creationtimestamp| type| source ---|---|--- 2025-12-02 18:31:20+00:00| seen| https://gist.github.com/amandrei/89649284ccfd597116452ae4b38efaf7 2025-12-02 18:44:33+00:00| seen| https://gist.github.com/amandrei/85086c228259a7f5d19ac75bebcf815c 2025-12-02 18:47:50+00:00| seen|...
CVE-2025-61727
creationtimestamp| type| source ---|---|--- 2025-12-02 16:54:18+00:00| seen| https://bsky.app/profile/golang.org/post/3m6zft5ymxz2q 2025-12-03 02:20:06+00:00| seen| https://bsky.app/profile/pmloik.bsky.social/post/3m72fgw55uc2d 2025-12-03 21:10:06+00:00| seen|...
CVE-2025-48631
creationtimestamp| type| source ---|---|--- 2025-12-02 11:03:43+00:00| seen| https://bsky.app/profile/securityrss.bsky.social/post/3m6ysabxve527 2025-12-02 11:23:04+00:00| seen| https://bsky.app/profile/basefortify.bsky.social/post/3m6ytc4pph22v 2025-12-02 11:23:05+00:00| seen|...
CVE-2025-66384
creationtimestamp| type| source ---|---|--- 2025-11-28 09:24:09+00:00| seen| https://bsky.app/profile/cve.skyfleet.blue/post/3m6okskv77i2k 2025-11-28 09:53:38+00:00| seen| https://gist.github.com/Darkcrai86/43f5e100cce6709387de5a479a30e8c8 2025-12-03 19:49:28+00:00| seen|...
CVE-2025-34351
creationtimestamp| type| source ---|---|--- 2025-11-27 04:32:56+00:00| seen| https://infosec.exchange/users/offseq/statuses/115619789202134613 2025-11-27 04:32:59+00:00| seen| https://bsky.app/profile/offseq.bsky.social/post/3m6lk2x6rq52g 2025-11-27 05:23:45+00:00| seen|...
CVE-2025-13392
creationtimestamp| type| source ---|---|--- 2025-11-26 22:12:59+00:00| seen| https://bsky.app/profile/o2cloud.bsky.social/post/3m6kutiiynw2j 2025-11-26 22:23:12+00:00| seen| https://bsky.app/profile/o2cloud.bsky.social/post/3m6kvfrdxep2a 2025-12-03 05:00:00+00:00| seen|...
CVE-2025-66259
creationtimestamp| type| source ---|---|--- 2025-11-26 07:33:29+00:00| seen| https://infosec.exchange/users/offseq/statuses/115614836849417254 2025-11-26 07:33:30+00:00| seen| https://bsky.app/profile/offseq.bsky.social/post/3m6jdoudibg2g 2025-11-26 15:28:46+00:00| seen|...