CVE-2022-49218

In the Linux kernel, the following vulnerability has been resolved: drm/dp: Fix OOB read when handling Post Cursor2 register The linkstatus array was not large enough to read the Adjust Request Post Cursor2 register, so remove the common helper function to avoid an OOB read, found with a...

CVE-2022-49214

In the Linux kernel, the following vulnerability has been resolved: powerpc/64s: Don't use DSISR for SLB faults Since commit 46ddcb3950a2 "powerpc/mm: Show if a bad page fault on data is read or write." we use pagefaultiswriteregs-dsisr in badpagefault to determine if the fault is for a read or...

CVE-2022-49214

CVE-2022-49214 pertains to the Linux kernel on PowerPC 64s where Data SLB (Data Segment) faults do not set DSISR to a useful value, causing misclassification of read vs. write faults. The fix reworks the printing logic to treat SLB faults separately and only print read/write when the fault type c...

CVE-2022-49173

In the Linux kernel, the following vulnerability has been resolved: spi: fsi: Implement a timeout for polling status The data transfer routines must poll the status register to determine when more data can be shifted in or out. If the hardware gets into a bad state, these polling loops may never...

CVE-2022-49173

In the Linux kernel, CVE-2022-49173 affects the SPI FSI path where data transfer routines poll a status register and may hang if a hardware bad state occurs. The fix adds a timeout to polling and returns an error when exceeded, preventing infinite loops. Affected component: spi: fsi in the Linux ...

CVE-2022-49146 virtio: use virtio_device_ready() in virtio_device_restore()

In the Linux kernel, the following vulnerability has been resolved: virtio: use virtiodeviceready in virtiodevicerestore After waking up a suspended VM, the kernel prints the following trace for virtio drivers which do not directly call virtiodeviceready in the .restore: PM: suspend exit irq 22:...

CVE-2022-49146

In the Linux kernel, the following vulnerability has been resolved: virtio: use virtiodeviceready in virtiodevicerestore After waking up a suspended VM, the kernel prints the following trace for virtio drivers which do not directly call virtiodeviceready in the .restore: PM: suspend exit irq 22:...

CVE-2022-49146

The CVE-2022-49146 entry describes a Linux kernel issue in virtio handling where drivers bypass the enable_cbs callback during virtio_device_restore(), causing suspend-resume traces and potential interrupt handling problems. The root cause is failure to call virtio_device_ready() in restore, so i...

CVE-2022-49146 virtio: use virtio_device_ready() in virtio_device_restore()

In the Linux kernel, the following vulnerability has been resolved: virtio: use virtiodeviceready in virtiodevicerestore After waking up a suspended VM, the kernel prints the following trace for virtio drivers which do not directly call virtiodeviceready in the .restore: PM: suspend exit irq 22:...

CVE-2025-25517

creationtimestamp| type| source ---|---|--- 2025-02-26 01:13:38+00:00| seen| https://bsky.app/profile/cve.skyfleet.blue/post/3lj276afptc2v 2025-02-26 01:44:43+00:00| seen| https://t.me/cvedetector/18929 2025-02-26 19:49:10+00:00| seen|...

PT-2025-8119 · Linux +2 · Linux Kernel +2

Name of the Vulnerable Software and Affected Versions: Linux kernel affected versions not specified Description: A issue in the Linux kernel has been identified, specifically in the mxser module. The problem occurs when the Line Status Register LSR is 0xff in the activate function, which can lead...

CVE-2024-45421

creationtimestamp| type| source ---|---|--- 2025-02-25 20:22:52+00:00| seen| https://t.me/DarkWebInformerCVEAlerts/5368 2025-02-25 21:23:51+00:00| published-proof-of-concept| https://t.me/DarkWebInformerNews/1187 2025-02-25 21:23:58+00:00| seen|...

CVE-2024-12368

creationtimestamp| type| source ---|---|--- 2025-02-25 18:22:34+00:00| published-proof-of-concept| https://t.me/DarkWebInformerCVEAlerts/5340 2025-02-25 19:48:45+00:00| seen| https://mastodon.social/users/CyberSignaler/statuses/114066255003294911 2025-02-25 21:33:58+00:00| seen|...

CVE-2023-20559

creationtimestamp| type| source ---|---|--- 2025-02-25 17:23:25+00:00| seen| https://t.me/DarkWebInformerCVEAlerts/5339...

CVE-2025-26985

creationtimestamp| type| source ---|---|--- 2025-02-25 17:22:39+00:00| seen| https://t.me/cvedetector/18867 2025-02-25 17:48:59+00:00| seen| https://mastodon.social/users/CyberSignaler/statuses/114065784094507463 2025-08-22 17:25:06+00:00| seen| MISP/8e1b6542-ae86-4729-a7a6-4e9f670b8bb7...

CVE-2025-26987

creationtimestamp| type| source ---|---|--- 2025-02-25 17:03:00+00:00| seen| https://bsky.app/profile/cve.skyfleet.blue/post/3lizdqxfyeh2k 2025-02-25 17:22:41+00:00| seen| https://t.me/cvedetector/18870 2025-08-22 17:25:06+00:00| seen| MISP/8e1b6542-ae86-4729-a7a6-4e9f670b8bb7...

Information Exposure

Overview glpi/glpi is a free Asset and IT Management Software package with ITIL Service Desk, licenses tracking and software auditing. Affected versions of this package are vulnerable to Information Exposure via the status.php endpoint. Workaround This vulnerability can be mitigated by: 1 deletin...

UBUNTU-CVE-2025-21626

GLPI is a free asset and IT management software package. Starting in version 0.71 and prior to version 10.0.18, an anonymous user can fetch sensitive information from the status.php endpoint. Version 10.0.18 contains a fix for the issue. Some workarounds are available. One may delete the status.p...

CVE-2025-21626 GLPI vulnerable to exposure of sensitive information in the `status.php` endpoint

GLPI is a free asset and IT management software package. Starting in version 0.71 and prior to version 10.0.18, an anonymous user can fetch sensitive information from the status.php endpoint. Version 10.0.18 contains a fix for the issue. Some workarounds are available. One may delete the status.p...

urllib3: Request body not stripped after redirect from 303 status changes request method to GET

A flaw was found in urllib3, an HTTP client library for Python. urllib3 doesn't remove the HTTP request body when an HTTP redirect response using status 301, 302, or 303, after changing the method in a request from one that could accept a request body such as POST to GET, as is required by HTTP...