Kushalkhemka/embedding-cve-nvd-dataset huggingface dataset:
: - https://git.kernel.org/stable/c/c9d6afb4f9c338049662d27d169fba7dd60e337d - https://git.kernel.org/stable/c/36b23e3baf9129d5b6c3a3a85b6b7ffb75ae287c
CVE ID: CVE-2024-57951 State: PUBLISHED Published: 2025-02-12T13:27:53.124Z Last Updated: 2025-11-03T20:56:20.172Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: hrtimers: Handle CPU state correctly on hotplug Consider a scenario where a CPU transitions from CPUHP_ONLINE to halfway through a CPU hotunplug down to CPUHP_HRTIMERS_PREPARE, and then back to CPUHP_ONLINE: Since hrtimers_prepare_cpu() does not run, cpu_base.hres_active remains set to 1 throughout. However, during a CPU unplug operation, the tick and the clockevents are shut down at CPUHP_AP_TICK_DYING. On return to the online state, for instance CFS incorrectly assum
the clockevents are shut down at CPUHP_AP_TICK_DYING. On return to the online state, for instance CFS incorrectly assumes that the hrtick is already active, and the chance of the clockevent device to transition to oneshot mode is also lost forever for the CPU, unless it goes back to a lower state than CPUHP_HRTIMERS_PREPARE once. This round-trip reveals another issue; cpu_base.online is not set to 1 after the transition, which appears as a WARN_ON_ONCE in enqueue_hrtimer(). Aside of that, the bulk of the per CPU state is not reset either, which means there are dangling pointers in the worst case. Address this by adding a corresponding startup() callback, which resets the stale per CPU state
nters in the worst case. Address this by adding a corresponding startup() callback, which resets the stale per CPU state and sets the online flag. [ tglx: Make the new callback unconditionally available, remove the online modification in the prepare() callback and clear the remaining state in the starting callback instead of the prepare callback ] Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/95e4f62df23f4df1ce6ef897d44b8e23c260921a - https://git.kernel.org/stable/c/14984139f1f2768883332965db566ef26db609e7 - https://git.kernel.org/stable/c/15b453db41d36184cf0ccc21e7df624014ab6a1a - https://git.kernel.org/stable/c/3d4
db609e7 - https://git.kernel.org/stable/c/15b453db41d36184cf0ccc21e7df624014ab6a1a - https://git.kernel.org/stable/c/3d41dbf82e10c44e53ea602398ab002baec27e75 - https://git.kernel.org/stable/c/a5cbbea145b400e40540c34816d16d36e0374fbc - https://git.kernel.org/stable/c/38492f6ee883c7b1d33338bf531a62cff69b4b28 - https://git.kernel.org/stable/c/2f8dea1692eef2b7ba6a256246ed82c365fdc686
CVE ID: CVE-2024-57952 State: PUBLISHED Published: 2025-02-12T13:52:45.229Z Last Updated: 2025-10-01T19:57:09.380Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: Revert "libfs: fix infinite directory reads for offset dir" The current directory offset allocator (based on mtree_alloc_cyclic) stores the next offset value to return in octx->next_offset. This mechanism typically returns values that increase monotonically over time. Eventually, though, the newly allocated offset value wraps back to a low number (say, 2) which is smaller than other already- allocated offset values. Yu Kuai <yukuai3@huawei.com> reports that, after comm
, 2) which is smaller than other already- allocated offset values. Yu Kuai <yukuai3@huawei.com> reports that, after commit 64a7ce76fb90 ("libfs: fix infinite directory reads for offset dir"), if a directory's offset allocator wraps, existing entries are no longer visible via readdir/getdents because offset_readdir() stops listing entries once an entry's offset is larger than octx->next_offset. These entries vanish persistently -- they can be looked up, but will never again appear in readdir(3) output. The reason for this is that the commit treats directory offsets as monotonically increasing integer values rather than opaque cookies, and introduces this comparison: if (dentry2offset(dentry)
nically increasing integer values rather than opaque cookies, and introduces this comparison: if (dentry2offset(dentry) >= last_index) { On 64-bit platforms, the directory offset value upper bound is 2^63 - 1. Directory offsets will monotonically increase for millions of years without wrapping. On 32-bit platforms, however, LONG_MAX is 2^31 - 1. The allocator can wrap after only a few weeks (at worst). Revert commit 64a7ce76fb90 ("libfs: fix infinite directory reads for offset dir") to prepare for a fix that can work properly on 32-bit systems and might apply to recent LTS kernels where shmem employs the simple_offset mechanism. Additional Analyst Notes: - CISA ADP Vulnrichment: References:
kernels where shmem employs the simple_offset mechanism. Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/9e9e710f68bac49bd9b587823c077d06363440e0 - https://git.kernel.org/stable/c/3f250b82040a72b0059ae00855a74d8570ad2147 - https://git.kernel.org/stable/c/b662d858131da9a8a14e68661656989b14dbf113
CVE ID: CVE-2024-57953 State: PUBLISHED Published: 2025-02-27T02:07:01.598Z Last Updated: 2025-10-01T19:36:43.523Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: rtc: tps6594: Fix integer overflow on 32bit systems The problem is this multiply in tps6594_rtc_set_offset() tmp = offset * TICKS_PER_HOUR; The "tmp" variable is an s64 but "offset" is a long in the (-277774)-277774 range. On 32bit systems a long can hold numbers up to approximately two billion. The number of TICKS_PER_HOUR is really large, (32768 * 3600) or roughly a hundred million. When you start multiplying by a hundred million it doesn't take long to overflow the
600) or roughly a hundred million. When you start multiplying by a hundred million it doesn't take long to overflow the two billion mark. Probably the safest way to fix this is to change the type of TICKS_PER_HOUR to long long because it's such a large number. Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/5127f3cbfc78a7b301b86328247230bec47e0bb3 - https://git.kernel.org/stable/c/53b0c7b15accb18d15d95c7fe68f61630ebfd1ca - https://git.kernel.org/stable/c/09c4a610153286cef54d4f0c85398f4e32fc227e
CVE ID: CVE-2024-57954 State: PUBLISHED Published: 2025-02-06T12:23:41.778Z Last Updated: 2025-09-18T06:47:03.832Z Severity: MEDIUM (CVSS 6.2 CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N) Vendors: Huawei Products: HarmonyOS Problem Types: CWE-285 Description: Permission verification vulnerability in the media library module Impact: Successful exploitation of this vulnerability may affect service confidentiality. Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://consumer.huawei.com/en/support/bulletin/2025/2/
CVE ID: CVE-2024-57955 State: PUBLISHED Published: 2025-02-06T12:25:22.348Z Last Updated: 2025-09-18T06:47:24.559Z Severity: MEDIUM (CVSS 6.1 CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:L/A:N) Vendors: Huawei Products: HarmonyOS Problem Types: CWE-787 Description: Arbitrary write vulnerability in the Gallery module Impact: Successful exploitation of this vulnerability may affect service confidentiality. Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://consumer.huawei.com/en/support/bulletin/2025/2/
CVE ID: CVE-2024-57956 State: PUBLISHED Published: 2025-02-06T12:26:10.611Z Last Updated: 2025-02-12T19:51:09.761Z Severity: LOW (CVSS 2.8 CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:N/I:N/A:L) Vendors: Huawei Products: HarmonyOS Problem Types: CWE-680 Description: Out-of-bounds read vulnerability in the interpreter string module Impact: Successful exploitation of this vulnerability may affect availability. Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://consumer.huawei.com/en/support/bulletin/2025/2/
CVE ID: CVE-2024-57957 State: PUBLISHED Published: 2025-02-06T12:27:07.878Z Last Updated: 2025-02-12T19:51:09.645Z Severity: MEDIUM (CVSS 6.6 CVSS:3.1/AV:P/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H) Vendors: Huawei Products: HarmonyOS Problem Types: CWE-657 Description: Vulnerability of improper log information control in the UI framework module Impact: Successful exploitation of this vulnerability may affect service confidentiality. Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://consumer.huawei.com/en/support/bulletin/2025/2/
CVE ID: CVE-2024-57958 State: PUBLISHED Published: 2025-02-06T12:29:41.313Z Last Updated: 2025-02-06T14:38:36.148Z Severity: MEDIUM (CVSS 5.7 CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:L) Vendors: Huawei Products: HarmonyOS, EMUI Problem Types: CWE-125 Description: Out-of-bounds array read vulnerability in the FFRT module Impact: Successful exploitation of this vulnerability may cause features to perform abnormally. Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://consumer.huawei.com/en/support/bulletin/2025/2/
CVE ID: CVE-2024-57959 State: PUBLISHED Published: 2025-02-06T12:31:09.281Z Last Updated: 2025-02-06T14:35:27.060Z Severity: MEDIUM (CVSS 6.1 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:H) Vendors: Huawei Products: HarmonyOS, EMUI Problem Types: CWE-416 Description: Use-After-Free (UAF) vulnerability in the display module Impact: Successful exploitation of this vulnerability may cause features to perform abnormally. Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://consumer.huawei.com/en/support/bulletin/2025/2/
CVE ID: CVE-2024-57960 State: PUBLISHED Published: 2025-02-06T12:32:39.794Z Last Updated: 2025-02-06T14:25:06.468Z Severity: HIGH (CVSS 7.7 CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:L/A:L) Vendors: Huawei Products: HarmonyOS, EMUI Problem Types: CWE-20 Description: Input verification vulnerability in the ExternalStorageProvider module Impact: Successful exploitation of this vulnerability may affect service confidentiality. Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://consumer.huawei.com/en/support/bulletin/2025/2/
CVE ID: CVE-2024-57961 State: PUBLISHED Published: 2025-02-06T12:33:50.291Z Last Updated: 2025-02-06T14:21:20.703Z Severity: MEDIUM (CVSS 6.8 CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:L) Vendors: Huawei Products: HarmonyOS, EMUI Problem Types: CWE-787 Description: Out-of-bounds write vulnerability in the emcom module Impact: Successful exploitation of this vulnerability may cause features to perform abnormally. Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://consumer.huawei.com/en/support/bulletin/2025/2/
CVE ID: CVE-2024-57962 State: PUBLISHED Published: 2025-02-06T12:34:43.361Z Last Updated: 2025-02-06T14:17:03.936Z Severity: MEDIUM (CVSS 6.1 CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:H) Vendors: Huawei Products: HarmonyOS Problem Types: CWE-701 Description: Vulnerability of incomplete verification information in the VPN service module Impact: Successful exploitation of this vulnerability may affect availability. Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://consumer.huawei.com/en/support/bulletin/2025/2/
CVE ID: CVE-2024-57963 State: PUBLISHED Published: 2025-02-18T06:33:02.885Z Last Updated: 2025-02-18T15:51:30.918Z Severity: HIGH (CVSS 7.3 CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H) Vendors: Hitachi Products: USB-CONVERTERCABLE DRIVER Problem Types: CWE-427 Description: Insecure Loading of Dynamic Link Libraries have been discovered in USB-CONVERTERCABLE DRIVER, which could allow local attackers to potentially disclose information or execute arbitray code on affected systems. This issue affects USB-CONVERTERCABLE DRIVER:. Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://www.hitachi.com/hirt/hitachi-sec/2025/001.html
CVE ID: CVE-2024-57964 State: PUBLISHED Published: 2025-02-18T06:33:57.761Z Last Updated: 2025-02-18T15:50:58.867Z Severity: HIGH (CVSS 7.3 CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H) Vendors: Hitachi Products: HVAC Energy Saving Program Problem Types: CWE-427 Description: Insecure Loading of Dynamic Link Libraries have been discovered in HVAC Energy Saving Program, which could allow local attackers to potentially disclose information or execute arbitray code on affected systems. This issue affects HVAC Energy Saving Program:. Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://www.hitachi.com/hirt/hitachi-sec/2025/001.html
CVE ID: CVE-2024-57965 State: PUBLISHED Published: 2025-01-29T00:00:00.000Z Last Updated: 2025-01-29T14:14:23.882Z Severity: NONE (CVSS N/A CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:N/A:N) Vendors: axios Products: axios Problem Types: CWE-346 Description: In axios before 1.7.8, lib/helpers/isURLSameOrigin.js does not use a URL object when determining an origin, and has a potentially unwanted setAttribute('href',href) call. NOTE: some parties feel that the code change only addresses a warning message from a SAST tool and does not fix a vulnerability. Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://github.com/axios/axios/issues/6351 - https://github.com/axios/axios/releas
CISA ADP Vulnrichment: References: - https://github.com/axios/axios/issues/6351 - https://github.com/axios/axios/releases/tag/v1.7.8 - https://github.com/axios/axios/commit/0a8d6e19da5b9899a2abafaaa06a75ee548597db - https://github.com/axios/axios/pull/6714
CVE ID: CVE-2024-57966 State: PUBLISHED Published: 2025-02-03T00:00:00.000Z Last Updated: 2025-02-09T05:02:36.861Z Severity: MEDIUM (CVSS 5 CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:N/I:L/A:L) Vendors: KDE Products: ark Problem Types: CWE-36 Description: libarchiveplugin.cpp in KDE ark before 24.12.0 can extract to an absolute path from an archive. Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://github.com/KDE/ark/commit/fe518d81b338941e0bf1c5ce5e75a9ab6de4bb58 - https://github.com/KDE/ark/compare/v24.11.90...v24.12.0
CVE ID: CVE-2024-57967 State: PUBLISHED Published: 2025-02-03T00:00:00.000Z Last Updated: 2025-02-12T20:51:24.795Z Severity: MEDIUM (CVSS 4.2 CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N) Vendors: CyberArk Products: Privileged Access Manager Problem Types: CWE-266 Description: PVWA (Password Vault Web Access) in CyberArk Privileged Access Manager Self-Hosted before 14.4 has potentially elevated privileges in LDAP mapping. Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://docs.cyberark.com/pam-self-hosted/latest/en/content/release%20notes/rn-whatsnew14-4.htm#Securitybugfixes - https://www.cyberark.com/ca24-15/
CVE ID: CVE-2024-57968 State: PUBLISHED Published: 2025-02-03T00:00:00.000Z Last Updated: 2025-10-21T22:55:30.718Z Severity: CRITICAL (CVSS 9.9 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H) Vendors: Advantive Products: VeraCore Problem Types: CWE-434 Description: Advantive VeraCore before 2024.4.2.1 allows remote authenticated users to upload files to unintended folders (e.g., ones that are accessible during web browsing by other users). upload.aspx can be used for this. Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://advantive.my.site.com/support/s/article/VeraCore-Release-Notes-2024-4-2-1 - https://intezer.com/blog/research/xe-group-exploiting-zero-days/ - https://
/article/VeraCore-Release-Notes-2024-4-2-1 - https://intezer.com/blog/research/xe-group-exploiting-zero-days/ - https://www.solissecurity.com/en-us/insights/xe-group-from-credit-card-skimming-to-exploiting-zero-days/
CVE ID: CVE-2024-57969 State: PUBLISHED Published: 2025-02-14T00:00:00.000Z Last Updated: 2025-02-14T15:42:21.986Z Severity: MEDIUM (CVSS 4.3 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N) Vendors: MISP Products: MISP Problem Types: CWE-863 Description: app/Model/Attribute.php in MISP before 2.4.198 ignores an ACL during a GUI attribute search. Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://github.com/MISP/MISP/compare/v2.4.197...v2.4.198 - https://github.com/MISP/MISP/commit/4f27f83a775aba4d3cca9255f69c3c9998b7df7f
CVE ID: CVE-2024-57970 State: PUBLISHED Published: 2025-02-16T00:00:00.000Z Last Updated: 2025-02-18T17:05:13.914Z Severity: MEDIUM (CVSS 4 CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L) Vendors: libarchive Products: libarchive Problem Types: CWE-126 Description: libarchive through 3.7.7 has a heap-based buffer over-read in header_gnu_longlink in archive_read_support_format_tar.c via a TAR archive because it mishandles truncation in the middle of a GNU long linkname. Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://github.com/libarchive/libarchive/issues/2415 - https://github.com/libarchive/libarchive/pull/2422
CVE ID: CVE-2024-57971 State: PUBLISHED Published: 2025-02-16T00:00:00.000Z Last Updated: 2025-03-21T13:48:38.429Z Severity: CRITICAL (CVSS 9.1 CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H) Vendors: eng Products: KNOWAGE Problem Types: CWE-99 Description: DataSourceResource.java in the SpagoBI API support in Knowage Server in KNOWAGE before 8.1.30 does not ensure that java:comp/env/jdbc/ occurs at the beginning of a JNDI Name. Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://github.com/KnowageLabs/Knowage-Server/commit/f7d0362f737e1b0db1cc9cc95b1236d62d83dd0c - https://spagobi.readthedocs.io - https://github.com/KnowageLabs/Knowage-Server/compare/v8.1.29...v8.1.30 - h
62d83dd0c - https://spagobi.readthedocs.io - https://github.com/KnowageLabs/Knowage-Server/compare/v8.1.29...v8.1.30 - https://github.com/darumaseye/CVEs/blob/ec2de9f7ecffde466e687745bfdfc672e86241d7/CVE-2024-57971.md
CVE ID: CVE-2024-57972 State: PUBLISHED Published: 2025-03-06T00:00:00.000Z Last Updated: 2025-03-07T18:01:18.310Z Severity: MEDIUM (CVSS 6.5 CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H) Vendors: Microsoft Products: HoloLens Problem Types: CWE-770 Description: The pairing API request handler in Microsoft HoloLens 1 (Windows Holographic) through 10.0.17763.3046 and HoloLens 2 (Windows Holographic) through 10.0.22621.1244 allows remote attackers to cause a Denial of Service (resource consumption and device unusability) by sending many requests through the Device Portal framework. Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://github.com/tania-silva/Hololens
CVE ID: CVE-2024-57973 State: PUBLISHED Published: 2025-02-27T02:07:02.342Z Last Updated: 2025-11-03T19:32:49.370Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: rdma/cxgb4: Prevent potential integer overflow on 32bit The "gl->tot_len" variable is controlled by the user. It comes from process_responses(). On 32bit systems, the "gl->tot_len + sizeof(struct cpl_pass_accept_req) + sizeof(struct rss_header)" addition could have an integer wrapping bug. Use size_add() to prevent this. Additional Analyst Notes: - CVE Program Container: References: - https://git.kernel.org/stable/c/2b759f78b83221f4a1cae3aeb20b500e375f3ee6 - https://gi
E Program Container: References: - https://git.kernel.org/stable/c/2b759f78b83221f4a1cae3aeb20b500e375f3ee6 - https://git.kernel.org/stable/c/d64148a10a85952352de6091ceed99fb9ce2d3ee - https://git.kernel.org/stable/c/e53ca458f543aa352d09b484550de173cb9085c2 - https://git.kernel.org/stable/c/4422f452d028850b9cc4fd8f1cf45a8ff91855eb - https://git.kernel.org/stable/c/de8d88b68d0cfd41152a7a63d6aec0ed3e1b837a - https://git.kernel.org/stable/c/dd352107f22bfbecbbf3b74bde14f3f932296309 - https://git.kernel.org/stable/c/aeb814484387811b3579d5c78ad4eb301e3bf1c8 - https://git.kernel.org/stable/c/bd96a3935e89486304461a21752f824fc25e0f0b
CVE ID: CVE-2024-57974 State: PUBLISHED Published: 2025-02-27T02:07:02.973Z Last Updated: 2025-05-04T10:07:29.082Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: udp: Deal with race between UDP socket address change and rehash If a UDP socket changes its local address while it's receiving datagrams, as a result of connect(), there is a period during which a lookup operation might fail to find it, after the address is changed but before the secondary hash (port and address) and the four-tuple hash (local and remote ports and addresses) are updated. Secondary hash chains were introduced by commit 30fff9231fad ("udp: bind() optimi
mote ports and addresses) are updated. Secondary hash chains were introduced by commit 30fff9231fad ("udp: bind() optimisation") and, as a result, a rehash operation became needed to make a bound socket reachable again after a connect(). This operation was introduced by commit 719f835853a9 ("udp: add rehash on connect()") which isn't however a complete fix: the socket will be found once the rehashing completes, but not while it's pending. This is noticeable with a socat(1) server in UDP4-LISTEN mode, and a client sending datagrams to it. After the server receives the first datagram (cf. _xioopen_ipdgram_listen()), it issues a connect() to the address of the sender, in order to set up a direc
datagram (cf. _xioopen_ipdgram_listen()), it issues a connect() to the address of the sender, in order to set up a directed flow. Now, if the client, running on a different CPU thread, happens to send a (subsequent) datagram while the server's socket changes its address, but is not rehashed yet, this will result in a failed lookup and a port unreachable error delivered to the client, as apparent from the following reproducer: LEN=$(($(cat /proc/sys/net/core/wmem_default) / 4)) dd if=/dev/urandom bs=1 count=${LEN} of=tmp.in while :; do taskset -c 1 socat UDP4-LISTEN:1337,null-eof OPEN:tmp.out,create,trunc & sleep 0.1 || sleep 1 taskset -c 2 socat OPEN:tmp.in UDP4:localhost:1337,shut-null wait
l-eof OPEN:tmp.out,create,trunc & sleep 0.1 || sleep 1 taskset -c 2 socat OPEN:tmp.in UDP4:localhost:1337,shut-null wait done where the client will eventually get ECONNREFUSED on a write() (typically the second or third one of a given iteration): 2024/11/13 21:28:23 socat[46901] E write(6, 0x556db2e3c000, 8192): Connection refused This issue was first observed as a seldom failure in Podman's tests checking UDP functionality while using pasta(1) to connect the container's network namespace, which leads us to a reproducer with the lookup error resulting in an ICMP packet on a tap device: LOCAL_ADDR="$(ip -j -4 addr show|jq -rM '.[] | .addr_info[0] | select(.scope == "global").local')" while :;
tap device: LOCAL_ADDR="$(ip -j -4 addr show|jq -rM '.[] | .addr_info[0] | select(.scope == "global").local')" while :; do ./pasta --config-net -p pasta.pcap -u 1337 socat UDP4-LISTEN:1337,null-eof OPEN:tmp.out,create,trunc & sleep 0.2 || sleep 1 socat OPEN:tmp.in UDP4:${LOCAL_ADDR}:1337,shut-null wait cmp tmp.in tmp.out done Once this fails: tmp.in tmp.out differ: char 8193, line 29 we can finally have a look at what's going on: $ tshark -r pasta.pcap 1 0.000000 :: ? ff02::16 ICMPv6 110 Multicast Listener Report Message v2 2 0.168690 88.198.0.161 ? 88.198.0.164 UDP 8234 60260 ? 1337 Len=8192 3 0.168767 88.198.0.161 ? 88.198.0.164 UDP 8234 60260 ? 1337 Len=8192 4 0.168806 88.198.0.161 ? 88.
0260 ? 1337 Len=8192 3 0.168767 88.198.0.161 ? 88.198.0.164 UDP 8234 60260 ? 1337 Len=8192 4 0.168806 88.198.0.161 ? 88.198.0.164 UDP 8234 60260 ? 1337 Len=8192 5 0.168827 c6:47:05:8d:dc:04 ? Broadcast ARP 42 Who has 88.198.0.161? Tell 88.198.0.164 6 0.168851 9a:55:9a:55:9a:55 ? c6:47:05:8d:dc:04 ARP 42 88.198.0.161 is at 9a:55:9a:55:9a:55 7 0.168875 88.198.0.161 ? 88.198.0.164 UDP 8234 60260 ? 1337 Len=8192 8 0.168896 88.198.0.164 ? 88.198.0.161 ICMP 590 Destination unreachable (Port unreachable) 9 0.168926 88.198.0.161 ? 88.198.0.164 UDP 8234 60260 ? 1337 Len=8192 10 0.168959 88.198.0.161 ? 88.198.0.164 UDP 8234 60260 ? 1337 Len=8192 11 0.168989 88.198.0.161 ? 88.198.0.164 UDP 4138 60260 ?