https://db.gcve.eu/sightings/feed 2026-06-06T08:01:32.047398+00:00 Vulnerability-Lookup info@gcve.eu python-feedgen Contains only the most 10 recent sightings. https://db.gcve.eu/sighting/8178263e-4cf5-4d42-b9b1-5b827359f843/export 2026-06-06T08:01:32.457835+00:00 cedric https://db.gcve.eu/user/cedric {"uuid": "8178263e-4cf5-4d42-b9b1-5b827359f843", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2022-4890", "type": "seen", "source": "https://t.me/cibsecurity/56531", "content": "\u203c CVE-2022-4890 \u203c\n\nA vulnerability, which was classified as critical, has been found in abhilash1985 PredictApp. This issue affects some unknown processing of the file config/initializers/new_framework_defaults_7_0.rb of the component Cookie Handler. The manipulation leads to deserialization. The attack may be initiated remotely. The name of the patch is b067372f3ee26fe1b657121f0f41883ff4461a06. It is recommended to apply a patch to fix this issue. The associated identifier of this vulnerability is VDB-218387.\n\n\ud83d\udcd6 Read\n\nvia \"National Vulnerability Database\".", "creation_timestamp": "2023-01-16T16:25:11.000000Z"} 2023-01-16T16:25:11+00:00 https://db.gcve.eu/sighting/952c0791-bd79-4ef1-a603-e919c0abbd59/export 2026-06-06T08:01:32.457779+00:00 cedric https://db.gcve.eu/user/cedric {"uuid": "952c0791-bd79-4ef1-a603-e919c0abbd59", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2022-48909", "type": "seen", "source": "https://t.me/cvedetector/3858", "content": "{\n \"Source\": \"CVE FEED\",\n \"Title\": \"CVE-2022-48909 - \"Linux SMC Connection Leak\"\", \n \"Content\": \"CVE ID : CVE-2022-48909 \nPublished : Aug. 22, 2024, 2:15 a.m. | 37\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved: \n \nnet/smc: fix connection leak \n \nThere's a potential leak issue under following execution sequence : \n \nsmc_release smc_connect_work \nif (sk->sk_state == SMC_INIT) \n send_clc_confirim \n tcp_abort(); \n ... \n sk.sk_state = SMC_ACTIVE \nsmc_close_active \nswitch(sk->sk_state) { \n... \ncase SMC_ACTIVE: \n smc_close_final() \n // then wait peer closed \n \nUnfortunately, tcp_abort() may discard CLC CONFIRM messages that are \nstill in the tcp send buffer, in which case our connection token cannot \nbe delivered to the server side, which means that we cannot get a \npassive close message at all. Therefore, it is impossible for the to be \ndisconnected at all. \n \nThis patch tries a very simple way to avoid this issue, once the state \nhas changed to SMC_ACTIVE after tcp_abort(), we can actively abort the \nsmc connection, considering that the state is SMC_INIT before \ntcp_abort(), abandoning the complete disconnection process should not \ncause too much problem. \n \nIn fact, this problem may exist as long as the CLC CONFIRM message is \nnot received by the server. Whether a timer should be added after \nsmc_close_final() needs to be discussed in the future. But even so, this \npatch provides a faster release for connection in above case, it should \nalso be valuable. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n \"Detection Date\": \"22 Aug 2024\",\n \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-08-22T05:07:58.000000Z"} 2024-08-22T05:07:58+00:00 https://db.gcve.eu/sighting/f03a680d-0982-41c4-9176-14385ad4757f/export 2026-06-06T08:01:32.457729+00:00 cedric https://db.gcve.eu/user/cedric {"uuid": "f03a680d-0982-41c4-9176-14385ad4757f", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2022-48905", "type": "seen", "source": "https://t.me/cvedetector/3859", "content": "{\n \"Source\": \"CVE FEED\",\n \"Title\": \"CVE-2022-48905 - IBM vNIC Memory Leak (Information Disclosure)\", \n \"Content\": \"CVE ID : CVE-2022-48905 \nPublished : Aug. 22, 2024, 2:15 a.m. | 37\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved: \n \nibmvnic: free reset-work-item when flushing \n \nFix a tiny memory leak when flushing the reset work queue. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n \"Detection Date\": \"22 Aug 2024\",\n \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-08-22T05:08:01.000000Z"} 2024-08-22T05:08:01+00:00 https://db.gcve.eu/sighting/c41fd379-a47b-4ceb-9741-71120bb32bb7/export 2026-06-06T08:01:32.457679+00:00 cedric https://db.gcve.eu/user/cedric {"uuid": "c41fd379-a47b-4ceb-9741-71120bb32bb7", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2022-48907", "type": "seen", "source": "https://t.me/cvedetector/3860", "content": "{\n \"Source\": \"CVE FEED\",\n \"Title\": \"CVE-2022-48907 - Linux Kernel auxdisplay lcd2s Memory Leak\", \n \"Content\": \"CVE ID : CVE-2022-48907 \nPublished : Aug. 22, 2024, 2:15 a.m. | 37\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved: \n \nauxdisplay: lcd2s: Fix memory leak in ->remove() \n \nOnce allocated the struct lcd2s_data is never freed. \nFix the memory leak by switching to devm_kzalloc(). \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n \"Detection Date\": \"22 Aug 2024\",\n \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-08-22T05:08:02.000000Z"} 2024-08-22T05:08:02+00:00 https://db.gcve.eu/sighting/0f2ee6ce-fd3b-4ea5-8ff7-e527763495c3/export 2026-06-06T08:01:32.457618+00:00 cedric https://db.gcve.eu/user/cedric {"uuid": "0f2ee6ce-fd3b-4ea5-8ff7-e527763495c3", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2022-48908", "type": "seen", "source": "https://t.me/cvedetector/3869", "content": "{\n \"Source\": \"CVE FEED\",\n \"Title\": \"CVE-2022-48908 - \"Linux Arcnet com20020 Null Pointer Dereference Vulnerability\"\", \n \"Content\": \"CVE ID : CVE-2022-48908 \nPublished : Aug. 22, 2024, 2:15 a.m. | 37\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved: \n \nnet: arcnet: com20020: Fix null-ptr-deref in com20020pci_probe() \n \nDuring driver initialization, the pointer of card info, i.e. the \nvariable 'ci' is required. However, the definition of \n'com20020pci_id_table' reveals that this field is empty for some \ndevices, which will cause null pointer dereference when initializing \nthese devices. \n \nThe following log reveals it: \n \n[ 3.973806] KASAN: null-ptr-deref in range [0x0000000000000028-0x000000000000002f] \n[ 3.973819] RIP: 0010:com20020pci_probe+0x18d/0x13e0 [com20020_pci] \n[ 3.975181] Call Trace: \n[ 3.976208] local_pci_probe+0x13f/0x210 \n[ 3.977248] pci_device_probe+0x34c/0x6d0 \n[ 3.977255] ? pci_uevent+0x470/0x470 \n[ 3.978265] really_probe+0x24c/0x8d0 \n[ 3.978273] __driver_probe_device+0x1b3/0x280 \n[ 3.979288] driver_probe_device+0x50/0x370 \n \nFix this by checking whether the 'ci' is a null pointer first. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n \"Detection Date\": \"22 Aug 2024\",\n \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-08-22T05:08:50.000000Z"} 2024-08-22T05:08:50+00:00 https://db.gcve.eu/sighting/7fdf206e-a6de-42b7-ac33-be4aae635ab6/export 2026-06-06T08:01:32.457554+00:00 cedric https://db.gcve.eu/user/cedric {"uuid": "7fdf206e-a6de-42b7-ac33-be4aae635ab6", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2022-48906", "type": "seen", "source": "https://t.me/cvedetector/3872", "content": "{\n \"Source\": \"CVE FEED\",\n \"Title\": \"CVE-2022-48906 - Linux MPTCP Shift-OutOfBounds Vulnerability\", \n \"Content\": \"CVE ID : CVE-2022-48906 \nPublished : Aug. 22, 2024, 2:15 a.m. | 37\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved: \n \nmptcp: Correctly set DATA_FIN timeout when number of retransmits is large \n \nSyzkaller with UBSAN uncovered a scenario where a large number of \nDATA_FIN retransmits caused a shift-out-of-bounds in the DATA_FIN \ntimeout calculation: \n \n================================================================================ \nUBSAN: shift-out-of-bounds in net/mptcp/protocol.c:470:29 \nshift exponent 32 is too large for 32-bit type 'unsigned int' \nCPU: 1 PID: 13059 Comm: kworker/1:0 Not tainted 5.17.0-rc2-00630-g5fbf21c90c60 #1 \nHardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.13.0-1ubuntu1.1 04/01/2014 \nWorkqueue: events mptcp_worker \nCall Trace: \n \n __dump_stack lib/dump_stack.c:88 [inline] \n dump_stack_lvl+0xcd/0x134 lib/dump_stack.c:106 \n ubsan_epilogue+0xb/0x5a lib/ubsan.c:151 \n __ubsan_handle_shift_out_of_bounds.cold+0xb2/0x20e lib/ubsan.c:330 \n mptcp_set_datafin_timeout net/mptcp/protocol.c:470 [inline] \n __mptcp_retrans.cold+0x72/0x77 net/mptcp/protocol.c:2445 \n mptcp_worker+0x58a/0xa70 net/mptcp/protocol.c:2528 \n process_one_work+0x9df/0x16d0 kernel/workqueue.c:2307 \n worker_thread+0x95/0xe10 kernel/workqueue.c:2454 \n kthread+0x2f4/0x3b0 kernel/kthread.c:377 \n ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:295 \n \n================================================================================ \n \nThis change limits the maximum timeout by limiting the size of the \nshift, which keeps all intermediate values in-bounds. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n \"Detection Date\": \"22 Aug 2024\",\n \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-08-22T05:08:53.000000Z"} 2024-08-22T05:08:53+00:00 https://db.gcve.eu/sighting/44311bf0-47ce-49bf-b501-d352cc0cbedb/export 2026-06-06T08:01:32.457498+00:00 cedric https://db.gcve.eu/user/cedric {"uuid": "44311bf0-47ce-49bf-b501-d352cc0cbedb", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2022-48909", "type": "seen", "source": "https://vulnerability.circl.lu/bundle/816dcc8e-f25a-4895-9b59-1bbd9caeccb8", "content": "", "creation_timestamp": "2025-12-03T14:14:49.267740Z"} 2025-12-03T14:14:49.267740+00:00 https://db.gcve.eu/sighting/6fd20309-6559-4b1e-bdca-eab54afecec9/export 2026-06-06T08:01:32.457427+00:00 cedric https://db.gcve.eu/user/cedric {"uuid": "6fd20309-6559-4b1e-bdca-eab54afecec9", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2022-48901", "type": "seen", "source": "https://vulnerability.circl.lu/bundle/816dcc8e-f25a-4895-9b59-1bbd9caeccb8", "content": "", "creation_timestamp": "2025-12-03T14:14:49.267740Z"} 2025-12-03T14:14:49.267740+00:00 https://db.gcve.eu/sighting/b04f0442-b739-4308-881b-cddcfb0ca4a8/export 2026-06-06T08:01:32.456330+00:00 cedric https://db.gcve.eu/user/cedric {"uuid": "b04f0442-b739-4308-881b-cddcfb0ca4a8", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2022-48902", "type": "seen", "source": "https://vulnerability.circl.lu/bundle/816dcc8e-f25a-4895-9b59-1bbd9caeccb8", "content": "", "creation_timestamp": "2025-12-03T14:14:49.267740Z"} 2025-12-03T14:14:49.267740+00:00