{"vulnerability": "2025-37", "sightings": [{"uuid": "eebfb761-9b85-43b3-ae52-296e467f75ad", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37891", "type": "seen", "source": "https://infosec.exchange/users/vuldb/statuses/114533369295562334", "content": "", "creation_timestamp": "2025-05-19T07:42:03.299378Z"}, {"uuid": "1d768c5e-8dc5-44a8-b5ca-a87dfaca0c80", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37992", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lq3qfvghnb2o", "content": "", "creation_timestamp": "2025-05-26T17:51:08.779871Z"}, {"uuid": "3038ce5f-b26a-4551-b9ae-0443c8149486", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37891", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lpja7ydo2e2h", "content": "", "creation_timestamp": "2025-05-19T09:13:35.321182Z"}, {"uuid": "7ce4e917-f35d-4a62-945a-fbf8b84b561c", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37899", "type": "seen", "source": "https://bsky.app/profile/StevenSaus.faithcollapsing.com.ap.brid.gy/post/3lrjkc2r5vpu2", "content": "", "creation_timestamp": "2025-06-13T23:06:59.561556Z"}, {"uuid": "63541148-1471-40ef-9d97-024660674236", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37089", "type": "seen", "source": "https://bsky.app/profile/jfreeg.bsky.social/post/3lqqekb3xjj2v", "content": "", "creation_timestamp": "2025-06-03T22:44:45.631755Z"}, {"uuid": "49b8dca9-6bce-4d5b-b339-cbbd94ccacaa", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37093", "type": "seen", "source": "https://bsky.app/profile/jfreeg.bsky.social/post/3lqqekb3xjj2v", "content": "", "creation_timestamp": "2025-06-03T22:44:45.707322Z"}, {"uuid": "2af8808d-34d8-48c2-b7eb-b25fcc1e1c35", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37102", "type": "seen", "source": "https://infosec.exchange/users/cR0w/statuses/114819222425065137", "content": "", "creation_timestamp": "2025-07-08T19:18:16.026795Z"}, {"uuid": "5e2effc0-14b3-4811-99cf-a12e6cf4f1bc", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37899", "type": "seen", "source": "https://bsky.app/profile/bluesky.awakari.com/post/3lsxdz26odb2m", "content": "", "creation_timestamp": "2025-07-02T04:14:08.613796Z"}, {"uuid": "778c82a4-90eb-488e-9a57-b3376d13cfe5", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37103", "type": "seen", "source": "https://infosec.exchange/users/cR0w/statuses/114819241519168433", "content": "", "creation_timestamp": "2025-07-08T19:23:07.383820Z"}, {"uuid": "6afbd403-1184-449b-a3d8-ba235fe9f29d", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3768", "type": "seen", "source": "https://bsky.app/profile/2rZiKKbOU3nTafniR2qMMSE0gwZ.activitypub.awakari.com.ap.brid.gy/post/3lquhl7kkn3i2", "content": "", "creation_timestamp": "2025-06-05T13:49:39.677989Z"}, {"uuid": "e1d942e9-1546-44e3-8f1f-90218ead0055", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37899", "type": "seen", "source": "https://bsky.app/profile/youranonriots.bsky.social/post/3lq45hwfcls25", "content": "", "creation_timestamp": "2025-05-26T21:44:58.215104Z"}, {"uuid": "70aa6cc4-2c02-4b73-9dcd-6f4d1a9c0966", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37899", "type": "seen", "source": "https://bsky.app/profile/pmloik.bsky.social/post/3lqqqlu6mid2s", "content": "", "creation_timestamp": "2025-06-04T02:20:23.536451Z"}, {"uuid": "5d32b5a9-337d-4231-800b-a93394919ff3", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37899", "type": "seen", "source": "https://bsky.app/profile/lcheylus.bsky.social/post/3lqavrgqyvi22", "content": "", "creation_timestamp": "2025-05-28T19:10:24.034139Z"}, {"uuid": "357f4e0a-0752-48df-b2c5-7273dd18b9ec", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "cve-2025-37899", "type": "seen", "source": "https://bsky.app/profile/bluesky.awakari.com/post/3lqavrsaxpv22", "content": "", "creation_timestamp": "2025-05-28T19:10:36.448954Z"}, {"uuid": "017dd781-58c2-4143-8dae-09157e724413", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3751", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lpplkdr4472c", "content": "", "creation_timestamp": "2025-05-21T21:52:13.102877Z"}, {"uuid": "3bb918c7-11d5-4d56-ab90-641ea23c23e7", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37093", "type": "seen", "source": "https://threatintel.cc/2025/06/05/hewlett-packard-enterprise-warns-of.html", "content": "", "creation_timestamp": "2025-06-05T10:12:25.000000Z"}, {"uuid": "a8890c5b-bb37-4682-a264-c9764a7b4369", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37089", "type": "seen", "source": "https://infosec.exchange/users/cR0w/statuses/114614060543344731", "content": "", "creation_timestamp": "2025-06-02T13:42:53.816713Z"}, {"uuid": "813910f6-4128-4f27-8f4a-79a97fe2a6ee", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37090", "type": "seen", "source": "https://infosec.exchange/users/cR0w/statuses/114614060543344731", "content": "", "creation_timestamp": "2025-06-02T13:42:53.904943Z"}, {"uuid": "6bca9b37-23a8-4d65-8d29-8ba406905a80", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37752", "type": "seen", "source": "https://bsky.app/profile/bluedevil.bsky.social/post/3lqmxsphzi222", "content": "", "creation_timestamp": "2025-06-02T14:19:00.267874Z"}, {"uuid": "8bbbe6b7-d19d-42bc-a04c-546a7b4a6446", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37096", "type": "seen", "source": "https://bsky.app/profile/2rZiKKbOU3nTafniR2qMMSE0gwZ.activitypub.awakari.com.ap.brid.gy/post/3lqmyxginkhx2", "content": "", "creation_timestamp": "2025-06-02T14:39:23.984786Z"}, {"uuid": "a3ba3f9f-10fa-4c3d-8b09-5e17052afdb1", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37100", "type": "seen", "source": "https://infosec.exchange/users/cR0w/statuses/114659891090126886", "content": "", "creation_timestamp": "2025-06-10T15:58:12.650517Z"}, {"uuid": "dccadf73-35bb-43c1-ac66-2737279e4fec", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37095", "type": "seen", "source": "https://bsky.app/profile/2rZiKKbOU3nTafniR2qMMSE0gwZ.activitypub.awakari.com.ap.brid.gy/post/3lqmyxhtirqa2", "content": "", "creation_timestamp": "2025-06-02T14:39:35.203204Z"}, {"uuid": "025a6a1f-8cf6-4c9f-a79c-aa1bc45307ae", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37094", "type": "seen", "source": "https://bsky.app/profile/2rZiKKbOU3nTafniR2qMMSE0gwZ.activitypub.awakari.com.ap.brid.gy/post/3lqmyxiqjjiy2", "content": "", "creation_timestamp": "2025-06-02T14:39:35.809344Z"}, {"uuid": "161efa4e-b059-46b4-b400-5dcb4c713464", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37899", "type": "seen", "source": "https://bsky.app/profile/undercode.bsky.social/post/3lq4hvk6cd42q", "content": "", "creation_timestamp": "2025-05-27T00:51:30.238452Z"}, {"uuid": "a694a238-8d1d-4835-aa4c-88b31f1fc3fb", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37091", "type": "seen", "source": "https://bsky.app/profile/2rZiKKbOU3nTafniR2qMMSE0gwZ.activitypub.awakari.com.ap.brid.gy/post/3lqmyxkgr62d2", "content": "", "creation_timestamp": "2025-06-02T14:39:36.312065Z"}, {"uuid": "3809f409-aef2-4fcf-b63f-017f3564c51d", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37093", "type": "seen", "source": "https://bsky.app/profile/2rZiKKbOU3nTafniR2qMMSE0gwZ.activitypub.awakari.com.ap.brid.gy/post/3lqmyxl6wkqm2", "content": "", "creation_timestamp": "2025-06-02T14:39:56.823826Z"}, {"uuid": "e49dc0f9-b218-446c-b11c-e280a0aba0b3", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37090", "type": "seen", "source": "https://bsky.app/profile/2rZiKKbOU3nTafniR2qMMSE0gwZ.activitypub.awakari.com.ap.brid.gy/post/3lqmyxnainum2", "content": "", "creation_timestamp": "2025-06-02T14:39:58.001545Z"}, {"uuid": "a09e7fc0-f9f2-463a-bc23-02f2c9819a4c", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37089", "type": "seen", "source": "https://bsky.app/profile/2rZiKKbOU3nTafniR2qMMSE0gwZ.activitypub.awakari.com.ap.brid.gy/post/3lqmyxodruce2", "content": "", "creation_timestamp": "2025-06-02T14:39:58.532306Z"}, {"uuid": "69bfaada-b91c-4373-8342-c1214770e894", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37899", "type": "seen", "source": "https://bsky.app/profile/pmloik.bsky.social/post/3lq4mqal7ra2b", "content": "", "creation_timestamp": "2025-05-27T02:18:00.966163Z"}, {"uuid": "334fd837-3cae-4433-8701-8ea97f531575", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37093", "type": "seen", "source": "https://infosec.exchange/users/cR0w/statuses/114614292119408176", "content": "", "creation_timestamp": "2025-06-02T14:41:47.524120Z"}, {"uuid": "25a4cc54-c465-4216-b155-fcef3347b9ec", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37094", "type": "seen", "source": "https://infosec.exchange/users/cR0w/statuses/114614292119408176", "content": "", "creation_timestamp": "2025-06-02T14:41:47.634995Z"}, {"uuid": "3d76870b-c38a-4818-bc88-1dfc726cf5a5", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37096", "type": "seen", "source": "https://infosec.exchange/users/cR0w/statuses/114614292119408176", "content": "", "creation_timestamp": "2025-06-02T14:41:47.731528Z"}, {"uuid": "54edcc13-c6d7-4e99-bd63-05f6328af6bd", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37092", "type": "seen", "source": "https://bsky.app/profile/2rZiKKbOU3nTafniR2qMMSE0gwZ.activitypub.awakari.com.ap.brid.gy/post/3lqmzarzu3pa2", "content": "", "creation_timestamp": "2025-06-02T14:44:48.821100Z"}, {"uuid": "e22598e1-4c9d-4d2f-88a6-2d94f17e3afe", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37928", "type": "seen", "source": "https://bsky.app/profile/beikokucyber.bsky.social/post/3lrquv7nxa52c", "content": "", "creation_timestamp": "2025-06-16T21:02:28.002380Z"}, {"uuid": "5e09623f-094e-47d8-84d3-236bcd0f920c", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37093", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lqnbaz73f62o", "content": "", "creation_timestamp": "2025-06-02T17:07:54.330842Z"}, {"uuid": "43f7e4ec-827a-4787-8d3f-6a23d6f737b6", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37890", "type": "seen", "source": "https://infosec.exchange/users/vuldb/statuses/114517813757606851", "content": "", "creation_timestamp": "2025-05-16T13:46:04.425697Z"}, {"uuid": "9075317f-c0cb-4408-a352-2b7a7b32951a", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37899", "type": "seen", "source": "https://bsky.app/profile/pmloik.bsky.social/post/3lqbnqbwyos2p", "content": "", "creation_timestamp": "2025-05-29T02:19:14.706616Z"}, {"uuid": "8889130f-d593-40f7-acb5-3de8ada80358", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37104", "type": "seen", "source": "https://infosec.exchange/users/cR0w/statuses/114863407251794206", "content": "", "creation_timestamp": "2025-07-16T14:35:03.169334Z"}, {"uuid": "9ff6ae5c-9e4e-40e5-af56-39dd61448941", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37899", "type": "seen", "source": "https://bsky.app/profile/bluesky.awakari.com/post/3lqg72tzl4b2n", "content": "", "creation_timestamp": "2025-05-30T21:40:01.779109Z"}, {"uuid": "b58aa5b8-d49c-458b-a6f2-8f6107bd4472", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37899", "type": "seen", "source": "https://bsky.app/profile/bluesky.awakari.com/post/3lqg72xgwwl2c", "content": "", "creation_timestamp": "2025-05-30T21:40:05.353309Z"}, {"uuid": "24a3cfc9-9193-4e6b-9931-2ac2645b9eb8", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37099", "type": "seen", "source": "https://infosec.exchange/users/vuldb/statuses/114633000374671229", "content": "", "creation_timestamp": "2025-06-05T21:59:32.640251Z"}, {"uuid": "383aeaad-3759-4ab9-93f1-bdda624a56b4", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37096", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lqnd7n2ybd2r", "content": "", "creation_timestamp": "2025-06-02T17:42:55.285314Z"}, {"uuid": "35abde48-faa1-40df-af88-b9127d31a4b9", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "cve-2025-37899", "type": "seen", "source": "https://bsky.app/profile/kriware.bsky.social/post/3lqbyforfgi22", "content": "", "creation_timestamp": "2025-05-29T05:30:10.147349Z"}, {"uuid": "9a5ba644-01dc-48bd-89ae-f7c2148a2347", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37089", "type": "seen", "source": "https://mstdn.ca/users/rfwaveio/statuses/114647946130955056", "content": "", "creation_timestamp": "2025-06-08T13:20:31.584901Z"}, {"uuid": "8a2319cf-712d-4f83-9781-59ef38f5b4b5", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37095", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lqne2japul2e", "content": "", "creation_timestamp": "2025-06-02T17:57:57.314972Z"}, {"uuid": "e49fbe16-5610-43db-8e7f-f348d1470c76", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37096", "type": "seen", "source": "https://mstdn.ca/users/rfwaveio/statuses/114647946130955056", "content": "", "creation_timestamp": "2025-06-08T13:20:31.685745Z"}, {"uuid": "b3564e1e-ab7d-4539-95ec-16854265ab84", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "cve-2025-37899", "type": "seen", "source": "https://bsky.app/profile/linux.activitypub.awakari.com.ap.brid.gy/post/3lpwqtvjxcyz2", "content": "", "creation_timestamp": "2025-05-24T18:15:44.411986Z"}, {"uuid": "a229a0fb-a900-4b6b-a73a-deb737f54625", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "cve-2025-37899", "type": "seen", "source": "https://bsky.app/profile/bluesky.awakari.com/post/3lpwr7ntmun2c", "content": "", "creation_timestamp": "2025-05-24T18:22:14.703392Z"}, {"uuid": "5a8980a0-6c61-407b-abed-fe8fa8ab4138", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3755", "type": "seen", "source": "https://bsky.app/profile/2rZiKKbOU3nTafniR2qMMSE0gwZ.activitypub.awakari.com.ap.brid.gy/post/3lqc3jktzvro2", "content": "", "creation_timestamp": "2025-05-29T06:26:11.963751Z"}, {"uuid": "0604c364-5a78-407a-9272-574ea9d39379", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "cve-2025-37899", "type": "seen", "source": "https://bsky.app/profile/betterhn20.e-work.xyz/post/3lpwsjiux522b", "content": "", "creation_timestamp": "2025-05-24T18:45:39.052406Z"}, {"uuid": "603c2435-a945-43df-a7a8-437fb41c23bb", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "cve-2025-37899", "type": "seen", "source": "https://bsky.app/profile/bluesky.awakari.com/post/3lpwt3im5g22g", "content": "", "creation_timestamp": "2025-05-24T18:55:42.338216Z"}, {"uuid": "34296931-dfdc-4df4-80ba-ccc0696e097c", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "cve-2025-37899", "type": "seen", "source": "https://bsky.app/profile/betterhn50.e-work.xyz/post/3lpwuagywiw2c", "content": "", "creation_timestamp": "2025-05-24T19:16:22.862796Z"}, {"uuid": "5cb14328-6e5a-4b62-bb53-6792d0f1f8dc", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3755", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lqc5s3mrhv27", "content": "", "creation_timestamp": "2025-05-29T07:06:34.984385Z"}, {"uuid": "bc36ee41-b601-4a90-a264-cbf6911a7823", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37899", "type": "seen", "source": "https://bsky.app/profile/lobsters-feed.bsky.social/post/3lpwuh2pu4g2e", "content": "", "creation_timestamp": "2025-05-24T19:20:04.979757Z"}, {"uuid": "8e09a84f-6d0d-42b7-acb7-8c4ab778113b", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37899", "type": "seen", "source": "https://bsky.app/profile/bluesky.awakari.com/post/3lpwv6np3jt2c", "content": "", "creation_timestamp": "2025-05-24T19:33:15.813512Z"}, {"uuid": "af6c5a0f-1218-4d63-8bfa-db1747f54732", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "cve-2025-37899", "type": "seen", "source": "https://bsky.app/profile/linux.activitypub.awakari.com.ap.brid.gy/post/3lpwv6yjjamj2", "content": "", "creation_timestamp": "2025-05-24T19:34:02.034599Z"}, {"uuid": "a576b3d2-acd4-429d-9dfd-5d043e9e9dd6", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37890", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lpciznhsnp2o", "content": "", "creation_timestamp": "2025-05-16T17:02:28.723544Z"}, {"uuid": "07e78097-7a48-4a9d-ab8d-f295649dd8c4", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "cve-2025-37899", "type": "seen", "source": "https://bsky.app/profile/bluesky.awakari.com/post/3lpww5axcd32c", "content": "", "creation_timestamp": "2025-05-24T19:50:23.628234Z"}, {"uuid": "cff26c06-32cb-4b0f-b1d0-95f8a2145e56", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "cve-2025-37899", "type": "seen", "source": "https://bsky.app/profile/hnbot.gsuscs.xyz/post/3lpwwok4ul222", "content": "", "creation_timestamp": "2025-05-24T20:00:03.331189Z"}, {"uuid": "0a97e3cc-6868-496b-81b4-d31bdc956f8c", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "cve-2025-37899", "type": "seen", "source": "https://bsky.app/profile/hn100.atproto.rocks/post/3lpwwot2fsp2z", "content": "", "creation_timestamp": "2025-05-24T20:00:12.920560Z"}, {"uuid": "0c021de9-d2af-49d4-811e-c0d2c00808de", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37899", "type": "seen", "source": "https://bsky.app/profile/pmloik.bsky.social/post/3lqgojs324f2w", "content": "", "creation_timestamp": "2025-05-31T02:16:49.236642Z"}, {"uuid": "7b4af707-304f-400a-b6cb-2d750383609d", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37899", "type": "seen", "source": "https://bsky.app/profile/bluesky.awakari.com/post/3lpx2ibmhvm2g", "content": "", "creation_timestamp": "2025-05-24T21:08:07.552101Z"}, {"uuid": "e1806873-6c51-4f7e-95c0-e205124e41e6", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37899", "type": "seen", "source": "https://bsky.app/profile/LLMs.activitypub.awakari.com.ap.brid.gy/post/3lpx2ieapxp72", "content": "", "creation_timestamp": "2025-05-24T21:10:53.900667Z"}, {"uuid": "b5fe841f-4a49-48da-81ea-9a1a2169714c", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "cve-2025-37899", "type": "seen", "source": "https://bsky.app/profile/newsyc200.bsky.social/post/3lpx3duaref2w", "content": "", "creation_timestamp": "2025-05-24T21:23:33.346744Z"}, {"uuid": "49840ddf-c04d-48ce-a5d4-58ad74ab5f56", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37099", "type": "seen", "source": "http://www.zerodayinitiative.com/advisories/ZDI-25-325/", "content": "", "creation_timestamp": "2025-06-05T03:00:00.000000Z"}, {"uuid": "7d5e8e90-0995-4d0c-a624-80933fee16dc", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "cve-2025-37899", "type": "seen", "source": "https://bsky.app/profile/hnfeed.bsky.social/post/3lpx5kkodsx2b", "content": "", "creation_timestamp": "2025-05-24T22:03:05.493018Z"}, {"uuid": "09eee49a-38e4-4253-a8ee-f3175596664e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "cve-2025-37899", "type": "seen", "source": "https://bsky.app/profile/bluesky.awakari.com/post/3lpx73kdxrf2n", "content": "", "creation_timestamp": "2025-05-24T22:30:29.160840Z"}, {"uuid": "8fd03965-22df-4125-9e17-7d3afe3e8ff8", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "cve-2025-37899", "type": "seen", "source": "https://bsky.app/profile/newsyc250.bsky.social/post/3lpx7at2f3d2j", "content": "", "creation_timestamp": "2025-05-24T22:33:25.979923Z"}, {"uuid": "940a45d1-1d6b-4453-861a-0d47408fe896", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37899", "type": "seen", "source": "https://bsky.app/profile/hacker-news-jp.bsky.social/post/3lpxd6sepyj2y", "content": "", "creation_timestamp": "2025-05-24T23:43:53.371587Z"}, {"uuid": "f17d00d9-58ed-40ec-976f-f32e12c34a1f", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37778", "type": "seen", "source": "https://bsky.app/profile/hacker-news-jp.bsky.social/post/3lpxd6si6t42y", "content": "", "creation_timestamp": "2025-05-24T23:43:53.899851Z"}, {"uuid": "90741b0b-d4ab-44c8-9d98-0f2a398d8009", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "cve-2025-37899", "type": "seen", "source": "https://bsky.app/profile/bluesky.awakari.com/post/3lpxdvihnn622", "content": "", "creation_timestamp": "2025-05-24T23:56:34.535878Z"}, {"uuid": "216a20df-9dca-4acb-893e-0ddb0616dc99", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "cve-2025-37899", "type": "seen", "source": "https://bsky.app/profile/linux.activitypub.awakari.com.ap.brid.gy/post/3lpxdvlndyuo2", "content": "", "creation_timestamp": "2025-05-24T23:56:44.045937Z"}, {"uuid": "07cccad4-981a-4149-9ccd-a303690c0114", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37093", "type": "seen", "source": "https://bsky.app/profile/securityrss.bsky.social/post/3lqrkes3eoj2g", "content": "", "creation_timestamp": "2025-06-04T10:01:44.173823Z"}, {"uuid": "0e7bd3c8-8a1b-45e0-85a1-6aa079d2403e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3730", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lmxo5cc3yo2r", "content": "", "creation_timestamp": "2025-04-16T22:44:19.207961Z"}, {"uuid": "7b5c621a-eac9-4540-83a4-76790d586527", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3729", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lmxo5cfc6a2g", "content": "", "creation_timestamp": "2025-04-16T22:44:19.801059Z"}, {"uuid": "24bc4ac9-c23a-4368-81c4-73b66960b881", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3727", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lmxo5cpjcs2i", "content": "", "creation_timestamp": "2025-04-16T22:44:21.695949Z"}, {"uuid": "e1df0c29-32c8-4aaa-a9e8-455374896446", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "cve-2025-37899", "type": "seen", "source": "https://bsky.app/profile/hnbest.bsky.social/post/3lpxe427kny2q", "content": "", "creation_timestamp": "2025-05-25T00:00:14.539836Z"}, {"uuid": "8a9c25b5-d48c-4bbd-8bc2-eecad6436cde", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "cve-2025-37899", "type": "seen", "source": "https://bsky.app/profile/bluesky.awakari.com/post/3lpxeco4qtq25", "content": "", "creation_timestamp": "2025-05-25T00:03:56.657913Z"}, {"uuid": "64d31f3a-22ae-401f-8f5e-e870272c3888", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "cve-2025-37899", "type": "seen", "source": "https://bsky.app/profile/bluesky.awakari.com/post/3lpxef4mhrx2g", "content": "", "creation_timestamp": "2025-05-25T00:05:18.959543Z"}, {"uuid": "396e00e4-7da5-480b-9ccd-5b645a50bd4f", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37991", "type": "seen", "source": "https://bsky.app/profile/ferramentaslinux.bsky.social/post/3lrbonca3vk2e", "content": "", "creation_timestamp": "2025-06-10T20:00:42.760097Z"}, {"uuid": "b13226bb-7301-4c92-a985-f1b40c0b1fe6", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "cve-2025-37899", "type": "seen", "source": "https://bsky.app/profile/linux.activitypub.awakari.com.ap.brid.gy/post/3lpxee4mjboo2", "content": "", "creation_timestamp": "2025-05-25T00:06:03.671456Z"}, {"uuid": "354cd1b7-1207-48eb-827a-40441d88e84a", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3774", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lrrktj25ox2k", "content": "", "creation_timestamp": "2025-06-17T03:35:09.030531Z"}, {"uuid": "6074ea82-edd9-452e-9c56-e47101707f1c", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "cve-2025-37899", "type": "seen", "source": "https://bsky.app/profile/bluesky.awakari.com/post/3lpqyqrgb452s", "content": "", "creation_timestamp": "2025-05-22T11:21:06.615390Z"}, {"uuid": "a2f5cc96-b402-4fc3-873a-12218609798f", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "cve-2025-37899", "type": "seen", "source": "https://bsky.app/profile/linux.activitypub.awakari.com.ap.brid.gy/post/3lpxef6fwpu72", "content": "", "creation_timestamp": "2025-05-25T00:07:53.766011Z"}, {"uuid": "d545fbd4-9959-48fb-8273-df52f5c2ab4d", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "cve-2025-37899", "type": "seen", "source": "https://bsky.app/profile/linux.activitypub.awakari.com.ap.brid.gy/post/3lpqyqtjlujv2", "content": "", "creation_timestamp": "2025-05-22T11:21:41.787505Z"}, {"uuid": "f2dbd591-be46-4bab-9cb4-fcdeab1884da", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "cve-2025-37899", "type": "seen", "source": "https://bsky.app/profile/ryanhe.mistyreverie.org.ap.brid.gy/post/3lpxgtttozcy2", "content": "", "creation_timestamp": "2025-05-25T00:49:29.040214Z"}, {"uuid": "1d7f8954-4fa1-42c8-8c0a-62056dda9d81", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "cve-2025-37899", "type": "seen", "source": "https://bsky.app/profile/betterhn300.e-work.xyz/post/3lpxgvrk4ju2p", "content": "", "creation_timestamp": "2025-05-25T00:50:25.848029Z"}, {"uuid": "06ba4d0a-0523-497a-8c4a-65d90e71bd62", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3760", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lmze2iqxhi2y", "content": "", "creation_timestamp": "2025-04-17T14:49:08.658291Z"}, {"uuid": "7385bf7d-3738-46f1-9a7d-475d88329286", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3765", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3ln274ocr5f2y", "content": "", "creation_timestamp": "2025-04-17T22:53:31.246366Z"}, {"uuid": "9aebac35-3947-4bfe-9fa2-d178d2f1e973", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3764", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3ln274omk3i2h", "content": "", "creation_timestamp": "2025-04-17T22:53:31.853677Z"}, {"uuid": "294f4bfa-4a5e-4e61-b0d4-7dd267cb57a4", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3785", "type": "seen", "source": "https://infosec.exchange/users/vuldb/statuses/114356638723386779", "content": "", "creation_timestamp": "2025-04-18T02:37:08.491650Z"}, {"uuid": "29d39f7b-5410-4064-9684-2701df098b92", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37103", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3ltijdmxboy2i", "content": "", "creation_timestamp": "2025-07-09T00:04:48.128928Z"}, {"uuid": "9e9be4f2-18bd-4a1a-946e-5a35e19b074e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "cve-2025-37899", "type": "seen", "source": "https://bsky.app/profile/bluesky.awakari.com/post/3lpxignpuro2g", "content": "", "creation_timestamp": "2025-05-25T01:17:45.770240Z"}, {"uuid": "798a174d-bea9-4043-8223-a202b2ed7445", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "cve-2025-37899", "type": "seen", "source": "https://bsky.app/profile/linux.activitypub.awakari.com.ap.brid.gy/post/3lpxigpv6rn52", "content": "", "creation_timestamp": "2025-05-25T01:17:52.391406Z"}, {"uuid": "65816b5e-3eb6-4977-b57b-551381b96f7d", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3705", "type": "seen", "source": "https://bsky.app/profile/infosec.skyfleet.blue/post/3ltgeobo4r42o", "content": "", "creation_timestamp": "2025-07-08T03:35:57.662856Z"}, {"uuid": "ddb1be84-df07-4046-9a3c-551fe2a6a63f", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37093", "type": "seen", "source": "https://bsky.app/profile/2rZiKKbOU3nTafniR2qMMSE0gwZ.activitypub.awakari.com.ap.brid.gy/post/3lrbr4sant6n2", "content": "", "creation_timestamp": "2025-06-10T20:48:19.381690Z"}, {"uuid": "27d5f962-dc36-4cd7-b01b-7ce1d9e00ef4", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3786", "type": "seen", "source": "https://bsky.app/profile/2rZiKKbOU3nTafniR2qMMSE0gwZ.activitypub.awakari.com.ap.brid.gy/post/3ln3ikuqwlji2", "content": "", "creation_timestamp": "2025-04-18T11:15:19.159729Z"}, {"uuid": "4bf73754-d30e-4c83-854e-2ae09c828f21", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3787", "type": "seen", "source": "https://bsky.app/profile/2rZiKKbOU3nTafniR2qMMSE0gwZ.activitypub.awakari.com.ap.brid.gy/post/3ln3ilpusivj2", "content": "", "creation_timestamp": "2025-04-18T11:16:03.758142Z"}, {"uuid": "17f5198f-0053-4906-9f1d-2df90a02c08e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3788", "type": "seen", "source": "https://bsky.app/profile/2rZiKKbOU3nTafniR2qMMSE0gwZ.activitypub.awakari.com.ap.brid.gy/post/3ln3iuub3jhe2", "content": "", "creation_timestamp": "2025-04-18T11:26:52.674543Z"}, {"uuid": "004a8d32-b64b-452c-9345-82cb1703a841", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3786", "type": "seen", "source": "https://infosec.exchange/users/cR0w/statuses/114359036491292285", "content": "", "creation_timestamp": "2025-04-18T12:46:55.862939Z"}, {"uuid": "d7359b01-b96b-4173-8105-3e402842e2dd", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3785", "type": "seen", "source": "https://infosec.exchange/users/cR0w/statuses/114359077561921981", "content": "", "creation_timestamp": "2025-04-18T12:57:22.596257Z"}, {"uuid": "31596b80-4e51-49e3-b5b9-ea95248b093c", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3791", "type": "seen", "source": "https://bsky.app/profile/2rZiKKbOU3nTafniR2qMMSE0gwZ.activitypub.awakari.com.ap.brid.gy/post/3ln3uthrxn5l2", "content": "", "creation_timestamp": "2025-04-18T14:54:47.192518Z"}, {"uuid": "07e28782-38ce-412c-8899-6622cd49ad73", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37838", "type": "seen", "source": "https://bsky.app/profile/2rZiKKbOU3nTafniR2qMMSE0gwZ.activitypub.awakari.com.ap.brid.gy/post/3ln3uu7st6u72", "content": "", "creation_timestamp": "2025-04-18T14:55:34.273739Z"}, {"uuid": "fbe14880-259d-4f41-bdee-769030854a4e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3790", "type": "seen", "source": "https://bsky.app/profile/2rZiKKbOU3nTafniR2qMMSE0gwZ.activitypub.awakari.com.ap.brid.gy/post/3ln3uugto3vs2", "content": "", "creation_timestamp": "2025-04-18T14:55:35.951163Z"}, {"uuid": "fed85c65-45ca-449b-af98-be3a9535ec1b", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3789", "type": "seen", "source": "https://bsky.app/profile/2rZiKKbOU3nTafniR2qMMSE0gwZ.activitypub.awakari.com.ap.brid.gy/post/3ln3uuhysjw72", "content": "", "creation_timestamp": "2025-04-18T14:55:36.615810Z"}, {"uuid": "970b27b6-a03f-4915-91c4-1f09d650696b", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37838", "type": "seen", "source": "https://infosec.exchange/users/vuldb/statuses/114360157668378334", "content": "", "creation_timestamp": "2025-04-18T17:32:03.415199Z"}, {"uuid": "84c22d17-e013-4b49-aabe-ca3fbfb352c1", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3785", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3ln42fp2qm72c", "content": "", "creation_timestamp": "2025-04-18T16:34:24.782885Z"}, {"uuid": "3c1de7c7-9814-4f01-9e9e-fc0d12af23b1", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3787", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3ln42fpylzc2b", "content": "", "creation_timestamp": "2025-04-18T16:34:29.250826Z"}, {"uuid": "9b3d8eed-aa1b-44ff-883a-1b861e62c161", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3789", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3ln42fq7ion2r", "content": "", "creation_timestamp": "2025-04-18T16:34:30.423909Z"}, {"uuid": "93c2cdff-39a8-4f77-b436-f690cd9d34c8", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3788", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3ln42fqcy2c2b", "content": "", "creation_timestamp": "2025-04-18T16:34:31.028132Z"}, {"uuid": "0e7271b0-706c-49db-8d74-ff21f2265d46", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3786", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3ln42fqgdgn2r", "content": "", "creation_timestamp": "2025-04-18T16:34:31.563157Z"}, {"uuid": "ab0aa93b-1b7e-4545-b488-a0b39b5a3d9a", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3790", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3ln42fr2yy62d", "content": "", "creation_timestamp": "2025-04-18T16:34:34.966177Z"}, {"uuid": "83595d55-bfcb-4af8-b7e6-1946e8c60b8b", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3785", "type": "seen", "source": "https://mastodon.social/users/CyberSignaler/statuses/114360221183804192", "content": "", "creation_timestamp": "2025-04-18T17:48:12.779566Z"}, {"uuid": "72cb06e8-c8d1-4919-bc70-14b9e6eccd16", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3786", "type": "seen", "source": "https://mastodon.social/users/CyberSignaler/statuses/114360221222836607", "content": "", "creation_timestamp": "2025-04-18T17:48:13.612556Z"}, {"uuid": "a60c66e8-7452-4a87-ac52-7bb9f1aeaa75", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3795", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3ln4hrgamvk2b", "content": "", "creation_timestamp": "2025-04-18T20:33:41.673721Z"}, {"uuid": "fcf4eae3-bed2-4cad-8458-9774195d004c", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3796", "type": "seen", "source": "https://bsky.app/profile/2rZiKKbOU3nTafniR2qMMSE0gwZ.activitypub.awakari.com.ap.brid.gy/post/3ln4ry6mh4nc2", "content": "", "creation_timestamp": "2025-04-18T23:36:25.190267Z"}, {"uuid": "a30c1e4f-d724-4458-a4f1-8ff7311556a0", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3795", "type": "seen", "source": "https://bsky.app/profile/2rZiKKbOU3nTafniR2qMMSE0gwZ.activitypub.awakari.com.ap.brid.gy/post/3ln4ry7z6ksm2", "content": "", "creation_timestamp": "2025-04-18T23:36:25.781544Z"}, {"uuid": "4ea46255-167b-4f45-b224-771661b33f55", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3796", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3ln4vhsxem22b", "content": "", "creation_timestamp": "2025-04-19T00:38:47.279339Z"}, {"uuid": "9410fdd7-b804-47d9-bd34-4817b08b8cfd", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3797", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3ln5qctewf42u", "content": "", "creation_timestamp": "2025-04-19T08:39:11.438888Z"}, {"uuid": "74a8f79c-b4ed-4d25-ae88-3ec0080dfd77", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3797", "type": "seen", "source": "https://bsky.app/profile/2rZiKKbOU3nTafniR2qMMSE0gwZ.activitypub.awakari.com.ap.brid.gy/post/3ln5rld33x3r2", "content": "", "creation_timestamp": "2025-04-19T09:02:33.843559Z"}, {"uuid": "c03447ec-9a54-43fd-bb46-19e01566a047", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "cve-2025-37899", "type": "seen", "source": "https://bsky.app/profile/bluesky.awakari.com/post/3lpxlaqxmby2n", "content": "", "creation_timestamp": "2025-05-25T02:08:08.814040Z"}, {"uuid": "36e12577-0284-48f9-8416-1a10e0ebcdc9", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37899", "type": "seen", "source": "https://bsky.app/profile/bluesky.awakari.com/post/3lpr63lyiq22p", "content": "", "creation_timestamp": "2025-05-22T12:56:38.606775Z"}, {"uuid": "7eea033b-99fc-4c97-9e57-1117e1b07a3a", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "cve-2025-37899", "type": "seen", "source": "https://bsky.app/profile/linux.activitypub.awakari.com.ap.brid.gy/post/3lpxlatozl452", "content": "", "creation_timestamp": "2025-05-25T02:09:38.448832Z"}, {"uuid": "4ec2afc5-9912-4b65-8768-672e268ba443", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3798", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3ln65qeca422v", "content": "", "creation_timestamp": "2025-04-19T12:39:24.035306Z"}, {"uuid": "4f10de04-15f4-4c25-818c-908fe8e1f379", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3799", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3ln65qefr2d2g", "content": "", "creation_timestamp": "2025-04-19T12:39:24.607359Z"}, {"uuid": "18d824a0-f0f8-4504-8b33-1ac9f30cf556", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37899", "type": "seen", "source": "https://bsky.app/profile/bluesky.awakari.com/post/3lpr63pz3wv2g", "content": "", "creation_timestamp": "2025-05-22T12:56:42.769951Z"}, {"uuid": "7aca76a3-3d17-41dc-a9e6-28483ebceda7", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37899", "type": "seen", "source": "https://bsky.app/profile/bluesky.awakari.com/post/3lprargsl3t2e", "content": "", "creation_timestamp": "2025-05-22T13:44:38.937100Z"}, {"uuid": "a5ffae55-a1c9-43a2-876a-8f751b854f3e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37899", "type": "seen", "source": "https://bsky.app/profile/bluesky.awakari.com/post/3lprarjpphk2l", "content": "", "creation_timestamp": "2025-05-22T13:44:41.843179Z"}, {"uuid": "3ab1e88b-c29e-45b3-8682-24bdc5073a8f", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37095", "type": "seen", "source": "http://www.zerodayinitiative.com/advisories/ZDI-25-318/", "content": "", "creation_timestamp": "2025-06-02T03:00:00.000000Z"}, {"uuid": "a0552672-d2ba-461d-948a-12283ba579d8", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37091", "type": "seen", "source": "http://www.zerodayinitiative.com/advisories/ZDI-25-314/", "content": "", "creation_timestamp": "2025-06-02T03:00:00.000000Z"}, {"uuid": "13775ae1-1464-4576-84a7-453a3c415164", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37090", "type": "seen", "source": "http://www.zerodayinitiative.com/advisories/ZDI-25-313/", "content": "", "creation_timestamp": "2025-06-02T03:00:00.000000Z"}, {"uuid": "2bf5c4c3-e5ad-4791-b777-07be7bfd143d", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37096", "type": "seen", "source": "http://www.zerodayinitiative.com/advisories/ZDI-25-319/", "content": "", "creation_timestamp": "2025-06-02T03:00:00.000000Z"}, {"uuid": "f71b0156-da3d-4c8c-a8b9-c54dad5d56f3", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37089", "type": "seen", "source": "http://www.zerodayinitiative.com/advisories/ZDI-25-312/", "content": "", "creation_timestamp": "2025-06-02T03:00:00.000000Z"}, {"uuid": "0a0515ca-9f63-40a4-9f2b-2691bf6774a8", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37094", "type": "seen", "source": "http://www.zerodayinitiative.com/advisories/ZDI-25-317/", "content": "", "creation_timestamp": "2025-06-02T03:00:00.000000Z"}, {"uuid": "fca5d411-3859-418d-8bef-7d83727e280a", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "cve-2025-37899", "type": "seen", "source": "https://bsky.app/profile/hackernewstop5.bsky.social/post/3lpxttt7bpp2g", "content": "", "creation_timestamp": "2025-05-25T04:41:58.761931Z"}, {"uuid": "365fe58b-36cd-4916-b5a7-d71b847ed9db", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37093", "type": "seen", "source": "http://www.zerodayinitiative.com/advisories/ZDI-25-316/", "content": "", "creation_timestamp": "2025-06-02T03:00:00.000000Z"}, {"uuid": "ad2a66e6-a1e1-41db-8bd3-f4d71b9b9a54", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37899", "type": "seen", "source": "https://bsky.app/profile/bluesky.awakari.com/post/3lprdjkqahm2g", "content": "", "creation_timestamp": "2025-05-22T14:33:55.857915Z"}, {"uuid": "091c7e14-0bf1-482b-9885-f763b8f9b5fe", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37092", "type": "seen", "source": "http://www.zerodayinitiative.com/advisories/ZDI-25-315/", "content": "", "creation_timestamp": "2025-06-02T03:00:00.000000Z"}, {"uuid": "4d906eeb-8869-43a2-baba-d07fb96bc7f1", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37899", "type": "seen", "source": "https://bsky.app/profile/bluesky.awakari.com/post/3lprdjm2a7h2r", "content": "", "creation_timestamp": "2025-05-22T14:33:57.459930Z"}, {"uuid": "a780f5ea-a2ce-4ed1-a38c-4a4dc5aca8ea", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37899", "type": "seen", "source": "https://bsky.app/profile/pmloik.bsky.social/post/3lqoa53q2yt2a", "content": "", "creation_timestamp": "2025-06-03T02:20:28.773369Z"}, {"uuid": "b7094176-c31b-4b15-842d-74ebbe22894d", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37899", "type": "seen", "source": "https://bsky.app/profile/technofeed.bsky.social/post/3lpxyosuexw2d", "content": "", "creation_timestamp": "2025-05-25T06:08:39.209215Z"}, {"uuid": "884b03fe-a5c0-4b0d-9ba2-7c63722c3f0f", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3786", "type": "seen", "source": "https://bsky.app/profile/redteamnews.bsky.social/post/3lncwex3g2h2d", "content": "", "creation_timestamp": "2025-04-21T10:11:03.682454Z"}, {"uuid": "4db6ef62-6017-40ec-bd26-5b2a336590b6", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37093", "type": "seen", "source": "https://bsky.app/profile/2rZiKKbOU3nTafniR2qMMSE0gwZ.activitypub.awakari.com.ap.brid.gy/post/3lqwcu7prube2", "content": "", "creation_timestamp": "2025-06-06T07:30:54.486028Z"}, {"uuid": "10fdacdb-c1bf-4a83-8aff-ef22fe29592f", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37093", "type": "seen", "source": "https://bsky.app/profile/2rZiKKbOU3nTafniR2qMMSE0gwZ.activitypub.awakari.com.ap.brid.gy/post/3lr5ufiquc5b2", "content": "", "creation_timestamp": "2025-06-09T07:36:50.601391Z"}, {"uuid": "a20cb2d2-d558-4b83-8dca-0c39a1776edd", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37899", "type": "seen", "source": "https://bsky.app/profile/bluesky.awakari.com/post/3lpxzx46hrm2c", "content": "", "creation_timestamp": "2025-05-25T06:31:11.139675Z"}, {"uuid": "2fe27786-f33f-4abf-94aa-e1ba812a85fd", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "cve-2025-37899", "type": "seen", "source": "https://bsky.app/profile/linux.activitypub.awakari.com.ap.brid.gy/post/3lpxzxj5ll7o2", "content": "", "creation_timestamp": "2025-05-25T06:34:40.211762Z"}, {"uuid": "37b8c919-3f3a-4cbd-b1b6-ff6b736f0deb", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37899", "type": "seen", "source": "https://bsky.app/profile/cyberveille.bsky.social/post/3lqcldzimfv2p", "content": "", "creation_timestamp": "2025-05-29T11:09:16.471118Z"}, {"uuid": "664758d9-2067-45bf-8048-c9ac8639fd8a", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "cve-2025-37899", "type": "seen", "source": "https://bsky.app/profile/bluesky.awakari.com/post/3lpy2drxm3y22", "content": "", "creation_timestamp": "2025-05-25T06:38:16.546875Z"}, {"uuid": "7d76f520-605f-4c91-975b-479b6659ddc9", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "cve-2025-37899", "type": "seen", "source": "https://bsky.app/profile/bluesky.awakari.com/post/3lpy2dryckx26", "content": "", "creation_timestamp": "2025-05-25T06:38:17.086710Z"}, {"uuid": "c35e4595-b894-41e1-a6f3-5d0ca18beea9", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "cve-2025-37899", "type": "seen", "source": "https://bsky.app/profile/mm-hacker-news.bsky.social/post/3lpy5g2pqz427", "content": "", "creation_timestamp": "2025-05-25T07:33:14.197572Z"}, {"uuid": "0606aeac-262c-4378-ad61-6f11e8888105", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37093", "type": "seen", "source": "https://bsky.app/profile/2rZiKKbOU3nTafniR2qMMSE0gwZ.activitypub.awakari.com.ap.brid.gy/post/3lqwiv4fnxgf2", "content": "", "creation_timestamp": "2025-06-06T09:21:58.431126Z"}, {"uuid": "79aeafa6-14b9-44ff-90b9-041e4309129e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "cve-2025-37899", "type": "seen", "source": "https://bsky.app/profile/topickapp.bsky.social/post/3lpyfgyxymv2c", "content": "", "creation_timestamp": "2025-05-25T09:56:56.756810Z"}, {"uuid": "7a43409f-3a9f-4452-b94c-6e57a0c0b564", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37999", "type": "seen", "source": "https://bsky.app/profile/2rZiKKbOU3nTafniR2qMMSE0gwZ.activitypub.awakari.com.ap.brid.gy/post/3lqcuf2yz4fn2", "content": "", "creation_timestamp": "2025-05-29T13:51:01.111779Z"}, {"uuid": "56a4d26a-7c15-465f-ac85-8913f38f4814", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37103", "type": "seen", "source": "https://bsky.app/profile/getpokemon7.bsky.social/post/3ltzs5qvfpc2c", "content": "", "creation_timestamp": "2025-07-15T20:57:50.576332Z"}, {"uuid": "9a28a3a9-6695-449c-b9a5-25bc1f1a4191", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37899", "type": "seen", "source": "https://bsky.app/profile/bluesky.awakari.com/post/3lpriiadyu326", "content": "", "creation_timestamp": "2025-05-22T16:02:40.023072Z"}, {"uuid": "b71596f7-5939-453a-a0ec-67001b2c1504", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37996", "type": "seen", "source": "https://bsky.app/profile/linux.activitypub.awakari.com.ap.brid.gy/post/3lqcuf4h445n2", "content": "", "creation_timestamp": "2025-05-29T13:51:01.709521Z"}, {"uuid": "9f58c7e7-3627-4c40-959a-a89863180662", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37899", "type": "seen", "source": "https://bsky.app/profile/bluesky.awakari.com/post/3lpriidxs4625", "content": "", "creation_timestamp": "2025-05-22T16:02:43.774451Z"}, {"uuid": "52bb3571-ba34-4a4e-993a-dfa77e9d7885", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37994", "type": "seen", "source": "https://bsky.app/profile/linux.activitypub.awakari.com.ap.brid.gy/post/3lqcuf73iwm22", "content": "", "creation_timestamp": "2025-05-29T13:51:02.518937Z"}, {"uuid": "bf3a7ce6-d020-4f17-9e2d-c22f753b4c85", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3704", "type": "seen", "source": "https://bsky.app/profile/2rZiKKbOU3nTafniR2qMMSE0gwZ.activitypub.awakari.com.ap.brid.gy/post/3lq624djpv2a2", "content": "", "creation_timestamp": "2025-05-27T15:50:52.496878Z"}, {"uuid": "dc225989-c129-4146-aa3b-2293d95d2f98", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37998", "type": "seen", "source": "https://bsky.app/profile/2rZiKKbOU3nTafniR2qMMSE0gwZ.activitypub.awakari.com.ap.brid.gy/post/3lqcufagmdgn2", "content": "", "creation_timestamp": "2025-05-29T13:51:03.121458Z"}, {"uuid": "38ea7f87-99e0-412c-a077-38280e46a2cf", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37995", "type": "seen", "source": "https://bsky.app/profile/2rZiKKbOU3nTafniR2qMMSE0gwZ.activitypub.awakari.com.ap.brid.gy/post/3lqcufdfi52n2", "content": "", "creation_timestamp": "2025-05-29T13:51:12.329293Z"}, {"uuid": "b091921a-a881-4d29-8964-83e40f9fedfd", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37997", "type": "seen", "source": "https://bsky.app/profile/2rZiKKbOU3nTafniR2qMMSE0gwZ.activitypub.awakari.com.ap.brid.gy/post/3lqcufrxc6u32", "content": "", "creation_timestamp": "2025-05-29T13:51:54.582385Z"}, {"uuid": "38a23462-a8d5-4e64-98f0-59780fc4e847", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37093", "type": "seen", "source": "https://bsky.app/profile/2rZiKKbOU3nTafniR2qMMSE0gwZ.activitypub.awakari.com.ap.brid.gy/post/3lqrt7srkm4k2", "content": "", "creation_timestamp": "2025-06-04T12:40:09.919168Z"}, {"uuid": "f8bb7b17-f8c8-418c-96c9-3bb5ec5c641b", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3767", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lngewdoelk2v", "content": "", "creation_timestamp": "2025-04-22T19:09:20.284380Z"}, {"uuid": "10266145-41bb-48e3-8d37-7f4f3f7927e1", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37087", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lngzdixnwv2j", "content": "", "creation_timestamp": "2025-04-23T01:14:34.714484Z"}, {"uuid": "da1b7496-14eb-49e8-9c55-681531ee4574", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37088", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lngzdjkigy2d", "content": "", "creation_timestamp": "2025-04-23T01:14:36.891340Z"}, {"uuid": "dccc9cf3-2bdd-49dd-98e7-071167bc63ed", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37993", "type": "seen", "source": "https://bsky.app/profile/2rZiKKbOU3nTafniR2qMMSE0gwZ.activitypub.awakari.com.ap.brid.gy/post/3lqcuoocksnn2", "content": "", "creation_timestamp": "2025-05-29T13:56:24.300935Z"}, {"uuid": "cf73ccff-0bed-46b6-a981-137384b0657c", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37899", "type": "seen", "source": "https://bsky.app/profile/moaijobs.bsky.social/post/3lq62o5r47p2l", "content": "", "creation_timestamp": "2025-05-27T16:00:03.683036Z"}, {"uuid": "5826906c-6973-4739-bee3-169427809d4c", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3755", "type": "seen", "source": "https://infosec.exchange/users/cR0w/statuses/114591476438104441", "content": "", "creation_timestamp": "2025-05-29T13:59:27.932888Z"}, {"uuid": "b58b2798-fcee-42dd-8acb-fa1e7fc5597e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37928", "type": "seen", "source": "https://bsky.app/profile/nimblenerd.social/post/3lrmx5ps3nt2l", "content": "", "creation_timestamp": "2025-06-15T07:32:18.796236Z"}, {"uuid": "bde2c5e3-4192-4550-857a-021f4379e101", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "cve-2025-37899", "type": "seen", "source": "https://infosec.exchange/users/Tinolle/statuses/114553072091140722", "content": "", "creation_timestamp": "2025-05-22T19:12:43.868611Z"}, {"uuid": "fefc20d7-8d30-4b60-94e9-c1de21e5dbc1", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37087", "type": "seen", "source": "https://mastodon.social/users/CyberSignaler/statuses/114388062197378576", "content": "", "creation_timestamp": "2025-04-23T15:48:39.240327Z"}, {"uuid": "2ee4b3e4-a945-47cb-93dd-ec33d78221e0", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3761", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lnkenug2qx2r", "content": "", "creation_timestamp": "2025-04-24T09:15:13.491579Z"}, {"uuid": "9c39e4c4-566c-45d6-927f-352c0dcfdd9a", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3761", "type": "seen", "source": "https://mastodon.social/users/CyberSignaler/statuses/114392307953537683", "content": "", "creation_timestamp": "2025-04-24T09:48:18.191304Z"}, {"uuid": "1dbf9f12-3ead-4558-a92f-9cc757113f5b", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3776", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lnkhza2efd2g", "content": "", "creation_timestamp": "2025-04-24T10:15:17.231780Z"}, {"uuid": "2acb7a40-79d7-4ef8-85bd-c3227e51b6bc", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37899", "type": "seen", "source": "https://bsky.app/profile/chrisshort.net/post/3lq6dqufued26", "content": "", "creation_timestamp": "2025-05-27T18:42:38.274149Z"}, {"uuid": "9fa7756a-fde7-4f71-8c39-8b3b472ad6f0", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "cve-2025-37899", "type": "seen", "source": "https://hachyderm.io/users/ChrisShort/statuses/114581265361516053", "content": "", "creation_timestamp": "2025-05-27T18:42:39.455324Z"}, {"uuid": "8d23cffb-5724-4856-addc-5b611dfc00a9", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "cve-2025-37899", "type": "seen", "source": "https://bsky.app/profile/bluesky.awakari.com/post/3lq6dqze6he2i", "content": "", "creation_timestamp": "2025-05-27T18:42:42.713523Z"}, {"uuid": "0801295c-511f-4e18-9281-ad3feff304f2", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3776", "type": "seen", "source": "https://mastodon.social/users/CyberSignaler/statuses/114392780001153736", "content": "", "creation_timestamp": "2025-04-24T11:48:23.159241Z"}, {"uuid": "ecddb1e2-7f52-4f79-b296-613e6535b4db", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3793", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lnkscidzb32h", "content": "", "creation_timestamp": "2025-04-24T13:19:23.606705Z"}, {"uuid": "33b969f0-9696-48ef-9ed7-7cff3d8ab2bf", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3752", "type": "seen", "source": "https://bsky.app/profile/2rZiKKbOU3nTafniR2qMMSE0gwZ.activitypub.awakari.com.ap.brid.gy/post/3lnmiyyayffr2", "content": "", "creation_timestamp": "2025-04-25T05:42:36.093966Z"}, {"uuid": "48217d2e-e6fb-4aa7-b73d-4c7965b3e153", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3775", "type": "seen", "source": "https://bsky.app/profile/2rZiKKbOU3nTafniR2qMMSE0gwZ.activitypub.awakari.com.ap.brid.gy/post/3lnmiyzlvwvb2", "content": "", "creation_timestamp": "2025-04-25T05:42:36.652704Z"}, {"uuid": "ff6a1081-1e90-479d-8332-d08df99cca5a", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3743", "type": "seen", "source": "https://bsky.app/profile/2rZiKKbOU3nTafniR2qMMSE0gwZ.activitypub.awakari.com.ap.brid.gy/post/3lnmnxqyqlmr2", "content": "", "creation_timestamp": "2025-04-25T07:07:21.783482Z"}, {"uuid": "7a5eab5b-5cc7-4af3-a242-eea67296dadb", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37899", "type": "seen", "source": "https://bsky.app/profile/dausnart.com/post/3lq6fu3boy22e", "content": "", "creation_timestamp": "2025-05-27T19:20:19.350881Z"}, {"uuid": "bc23d5e7-d9a9-401b-ab69-d0991551243a", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37899", "type": "seen", "source": "https://bsky.app/profile/dausnart.com/post/3lq6fua4lz22e", "content": "", "creation_timestamp": "2025-05-27T19:20:19.811672Z"}, {"uuid": "9afb995e-18ed-465b-906f-3447360e5f19", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37899", "type": "seen", "source": "https://bsky.app/profile/dausnart.com/post/3lq6fua4myc2e", "content": "", "creation_timestamp": "2025-05-27T19:20:20.291749Z"}, {"uuid": "75429eca-55aa-421a-b24e-dcb578b0cdaf", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37899", "type": "seen", "source": "https://bsky.app/profile/dausnart.com/post/3lq6fua4nxk2e", "content": "", "creation_timestamp": "2025-05-27T19:20:20.802995Z"}, {"uuid": "3e180112-f01a-4f1b-8782-2d92bb067511", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37899", "type": "seen", "source": "https://bsky.app/profile/dausnart.com/post/3lq6fua4ows2e", "content": "", "creation_timestamp": "2025-05-27T19:20:21.290427Z"}, {"uuid": "b1dcbb9d-d7ba-46fb-b915-039f29171fca", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3743", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lnnmts3hbo2j", "content": "", "creation_timestamp": "2025-04-25T16:19:40.798809Z"}, {"uuid": "6aa5104a-9158-4c94-83b8-56a05d4bc4fb", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37899", "type": "seen", "source": "https://bsky.app/profile/dausnart.com/post/3lq6fua4pw22e", "content": "", "creation_timestamp": "2025-05-27T19:20:21.783833Z"}, {"uuid": "f898a590-f1d1-47f2-864a-5472afe925e5", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37899", "type": "seen", "source": "https://bsky.app/profile/dausnart.com/post/3lq6fua4qvc2e", "content": "", "creation_timestamp": "2025-05-27T19:20:22.290951Z"}, {"uuid": "f3e6df4c-c7e4-412e-b81f-272a5392bc1e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37899", "type": "seen", "source": "https://bsky.app/profile/dausnart.com/post/3lq6fua4qvd2e", "content": "", "creation_timestamp": "2025-05-27T19:20:22.798840Z"}, {"uuid": "10df0284-6fad-4858-8fe1-e9627625c99a", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37752", "type": "seen", "source": "https://bsky.app/profile/0xor0ne.bsky.social/post/3lprysliva22j", "content": "", "creation_timestamp": "2025-05-22T20:54:50.567541Z"}, {"uuid": "662b568c-65d4-4566-900c-505427d83694", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37899", "type": "seen", "source": "https://bsky.app/profile/dausnart.com/post/3lq6fua4rul2e", "content": "", "creation_timestamp": "2025-05-27T19:20:23.312531Z"}, {"uuid": "235d4b92-5a1d-491b-80a8-ada47316c3cc", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37899", "type": "seen", "source": "https://bsky.app/profile/dausnart.com/post/3lq6fua4rum2e", "content": "", "creation_timestamp": "2025-05-27T19:20:23.794365Z"}, {"uuid": "4c16e5af-62a6-4fd4-8c36-d209b657cdda", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37899", "type": "seen", "source": "https://bsky.app/profile/dausnart.com/post/3lq6fua4run2e", "content": "", "creation_timestamp": "2025-05-27T19:20:24.252328Z"}, {"uuid": "2cdb8698-2b5c-47bf-ae19-bb64d4a0a8e3", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37899", "type": "seen", "source": "https://bsky.app/profile/dausnart.com/post/3lq6fua4stv2e", "content": "", "creation_timestamp": "2025-05-27T19:20:24.728369Z"}, {"uuid": "b3a36fb5-07c4-44c5-98ff-b6cdc83f32c4", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37899", "type": "seen", "source": "https://bsky.app/profile/bluesky.awakari.com/post/3lq6hoae4bx2c", "content": "", "creation_timestamp": "2025-05-27T19:52:44.252481Z"}, {"uuid": "9c5e8287-8603-48f7-abe1-bf8ba403b037", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37899", "type": "seen", "source": "https://bsky.app/profile/linux.activitypub.awakari.com.ap.brid.gy/post/3lq6hrgkam4u2", "content": "", "creation_timestamp": "2025-05-27T19:57:19.593428Z"}, {"uuid": "3384a6bf-fed9-4cd2-bd2d-0ee4df1865df", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37093", "type": "seen", "source": "https://bsky.app/profile/2rZiKKbOU3nTafniR2qMMSE0gwZ.activitypub.awakari.com.ap.brid.gy/post/3lqwnt5lrlfy2", "content": "", "creation_timestamp": "2025-06-06T10:47:37.333217Z"}, {"uuid": "ccfa7702-f438-4beb-a72a-22e94d5a1710", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3706", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lntu45ozdh2y", "content": "", "creation_timestamp": "2025-04-28T03:45:38.168247Z"}, {"uuid": "a1bf7249-7470-4991-9e91-6ad421dcc4d6", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37752", "type": "seen", "source": "https://bsky.app/profile/0xor0ne.bsky.social/post/3lpeqlhy3bc2i", "content": "", "creation_timestamp": "2025-05-17T14:23:14.488073Z"}, {"uuid": "907c17cc-3ef4-40f3-b815-7323abc944f6", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37093", "type": "seen", "source": "https://bsky.app/profile/infosec.skyfleet.blue/post/3lqsc74ah7y2e", "content": "", "creation_timestamp": "2025-06-04T17:08:06.385798Z"}, {"uuid": "4903f7f2-3b2c-4007-8a8d-181bda00339c", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37899", "type": "seen", "source": "https://bsky.app/profile/bluesky.awakari.com/post/3lq6ma7ysly25", "content": "", "creation_timestamp": "2025-05-27T21:14:22.788378Z"}, {"uuid": "84056249-d018-4229-9b4c-2466ef692644", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37899", "type": "seen", "source": "https://bsky.app/profile/bluesky.awakari.com/post/3lq6mafytd32c", "content": "", "creation_timestamp": "2025-05-27T21:14:28.931399Z"}, {"uuid": "89443d0e-4a18-4e58-a6b6-0b16d88eebcd", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37899", "type": "seen", "source": "https://bsky.app/profile/2rZiKKbOU3nTafniR2qMMSE0gwZ.activitypub.awakari.com.ap.brid.gy/post/3lq6maf6tsso2", "content": "", "creation_timestamp": "2025-05-27T21:16:31.130378Z"}, {"uuid": "8a337307-7a76-4506-ab4f-38736c6ad11d", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37899", "type": "seen", "source": "https://bsky.app/profile/bluesky.awakari.com/post/3lqp2fi5l362i", "content": "", "creation_timestamp": "2025-06-03T10:10:27.384942Z"}, {"uuid": "72f5e90a-d077-4986-8eee-4da2ce8f37ed", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37899", "type": "seen", "source": "https://bsky.app/profile/linkersec.bsky.social/post/3lqx26mgxj22g", "content": "", "creation_timestamp": "2025-06-06T14:27:57.115464Z"}, {"uuid": "daa0e64d-16ca-4bdc-9f4f-eba660cea240", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37899", "type": "seen", "source": "https://bsky.app/profile/linkersec.bsky.social/post/3lqx26nr26s2g", "content": "", "creation_timestamp": "2025-06-06T14:27:57.619882Z"}, {"uuid": "df217296-c17e-48dd-ad5d-87fdb741b749", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "cve-2025-37899", "type": "seen", "source": "https://bsky.app/profile/tech-trending.bsky.social/post/3lpyhqv3zax2m", "content": "", "creation_timestamp": "2025-05-25T10:38:16.249477Z"}, {"uuid": "e2214800-ce41-4601-8098-05b3565d34ef", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37093", "type": "seen", "source": "https://bsky.app/profile/thedailytechfeed.com/post/3lqx3hriols2j", "content": "", "creation_timestamp": "2025-06-06T14:50:59.108494Z"}, {"uuid": "15f1c16d-e21c-46f7-86f2-558a4d712c8a", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "cve-2025-37899", "type": "seen", "source": "https://bsky.app/profile/bluesky.awakari.com/post/3lpykxaeuoz2c", "content": "", "creation_timestamp": "2025-05-25T11:35:29.185067Z"}, {"uuid": "0ed86591-8456-48ca-901f-f2187718347e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37101", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lsiltljqjv2a", "content": "", "creation_timestamp": "2025-06-26T07:24:19.226666Z"}, {"uuid": "68c77437-9c61-43f4-a6de-70d113131325", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "cve-2025-37899", "type": "seen", "source": "https://bsky.app/profile/newsyc500.bsky.social/post/3lpylfpsd5r2d", "content": "", "creation_timestamp": "2025-05-25T11:43:35.836800Z"}, {"uuid": "80a12806-6b66-40c0-8735-8b033ba41d82", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37752", "type": "seen", "source": "https://bsky.app/profile/pmloik.bsky.social/post/3lpskurx42h2r", "content": "", "creation_timestamp": "2025-05-23T02:18:08.541262Z"}, {"uuid": "a7622f72-bf9a-4058-8573-c9854a8c6063", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37899", "type": "seen", "source": "https://bsky.app/profile/pmloik.bsky.social/post/3lqj7m3wi7j2s", "content": "", "creation_timestamp": "2025-06-01T02:27:39.671338Z"}, {"uuid": "3fd0a89a-39e5-4552-b4a0-fefe2727a7ff", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "cve-2025-37899", "type": "seen", "source": "https://bsky.app/profile/kdmsnr.com/post/3lpynl2ikwz2k", "content": "", "creation_timestamp": "2025-05-25T12:22:21.447644Z"}, {"uuid": "da44af19-36fa-4513-9c83-528badf67dc5", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37899", "type": "seen", "source": "https://bsky.app/profile/mengli512.bsky.social/post/3lpynrbrkb22w", "content": "", "creation_timestamp": "2025-05-25T12:25:55.454507Z"}, {"uuid": "6aa9a421-a972-48f9-bc95-6ec562d0dd01", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "cve-2025-37899", "type": "seen", "source": "https://bsky.app/profile/nopfx.bsky.social/post/3lqdlkyjcxc2w", "content": "", "creation_timestamp": "2025-05-29T20:45:51.200230Z"}, {"uuid": "df5e4425-2ab3-4de0-8d5e-b863583c3565", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37899", "type": "seen", "source": "https://poliverso.org/objects/0477a01e-dcdbfda8-5e742c5ac857b143", "content": "", "creation_timestamp": "2025-05-23T06:55:03.422936Z"}, {"uuid": "eef0dbfc-5dd5-4e88-ac39-1fdb2e21902a", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37093", "type": "seen", "source": "https://bsky.app/profile/potato.software/post/3lqx4em53ju25", "content": "", "creation_timestamp": "2025-06-06T15:07:06.835511Z"}, {"uuid": "910cfad5-6379-47c0-9481-83d1e06bb05c", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37899", "type": "seen", "source": "https://bsky.app/profile/bluesky.awakari.com/post/3lpt2m25xb72n", "content": "", "creation_timestamp": "2025-05-23T06:59:35.138034Z"}, {"uuid": "6a1a2581-958a-4d34-bf21-89adb23dc847", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37899", "type": "seen", "source": "https://bsky.app/profile/2rZiKKbOU3nTafniR2qMMSE0gwZ.activitypub.awakari.com.ap.brid.gy/post/3lpt2m6tembs2", "content": "", "creation_timestamp": "2025-05-23T06:59:46.385321Z"}, {"uuid": "b0d26818-14c7-4470-aed2-53833671c200", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37899", "type": "seen", "source": "https://bsky.app/profile/skynetandchill.com/post/3lpz2pviwj223", "content": "", "creation_timestamp": "2025-05-25T16:17:45.792705Z"}, {"uuid": "015cbc50-5d18-4d63-aaf0-16b0722a07a3", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37899", "type": "seen", "source": "https://bsky.app/profile/bluesky.awakari.com/post/3lpt6p63chd22", "content": "", "creation_timestamp": "2025-05-23T08:12:54.874838Z"}, {"uuid": "ceb8a54f-4542-45d5-be05-9dd97bce234c", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "cve-2025-37899", "type": "seen", "source": "https://bsky.app/profile/jos1264.social.skynetcloud.site.ap.brid.gy/post/3lpt6rbwn5xp2", "content": "", "creation_timestamp": "2025-05-23T08:15:29.543508Z"}, {"uuid": "e24f3680-641b-4c7b-adca-3ecd11cda52a", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37899", "type": "seen", "source": "https://bsky.app/profile/Grub-09.mastodon.uno.ap.brid.gy/post/3lqp774ee4uj2", "content": "", "creation_timestamp": "2025-06-03T11:36:51.668792Z"}, {"uuid": "7353b8da-6fc3-4342-8354-6320f57da009", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37899", "type": "seen", "source": "https://bsky.app/profile/2rZiKKbOU3nTafniR2qMMSE0gwZ.activitypub.awakari.com.ap.brid.gy/post/3lpt6wsbsadp2", "content": "", "creation_timestamp": "2025-05-23T08:18:33.948377Z"}, {"uuid": "86f81f48-a3b8-4d19-b6c8-b4e1a2da2b3e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37899", "type": "seen", "source": "https://bsky.app/profile/pmloik.bsky.social/post/3lq75bi67uf2w", "content": "", "creation_timestamp": "2025-05-28T02:19:18.663082Z"}, {"uuid": "c88cbe62-f076-445d-8f38-29476721ff7a", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37899", "type": "seen", "source": "https://bsky.app/profile/dejayk.bsky.social/post/3lpzphdga422s", "content": "", "creation_timestamp": "2025-05-25T22:28:46.021743Z"}, {"uuid": "481dc070-87cc-4c01-adc2-db1513be52dd", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37899", "type": "seen", "source": "https://bsky.app/profile/xchatter.techmeme.com/post/3lpzqqvojtp2b", "content": "", "creation_timestamp": "2025-05-25T22:51:58.959734Z"}, {"uuid": "01e9a3f5-1d65-445d-bfa8-1a66830b8532", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37743", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lo4hlqbzch2h", "content": "", "creation_timestamp": "2025-05-01T13:55:37.641903Z"}, {"uuid": "6ec3bc62-d28a-4fe8-babe-1aaa87cf2330", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37740", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lo4hlqln4d2r", "content": "", "creation_timestamp": "2025-05-01T13:55:38.351148Z"}, {"uuid": "4317d2b3-c0da-4915-badb-ec386a885ce8", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37744", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lo4hlqpa4n2h", "content": "", "creation_timestamp": "2025-05-01T13:55:38.999758Z"}, {"uuid": "06fc3c2b-45bb-4daa-a293-130c312b37f3", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37741", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lo4hlqskoe2h", "content": "", "creation_timestamp": "2025-05-01T13:55:39.599368Z"}, {"uuid": "56eb464b-0ad0-4648-a5f2-0d76a82338fa", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37748", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lo4hlqvwxn2h", "content": "", "creation_timestamp": "2025-05-01T13:55:40.184395Z"}, {"uuid": "8dde0000-cd3d-4d4a-abce-aaec01bf6fae", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37742", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lo4hlqzaw42k", "content": "", "creation_timestamp": "2025-05-01T13:55:40.817789Z"}, {"uuid": "a7b08bd9-b0c9-40c9-b1a3-919ea809e0fb", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37757", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lo4hlr4kuv2h", "content": "", "creation_timestamp": "2025-05-01T13:55:41.433140Z"}, {"uuid": "df4e4327-d0db-49a7-aace-637d533f9587", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37755", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lo4hlr7ybx2h", "content": "", "creation_timestamp": "2025-05-01T13:55:42.070482Z"}, {"uuid": "55b02d84-c385-41bd-929e-d0fe28c4ab4a", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37758", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lo4hlrfeae2h", "content": "", "creation_timestamp": "2025-05-01T13:55:42.698983Z"}, {"uuid": "76935545-cd15-4387-bb89-299740314ebc", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37746", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lo4hlripxj2p", "content": "", "creation_timestamp": "2025-05-01T13:55:43.352455Z"}, {"uuid": "aa3cadd4-baaa-493b-818b-2e6ea5907e03", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37753", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lo4hlrmajd2j", "content": "", "creation_timestamp": "2025-05-01T13:55:43.989309Z"}, {"uuid": "5d64b0d3-cd93-40b8-8d85-f4a16a39275d", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37745", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lo4hlrpvzv2e", "content": "", "creation_timestamp": "2025-05-01T13:55:44.597044Z"}, {"uuid": "37887711-7fd6-4ba0-8f3c-feac5a00b08c", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37759", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lo4hlrt76d2j", "content": "", "creation_timestamp": "2025-05-01T13:55:45.218364Z"}, {"uuid": "54b87adb-728b-4d01-acce-33c64dca4324", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37751", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lo4hlrwixv2e", "content": "", "creation_timestamp": "2025-05-01T13:55:45.846973Z"}, {"uuid": "f8bcb39e-6d5d-4e76-a51e-7524dcc24950", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37750", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lo4hls26jr2p", "content": "", "creation_timestamp": "2025-05-01T13:55:46.475362Z"}, {"uuid": "9072721d-f94a-4ce0-91ae-632b315e8db5", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37749", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lo4hls5hmv2e", "content": "", "creation_timestamp": "2025-05-01T13:55:47.099743Z"}, {"uuid": "c2b8983a-0558-4704-a131-0d632d0e99ea", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37756", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lo4hlsb53j22", "content": "", "creation_timestamp": "2025-05-01T13:55:47.689631Z"}, {"uuid": "23c5a344-3085-4979-b552-6c763165ae0f", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37747", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lo4hlsefpb2p", "content": "", "creation_timestamp": "2025-05-01T13:55:48.327944Z"}, {"uuid": "98a581cf-7478-47ef-b4f2-b5368deb029d", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37754", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lo4hlshobf2k", "content": "", "creation_timestamp": "2025-05-01T13:55:48.953921Z"}, {"uuid": "0e35d7b1-e9e8-4da8-b347-3757a2d3efb9", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37752", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lo4hlskxbf2e", "content": "", "creation_timestamp": "2025-05-01T13:55:49.520064Z"}, {"uuid": "35de631b-c8fc-418a-8a03-817afc8a0ccd", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37899", "type": "seen", "source": "https://bsky.app/profile/2rZiKKbOU3nTafniR2qMMSE0gwZ.activitypub.awakari.com.ap.brid.gy/post/3lptctagyt6v2", "content": "", "creation_timestamp": "2025-05-23T09:27:27.087876Z"}, {"uuid": "f4a5875d-013e-45d5-84a1-0736dbde2eda", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37899", "type": "seen", "source": "https://bsky.app/profile/derdreschi84.bsky.social/post/3lqpbwnqamc2s", "content": "", "creation_timestamp": "2025-06-03T12:25:21.942889Z"}, {"uuid": "215a9955-7b4f-4c67-a86f-2970dc03514a", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3746", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lo5yhuxjc72l", "content": "", "creation_timestamp": "2025-05-02T04:30:21.587992Z"}, {"uuid": "acf7e158-d1a1-497a-b021-df33b2e14590", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3707", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lo6e7oog5g22", "content": "", "creation_timestamp": "2025-05-02T08:00:32.253139Z"}, {"uuid": "9273e8f6-17a8-48df-9f69-4f1001e3f4f2", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3748", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lo6e7ozn3a2n", "content": "", "creation_timestamp": "2025-05-02T08:00:33.940798Z"}, {"uuid": "9c898928-4751-4316-a6a1-cb02634b259f", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3708", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lo6e7pe2ro2l", "content": "", "creation_timestamp": "2025-05-02T08:00:35.632140Z"}, {"uuid": "04ddb7c0-e2fc-417e-90c3-ea68666b928d", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3709", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lo6e7piwzo2l", "content": "", "creation_timestamp": "2025-05-02T08:00:36.196623Z"}, {"uuid": "3b8e1ca0-4e59-4595-8460-6ef66949e8e6", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37752", "type": "seen", "source": "https://bsky.app/profile/pmloik.bsky.social/post/3lpfysa6ung2j", "content": "", "creation_timestamp": "2025-05-18T02:22:39.067909Z"}, {"uuid": "a998c279-8952-45e0-9edd-fa3bbfd2b2fd", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37899", "type": "seen", "source": "https://bsky.app/profile/bluesky.awakari.com/post/3lpztpfn46g2a", "content": "", "creation_timestamp": "2025-05-25T23:44:49.609256Z"}, {"uuid": "79673987-24dd-454b-8745-d83bb673091e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37899", "type": "seen", "source": "https://bsky.app/profile/bluesky.awakari.com/post/3lpztpjsueb2s", "content": "", "creation_timestamp": "2025-05-25T23:44:54.082813Z"}, {"uuid": "a89f166a-cd82-44ad-9a6d-b8948e465d33", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37899", "type": "seen", "source": "https://bsky.app/profile/LLMs.activitypub.awakari.com.ap.brid.gy/post/3lpztpwvdzde2", "content": "", "creation_timestamp": "2025-05-25T23:46:04.313535Z"}, {"uuid": "a231de91-133c-4e80-b9c2-ce0d882f9e1a", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "cve-2025-37899", "type": "seen", "source": "https://bsky.app/profile/levlaz.org/post/3lpzwnmevlw2m", "content": "", "creation_timestamp": "2025-05-26T00:37:30.792943Z"}, {"uuid": "0cfac1f9-3dd7-41bd-bcf9-8fb1c2c298f8", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37899", "type": "seen", "source": "https://bsky.app/profile/dasgeldco.bsky.social/post/3lt5oyfpbbx2m", "content": "", "creation_timestamp": "2025-07-04T16:46:36.832365Z"}, {"uuid": "92fc786b-fe24-470b-9764-da1aebb04095", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37899", "type": "seen", "source": "https://bsky.app/profile/linuxiac.bsky.social/post/3lqdt3dpvus2r", "content": "", "creation_timestamp": "2025-05-29T23:00:27.040677Z"}, {"uuid": "ad428781-5b08-41e0-8f81-e44afe5afe87", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37899", "type": "seen", "source": "https://bsky.app/profile/pmloik.bsky.social/post/3lq24gargcq2z", "content": "", "creation_timestamp": "2025-05-26T02:20:46.397323Z"}, {"uuid": "7991d0c6-600a-48b4-af37-b07eb574f41b", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37093", "type": "seen", "source": "https://bsky.app/profile/eyalestrin.bsky.social/post/3lr6w6mhx5h2o", "content": "", "creation_timestamp": "2025-06-09T17:37:37.800240Z"}, {"uuid": "595a33e6-c163-4fa0-b7f5-207362f0a0f3", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "cve-2025-37899", "type": "seen", "source": "https://bsky.app/profile/sambowne.infosec.exchange.ap.brid.gy/post/3lq277bsneqi2", "content": "", "creation_timestamp": "2025-05-26T03:13:48.681442Z"}, {"uuid": "d63cd364-a419-454c-a1d7-c2a1056cfb20", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37797", "type": "seen", "source": "https://bsky.app/profile/2rZiKKbOU3nTafniR2qMMSE0gwZ.activitypub.awakari.com.ap.brid.gy/post/3lo73vornkrk2", "content": "", "creation_timestamp": "2025-05-02T15:58:57.737313Z"}, {"uuid": "6e6cdb82-c2f0-4799-b415-ab5150a5c1ab", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37798", "type": "seen", "source": "https://bsky.app/profile/linux.activitypub.awakari.com.ap.brid.gy/post/3lo73wlmc5dt2", "content": "", "creation_timestamp": "2025-05-02T15:58:59.987729Z"}, {"uuid": "8570bc51-2606-44b9-a543-769e65041c1a", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37798", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lo7frfth3s2h", "content": "", "creation_timestamp": "2025-05-02T18:01:00.719019Z"}, {"uuid": "d1a0201b-7d40-4f10-96c8-47c0e50bc45a", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37797", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lo7frg2lug2r", "content": "", "creation_timestamp": "2025-05-02T18:01:01.931122Z"}, {"uuid": "b3230639-28b0-48a3-9304-383e22ec51ea", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3779", "type": "seen", "source": "https://bsky.app/profile/2rZiKKbOU3nTafniR2qMMSE0gwZ.activitypub.awakari.com.ap.brid.gy/post/3loafnnmijkc2", "content": "", "creation_timestamp": "2025-05-03T03:33:27.064156Z"}, {"uuid": "5d23e788-e369-4026-9ccc-18b1b239766a", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37922", "type": "seen", "source": "https://bsky.app/profile/cyberalerts.bsky.social/post/3lpmjno7sdf2m", "content": "", "creation_timestamp": "2025-05-20T16:40:17.471745Z"}, {"uuid": "d376b351-02fc-4abb-91c1-1ad7184c6843", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37945", "type": "seen", "source": "https://bsky.app/profile/linux.activitypub.awakari.com.ap.brid.gy/post/3lpmlbbcpxys2", "content": "", "creation_timestamp": "2025-05-20T17:10:43.887887Z"}, {"uuid": "6f1f54dc-c008-4fd7-a2ec-90e97fa58d8a", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37899", "type": "seen", "source": "https://bsky.app/profile/bluesky.awakari.com/post/3lptg2bcnno2r", "content": "", "creation_timestamp": "2025-05-23T10:24:23.468208Z"}, {"uuid": "399cd08f-33a1-44ed-9f95-4ac68b959470", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37943", "type": "seen", "source": "https://bsky.app/profile/linux.activitypub.awakari.com.ap.brid.gy/post/3lpmlbhezjr52", "content": "", "creation_timestamp": "2025-05-20T17:10:44.475796Z"}, {"uuid": "5092d43a-c721-4a8a-89c3-8bfe3c0aa004", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37899", "type": "seen", "source": "https://bsky.app/profile/bluesky.awakari.com/post/3lptg2hu5qw2r", "content": "", "creation_timestamp": "2025-05-23T10:24:30.094811Z"}, {"uuid": "2e59a0b9-a23c-40dc-a136-23a7b25c294b", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37944", "type": "seen", "source": "https://bsky.app/profile/linux.activitypub.awakari.com.ap.brid.gy/post/3lpmlbiibwd42", "content": "", "creation_timestamp": "2025-05-20T17:10:45.207983Z"}, {"uuid": "ea1c9db5-5dd9-4b2a-8b87-ea279beb72c5", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37940", "type": "seen", "source": "https://bsky.app/profile/FunctionalProgramming.activitypub.awakari.com.ap.brid.gy/post/3lpmlbrps3u42", "content": "", "creation_timestamp": "2025-05-20T17:10:47.380927Z"}, {"uuid": "2303b365-edef-4241-9ece-76805c88d2c1", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37899", "type": "seen", "source": "https://bsky.app/profile/2rZiKKbOU3nTafniR2qMMSE0gwZ.activitypub.awakari.com.ap.brid.gy/post/3lptg2caupg72", "content": "", "creation_timestamp": "2025-05-23T10:26:02.799790Z"}, {"uuid": "1d3eb4bf-359d-4d16-8c0d-6671466ac464", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37899", "type": "seen", "source": "https://bsky.app/profile/technews4869.bsky.social/post/3lq2hy3uk5u2q", "content": "", "creation_timestamp": "2025-05-26T05:47:36.676559Z"}, {"uuid": "86641a16-cf07-446f-9198-47d002783ea5", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3715", "type": "seen", "source": "https://bsky.app/profile/2rZiKKbOU3nTafniR2qMMSE0gwZ.activitypub.awakari.com.ap.brid.gy/post/3lpggdri2rer2", "content": "", "creation_timestamp": "2025-05-18T06:25:13.771119Z"}, {"uuid": "d1072eba-e6ab-4e6a-a7b6-7ea8b2dc31b3", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37942", "type": "seen", "source": "https://bsky.app/profile/linux.activitypub.awakari.com.ap.brid.gy/post/3lpmlbnwiuzs2", "content": "", "creation_timestamp": "2025-05-20T17:10:46.101224Z"}, {"uuid": "252ab541-5aec-444b-bcef-db992870b0de", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37941", "type": "seen", "source": "https://bsky.app/profile/linux.activitypub.awakari.com.ap.brid.gy/post/3lpmlbp3kdnn2", "content": "", "creation_timestamp": "2025-05-20T17:10:46.687681Z"}, {"uuid": "94889b48-b84b-4734-afb4-a1ec705817fa", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37799", "type": "seen", "source": "https://bsky.app/profile/2rZiKKbOU3nTafniR2qMMSE0gwZ.activitypub.awakari.com.ap.brid.gy/post/3lobd5iffbx52", "content": "", "creation_timestamp": "2025-05-03T12:58:04.535306Z"}, {"uuid": "cb7a5107-62f8-4166-8b46-b38dc4c6672f", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37799", "type": "seen", "source": "https://bsky.app/profile/linux.activitypub.awakari.com.ap.brid.gy/post/3lobejp6emaq2", "content": "", "creation_timestamp": "2025-05-03T12:58:59.185003Z"}, {"uuid": "0c54f582-5ab6-4895-b272-349417dc3fea", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37799", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lobj433suj2h", "content": "", "creation_timestamp": "2025-05-03T14:05:58.563769Z"}, {"uuid": "2adb830d-3eb0-4e43-bea6-f686970f16bf", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37939", "type": "seen", "source": "https://bsky.app/profile/linux.activitypub.awakari.com.ap.brid.gy/post/3lpmlbxtnvky2", "content": "", "creation_timestamp": "2025-05-20T17:10:48.179363Z"}, {"uuid": "1092d602-9318-44d6-becb-b06489b2ef18", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37938", "type": "seen", "source": "https://bsky.app/profile/linux.activitypub.awakari.com.ap.brid.gy/post/3lpmlc4j2apy2", "content": "", "creation_timestamp": "2025-05-20T17:10:48.978888Z"}, {"uuid": "c6064eb4-aa1c-4a68-afee-23d849767c96", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37937", "type": "seen", "source": "https://bsky.app/profile/linux.activitypub.awakari.com.ap.brid.gy/post/3lpmlc5xzw542", "content": "", "creation_timestamp": "2025-05-20T17:10:49.595632Z"}, {"uuid": "d140d3a3-92a2-4423-8011-f013085e1091", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37899", "type": "seen", "source": "https://bsky.app/profile/ytroncal.bsky.social/post/3lq2kwv3bgc2q", "content": "", "creation_timestamp": "2025-05-26T06:40:41.292568Z"}, {"uuid": "dbb110f7-badc-4443-b50a-4b55632969af", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3715", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lpgpqrbxpg2o", "content": "", "creation_timestamp": "2025-05-18T09:13:26.589922Z"}, {"uuid": "92f4f9fe-f9dd-4e46-9301-58c06976e778", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37899", "type": "seen", "source": "https://bsky.app/profile/pmloik.bsky.social/post/3lqe64gjdrg2z", "content": "", "creation_timestamp": "2025-05-30T02:17:41.802804Z"}, {"uuid": "e47dbaa0-dff3-404c-93a5-32fb2c0447eb", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "cve-2025-37899", "type": "seen", "source": "https://bsky.app/profile/mm-hacker-news.bsky.social/post/3lq2nv2o6ey2g", "content": "", "creation_timestamp": "2025-05-26T07:33:16.814296Z"}, {"uuid": "dec8932c-6dc2-4804-802b-6fe6cc2d3f85", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37899", "type": "seen", "source": "https://bsky.app/profile/prohoster.bsky.social/post/3lq2ovnzhzx2c", "content": "", "creation_timestamp": "2025-05-26T07:51:31.334939Z"}, {"uuid": "f618b2fc-732f-46f9-b03c-b246e6d2ece5", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37899", "type": "seen", "source": "https://bsky.app/profile/technews4869.bsky.social/post/3lq2oy5n42p2r", "content": "", "creation_timestamp": "2025-05-26T07:52:54.205889Z"}, {"uuid": "a2394f3e-cf04-465c-8a92-470dc4663d4d", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37899", "type": "seen", "source": "https://bsky.app/profile/bluesky.awakari.com/post/3lq2qybmk5s25", "content": "", "creation_timestamp": "2025-05-26T08:28:45.929777Z"}, {"uuid": "3ec9bb40-e76f-45b0-bcb1-3bc7c6cf6fbb", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3705", "type": "seen", "source": "https://infosec.exchange/users/certvde/statuses/114811366375846832", "content": "", "creation_timestamp": "2025-07-07T10:00:22.128228Z"}, {"uuid": "6b1f2745-9bfb-4ba7-86db-92694173e1de", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37899", "type": "seen", "source": "https://bsky.app/profile/bluesky.awakari.com/post/3lq2rzrsp2f2e", "content": "", "creation_timestamp": "2025-05-26T08:47:30.251891Z"}, {"uuid": "41827738-3412-4179-a151-dc04c6e4f490", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37899", "type": "seen", "source": "https://bsky.app/profile/bluesky.awakari.com/post/3lq2rzs5byq2c", "content": "", "creation_timestamp": "2025-05-26T08:47:30.950614Z"}, {"uuid": "91b0c71c-5036-45bf-84c4-97951206bca7", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3746", "type": "seen", "source": "https://bsky.app/profile/ransomnews.online/post/3logbq4rhar2i", "content": "", "creation_timestamp": "2025-05-05T11:37:20.317537Z"}, {"uuid": "87f13de0-3ded-4160-bfaa-d16376cedfc1", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37799", "type": "seen", "source": "https://bsky.app/profile/omo.bsky.social/post/3lohweq5r2c2h", "content": "", "creation_timestamp": "2025-05-06T03:19:28.033925Z"}, {"uuid": "bcba5061-2729-4ccc-9428-95cc9842492c", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37899", "type": "seen", "source": "https://bsky.app/profile/2rZiKKbOU3nTafniR2qMMSE0gwZ.activitypub.awakari.com.ap.brid.gy/post/3lq2s2z3rzlj2", "content": "", "creation_timestamp": "2025-05-26T08:50:29.428058Z"}, {"uuid": "1c572cf8-5b64-4717-a426-28a044e9c6c2", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37979", "type": "seen", "source": "https://infosec.exchange/users/vuldb/statuses/114541863164980272", "content": "", "creation_timestamp": "2025-05-20T19:42:09.864617Z"}, {"uuid": "486d4d1d-4889-4481-9cbe-fbb198dea903", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3745", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lssnl2xyet2s", "content": "", "creation_timestamp": "2025-06-30T07:21:58.430570Z"}, {"uuid": "0f3470dd-682b-42d8-af1f-6219cd454ebb", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37978", "type": "seen", "source": "https://infosec.exchange/users/vuldb/statuses/114541915882776475", "content": "", "creation_timestamp": "2025-05-20T19:55:33.742948Z"}, {"uuid": "cec63ccd-64e4-4386-ac67-32f875194383", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37981", "type": "seen", "source": "https://infosec.exchange/users/vuldb/statuses/114541968902367001", "content": "", "creation_timestamp": "2025-05-20T20:09:02.679016Z"}, {"uuid": "25751629-b423-4fa9-92d2-2d5bb0040600", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37730", "type": "seen", "source": "https://bsky.app/profile/2rZiKKbOU3nTafniR2qMMSE0gwZ.activitypub.awakari.com.ap.brid.gy/post/3lojlqlndmjh2", "content": "", "creation_timestamp": "2025-05-06T19:20:01.256647Z"}, {"uuid": "bbc8539d-6f64-45d3-b18e-c7c8f69bfe9b", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37752", "type": "seen", "source": "https://bsky.app/profile/raptor.infosec.exchange.ap.brid.gy/post/3lokm62zwgry2", "content": "", "creation_timestamp": "2025-05-07T04:55:30.933302Z"}, {"uuid": "cd1a221c-7400-4d70-8746-484134031a81", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37752", "type": "seen", "source": "https://bsky.app/profile/bluesky.awakari.com/post/3lokmaiff5l27", "content": "", "creation_timestamp": "2025-05-07T04:56:05.212027Z"}, {"uuid": "50176d0b-7ee4-4140-9132-c419d6801581", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3766", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lokxyklrhm2w", "content": "", "creation_timestamp": "2025-05-07T08:26:24.345152Z"}, {"uuid": "0e4d0e74-6c74-4682-b7b7-7fe82859ae1d", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37093", "type": "seen", "source": "https://bsky.app/profile/opsmatters.com/post/3lqtfu3i5xo2k", "content": "", "creation_timestamp": "2025-06-05T03:46:07.722817Z"}, {"uuid": "73c40d9e-7efc-4e51-b57a-c352483d1e1b", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37097", "type": "seen", "source": "https://infosec.exchange/users/cR0w/statuses/114778583008935449", "content": "", "creation_timestamp": "2025-07-01T15:03:07.666060Z"}, {"uuid": "41d6755a-04fd-48f2-9c93-857041b1ae6d", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37834", "type": "seen", "source": "https://bsky.app/profile/2rZiKKbOU3nTafniR2qMMSE0gwZ.activitypub.awakari.com.ap.brid.gy/post/3loneaif7srj2", "content": "", "creation_timestamp": "2025-05-08T07:11:02.359882Z"}, {"uuid": "67916a59-72a2-417b-b1a7-3ce257ce1042", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37833", "type": "seen", "source": "https://bsky.app/profile/2rZiKKbOU3nTafniR2qMMSE0gwZ.activitypub.awakari.com.ap.brid.gy/post/3loneasyv3mj2", "content": "", "creation_timestamp": "2025-05-08T07:11:15.533435Z"}, {"uuid": "c65f97a9-9079-43ba-962d-6dc2ad360d07", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37832", "type": "seen", "source": "https://bsky.app/profile/2rZiKKbOU3nTafniR2qMMSE0gwZ.activitypub.awakari.com.ap.brid.gy/post/3loneb3on7cx2", "content": "", "creation_timestamp": "2025-05-08T07:11:29.091875Z"}, {"uuid": "52b9a382-ba36-4183-b917-a5ebb1658d53", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37831", "type": "seen", "source": "https://bsky.app/profile/2rZiKKbOU3nTafniR2qMMSE0gwZ.activitypub.awakari.com.ap.brid.gy/post/3lonebcctogx2", "content": "", "creation_timestamp": "2025-05-08T07:11:39.379154Z"}, {"uuid": "12c09f5e-8cd8-41f3-a564-cac0ed4f94fb", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37830", "type": "seen", "source": "https://bsky.app/profile/2rZiKKbOU3nTafniR2qMMSE0gwZ.activitypub.awakari.com.ap.brid.gy/post/3lonebiaoe3c2", "content": "", "creation_timestamp": "2025-05-08T07:11:39.973666Z"}, {"uuid": "a794d955-2054-49b5-9076-8973df06f194", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37828", "type": "seen", "source": "https://bsky.app/profile/2rZiKKbOU3nTafniR2qMMSE0gwZ.activitypub.awakari.com.ap.brid.gy/post/3lonebjyfse32", "content": "", "creation_timestamp": "2025-05-08T07:11:40.520257Z"}, {"uuid": "5dd7f0c1-764e-4ca1-8930-051eaa310358", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37829", "type": "seen", "source": "https://bsky.app/profile/2rZiKKbOU3nTafniR2qMMSE0gwZ.activitypub.awakari.com.ap.brid.gy/post/3lonebphnbqx2", "content": "", "creation_timestamp": "2025-05-08T07:11:41.273666Z"}, {"uuid": "72b9bbb5-4d80-411c-afcc-7f3a1924fe29", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37826", "type": "seen", "source": "https://bsky.app/profile/2rZiKKbOU3nTafniR2qMMSE0gwZ.activitypub.awakari.com.ap.brid.gy/post/3lonebwerh6c2", "content": "", "creation_timestamp": "2025-05-08T07:11:51.179643Z"}, {"uuid": "2aef7889-160f-4f43-b038-9ef4b36251ee", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37827", "type": "seen", "source": "https://bsky.app/profile/2rZiKKbOU3nTafniR2qMMSE0gwZ.activitypub.awakari.com.ap.brid.gy/post/3lonebx2sjxj2", "content": "", "creation_timestamp": "2025-05-08T07:11:51.709538Z"}, {"uuid": "d28fa0d6-8038-4b94-8ccf-718534080347", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37826", "type": "seen", "source": "https://bsky.app/profile/potato.software/post/3lonid7trt72z", "content": "", "creation_timestamp": "2025-05-08T08:24:01.112834Z"}, {"uuid": "2a4d87af-19cc-472a-a693-a220d89af0b9", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37816", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3loniqqkbaj2e", "content": "", "creation_timestamp": "2025-05-08T08:31:35.135172Z"}, {"uuid": "1c842eb0-8a1d-4112-ac19-c5fb580b3b53", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37818", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3loniqqtvxp2h", "content": "", "creation_timestamp": "2025-05-08T08:31:35.709763Z"}, {"uuid": "50f3119d-ad6d-4495-94e7-36602beb4076", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37819", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3loniqqxfmz2r", "content": "", "creation_timestamp": "2025-05-08T08:31:36.489652Z"}, {"uuid": "64a63007-45d7-4d68-87fe-8a79c963d940", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37817", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3loniqr33wi2l", "content": "", "creation_timestamp": "2025-05-08T08:31:37.027797Z"}, {"uuid": "5333f12d-e873-4d89-a7f7-2fdf68c2d4c6", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37821", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3loniqr6q3o2o", "content": "", "creation_timestamp": "2025-05-08T08:31:37.564602Z"}, {"uuid": "73be9877-d319-413c-a74b-19ccaeb91ded", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37826", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3loniqrcggp22", "content": "", "creation_timestamp": "2025-05-08T08:31:38.087146Z"}, {"uuid": "dc30947a-5a06-475f-9cb6-7a9bbae8e9ea", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37820", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3loniqrg3wy2h", "content": "", "creation_timestamp": "2025-05-08T08:31:38.689181Z"}, {"uuid": "6bf86505-526b-4817-b1e4-6d65e73f4858", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37825", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3loniqrjp5z2p", "content": "", "creation_timestamp": "2025-05-08T08:31:39.191519Z"}, {"uuid": "6e5efd5d-258a-4934-bce9-2bc61e763b9a", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37829", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3loniqrn25i2l", "content": "", "creation_timestamp": "2025-05-08T08:31:39.669075Z"}, {"uuid": "b44d4e3d-a4fb-46a7-b531-5dbcadecb2bb", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37827", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3loniqrqh2h2h", "content": "", "creation_timestamp": "2025-05-08T08:31:40.154806Z"}, {"uuid": "31595995-fbe7-4674-aff7-59deeab9ab6b", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37822", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3loniqru2pg2o", "content": "", "creation_timestamp": "2025-05-08T08:31:40.645476Z"}, {"uuid": "04f62978-084c-4fb3-8a4a-0820e2a832fd", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37824", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3loniqrxhtt2n", "content": "", "creation_timestamp": "2025-05-08T08:31:41.168443Z"}, {"uuid": "d78b5ac9-937c-4b88-aefb-ccac37bffd24", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37831", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3loniqs2szb2p", "content": "", "creation_timestamp": "2025-05-08T08:31:41.646024Z"}, {"uuid": "0f3bbba6-b7fc-4afe-a570-3b00375d1f0e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37832", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3loniqs67sz2r", "content": "", "creation_timestamp": "2025-05-08T08:31:42.309472Z"}, {"uuid": "ec6623ce-9d77-4ba8-bbfa-695b7b80cdc5", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37828", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3loniqsbwmp2h", "content": "", "creation_timestamp": "2025-05-08T08:31:42.891250Z"}, {"uuid": "22c3746a-6e88-4959-9b85-b8fe4cbb8cb0", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37834", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3loniqsfmey2l", "content": "", "creation_timestamp": "2025-05-08T08:31:43.459859Z"}, {"uuid": "ecd205e1-9cc5-47e3-b285-fbd83517385d", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37830", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3loniqsmema2j", "content": "", "creation_timestamp": "2025-05-08T08:31:44.568872Z"}, {"uuid": "423247a3-1e8d-45d7-aee3-1b7ef7ec90d9", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37833", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3loniqspppt2t", "content": "", "creation_timestamp": "2025-05-08T08:31:45.177955Z"}, {"uuid": "e6cd46e6-610d-4650-967b-d4ffd57924c7", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37823", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3loniqst5bj2e", "content": "", "creation_timestamp": "2025-05-08T08:31:45.752102Z"}, {"uuid": "943cbc1c-8c32-4ce1-bdde-d2741d3bd143", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37098", "type": "seen", "source": "https://infosec.exchange/users/cR0w/statuses/114778583008935449", "content": "", "creation_timestamp": "2025-07-01T15:03:07.767305Z"}, {"uuid": "7622f60a-49b6-454e-a1db-a3b738dca5f4", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37099", "type": "seen", "source": "https://infosec.exchange/users/cR0w/statuses/114778583008935449", "content": "", "creation_timestamp": "2025-07-01T15:03:07.866668Z"}, {"uuid": "af951271-2d3f-4b4f-897d-7f9b9f295b61", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3705", "type": "seen", "source": "https://bsky.app/profile/certvde.infosec.exchange.ap.brid.gy/post/3ltejp326l5t2", "content": "", "creation_timestamp": "2025-07-07T10:01:38.824194Z"}, {"uuid": "c1f928b1-0e1e-4ba8-ad84-47587629d744", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3759", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lonw6bewky2j", "content": "", "creation_timestamp": "2025-05-08T12:31:49.609078Z"}, {"uuid": "60bf59f1-9a46-4ef1-aa88-cd054f3ca9fe", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3758", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lonw6biat42p", "content": "", "creation_timestamp": "2025-05-08T12:31:50.276996Z"}, {"uuid": "d628edcc-6414-42fb-8545-2fe3e550f5a1", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3759", "type": "seen", "source": "https://bsky.app/profile/2rZiKKbOU3nTafniR2qMMSE0gwZ.activitypub.awakari.com.ap.brid.gy/post/3loo2k76fvm32", "content": "", "creation_timestamp": "2025-05-08T14:05:34.272163Z"}, {"uuid": "7b44a5c5-ed04-487c-b95a-60d9b68a4fda", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3758", "type": "seen", "source": "https://bsky.app/profile/2rZiKKbOU3nTafniR2qMMSE0gwZ.activitypub.awakari.com.ap.brid.gy/post/3loo2k7pjag32", "content": "", "creation_timestamp": "2025-05-08T14:05:34.794750Z"}, {"uuid": "b869bfbf-71cf-4eab-a4fb-9f68ee253e52", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37823", "type": "seen", "source": "https://infosec.exchange/users/vuldb/statuses/114473653498479043", "content": "", "creation_timestamp": "2025-05-08T18:35:33.067803Z"}, {"uuid": "adf3be8d-2fee-477a-ae8a-c6a6ddaed88d", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37899", "type": "seen", "source": "https://bsky.app/profile/bluesky.awakari.com/post/3lptuhrbzo226", "content": "", "creation_timestamp": "2025-05-23T14:42:28.756695Z"}, {"uuid": "fbd49b8d-9a08-4722-8d2a-e6c0fa2a1326", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37899", "type": "seen", "source": "https://bsky.app/profile/bluesky.awakari.com/post/3lptuhus6w32i", "content": "", "creation_timestamp": "2025-05-23T14:42:32.210008Z"}, {"uuid": "3e656c8b-de5d-40b4-be8c-6fe68c7821a5", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3711", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lopmefbwt32h", "content": "", "creation_timestamp": "2025-05-09T04:41:35.339435Z"}, {"uuid": "4234ce62-9ccb-461e-939e-7b1e401d4274", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3714", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lopmefkfmq2j", "content": "", "creation_timestamp": "2025-05-09T04:41:36.488745Z"}, {"uuid": "585c4157-54d8-46f6-85e8-98fb7454157d", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3710", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lopmefu3td22", "content": "", "creation_timestamp": "2025-05-09T04:41:37.686688Z"}, {"uuid": "c2a1046e-c235-4c14-9cfc-11df5f4ff5f5", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37877", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lopz7xulq62h", "content": "", "creation_timestamp": "2025-05-09T08:31:45.191254Z"}, {"uuid": "cd3b73c7-9373-47b9-b8bb-259fd143bd8e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37879", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lopz7y64cr2p", "content": "", "creation_timestamp": "2025-05-09T08:31:45.823256Z"}, {"uuid": "915dbe58-0de9-4fe5-b866-096952fffa32", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37881", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lopz7ybev42t", "content": "", "creation_timestamp": "2025-05-09T08:31:46.367216Z"}, {"uuid": "13934da7-3d5b-4881-a0b5-1e8a8185640b", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37880", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lopz7yf3ud2l", "content": "", "creation_timestamp": "2025-05-09T08:31:46.968117Z"}, {"uuid": "7888c6a0-60ef-4c71-bcdc-9949fa69a92f", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37884", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lopz7yinkc2h", "content": "", "creation_timestamp": "2025-05-09T08:31:47.523161Z"}, {"uuid": "896beb79-c60c-43b7-a798-9bcf9ec52c89", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37889", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lopz7ylxro2h", "content": "", "creation_timestamp": "2025-05-09T08:31:48.116554Z"}, {"uuid": "73f22829-0204-400d-8ab0-f8a9412da9f8", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37888", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lopz7ypn6z24", "content": "", "creation_timestamp": "2025-05-09T08:31:48.677375Z"}, {"uuid": "10d3dcd9-a03a-473b-a0f1-25a73bac7195", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37882", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lopz7ytbko2n", "content": "", "creation_timestamp": "2025-05-09T08:31:49.242381Z"}, {"uuid": "a09b991b-56de-4ea8-89ed-fd6a26443c96", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37885", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lopz7ywwmq2j", "content": "", "creation_timestamp": "2025-05-09T08:31:49.822742Z"}, {"uuid": "6c1b1857-05b3-4b72-bed1-580237353b84", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37887", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lopz7z2a7o2n", "content": "", "creation_timestamp": "2025-05-09T08:31:50.380693Z"}, {"uuid": "025fbbea-b704-4f27-b8f7-1c0bdba8cb1e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37883", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lopz7z5kau2t", "content": "", "creation_timestamp": "2025-05-09T08:31:50.948385Z"}, {"uuid": "6983e3ce-d2e0-4b03-b395-28276de2c925", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37886", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lopz7zaxnx2e", "content": "", "creation_timestamp": "2025-05-09T08:31:51.495278Z"}, {"uuid": "31a571f7-fc31-4b1c-b146-749fcd824f9e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37876", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lopz7ziiug2h", "content": "", "creation_timestamp": "2025-05-09T08:31:52.612455Z"}, {"uuid": "e9072250-a3f6-4711-b5a1-c3fe40ed56a4", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37854", "type": "seen", "source": "https://bsky.app/profile/potato.software/post/3loq3qafuzy2k", "content": "", "creation_timestamp": "2025-05-09T09:16:38.577299Z"}, {"uuid": "80534d9b-571b-4d0f-9eb8-83f2ec41510e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37882", "type": "seen", "source": "https://bsky.app/profile/linux.activitypub.awakari.com.ap.brid.gy/post/3lopwp33ml4e2", "content": "", "creation_timestamp": "2025-05-09T09:21:34.242706Z"}, {"uuid": "2008ace9-b40d-4dd1-8524-1c5fee60157b", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37884", "type": "seen", "source": "https://bsky.app/profile/linux.activitypub.awakari.com.ap.brid.gy/post/3lopwp5fhbcx2", "content": "", "creation_timestamp": "2025-05-09T09:21:35.004094Z"}, {"uuid": "b0c0cdd1-7ae5-4933-9657-151f1682dba5", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37889", "type": "seen", "source": "https://bsky.app/profile/linux.activitypub.awakari.com.ap.brid.gy/post/3lopwpj3tvyu2", "content": "", "creation_timestamp": "2025-05-09T09:21:37.069304Z"}, {"uuid": "4f7a1ccf-e8e0-4e0d-b46c-d9a75217cf4a", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37883", "type": "seen", "source": "https://bsky.app/profile/linux.activitypub.awakari.com.ap.brid.gy/post/3lopwpegkkku2", "content": "", "creation_timestamp": "2025-05-09T09:21:37.715427Z"}, {"uuid": "2ae9db8f-2d0d-4c4b-bbeb-c1673ae1502b", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37888", "type": "seen", "source": "https://bsky.app/profile/linux.activitypub.awakari.com.ap.brid.gy/post/3lopwpsfsykk2", "content": "", "creation_timestamp": "2025-05-09T09:21:39.557678Z"}, {"uuid": "ac25d93f-6c63-4d6d-847b-297702e611fd", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37887", "type": "seen", "source": "https://bsky.app/profile/linux.activitypub.awakari.com.ap.brid.gy/post/3lopwq665cle2", "content": "", "creation_timestamp": "2025-05-09T09:21:40.446916Z"}, {"uuid": "a81fa361-cd6e-4f7f-90e8-ad7e0f1f1e8f", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37886", "type": "seen", "source": "https://bsky.app/profile/linux.activitypub.awakari.com.ap.brid.gy/post/3lopwqddvkzx2", "content": "", "creation_timestamp": "2025-05-09T09:21:41.160449Z"}, {"uuid": "a478a915-0906-4a70-9d3d-783fc4d2dbe9", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37885", "type": "seen", "source": "https://bsky.app/profile/linux.activitypub.awakari.com.ap.brid.gy/post/3lopwqiszvvu2", "content": "", "creation_timestamp": "2025-05-09T09:21:42.376739Z"}, {"uuid": "28fa43f1-ae34-454a-94ba-fe60efedff69", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37097", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lsw6j3mwzn2r", "content": "", "creation_timestamp": "2025-07-01T17:03:05.996215Z"}, {"uuid": "94832ad6-f0ef-4367-8572-93d1d0632848", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3714", "type": "seen", "source": "https://infosec.exchange/users/cR0w/statuses/114477842355664363", "content": "", "creation_timestamp": "2025-05-09T12:20:49.447027Z"}, {"uuid": "2994a9b9-5f44-4e6a-b57d-d4de93e8568e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3713", "type": "seen", "source": "https://infosec.exchange/users/cR0w/statuses/114477847717737333", "content": "", "creation_timestamp": "2025-05-09T12:22:11.334359Z"}, {"uuid": "6d6342bd-651d-4676-b06e-a7f4e7df2c53", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3712", "type": "seen", "source": "https://infosec.exchange/users/cR0w/statuses/114477847717737333", "content": "", "creation_timestamp": "2025-05-09T12:22:11.394893Z"}, {"uuid": "f66608ae-d4e8-458b-8457-7f90b4fdd808", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3711", "type": "seen", "source": "https://infosec.exchange/users/cR0w/statuses/114477847717737333", "content": "", "creation_timestamp": "2025-05-09T12:22:11.455985Z"}, {"uuid": "91dae665-bb65-4c9a-9ad8-0d41dc7461cb", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3710", "type": "seen", "source": "https://infosec.exchange/users/cR0w/statuses/114477847717737333", "content": "", "creation_timestamp": "2025-05-09T12:22:11.511797Z"}, {"uuid": "cabc8186-dd2c-4e83-9cb4-146d31969112", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37874", "type": "seen", "source": "https://infosec.exchange/users/vuldb/statuses/114479439792019818", "content": "", "creation_timestamp": "2025-05-09T19:07:04.246209Z"}, {"uuid": "d94b6ea9-9565-4cd5-9ff3-c0f6eaff1d48", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37869", "type": "seen", "source": "https://infosec.exchange/users/vuldb/statuses/114479492858231080", "content": "", "creation_timestamp": "2025-05-09T19:20:33.917689Z"}, {"uuid": "a2daab76-0abb-4df6-87ca-1bd7d4885b15", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3794", "type": "seen", "source": "https://bsky.app/profile/2rZiKKbOU3nTafniR2qMMSE0gwZ.activitypub.awakari.com.ap.brid.gy/post/3lormmzq2ajr2", "content": "", "creation_timestamp": "2025-05-10T00:05:23.791461Z"}, {"uuid": "f816eb22-97c1-473f-8988-653cb91e357f", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3794", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lorvkydzjj2h", "content": "", "creation_timestamp": "2025-05-10T02:31:40.334114Z"}, {"uuid": "0403407c-955a-4d8f-b1ea-7c1cfd9d0e53", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37899", "type": "seen", "source": "https://bsky.app/profile/pmloik.bsky.social/post/3lqlpry5frg2u", "content": "", "creation_timestamp": "2025-06-02T02:22:36.254040Z"}, {"uuid": "2080aad3-8dbb-4cd3-a8f9-31a265331677", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37889", "type": "seen", "source": "https://bsky.app/profile/2rZiKKbOU3nTafniR2qMMSE0gwZ.activitypub.awakari.com.ap.brid.gy/post/3lotadoxxk232", "content": "", "creation_timestamp": "2025-05-10T15:17:35.831710Z"}, {"uuid": "cab3d136-6c68-48a5-8eb5-1c41197387bf", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37752", "type": "seen", "source": "https://infosec.exchange/users/Tinolle/statuses/114490626920406283", "content": "", "creation_timestamp": "2025-05-11T18:32:06.219227Z"}, {"uuid": "584ce4f6-ce7e-4b24-99ee-330c52921e79", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37899", "type": "seen", "source": "https://bsky.app/profile/bluesky.awakari.com/post/3lpu3y2wqxg22", "content": "", "creation_timestamp": "2025-05-23T16:56:51.780285Z"}, {"uuid": "835f903f-d04f-435e-9f10-fe8ae0c066fe", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37899", "type": "seen", "source": "https://bsky.app/profile/2rZiKKbOU3nTafniR2qMMSE0gwZ.activitypub.awakari.com.ap.brid.gy/post/3lpu3yczgzrn2", "content": "", "creation_timestamp": "2025-05-23T16:57:10.464001Z"}, {"uuid": "d8897ef1-e702-4d3b-98b6-74b3c743ee13", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37101", "type": "seen", "source": "https://bsky.app/profile/2rZiKKbOU3nTafniR2qMMSE0gwZ.activitypub.awakari.com.ap.brid.gy/post/3lsj4u5m27cj2", "content": "", "creation_timestamp": "2025-06-26T12:29:08.758017Z"}, {"uuid": "91203eb1-7cb8-4cd9-b546-d0287da253bf", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37780", "type": "seen", "source": "https://bsky.app/profile/ferramentaslinux.bsky.social/post/3lrtheiu25s2v", "content": "", "creation_timestamp": "2025-06-17T21:38:25.241539Z"}, {"uuid": "e602a04d-aaf1-4815-823b-1e46ebb3cfae", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3771", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lsj5qbg5lc2a", "content": "", "creation_timestamp": "2025-06-26T12:44:35.338957Z"}, {"uuid": "4ac910f7-8fb9-462a-8bfe-6a953410dda3", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3722", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lsj5z7tkcj2r", "content": "", "creation_timestamp": "2025-06-26T12:49:35.715055Z"}, {"uuid": "b32c27ab-6e89-48e3-b930-62472ce991ed", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37899", "type": "seen", "source": "https://bsky.app/profile/bluesky.awakari.com/post/3lq36ji2qxr22", "content": "", "creation_timestamp": "2025-05-26T12:31:01.915959Z"}, {"uuid": "20cebb5c-c251-4b1c-a563-fa98cd951cf2", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37899", "type": "seen", "source": "https://bsky.app/profile/bluesky.awakari.com/post/3lq36jo273n2g", "content": "", "creation_timestamp": "2025-05-26T12:31:08.009246Z"}, {"uuid": "39491b5c-2c9e-4535-b9b5-d9546a207f9e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37899", "type": "seen", "source": "https://bsky.app/profile/bearstech.com/post/3lqa43dibwy2m", "content": "", "creation_timestamp": "2025-05-28T11:30:38.716560Z"}, {"uuid": "c3ab68f7-e932-4512-a8ad-14f91f8f2340", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37899", "type": "seen", "source": "https://bsky.app/profile/2rZiKKbOU3nTafniR2qMMSE0gwZ.activitypub.awakari.com.ap.brid.gy/post/3lq36jz5hehy2", "content": "", "creation_timestamp": "2025-05-26T12:31:40.604212Z"}, {"uuid": "e1b48e88-761b-48eb-a9d9-44c2b5b1725a", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3757", "type": "seen", "source": "https://infosec.exchange/users/cR0w/statuses/114501563358261613", "content": "", "creation_timestamp": "2025-05-13T16:53:23.303698Z"}, {"uuid": "ea6330ae-8847-4065-96e7-c240c63feab0", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3744", "type": "seen", "source": "https://infosec.exchange/users/cR0w/statuses/114502062413712501", "content": "", "creation_timestamp": "2025-05-13T19:00:18.122245Z"}, {"uuid": "5e5a0bfb-c90b-436f-8305-40f65e853f1b", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3744", "type": "seen", "source": "https://bsky.app/profile/2rZiKKbOU3nTafniR2qMMSE0gwZ.activitypub.awakari.com.ap.brid.gy/post/3lp36v5yt6r72", "content": "", "creation_timestamp": "2025-05-13T19:21:22.425497Z"}, {"uuid": "1ec76b74-e868-4d62-a3ad-b114236928b5", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37752", "type": "seen", "source": "https://bsky.app/profile/linkersec.bsky.social/post/3lp3dfymsqk2a", "content": "", "creation_timestamp": "2025-05-13T20:33:23.611152Z"}, {"uuid": "61f969e1-4334-4bfe-a9ee-e31e3b08b83e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37752", "type": "seen", "source": "https://bsky.app/profile/linkersec.bsky.social/post/3lp3dfzjavk2a", "content": "", "creation_timestamp": "2025-05-13T20:33:24.143200Z"}, {"uuid": "08f4d386-3aa9-4a89-b04f-88f3383af55d", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3744", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lp3eaemcd424", "content": "", "creation_timestamp": "2025-05-13T20:48:10.636561Z"}, {"uuid": "f41d1757-ad08-4c96-ac7d-e50fa5221959", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37899", "type": "seen", "source": "https://bsky.app/profile/eyalestrin.bsky.social/post/3lqmecgbd7d2i", "content": "", "creation_timestamp": "2025-06-02T08:29:42.770510Z"}, {"uuid": "e9be6db4-1cf6-4789-8558-2085a6199a6c", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3755", "type": "seen", "source": "https://www.cisa.gov/news-events/ics-advisories/icsa-25-153-03", "content": "", "creation_timestamp": "2025-06-03T10:00:00.000000Z"}, {"uuid": "365bb29f-e799-4c70-a9b5-0073ec71d3ad", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37899", "type": "seen", "source": "https://bsky.app/profile/2rZiKKbOU3nTafniR2qMMSE0gwZ.activitypub.awakari.com.ap.brid.gy/post/3lpui4xpg56m2", "content": "", "creation_timestamp": "2025-05-23T20:34:32.898247Z"}, {"uuid": "dd54a945-1a7a-4edf-aeb0-e5f9ed4b00a8", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3705", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3ltep7d743t2m", "content": "", "creation_timestamp": "2025-07-07T11:39:07.129625Z"}, {"uuid": "b5befa5e-a2e6-4167-87c2-3b7affc9f95f", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3757", "type": "seen", "source": "https://bsky.app/profile/getpokemon7.bsky.social/post/3lpimsl4wmc2k", "content": "", "creation_timestamp": "2025-05-19T03:26:04.841074Z"}, {"uuid": "78a861ae-6b5a-405c-bd54-395ac8b2c449", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3777", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lteq4nae6w2k", "content": "", "creation_timestamp": "2025-07-07T11:55:30.800279Z"}, {"uuid": "f383f308-69e4-45b7-a68b-b6eeb438e7a5", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3702", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lt2zfy7fdv2m", "content": "", "creation_timestamp": "2025-07-03T15:15:10.504381Z"}, {"uuid": "49816f00-4ba5-4896-9d0c-d57575653137", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37899", "type": "seen", "source": "https://bsky.app/profile/eicker.bsky.social/post/3lqacpa3jzo2v", "content": "", "creation_timestamp": "2025-05-28T13:29:08.206358Z"}, {"uuid": "00af8dfb-ac25-450f-9339-cf9a34096da3", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "cve-2025-37899", "type": "seen", "source": "https://bsky.app/profile/bluesky.awakari.com/post/3lqacssnm2a2s", "content": "", "creation_timestamp": "2025-05-28T13:31:08.486110Z"}, {"uuid": "3c34b54a-8bd0-43f0-9430-c369e6b04217", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "cve-2025-37899", "type": "seen", "source": "https://bsky.app/profile/bluesky.awakari.com/post/3lqacumd4ty2e", "content": "", "creation_timestamp": "2025-05-28T13:32:09.248236Z"}, {"uuid": "9fc0cff3-1943-4096-ab12-3c0f61422a6d", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3773", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lsjklurn4h2m", "content": "", "creation_timestamp": "2025-06-26T16:34:46.533770Z"}, {"uuid": "9f9b3f4d-8027-4654-b4e8-b513f666053b", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37992", "type": "seen", "source": "https://bsky.app/profile/2rZiKKbOU3nTafniR2qMMSE0gwZ.activitypub.awakari.com.ap.brid.gy/post/3lq3i3ev3pjy2", "content": "", "creation_timestamp": "2025-05-26T15:23:16.121831Z"}, {"uuid": "e8edfe3d-73a6-4375-a58b-77c0c26eeac3", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "cve-2025-37899", "type": "seen", "source": "https://bsky.app/profile/bluesky.awakari.com/post/3lqadj67mq42g", "content": "", "creation_timestamp": "2025-05-28T13:43:39.233544Z"}, {"uuid": "44e60563-fbb4-43ea-b8cc-48b3d99510ad", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37899", "type": "seen", "source": "https://bsky.app/profile/linux.activitypub.awakari.com.ap.brid.gy/post/3lqadjfclyeu2", "content": "", "creation_timestamp": "2025-05-28T13:44:31.767466Z"}, {"uuid": "d8c38d55-d20f-4520-8d98-bbed7ab6d898", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3755", "type": "seen", "source": "https://bsky.app/profile/pigondrugs.bsky.social/post/3lqq3o5hcab2b", "content": "", "creation_timestamp": "2025-06-03T20:05:51.972484Z"}, {"uuid": "5397b0f8-3db1-4fc3-9bf6-fbb17715f8a7", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3769", "type": "seen", "source": "https://bsky.app/profile/2rZiKKbOU3nTafniR2qMMSE0gwZ.activitypub.awakari.com.ap.brid.gy/post/3lp4xf6b5fmv2", "content": "", "creation_timestamp": "2025-05-14T12:04:01.457194Z"}, {"uuid": "67877c3c-7020-4b84-bfac-36ceb920c653", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3769", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lp52pfhsjf2w", "content": "", "creation_timestamp": "2025-05-14T13:02:54.045615Z"}, {"uuid": "0f1c7499-627e-4043-bba7-1de3529b29b2", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3742", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lp6wrhl54a2o", "content": "", "creation_timestamp": "2025-05-15T06:57:49.373226Z"}, {"uuid": "b64f225d-0e03-41f5-9627-fd5b1e0368ae", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37093", "type": "seen", "source": "https://bsky.app/profile/redteamnews.bsky.social/post/3lqq6xkbwed2h", "content": "", "creation_timestamp": "2025-06-03T21:04:48.395442Z"}, {"uuid": "6b12699a-84b8-4962-a943-8944fc1ed5e2", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37093", "type": "seen", "source": "https://bsky.app/profile/getpokemon7.bsky.social/post/3lqq74o6k5c2d", "content": "", "creation_timestamp": "2025-06-03T21:07:40.279179Z"}, {"uuid": "ffae0a57-da54-42b4-828e-22f211a6080c", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37093", "type": "seen", "source": "https://bsky.app/profile/2rZiKKbOU3nTafniR2qMMSE0gwZ.activitypub.awakari.com.ap.brid.gy/post/3lqu7kc4ckjv2", "content": "", "creation_timestamp": "2025-06-05T11:28:48.619272Z"}, {"uuid": "de0f320f-b4c0-4af8-a832-3b53cd8ead8c", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37899", "type": "seen", "source": "https://bsky.app/profile/flexghost.mastodon.social.ap.brid.gy/post/3lqamg7ixkap2", "content": "", "creation_timestamp": "2025-05-28T16:23:13.711551Z"}, {"uuid": "b8504169-1025-428e-a7e5-1c3d2c837770", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37126", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lyykfxupro2o", "content": "", "creation_timestamp": "2025-09-17T00:12:34.273692Z"}, {"uuid": "b7cc941c-f939-457c-8092-f69f9d4c8ef1", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3753", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lu6tiqqzcx2w", "content": "", "creation_timestamp": "2025-07-17T21:05:11.531963Z"}, {"uuid": "b4b84d2d-b454-4614-ac81-0081773c4d61", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37107", "type": "seen", "source": "http://www.zerodayinitiative.com/advisories/ZDI-25-614/", "content": "", "creation_timestamp": "2025-07-17T03:00:00.000000Z"}, {"uuid": "a70bdbfa-b147-4709-b638-54efff3a78eb", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37106", "type": "seen", "source": "http://www.zerodayinitiative.com/advisories/ZDI-25-613/", "content": "", "creation_timestamp": "2025-07-17T03:00:00.000000Z"}, {"uuid": "cad8a122-0db8-4a25-b861-cb069d4bed17", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37105", "type": "seen", "source": "http://www.zerodayinitiative.com/advisories/ZDI-25-612/", "content": "", "creation_timestamp": "2025-07-17T03:00:00.000000Z"}, {"uuid": "dd39e60f-8349-4b56-bbf5-815f3c709393", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3740", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lu7tev2xxm2j", "content": "", "creation_timestamp": "2025-07-18T06:35:41.506580Z"}, {"uuid": "6f2f5039-0171-4108-bca0-c69fc2c2dac7", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37729", "type": "seen", "source": "https://bsky.app/profile/infosec.skyfleet.blue/post/3m34rk7557r2f", "content": "", "creation_timestamp": "2025-10-14T03:21:14.940470Z"}, {"uuid": "10be522f-9b32-4b43-8ce8-48f4e7e1bc49", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37103", "type": "seen", "source": "https://thehackernews.com/2025/07/hard-coded-credentials-found-in-hpe.html", "content": "", "creation_timestamp": "2025-07-21T01:25:00.000000Z"}, {"uuid": "35ff3cc1-adec-4e08-b0cb-453d6fd22454", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37729", "type": "seen", "source": "https://bsky.app/profile/getpokemon7.bsky.social/post/3m3b4pwbcns2j", "content": "", "creation_timestamp": "2025-10-15T20:51:56.938183Z"}, {"uuid": "af669b16-4299-4fd1-9888-7f73228d4d2d", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37103", "type": "seen", "source": "https://bsky.app/profile/it-connect.bsky.social/post/3luiaz3wf4w2e", "content": "", "creation_timestamp": "2025-07-21T15:00:57.540534Z"}, {"uuid": "c3ee880b-9ab4-4573-a664-623d83c73110", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37103", "type": "seen", "source": "https://bsky.app/profile/securityrss.bsky.social/post/3luig7dof2o2e", "content": "", "creation_timestamp": "2025-07-21T16:33:55.151208Z"}, {"uuid": "d6d3c5a1-549a-4478-a734-3804f3ebf40a", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37103", "type": "seen", "source": "https://infosec.exchange/users/edwardk/statuses/114892234059244634", "content": "", "creation_timestamp": "2025-07-21T16:46:04.793539Z"}, {"uuid": "29383542-ff0e-47df-9ce1-5054edeae940", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37102", "type": "seen", "source": "https://infosec.exchange/users/edwardk/statuses/114892234059244634", "content": "", "creation_timestamp": "2025-07-21T16:46:04.906760Z"}, {"uuid": "96abe6e9-5d0e-48c7-b320-59c3295472ef", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37103", "type": "seen", "source": "https://threatintel.cc/2025/07/21/cve-remote-access-risk-in.html", "content": "", "creation_timestamp": "2025-07-21T14:46:10.000000Z"}, {"uuid": "656515d1-0171-4edd-afbd-b674d7e6ab19", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37102", "type": "seen", "source": "https://threatintel.cc/2025/07/21/cve-remote-access-risk-in.html", "content": "", "creation_timestamp": "2025-07-21T14:46:10.000000Z"}, {"uuid": "ca523c4a-86a6-4d93-bb4f-53250e6f5bd9", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37103", "type": "seen", "source": "https://bsky.app/profile/calimegai.bsky.social/post/3lujtclkxux2y", "content": "", "creation_timestamp": "2025-07-22T06:01:02.906156Z"}, {"uuid": "2c150e3e-4eff-4c05-9fd7-26b790a7b940", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37103", "type": "seen", "source": "https://bsky.app/profile/nimblenerd.social/post/3luk4sqq25i2h", "content": "", "creation_timestamp": "2025-07-22T08:51:37.585234Z"}, {"uuid": "bb395761-3cb2-450e-849c-469336fa2519", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37103", "type": "seen", "source": "https://bsky.app/profile/cyberhub.blog/post/3lumtia6yfd2q", "content": "", "creation_timestamp": "2025-07-23T10:42:10.444943Z"}, {"uuid": "6991d136-e9d1-4061-b790-0ed0b5539c1e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37735", "type": "seen", "source": "https://bsky.app/profile/getpokemon7.bsky.social/post/3m5f34ppjrk2m", "content": "", "creation_timestamp": "2025-11-11T21:24:21.845919Z"}, {"uuid": "00f3ed39-edc6-471f-9f0e-56c756e31429", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37947", "type": "seen", "source": "https://bsky.app/profile/crowdcyber.bsky.social/post/3m2q64vwcmc2e", "content": "", "creation_timestamp": "2025-10-09T03:01:50.731510Z"}, {"uuid": "5e5654ed-ce3f-461f-b221-7e5defea6eb5", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37890", "type": "seen", "source": "https://bsky.app/profile/bluesky.awakari.com/post/3lv7odgalz72y", "content": "", "creation_timestamp": "2025-07-30T22:30:35.391955Z"}, {"uuid": "46631aeb-5987-4df9-8741-362a911e139e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37890", "type": "seen", "source": "https://bsky.app/profile/bluesky.awakari.com/post/3lv7odpxww32i", "content": "", "creation_timestamp": "2025-07-30T22:30:45.481635Z"}, {"uuid": "b0a09f89-ad0f-4cbf-9e2c-fe41490bdb55", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37890", "type": "seen", "source": "https://bsky.app/profile/Ubuntu.activitypub.awakari.com.ap.brid.gy/post/3lv7odyghmbs2", "content": "", "creation_timestamp": "2025-07-30T22:30:59.170592Z"}, {"uuid": "ae2b1867-0956-4b10-8f3b-3c2885d5c54a", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37890", "type": "seen", "source": "https://bsky.app/profile/pmloik.bsky.social/post/3lva3km4r5v2t", "content": "", "creation_timestamp": "2025-07-31T02:27:15.754091Z"}, {"uuid": "ac79ff03-3f04-436c-8c1d-aeb34658d32d", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3717", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3m5fcdijbfu2w", "content": "", "creation_timestamp": "2025-11-11T23:33:24.302684Z"}, {"uuid": "f63e8b55-502a-406b-b5ea-be6fe1426e0b", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37797", "type": "seen", "source": "https://bsky.app/profile/ferramentaslinux.bsky.social/post/3lvdxbpv56k2f", "content": "", "creation_timestamp": "2025-08-01T15:21:23.639601Z"}, {"uuid": "36e52985-759d-4fd1-81e8-ff84f0018ec9", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3776", "type": "seen", "source": "https://bsky.app/profile/beikokucyber.bsky.social/post/3lvjlbybrsy2p", "content": "", "creation_timestamp": "2025-08-03T21:03:05.551729Z"}, {"uuid": "6bf97e79-380c-4ddb-8e71-8330a339171e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37899", "type": "seen", "source": "https://bsky.app/profile/beikokucyber.bsky.social/post/3lvjlbydzqf2n", "content": "", "creation_timestamp": "2025-08-03T21:03:06.249516Z"}, {"uuid": "29703db5-863e-4f9e-b856-b75e50e74751", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37734", "type": "seen", "source": "https://bsky.app/profile/infosec.skyfleet.blue/post/3m5i4kv4qy22s", "content": "", "creation_timestamp": "2025-11-13T02:28:09.154012Z"}, {"uuid": "11e1b2de-98a3-4ec3-b32f-0f8b53864216", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37797", "type": "seen", "source": "https://bsky.app/profile/ferramentaslinux.bsky.social/post/3lvl7sdcczs2i", "content": "", "creation_timestamp": "2025-08-04T12:42:29.208610Z"}, {"uuid": "2381081d-aabe-49f2-b107-06d9ab094978", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37797", "type": "seen", "source": "https://bsky.app/profile/ferramentaslinux.bsky.social/post/3lvlahnw5xk2i", "content": "", "creation_timestamp": "2025-08-04T12:54:24.363198Z"}, {"uuid": "7d3a35a8-ed63-47ee-b6ff-16d4f604d911", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37797", "type": "seen", "source": "https://bsky.app/profile/ferramentaslinux.bsky.social/post/3lvlzyzuggs23", "content": "", "creation_timestamp": "2025-08-04T20:31:32.715376Z"}, {"uuid": "83e177f6-5c5d-4e2c-877e-7505f231438f", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37752", "type": "seen", "source": "https://bsky.app/profile/ferramentaslinux.bsky.social/post/3lvlzyzuggs23", "content": "", "creation_timestamp": "2025-08-04T20:31:32.796892Z"}, {"uuid": "126cf966-3b18-4c55-94a1-0c00621fc6a0", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37797", "type": "seen", "source": "https://bsky.app/profile/ferramentaslinux.bsky.social/post/3lvnqtihptc2f", "content": "", "creation_timestamp": "2025-08-05T12:52:41.617140Z"}, {"uuid": "a1d4facb-bd47-43f5-a071-2dafdf83858a", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37752", "type": "seen", "source": "https://bsky.app/profile/ferramentaslinux.bsky.social/post/3lvnqtihptc2f", "content": "", "creation_timestamp": "2025-08-05T12:52:41.740014Z"}, {"uuid": "56d5e7d2-c15d-4981-9f61-fa0450091e97", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3705", "type": "seen", "source": "MISP/853ff921-86fb-463b-bc2a-2860bf336b81", "content": "", "creation_timestamp": "2025-08-06T01:04:20.000000Z"}, {"uuid": "38911a88-6488-44c7-a844-0265dff27c8a", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37899", "type": "seen", "source": "MISP/1413a78e-c0b3-4092-97e7-909fb9773448", "content": "", "creation_timestamp": "2025-08-06T13:54:19.000000Z"}, {"uuid": "534cc142-7182-4a8b-8be5-2a64802b1e12", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37778", "type": "seen", "source": "MISP/1413a78e-c0b3-4092-97e7-909fb9773448", "content": "", "creation_timestamp": "2025-08-06T13:54:19.000000Z"}, {"uuid": "f55bf8be-7d47-4ffc-8a32-b3925b8ccc09", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3770", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lvs2x7d36e2e", "content": "", "creation_timestamp": "2025-08-07T06:04:19.881684Z"}, {"uuid": "d70d9c31-6a15-4e79-925e-fdb61d94c09e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37735", "type": "seen", "source": "https://bsky.app/profile/securitylab-jp.bsky.social/post/3m5finm4xpc2w", "content": "", "creation_timestamp": "2025-11-12T01:26:30.003538Z"}, {"uuid": "44d21d8b-6ba8-4396-b6f3-9c4daa21990a", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3720", "type": "seen", "source": "https://bsky.app/profile/ferramentaslinux.bsky.social/post/3m3sfjqnmlc2b", "content": "", "creation_timestamp": "2025-10-22T17:44:53.153971Z"}, {"uuid": "eb5ef4da-782d-4ccc-a61e-74b8e44a59c7", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3718", "type": "seen", "source": "https://infosec.exchange/users/cR0w/statuses/115333195472561898", "content": "", "creation_timestamp": "2025-10-07T13:48:23.320566Z"}, {"uuid": "f61b739e-8ecb-49c4-9cb8-382d17cea1e7", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3719", "type": "seen", "source": "https://infosec.exchange/users/cR0w/statuses/115333195472561898", "content": "", "creation_timestamp": "2025-10-07T13:48:23.411633Z"}, {"uuid": "9b4b1079-b227-4505-81ad-be410ba37206", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3764", "type": "seen", "source": "MISP/abd2a650-703d-4a2f-9f73-3051c1672e27", "content": "", "creation_timestamp": "2025-08-09T13:26:56.000000Z"}, {"uuid": "13fe0111-1e98-4d47-ba89-62fc5dc050d2", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3765", "type": "seen", "source": "MISP/abd2a650-703d-4a2f-9f73-3051c1672e27", "content": "", "creation_timestamp": "2025-08-09T13:26:56.000000Z"}, {"uuid": "92fa6c80-e0d9-4102-8127-40a0dd89133c", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3784", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3m6lrjnoccj26", "content": "", "creation_timestamp": "2025-11-27T06:46:27.250069Z"}, {"uuid": "0038dadd-7762-4d71-9bed-87ac43428b97", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37899", "type": "seen", "source": "https://bsky.app/profile/homelabs.bsky.social/post/3lw45wp6fs22x", "content": "", "creation_timestamp": "2025-08-11T06:24:21.009869Z"}, {"uuid": "9934e606-b23a-4493-a5d9-20584971c166", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3764", "type": "seen", "source": "MISP/abd2a650-703d-4a2f-9f73-3051c1672e27", "content": "", "creation_timestamp": "2025-08-11T18:47:39.000000Z"}, {"uuid": "dd888556-6454-4bd2-8651-514e521925fe", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3765", "type": "seen", "source": "MISP/abd2a650-703d-4a2f-9f73-3051c1672e27", "content": "", "creation_timestamp": "2025-08-11T18:47:39.000000Z"}, {"uuid": "5d505de2-88bd-4918-9c69-a0030234d1e5", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37947", "type": "seen", "source": "https://bsky.app/profile/Ubuntu.activitypub.awakari.com.ap.brid.gy/post/3m2ra4sgjieq2", "content": "", "creation_timestamp": "2025-10-09T13:11:12.067325Z"}, {"uuid": "854742a4-affb-4057-a0cf-e779b72f16f5", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37161", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3m5wqttlvnq2s", "content": "", "creation_timestamp": "2025-11-18T22:08:20.782918Z"}, {"uuid": "d1579911-81d5-43b1-976e-1eb102cd7da5", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37162", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3m5wr4rzu2i2s", "content": "", "creation_timestamp": "2025-11-18T22:13:21.137352Z"}, {"uuid": "ed4ec295-f1f2-4122-81a5-0104959e0665", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37899", "type": "seen", "source": "MISP/1413a78e-c0b3-4092-97e7-909fb9773448", "content": "", "creation_timestamp": "2025-08-14T11:44:21.000000Z"}, {"uuid": "03c398b9-0a50-4eb7-ab2a-1481c8a714b8", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37778", "type": "seen", "source": "MISP/1413a78e-c0b3-4092-97e7-909fb9773448", "content": "", "creation_timestamp": "2025-08-14T11:44:21.000000Z"}, {"uuid": "87f778b5-33e2-4381-9496-4be6ca7b20e2", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37729", "type": "seen", "source": "https://bsky.app/profile/thedailytechfeed.com/post/3m37ogrbh7s2k", "content": "", "creation_timestamp": "2025-10-15T07:03:44.900124Z"}, {"uuid": "427569a9-9a61-474b-8b51-874d1ff5a4f2", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37752", "type": "seen", "source": "https://bsky.app/profile/0xor0ne.bsky.social/post/3lwloyqsfhs2r", "content": "", "creation_timestamp": "2025-08-17T10:39:42.497881Z"}, {"uuid": "7ca10cbf-f895-4b2b-a173-91100c4e55fe", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37752", "type": "seen", "source": "https://bsky.app/profile/pmloik.bsky.social/post/3lwndvvkc6g2y", "content": "", "creation_timestamp": "2025-08-18T02:26:33.007237Z"}, {"uuid": "5ce0e1a8-0713-4dbd-bc2f-2124a345906c", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37103", "type": "seen", "source": "https://bsky.app/profile/undercode.bsky.social/post/3lwnmcce3eq2w", "content": "", "creation_timestamp": "2025-08-18T04:56:39.386965Z"}, {"uuid": "259f28c3-45f8-4cc2-8151-de2ba1eb7efb", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37736", "type": "seen", "source": "https://bsky.app/profile/infosec.skyfleet.blue/post/3m4p5ar72kl2s", "content": "", "creation_timestamp": "2025-11-03T04:03:50.050343Z"}, {"uuid": "a6202f46-dcba-480e-bd72-9f851ddc3dc6", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "cve-2025-37736", "type": "seen", "source": "https://bsky.app/profile/jos1264.social.skynetcloud.site.ap.brid.gy/post/3m4pcn3a5qyk2", "content": "", "creation_timestamp": "2025-11-03T05:41:03.666501Z"}, {"uuid": "3f39658b-8b00-46ea-bd9e-ae6bffb32d59", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37752", "type": "seen", "source": "https://bsky.app/profile/pmloik.bsky.social/post/3lwseanwnc52x", "content": "", "creation_timestamp": "2025-08-20T02:15:52.147715Z"}, {"uuid": "26281a01-f1ae-4f5c-b199-c93c588014f4", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37752", "type": "seen", "source": "https://bsky.app/profile/pmloik.bsky.social/post/3lwuuoepmx525", "content": "", "creation_timestamp": "2025-08-21T02:15:11.451944Z"}, {"uuid": "41fa07c2-d701-4044-8b05-1c802c653976", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3705", "type": "seen", "source": "MISP/853ff921-86fb-463b-bc2a-2860bf336b81", "content": "", "creation_timestamp": "2025-08-21T10:03:55.000000Z"}, {"uuid": "d1b51c5a-8cb6-48ed-b64a-78edfb562c89", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37728", "type": "seen", "source": "https://bsky.app/profile/thedailytechfeed.com/post/3m2oaintohc2g", "content": "", "creation_timestamp": "2025-10-08T08:39:07.260501Z"}, {"uuid": "9aa571c6-bdfe-4db3-a8f0-cae4868024c4", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37752", "type": "seen", "source": "https://bsky.app/profile/pmloik.bsky.social/post/3lwxf6nvpu22v", "content": "", "creation_timestamp": "2025-08-22T02:15:57.528054Z"}, {"uuid": "c76a8f1d-90d4-435f-bf0b-d3c8a2babb55", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37736", "type": "seen", "source": "https://bsky.app/profile/securitylab-jp.bsky.social/post/3m4tv7vravk2d", "content": "", "creation_timestamp": "2025-11-05T01:23:36.164658Z"}, {"uuid": "25d779a4-f849-4ab7-bace-db5bccc47585", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37752", "type": "seen", "source": "https://bsky.app/profile/pmloik.bsky.social/post/3lwzvi26y5o2r", "content": "", "creation_timestamp": "2025-08-23T02:12:51.694351Z"}, {"uuid": "26ceea57-f231-4465-9365-095ca721b315", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37734", "type": "seen", "source": "https://bsky.app/profile/thedailytechfeed.com/post/3m5m2kn6rre2t", "content": "", "creation_timestamp": "2025-11-14T16:02:51.901945Z"}, {"uuid": "c1b8f486-8096-43a2-a1fd-5c388fa4f16f", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37752", "type": "seen", "source": "https://bsky.app/profile/pmloik.bsky.social/post/3lx4gjn5bha2s", "content": "", "creation_timestamp": "2025-08-24T02:23:18.401483Z"}, {"uuid": "e1069370-6f75-41e2-aac8-13f566ff5a11", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37736", "type": "seen", "source": "https://bsky.app/profile/getpokemon7.bsky.social/post/3m4u3jouk5c2g", "content": "", "creation_timestamp": "2025-11-05T03:16:24.558790Z"}, {"uuid": "b10c4308-12ee-4f0c-a02e-56837f3aaa51", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37735", "type": "seen", "source": "https://bsky.app/profile/thedailytechfeed.com/post/3m5ehil7icv2f", "content": "", "creation_timestamp": "2025-11-11T15:33:04.786287Z"}, {"uuid": "1eabcc8f-46dc-4d04-acad-123251ce5f1a", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37752", "type": "seen", "source": "https://bsky.app/profile/ferramentaslinux.bsky.social/post/3lx5xkv2d3k2c", "content": "", "creation_timestamp": "2025-08-24T17:00:56.488963Z"}, {"uuid": "d591b4f3-ccdf-494c-9bfb-2e3a6aae8093", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37899", "type": "seen", "source": "https://bsky.app/profile/linkersec.bsky.social/post/3m5ujdkjwuk25", "content": "", "creation_timestamp": "2025-11-18T00:48:41.526529Z"}, {"uuid": "3a195580-1c65-4121-83db-854879d8a764", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37736", "type": "seen", "source": "https://bsky.app/profile/jos1264.social.skynetcloud.site.ap.brid.gy/post/3m53a26kyvnb2", "content": "", "creation_timestamp": "2025-11-07T23:27:37.789493Z"}, {"uuid": "a821d0af-a387-4749-a38e-bfe0bf861be1", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37736", "type": "seen", "source": "https://bsky.app/profile/jos1264.social.skynetcloud.site.ap.brid.gy/post/3m53fd3br6xc2", "content": "", "creation_timestamp": "2025-11-08T01:01:22.963461Z"}, {"uuid": "be8b0982-a112-43ea-8ff7-2da2bcf1ac35", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37736", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3m53kzxk5qf2n", "content": "", "creation_timestamp": "2025-11-08T02:42:31.120704Z"}, {"uuid": "eb3320b9-8f91-4aa2-bfe9-790117c5bb8c", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37947", "type": "seen", "source": "https://bsky.app/profile/r-netsec-bot.bsky.social/post/3m2p2pw33242u", "content": "", "creation_timestamp": "2025-10-08T16:28:23.733776Z"}, {"uuid": "da4805d4-eef6-4f82-96b4-f7485ab78f74", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37992", "type": "seen", "source": "https://gist.github.com/Darkcrai86/7af208503f0b241893248339e3c341bc", "content": "", "creation_timestamp": "2025-08-28T17:44:02.000000Z"}, {"uuid": "53ff45b0-2eb3-4e40-abb8-0d72ef8eb6c2", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37766", "type": "seen", "source": "https://gist.github.com/Darkcrai86/ff359fcfac284f38ca78751ddb9767e2", "content": "", "creation_timestamp": "2025-08-28T17:43:45.000000Z"}, {"uuid": "299cfcc1-37d4-499b-8b9a-571dffe0cafc", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37947", "type": "seen", "source": "https://bsky.app/profile/r-netsec.bsky.social/post/3m2p3e5hq2v2u", "content": "", "creation_timestamp": "2025-10-08T16:39:32.668783Z"}, {"uuid": "d7cbf0a2-1475-435e-9332-b423722527ab", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37752", "type": "seen", "source": "https://gist.github.com/Darkcrai86/9146c6003145a6dd1c7230cf7d607ea3", "content": "", "creation_timestamp": "2025-08-29T11:28:19.000000Z"}, {"uuid": "6af460c5-5f70-48aa-aada-3a508f44b187", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37752", "type": "seen", "source": "https://gist.github.com/Darkcrai86/c2e363fe546c0d30b06f5e312bb6e1bb", "content": "", "creation_timestamp": "2025-08-29T11:28:04.000000Z"}, {"uuid": "5d2108b5-a65c-447e-94c0-8982bad8ee1e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37752", "type": "seen", "source": "https://gist.github.com/Darkcrai86/367664d2a94230671ccc0ebf34735cf2", "content": "", "creation_timestamp": "2025-08-29T11:27:50.000000Z"}, {"uuid": "bd23ed34-8f8f-43fb-9398-33b1415cfb75", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37947", "type": "seen", "source": "https://bsky.app/profile/oversecurity.net.web.brid.gy/post/3m2paiks7f3z2", "content": "", "creation_timestamp": "2025-10-08T18:11:36.522665Z"}, {"uuid": "2d68c74f-f9be-46dd-9ddf-01530a1a92f2", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37103", "type": "seen", "source": "MISP/2bceffac-02c3-4c54-a709-6e253b38ec76", "content": "", "creation_timestamp": "2025-09-09T20:56:43.000000Z"}, {"uuid": "9aa3a5e1-b5b1-44a3-a1e0-3ec9b8d47460", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37947", "type": "seen", "source": "https://gist.github.com/Darkcrai86/45d158611b4db1aace5cbd8bd2963b4d", "content": "", "creation_timestamp": "2025-09-02T09:21:42.000000Z"}, {"uuid": "bffb6f59-1b99-470a-b0ce-0fe6bf82001b", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37105", "type": "seen", "source": "MISP/2bceffac-02c3-4c54-a709-6e253b38ec76", "content": "", "creation_timestamp": "2025-09-09T20:56:46.000000Z"}, {"uuid": "761d2e1c-9426-443a-9fe1-a7b82d473764", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37947", "type": "seen", "source": "https://bsky.app/profile/linkersec.bsky.social/post/3m3vn3zof5s2h", "content": "", "creation_timestamp": "2025-10-24T00:38:20.120857Z"}, {"uuid": "8e12e720-1618-48eb-b8db-e9f0b4060196", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37756", "type": "seen", "source": "https://bsky.app/profile/buherator.bsky.social/post/3lxxdrqsjg72k", "content": "", "creation_timestamp": "2025-09-03T19:16:02.019115Z"}, {"uuid": "f2fd06f0-ae37-42ee-b164-514b44c5d598", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37899", "type": "seen", "source": "https://bsky.app/profile/bluesky.awakari.com/post/3lxxzxxzk6e26", "content": "", "creation_timestamp": "2025-09-04T01:53:13.686959Z"}, {"uuid": "33faebb3-720e-422f-9937-ae15ba70a8c0", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37899", "type": "seen", "source": "https://bsky.app/profile/linux.activitypub.awakari.com.ap.brid.gy/post/3lxxzy3h64b22", "content": "", "creation_timestamp": "2025-09-04T01:53:27.507946Z"}, {"uuid": "21b0a064-78ba-4e21-be29-ed7bc584afd6", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "cve-2025-37899", "type": "seen", "source": "https://bsky.app/profile/LLMs.activitypub.awakari.com.ap.brid.gy/post/3lxy2lt4afs22", "content": "", "creation_timestamp": "2025-09-04T02:04:46.598255Z"}, {"uuid": "71c723cb-a1d2-43d1-939a-2449093478e4", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37123", "type": "seen", "source": "https://bsky.app/profile/getpokemon7.bsky.social/post/3lza2w2kn622t", "content": "", "creation_timestamp": "2025-09-19T23:56:33.415809Z"}, {"uuid": "d699366f-9f42-4fbc-bfc5-1e6cce530758", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "cve-2025-37899", "type": "seen", "source": "https://bsky.app/profile/bluesky.awakari.com/post/3lxyfd33eai2b", "content": "", "creation_timestamp": "2025-09-04T05:16:16.824026Z"}, {"uuid": "c9a73366-6a5c-47cd-8e5e-e322ab2588d8", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "cve-2025-37899", "type": "seen", "source": "https://bsky.app/profile/bluesky.awakari.com/post/3lxyfd5iurv2m", "content": "", "creation_timestamp": "2025-09-04T05:16:19.994743Z"}, {"uuid": "04b8cdc4-95a2-42ce-b85f-45292e5bdca0", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37899", "type": "seen", "source": "https://bsky.app/profile/ytroncal.bsky.social/post/3lxyhqd7pxk2e", "content": "", "creation_timestamp": "2025-09-04T05:59:36.748101Z"}, {"uuid": "34661a29-e11a-4460-8e7f-0bd25cdabdac", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "e92402ac-b04a-4e73-ad0b-3c8344ca18bd", "vulnerability": "CVE-2025-37899", "type": "exploited", "source": "https://www.enisa.europa.eu/sites/default/files/2025-10/ENISA%20Threat%20Landscape%202025.pdf", "content": "", "creation_timestamp": "2025-10-08T20:07:17.469416Z"}, {"uuid": "b36246d8-92ef-4f2a-955a-ae395a66efbc", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "cve-2025-37899", "type": "seen", "source": "https://bsky.app/profile/appsecfeed.bsky.social/post/3lxz2fzjd2q2p", "content": "", "creation_timestamp": "2025-09-04T11:33:45.227672Z"}, {"uuid": "977a2b05-7695-465b-ac19-5454c958cdba", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3784", "type": "seen", "source": "https://www.cisa.gov/news-events/ics-advisories/icsa-25-338-01", "content": "", "creation_timestamp": "2025-12-04T11:00:00.000000Z"}, {"uuid": "908f2f50-1f68-4714-8129-ee7a7a5a30bc", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37882", "type": "seen", "source": "https://bsky.app/profile/o2cloud.bsky.social/post/3mfccsjc2s322", "content": "", "creation_timestamp": "2026-02-20T14:25:22.254685Z"}, {"uuid": "750aa0f0-a109-4ad6-b3f2-08d4df675121", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37861", "type": "seen", "source": "https://bsky.app/profile/o2cloud.bsky.social/post/3mgff4w63em24", "content": "", "creation_timestamp": "2026-03-06T13:10:09.953021Z"}, {"uuid": "3222864e-9edc-4daf-bbe3-8d685d36041f", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37882", "type": "seen", "source": "https://bsky.app/profile/o2cloud.bsky.social/post/3mgff4w63em24", "content": "", "creation_timestamp": "2026-03-06T13:10:10.047966Z"}, {"uuid": "eb302262-f6d2-4a44-8912-700fac741353", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37164", "type": "seen", "source": "https://bsky.app/profile/getpokemon7.bsky.social/post/3meuh5tcgbc2w", "content": "", "creation_timestamp": "2026-02-15T02:06:03.296721Z"}, {"uuid": "9a1ccb07-3045-4a34-b2f0-198ca39251fc", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37164", "type": "seen", "source": "https://infosec.exchange/users/cR0w/statuses/115730294700387877", "content": "", "creation_timestamp": "2025-12-16T16:55:55.709502Z"}, {"uuid": "06f3843d-dcee-4a5b-b3ac-6c1dda6c67e1", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37164", "type": "seen", "source": "https://infosec.exchange/users/vuldb/statuses/115735540741211292", "content": "", "creation_timestamp": "2025-12-17T15:10:03.600728Z"}, {"uuid": "e3b7e23a-fb71-4802-aa92-2f489c0a1822", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37164", "type": "seen", "source": "https://poliverso.org/objects/0477a01e-12f62d7c-077c63f4f1d9f417", "content": "", "creation_timestamp": "2025-12-18T09:14:56.895409Z"}, {"uuid": "4d55d04a-e0c3-4d89-8c6b-8dfba0620b37", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37164", "type": "seen", "source": "https://bsky.app/profile/infosec.skyfleet.blue/post/3maatpxwei72x", "content": "", "creation_timestamp": "2025-12-18T09:16:52.825780Z"}, {"uuid": "bebc17f6-a6bc-4112-b154-f59a482dfb9e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37164", "type": "seen", "source": "https://bsky.app/profile/bleepingcomputer.com/post/3mab3j2kffa2y", "content": "", "creation_timestamp": "2025-12-18T11:36:11.353781Z"}, {"uuid": "a0478cc6-0183-492f-9d94-1ba136467b04", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37164", "type": "seen", "source": "https://bsky.app/profile/blackhatnews.tokyo/post/3mab3zhk66g2w", "content": "", "creation_timestamp": "2025-12-18T11:45:21.430095Z"}, {"uuid": "2f617aeb-0ed5-41fb-b9a5-71ae0a93d461", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "cve-2025-37164", "type": "seen", "source": "https://infosec.exchange/users/defendopsdiaries/statuses/115740409680221536", "content": "", "creation_timestamp": "2025-12-18T11:48:17.680171Z"}, {"uuid": "2f0d8b7a-62ed-411e-8e54-1fc737b2b71a", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37164", "type": "seen", "source": "https://bsky.app/profile/cybersentinel404.bsky.social/post/3mabh4x6eyt2y", "content": "", "creation_timestamp": "2025-12-18T15:04:09.811100Z"}, {"uuid": "e07ae073-f010-4b83-ac55-6dd3e835daf7", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37164", "type": "seen", "source": "https://bsky.app/profile/infosecbriefly.bsky.social/post/3mabhmnc4732o", "content": "", "creation_timestamp": "2025-12-18T15:12:56.460858Z"}, {"uuid": "4f117496-317f-4e5d-9205-f18f27bd2d57", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37164", "type": "seen", "source": "https://bsky.app/profile/blackhatnews.tokyo/post/3mabi6mkgo72m", "content": "", "creation_timestamp": "2025-12-18T15:22:59.292977Z"}, {"uuid": "8a69f935-dd7b-4eea-8b1f-4afee5ebc5c9", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37164", "type": "seen", "source": "https://thehackernews.com/2025/12/hpe-oneview-flaw-rated-cvss-100-allows.html", "content": "", "creation_timestamp": "2025-12-18T13:39:00.000000Z"}, {"uuid": "6589b3fc-596b-4a1b-b58b-56126c73c203", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37164", "type": "seen", "source": "https://bsky.app/profile/rapid7.com/post/3mabrvqeey22d", "content": "", "creation_timestamp": "2025-12-18T18:17:01.138118Z"}, {"uuid": "db87f2dd-69c5-48fd-981a-5e937f053483", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37164", "type": "seen", "source": "https://bsky.app/profile/securityrss.bsky.social/post/3mac6l6wcsn24", "content": "", "creation_timestamp": "2025-12-18T22:03:44.492280Z"}, {"uuid": "7f332693-0b9d-4cac-8334-6fb7da5b4487", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37164", "type": "seen", "source": "https://bsky.app/profile/pmloik.bsky.social/post/3macn2mdz322d", "content": "", "creation_timestamp": "2025-12-19T02:22:53.706143Z"}, {"uuid": "a3e05a1d-d8b9-4b8f-bec0-98f9dd8046b2", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37164", "type": "seen", "source": "https://infosec.exchange/users/offseq/statuses/115745315435788020", "content": "", "creation_timestamp": "2025-12-19T08:35:55.280302Z"}, {"uuid": "e6cbf8ba-3a4e-4089-b66a-a8807ba17ca5", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37164", "type": "seen", "source": "https://cyberplace.social/users/GossiTheDog/statuses/115745701289876342", "content": "", "creation_timestamp": "2025-12-19T10:14:09.369621Z"}, {"uuid": "6569cea5-4827-4751-86be-6c951c520dfb", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37164", "type": "seen", "source": "https://infosec.exchange/users/edwardk/statuses/115746327958380635", "content": "", "creation_timestamp": "2025-12-19T12:53:23.466485Z"}, {"uuid": "2ec6dc8f-2c27-4716-ada4-13e44811ab52", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37164", "type": "seen", "source": "https://bsky.app/profile/infosecbriefly.bsky.social/post/3madqnnpu4f2u", "content": "", "creation_timestamp": "2025-12-19T12:59:57.247404Z"}, {"uuid": "e30dcb80-2abc-45ff-86c4-b439c1aa861d", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37164", "type": "seen", "source": "https://bsky.app/profile/infosecbriefly.bsky.social/post/3madraxequt2o", "content": "", "creation_timestamp": "2025-12-19T13:10:41.237200Z"}, {"uuid": "84ccfc6d-1d2c-4cd1-8baa-d50b3a395cc5", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37164", "type": "seen", "source": "https://threatintel.cc/2025/12/19/hpe-oneview-vulnerable-to-remote.html", "content": "", "creation_timestamp": "2025-12-19T11:53:41.000000Z"}, {"uuid": "6613ae27-064e-49bf-8045-fff1c0142c66", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "cve-2025-37164", "type": "seen", "source": "https://cyberplace.social/users/GossiTheDog/statuses/115746866896615822", "content": "", "creation_timestamp": "2025-12-19T15:10:30.616528Z"}, {"uuid": "99539040-6c25-4a68-9ae2-9af81cf0acbe", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37164", "type": "seen", "source": "https://mastodon.social/ap/users/115426718704364579/statuses/115747042422772085", "content": "", "creation_timestamp": "2025-12-19T15:55:08.408516Z"}, {"uuid": "e2789b12-12d8-4edd-aae8-c994e06e700d", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37164", "type": "seen", "source": "https://bsky.app/profile/netsecio.bsky.social/post/3mae2ha7ry62z", "content": "", "creation_timestamp": "2025-12-19T15:55:15.626652Z"}, {"uuid": "71c20cda-97a9-4f1e-9661-79bacfc3bae6", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37164", "type": "seen", "source": "https://bsky.app/profile/thedailytechfeed.com/post/3maeazuesgn2y", "content": "", "creation_timestamp": "2025-12-19T17:53:04.943317Z"}, {"uuid": "915830a6-d246-44ed-857f-41ef32c79925", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37164", "type": "seen", "source": "https://bsky.app/profile/hack4career.com/post/3maedhzllql2q", "content": "", "creation_timestamp": "2025-12-19T18:36:46.456803Z"}, {"uuid": "17eb0d0c-39e3-4277-9d94-6228fc608310", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37164", "type": "confirmed", "source": "https://github.com/projectdiscovery/nuclei-templates/tree/main/http/cves/2025/CVE-2025-37164.yaml", "content": "", "creation_timestamp": "2025-12-19T16:39:28.000000Z"}, {"uuid": "18b14756-c412-4379-b84a-c2a609fba49c", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37164", "type": "seen", "source": "https://bsky.app/profile/beikokucyber.bsky.social/post/3mah44enans2d", "content": "", "creation_timestamp": "2025-12-20T21:03:00.463903Z"}, {"uuid": "55609f85-8eff-47e4-9a7d-2f39a77c5c24", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37164", "type": "seen", "source": "https://github.com/rapid7/metasploit-framework/blob/master/modules/exploits/linux/http/hpe_oneview_rce.rb", "content": "", "creation_timestamp": "2025-12-19T23:51:36.000000Z"}, {"uuid": "09ac3c8c-e7a1-4a94-b072-f479fa3de448", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37164", "type": "seen", "source": "https://bsky.app/profile/thedailytechfeed.com/post/3maqk5kesrc2z", "content": "", "creation_timestamp": "2025-12-24T15:08:07.337631Z"}, {"uuid": "d4d2dd78-11f4-49f0-9866-127db7ae3125", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37164", "type": "seen", "source": "https://bsky.app/profile/termsofsurrender.bsky.social/post/3maqn3b7ty62k", "content": "", "creation_timestamp": "2025-12-24T16:00:31.553008Z"}, {"uuid": "6c443c0b-89d2-4559-9c89-e5710925419d", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37164", "type": "seen", "source": "https://bsky.app/profile/PostgreSQL.activitypub.awakari.com.ap.brid.gy/post/3mazw4ilg6362", "content": "", "creation_timestamp": "2025-12-28T08:36:20.652886Z"}, {"uuid": "139a396f-c311-43ee-b047-e5452f6cfecc", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37164", "type": "seen", "source": "https://feedsin.space/feed/CISAKevBot/items/5922978", "content": "", "creation_timestamp": "2026-03-04T01:42:54.503043Z"}, {"uuid": "5b343778-03c2-498f-b0ca-17b23e33b005", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37164", "type": "seen", "source": "https://gist.github.com/a9v8i/1dba98ba0701159a1419ac7391479df3", "content": "", "creation_timestamp": "2026-01-04T06:08:25.000000Z"}, {"uuid": "dd9dab16-608e-4b67-beb1-206b2e4fdc46", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37164", "type": "seen", "source": "https://bsky.app/profile/tekfiend.bsky.social/post/3mbrvd3rslc2v", "content": "", "creation_timestamp": "2026-01-06T21:25:57.461255Z"}, {"uuid": "4f8d2846-5a75-4bd7-ae91-ef6fa5f1d974", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37164", "type": "seen", "source": "https://bsky.app/profile/pigondrugs.bsky.social/post/3mbub2k6ubk2a", "content": "", "creation_timestamp": "2026-01-07T20:01:14.543570Z"}, {"uuid": "c327e44d-3425-4ad6-b353-d02ba7f4165a", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37164", "type": "seen", "source": "https://bsky.app/profile/kitafox.bsky.social/post/3mbuojaxgqa23", "content": "", "creation_timestamp": "2026-01-08T00:02:05.368612Z"}, {"uuid": "b9f22f0b-caec-4a36-81ac-412c1b279dcb", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37164", "type": "seen", "source": "https://bsky.app/profile/infosecbriefly.bsky.social/post/3mbvcjl4yo62q", "content": "", "creation_timestamp": "2026-01-08T06:00:11.934566Z"}, {"uuid": "40004ede-34d9-4aaf-82f3-2efca9250ee8", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37164", "type": "seen", "source": "https://bsky.app/profile/anthonypjshaw.bsky.social/post/3mbvhdmfo6c2h", "content": "", "creation_timestamp": "2026-01-08T07:26:20.752531Z"}, {"uuid": "5657b541-cc5c-4892-9b31-d81b2de74048", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37164", "type": "seen", "source": "https://bsky.app/profile/infosecbriefly.bsky.social/post/3mbvt74nwnz2y", "content": "", "creation_timestamp": "2026-01-08T10:58:35.004863Z"}, {"uuid": "41ffda2a-661f-4df8-a388-04d94bbb4995", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37164", "type": "seen", "source": "https://bsky.app/profile/blackhatnews.tokyo/post/3mbvtwx2b7f26", "content": "", "creation_timestamp": "2026-01-08T11:11:52.977414Z"}, {"uuid": "06ef1b1c-f26e-4d37-8be2-7549017d1884", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37164", "type": "seen", "source": "https://bsky.app/profile/securityrss.bsky.social/post/3mbw5lbnuk42k", "content": "", "creation_timestamp": "2026-01-08T14:04:19.665370Z"}, {"uuid": "d5b1b843-1c34-42ed-a45b-f3c40e3ff7f1", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37164", "type": "seen", "source": "https://bsky.app/profile/helpnetsecurity.com/post/3mbwa4nulks2c", "content": "", "creation_timestamp": "2026-01-08T14:49:57.326567Z"}, {"uuid": "c7af7811-438b-4b9b-b231-43037a72ddc6", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37164", "type": "seen", "source": "https://infosec.exchange/users/DarkWebInformer/statuses/115860204501745807", "content": "", "creation_timestamp": "2026-01-08T15:33:41.897134Z"}, {"uuid": "d9c919ab-9eb6-427d-b772-8735636d82b4", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37164", "type": "seen", "source": "https://bsky.app/profile/2rZiKKbOU3nTafniR2qMMSE0gwZ.activitypub.awakari.com.ap.brid.gy/post/3mbwhw2bj4ro2", "content": "", "creation_timestamp": "2026-01-08T17:16:30.267522Z"}, {"uuid": "360236b5-97ef-49ee-a6ce-b25e998e49fb", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37164", "type": "seen", "source": "https://bsky.app/profile/infosec.skyfleet.blue/post/3mbwmnjxgeu2e", "content": "", "creation_timestamp": "2026-01-08T18:34:00.917794Z"}, {"uuid": "cf4c1c71-d64f-4856-b9fb-447ae1fc7e7b", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37164", "type": "seen", "source": "https://bsky.app/profile/beikokucyber.bsky.social/post/3mbwuxxtgq62d", "content": "", "creation_timestamp": "2026-01-08T21:03:11.892289Z"}, {"uuid": "c7f36413-e710-41bb-805e-293116106ae1", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37164", "type": "seen", "source": "https://bsky.app/profile/cybersentinel404.bsky.social/post/3mbx236sosz2r", "content": "", "creation_timestamp": "2026-01-08T22:34:17.658022Z"}, {"uuid": "6a2260ed-7dc3-4631-90b6-12158a482312", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37164", "type": "seen", "source": "https://www.darkreading.com/vulnerabilities-threats/maximum-severity-hpe-oneview-flaw-exploited", "content": "", "creation_timestamp": "2026-01-08T21:21:29.000000Z"}, {"uuid": "1b6f5412-dd5b-4e78-8f29-b79e059f7c1a", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37164", "type": "seen", "source": "https://bsky.app/profile/kitafox.bsky.social/post/3mbxcbetqxk2q", "content": "", "creation_timestamp": "2026-01-09T01:00:55.759908Z"}, {"uuid": "1ca52965-8fba-4490-827c-c5cf29a283c8", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37164", "type": "seen", "source": "https://bsky.app/profile/undercodenews.bsky.social/post/3mbxcozjqxc2z", "content": "", "creation_timestamp": "2026-01-09T01:08:33.624193Z"}, {"uuid": "1ca005c1-6615-4f50-bc98-dad9d9492dd2", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37164", "type": "seen", "source": "https://bsky.app/profile/pmloik.bsky.social/post/3mbxgzbhkc32h", "content": "", "creation_timestamp": "2026-01-09T02:25:52.170583Z"}, {"uuid": "d43cb566-4a9f-41a0-9a68-8f3498ef1df1", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37164", "type": "seen", "source": "https://bsky.app/profile/samilaiho.com/post/3mbxqbx3dic22", "content": "", "creation_timestamp": "2026-01-09T05:11:46.892858Z"}, {"uuid": "29785075-cbc7-420d-8551-0fd6dba8937f", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37164", "type": "seen", "source": "https://bsky.app/profile/hacker.at.thenote.app/post/3mby5wc6oac2o", "content": "", "creation_timestamp": "2026-01-09T09:15:48.331712Z"}, {"uuid": "73a97130-b4b8-4760-ae44-7c80daef1b1f", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37164", "type": "seen", "source": "https://bsky.app/profile/cybersentinel404.bsky.social/post/3mbygjyr4iq2k", "content": "", "creation_timestamp": "2026-01-09T11:49:59.400610Z"}, {"uuid": "ecaa4f14-3136-4eee-a8a2-2e786b0b2895", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37958", "type": "seen", "source": "https://bsky.app/profile/o2cloud.bsky.social/post/3mbynkk7rzk2z", "content": "", "creation_timestamp": "2026-01-09T13:55:34.607500Z"}, {"uuid": "7d17acd4-5491-40a5-ab27-dfd78cd0c671", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37164", "type": "seen", "source": "https://bsky.app/profile/guardian360.bsky.social/post/3mbyujb47jh2a", "content": "", "creation_timestamp": "2026-01-09T16:00:07.075127Z"}, {"uuid": "0a3e86cf-7886-4df8-ab48-bc03e209bc4a", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37164", "type": "seen", "source": "https://bsky.app/profile/thedailytechfeed.com/post/3mbyw37tzpe2z", "content": "", "creation_timestamp": "2026-01-09T16:28:03.837447Z"}, {"uuid": "c622048e-e519-40a5-8097-fca3a5d8f800", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37164", "type": "seen", "source": "https://bsky.app/profile/pmloik.bsky.social/post/3mbzxdeqjwl2x", "content": "", "creation_timestamp": "2026-01-10T02:23:10.359993Z"}, {"uuid": "01925a08-501b-46b0-b2f6-475a1bb28e30", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "cve-2025-37164", "type": "seen", "source": "https://bsky.app/profile/cyberhub.blog/post/3mc2hwfh4zg2f", "content": "", "creation_timestamp": "2026-01-10T07:20:08.580464Z"}, {"uuid": "691b1ee3-0595-457a-82bb-076533cbbda6", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2025-37786", "type": "seen", "source": "https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0291/", "content": "", "creation_timestamp": "2026-03-13T00:00:00.000000Z"}, {"uuid": "14bb43f5-0500-4fc0-9441-52e372160fdd", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2025-37920", "type": "seen", "source": "https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0291/", "content": "", "creation_timestamp": "2026-03-13T00:00:00.000000Z"}, {"uuid": "0c05ee09-6d03-40fe-b8ed-c001892646d3", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37164", "type": "seen", "source": "https://bsky.app/profile/hackread.bsky.social/post/3mc36fg5ah222", "content": "", "creation_timestamp": "2026-01-10T14:02:16.221342Z"}, {"uuid": "499b9792-5b09-4a6e-a8a1-39eb6e2b6f90", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37164", "type": "seen", "source": "https://mstdn.social/users/Hackread/statuses/115871169799209054", "content": "", "creation_timestamp": "2026-01-10T14:02:19.466166Z"}, {"uuid": "e424bafa-780e-4764-b0d8-bb4ecd0f7300", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37164", "type": "seen", "source": "https://bsky.app/profile/pmloik.bsky.social/post/3mc4i2q7v3x24", "content": "", "creation_timestamp": "2026-01-11T02:27:53.950863Z"}, {"uuid": "b0bfc1ef-428f-44e1-9cd1-b2afcb491ae7", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37164", "type": "seen", "source": "https://bsky.app/profile/infosec.skyfleet.blue/post/3mc4llghurt23", "content": "", "creation_timestamp": "2026-01-11T03:30:54.956272Z"}, {"uuid": "59f560e6-01d8-4445-9a65-115074762f07", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37164", "type": "seen", "source": "https://bsky.app/profile/allsafeus.bsky.social/post/3mc4ychwk522u", "content": "", "creation_timestamp": "2026-01-11T07:18:34.290182Z"}, {"uuid": "7ad39980-b67c-4c39-8d5a-bdad36a753e7", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2025-37822", "type": "seen", "source": "https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0291/", "content": "", "creation_timestamp": "2026-03-13T00:00:00.000000Z"}, {"uuid": "85ae0906-a148-4fe6-ac55-a077995cb07c", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37164", "type": "seen", "source": "https://bsky.app/profile/hacker.at.thenote.app/post/3mc65k6ulok2o", "content": "", "creation_timestamp": "2026-01-11T18:25:00.725253Z"}, {"uuid": "c776c5ca-3f22-468c-b247-91bae41d819f", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37164", "type": "seen", "source": "https://bsky.app/profile/pmloik.bsky.social/post/3mc6yjots7527", "content": "", "creation_timestamp": "2026-01-12T02:27:54.759207Z"}, {"uuid": "abf61fdd-9b7c-433d-a4a4-5f9a8f7a89df", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "cve-2025-37164", "type": "seen", "source": "https://bsky.app/profile/cyberhub.blog/post/3mc73h3krt222", "content": "", "creation_timestamp": "2026-01-12T03:20:09.715015Z"}, {"uuid": "e8105e8b-bcbc-4168-8923-d23bcd23b62d", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2025-37882", "type": "seen", "source": "https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0290/", "content": "", "creation_timestamp": "2026-03-13T00:00:00.000000Z"}, {"uuid": "03a2d5d6-6b5b-47ca-a7e8-7ef1433af9a9", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37164", "type": "seen", "source": "https://bsky.app/profile/pmloik.bsky.social/post/3mcbirzxw2e2p", "content": "", "creation_timestamp": "2026-01-13T02:24:14.129958Z"}, {"uuid": "30d21cfd-68ee-482b-9c1c-8e64fba10981", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2025-37899", "type": "seen", "source": "https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0289/", "content": "", "creation_timestamp": "2026-03-13T00:00:00.000000Z"}, {"uuid": "0aa2a5c3-6d78-4eca-9f78-aedd24ca06fe", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37165", "type": "seen", "source": "https://infosec.exchange/users/cR0w/statuses/115889127099102508", "content": "", "creation_timestamp": "2026-01-13T18:09:05.551304Z"}, {"uuid": "9a2b21a1-95b3-4966-93c6-d706af158bac", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37166", "type": "seen", "source": "https://infosec.exchange/users/cR0w/statuses/115889127099102508", "content": "", "creation_timestamp": "2026-01-13T18:09:05.653622Z"}, {"uuid": "b1d1c2ba-a86e-4ea5-afbc-0ed0c8ed3862", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37164", "type": "seen", "source": "https://bsky.app/profile/getpokemon7.bsky.social/post/3mcdilunqwc2p", "content": "", "creation_timestamp": "2026-01-13T21:26:09.263240Z"}, {"uuid": "a60c6e91-e96f-45ba-9be2-bfd947223109", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37186", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3mcdiwkhhzb2y", "content": "", "creation_timestamp": "2026-01-13T21:32:06.903228Z"}, {"uuid": "2c66b95f-b9cb-4fb6-a763-72c1fd5a7032", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37186", "type": "seen", "source": "https://bsky.app/profile/thehackerwire.bsky.social/post/3mcdkjffafh2m", "content": "", "creation_timestamp": "2026-01-13T22:00:31.628424Z"}, {"uuid": "b0453615-a48b-4e77-9b50-2400224c39cd", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37164", "type": "seen", "source": "https://bsky.app/profile/pmloik.bsky.social/post/3mcdzhbruzh23", "content": "", "creation_timestamp": "2026-01-14T02:27:46.267689Z"}, {"uuid": "35f2f25e-654b-44be-8bab-e41faab5c65f", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37164", "type": "seen", "source": "https://bsky.app/profile/securitylab-jp.bsky.social/post/3mce2npdlvs2k", "content": "", "creation_timestamp": "2026-01-14T02:49:16.232595Z"}, {"uuid": "1f6a44da-3f78-4968-bffc-f2964980b3eb", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37164", "type": "seen", "source": "https://bsky.app/profile/getpokemon7.bsky.social/post/3mce45a6et22e", "content": "", "creation_timestamp": "2026-01-14T03:15:54.767989Z"}, {"uuid": "1b3ce258-db7d-4734-8a96-94b44f3117f1", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37168", "type": "seen", "source": "https://bsky.app/profile/thehackerwire.bsky.social/post/3mceg6dk7ox2p", "content": "", "creation_timestamp": "2026-01-14T06:15:25.388202Z"}, {"uuid": "30c65f6b-c690-4d23-993c-784f02cda3d5", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37168", "type": "seen", "source": "https://bsky.app/profile/thehackerwire.bsky.social/post/3mcega74kpn2v", "content": "", "creation_timestamp": "2026-01-14T06:16:27.918866Z"}, {"uuid": "f34377be-c449-4a4a-a6d5-12f4bc1e95a7", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37164", "type": "seen", "source": "https://bsky.app/profile/getpokemon7.bsky.social/post/3mcfzcx3oa22r", "content": "", "creation_timestamp": "2026-01-14T21:30:47.329397Z"}, {"uuid": "22b2aa46-295f-4cd7-89b8-33b827becf30", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37164", "type": "seen", "source": "https://bsky.app/profile/pmloik.bsky.social/post/3mcgjrxmgpm2w", "content": "", "creation_timestamp": "2026-01-15T02:25:24.149516Z"}, {"uuid": "6d8ac3bc-b6b8-4c1d-b80f-fe7562599464", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37166", "type": "seen", "source": "https://bsky.app/profile/cyberdudebivash.bsky.social/post/3mcgmjmjzu22q", "content": "", "creation_timestamp": "2026-01-15T03:14:30.803698Z"}, {"uuid": "ca5ae3f9-d948-40ff-ad22-1014c4149f0c", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37164", "type": "seen", "source": "https://bsky.app/profile/blackhatnews.tokyo/post/3mcjrflxz4s2w", "content": "", "creation_timestamp": "2026-01-16T09:19:38.311106Z"}, {"uuid": "ad66df8c-ff7c-41a5-90e6-2ade6f4884e0", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37164", "type": "seen", "source": "The Shadowserver (honeypot/common-vulnerabilities) - (2026-01-15)", "content": "", "creation_timestamp": "2026-01-15T00:00:00.000000Z"}, {"uuid": "ae28588e-f512-4383-a07e-5ffc8db6193e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "c933734a-9be8-4142-889e-26e95c752803", "vulnerability": "CVE-2025-37967", "type": "seen", "source": "https://vulnerability.circl.lu/bundle/816dcc8e-f25a-4895-9b59-1bbd9caeccb8", "content": "", "creation_timestamp": "2025-12-03T14:14:49.267740Z"}, {"uuid": "eb390d20-cbde-4b00-bdc1-e53cda0cb66d", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "c933734a-9be8-4142-889e-26e95c752803", "vulnerability": "CVE-2025-37745", "type": "seen", "source": "https://vulnerability.circl.lu/bundle/816dcc8e-f25a-4895-9b59-1bbd9caeccb8", "content": "", "creation_timestamp": "2025-12-03T14:14:49.267740Z"}, {"uuid": "7e82c8f6-c341-46c9-87ec-aab20af76f66", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37164", "type": "seen", "source": "https://infosec.exchange/users/edwardk/statuses/115904985690991489", "content": "", "creation_timestamp": "2026-01-16T13:22:08.449836Z"}, {"uuid": "56c1aa1b-2751-422e-b7ff-fde97e017d01", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37164", "type": "seen", "source": "https://threatintel.cc/2026/01/16/active-exploitation-underway-for-critical.html", "content": "", "creation_timestamp": "2026-01-16T12:22:24.000000Z"}, {"uuid": "a5dce0be-942a-4a49-a1d6-04aaa7e83aaa", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37164", "type": "seen", "source": "https://bsky.app/profile/infosecbriefly.bsky.social/post/3mckblrunkt2y", "content": "", "creation_timestamp": "2026-01-16T14:09:26.245688Z"}, {"uuid": "a6dc8f40-3b86-4b2b-ae5a-e4d68cc25aa6", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "c933734a-9be8-4142-889e-26e95c752803", "vulnerability": "CVE-2025-37877", "type": "seen", "source": "https://vulnerability.circl.lu/bundle/816dcc8e-f25a-4895-9b59-1bbd9caeccb8", "content": "", "creation_timestamp": "2025-12-03T14:14:49.267740Z"}, {"uuid": "d64c9abb-f37a-4e43-b8d0-6453f9513702", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "c933734a-9be8-4142-889e-26e95c752803", "vulnerability": "CVE-2025-37954", "type": "seen", "source": "https://vulnerability.circl.lu/bundle/816dcc8e-f25a-4895-9b59-1bbd9caeccb8", "content": "", "creation_timestamp": "2025-12-03T14:14:49.267740Z"}, {"uuid": "425001da-b771-4b47-a033-09c48bc10cb3", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "c933734a-9be8-4142-889e-26e95c752803", "vulnerability": "CVE-2025-37867", "type": "seen", "source": "https://vulnerability.circl.lu/bundle/816dcc8e-f25a-4895-9b59-1bbd9caeccb8", "content": "", "creation_timestamp": "2025-12-03T14:14:49.267740Z"}, {"uuid": "cfbcb9bd-c381-49bf-a287-69081cfbe5f6", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "c933734a-9be8-4142-889e-26e95c752803", "vulnerability": "CVE-2025-37925", "type": "seen", "source": "https://vulnerability.circl.lu/bundle/816dcc8e-f25a-4895-9b59-1bbd9caeccb8", "content": "", "creation_timestamp": "2025-12-03T14:14:49.267740Z"}, {"uuid": "4928ee88-0e07-40bd-b200-32786832fa06", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "c933734a-9be8-4142-889e-26e95c752803", "vulnerability": "CVE-2025-37852", "type": "seen", "source": "https://vulnerability.circl.lu/bundle/816dcc8e-f25a-4895-9b59-1bbd9caeccb8", "content": "", "creation_timestamp": "2025-12-03T14:14:49.267740Z"}, {"uuid": "21e2996c-c9e0-4f73-8d9e-8ce3c8779e32", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "c933734a-9be8-4142-889e-26e95c752803", "vulnerability": "CVE-2025-37878", "type": "seen", "source": "https://vulnerability.circl.lu/bundle/816dcc8e-f25a-4895-9b59-1bbd9caeccb8", "content": "", "creation_timestamp": "2025-12-03T14:14:49.267740Z"}, {"uuid": "96af89b2-7f3a-48a9-adf4-982853eac38a", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "c933734a-9be8-4142-889e-26e95c752803", "vulnerability": "CVE-2025-37884", "type": "seen", "source": "https://vulnerability.circl.lu/bundle/816dcc8e-f25a-4895-9b59-1bbd9caeccb8", "content": "", "creation_timestamp": "2025-12-03T14:14:49.267740Z"}, {"uuid": "1a12f9b6-7a21-4e19-bb5f-08c5399ee103", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37164", "type": "exploited", "source": "The Shadowserver (honeypot/exploited-vulnerabilities) - (2026-01-17)", "content": "", "creation_timestamp": "2026-01-17T00:00:00.000000Z"}, {"uuid": "880fdb2e-75ac-418f-b670-7f115de6ed4c", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "c933734a-9be8-4142-889e-26e95c752803", "vulnerability": "CVE-2025-37834", "type": "seen", "source": "https://vulnerability.circl.lu/bundle/816dcc8e-f25a-4895-9b59-1bbd9caeccb8", "content": "", "creation_timestamp": "2025-12-03T14:14:49.267740Z"}, {"uuid": "42f7cb02-139c-403e-9803-b651fa21f913", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "c933734a-9be8-4142-889e-26e95c752803", "vulnerability": "CVE-2025-37951", "type": "seen", "source": "https://vulnerability.circl.lu/bundle/816dcc8e-f25a-4895-9b59-1bbd9caeccb8", "content": "", "creation_timestamp": "2025-12-03T14:14:49.267740Z"}, {"uuid": "0e8aff60-4a97-41f2-a24e-21c36c751844", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2025-37778", "type": "seen", "source": "https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0316/", "content": "", "creation_timestamp": "2026-03-19T00:00:00.000000Z"}, {"uuid": "038f9ee1-1f7a-4d70-ad31-c99da02e1ee3", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "c933734a-9be8-4142-889e-26e95c752803", "vulnerability": "CVE-2025-37963", "type": "seen", "source": "https://vulnerability.circl.lu/bundle/816dcc8e-f25a-4895-9b59-1bbd9caeccb8", "content": "", "creation_timestamp": "2025-12-03T14:14:49.267740Z"}, {"uuid": "3542eb07-c276-4e30-8509-013cc63d33c9", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2025-37747", "type": "seen", "source": "https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0316/", "content": "", "creation_timestamp": "2026-03-19T00:00:00.000000Z"}, {"uuid": "f1b3e3d4-18c3-4912-9d32-227ac59b1a4e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "c933734a-9be8-4142-889e-26e95c752803", "vulnerability": "CVE-2025-37980", "type": "seen", "source": "https://vulnerability.circl.lu/bundle/816dcc8e-f25a-4895-9b59-1bbd9caeccb8", "content": "", "creation_timestamp": "2025-12-03T14:14:49.267740Z"}, {"uuid": "24ec0292-da37-4b13-98d7-a093b72c2df8", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37164", "type": "seen", "source": "https://bsky.app/profile/rankednews.bsky.social/post/3mcp3gefmuu2e", "content": "", "creation_timestamp": "2026-01-18T12:02:20.819908Z"}, {"uuid": "16025b0a-0c79-4752-b5c3-50f3b16316be", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2025-37952", "type": "seen", "source": "https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0316/", "content": "", "creation_timestamp": "2026-03-19T00:00:00.000000Z"}, {"uuid": "f55e6ac8-0765-4216-813a-7b645dc4369c", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2025-37980", "type": "seen", "source": "https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0316/", "content": "", "creation_timestamp": "2026-03-19T00:00:00.000000Z"}, {"uuid": "5272679d-f9e9-42ed-8a68-59bd9713d0aa", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "c933734a-9be8-4142-889e-26e95c752803", "vulnerability": "CVE-2025-37739", "type": "seen", "source": "https://vulnerability.circl.lu/bundle/816dcc8e-f25a-4895-9b59-1bbd9caeccb8", "content": "", "creation_timestamp": "2025-12-03T14:14:49.267740Z"}, {"uuid": "e3b080dd-c2d7-4536-9482-69e99d644ade", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "c933734a-9be8-4142-889e-26e95c752803", "vulnerability": "CVE-2025-37885", "type": "seen", "source": "https://vulnerability.circl.lu/bundle/816dcc8e-f25a-4895-9b59-1bbd9caeccb8", "content": "", "creation_timestamp": "2025-12-03T14:14:49.267740Z"}, {"uuid": "7260ca1f-5b03-4fa0-9b30-2c81afd83011", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "c933734a-9be8-4142-889e-26e95c752803", "vulnerability": "CVE-2025-37756", "type": "seen", "source": "https://vulnerability.circl.lu/bundle/816dcc8e-f25a-4895-9b59-1bbd9caeccb8", "content": "", "creation_timestamp": "2025-12-03T14:14:49.267740Z"}, {"uuid": "3f61ad8b-651c-4bb5-8f68-c07a7afd2af1", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "c933734a-9be8-4142-889e-26e95c752803", "vulnerability": "CVE-2025-37942", "type": "seen", "source": "https://vulnerability.circl.lu/bundle/816dcc8e-f25a-4895-9b59-1bbd9caeccb8", "content": "", "creation_timestamp": "2025-12-03T14:14:49.267740Z"}, {"uuid": "fcc74ad6-43bb-478d-9bfa-569ae0a13112", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2025-37943", "type": "seen", "source": "https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0316/", "content": "", "creation_timestamp": "2026-03-19T00:00:00.000000Z"}, {"uuid": "e6e89bf4-7427-4e96-9e65-91c21e8d413f", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2025-37938", "type": "seen", "source": "https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0316/", "content": "", "creation_timestamp": "2026-03-19T00:00:00.000000Z"}, {"uuid": "a1c2067f-fd17-4947-b0b6-3b1ac27da60f", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "c933734a-9be8-4142-889e-26e95c752803", "vulnerability": "CVE-2025-37992", "type": "seen", "source": "https://vulnerability.circl.lu/bundle/816dcc8e-f25a-4895-9b59-1bbd9caeccb8", "content": "", "creation_timestamp": "2025-12-03T14:14:49.267740Z"}, {"uuid": "6daa993c-951b-448d-8f6e-2dfa0e9669af", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2025-37945", "type": "seen", "source": "https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0316/", "content": "", "creation_timestamp": "2026-03-19T00:00:00.000000Z"}, {"uuid": "824ffd2e-38df-47cf-a336-ef1ebf535905", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2025-37951", "type": "seen", "source": "https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0316/", "content": "", "creation_timestamp": "2026-03-19T00:00:00.000000Z"}, {"uuid": "cf4f81e6-a8f2-40eb-8669-5a0e19910498", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2025-37957", "type": "seen", "source": "https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0316/", "content": "", "creation_timestamp": "2026-03-19T00:00:00.000000Z"}, {"uuid": "d40a683e-d506-4e34-95c8-fb8c1edf2828", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2025-37961", "type": "seen", "source": "https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0316/", "content": "", "creation_timestamp": "2026-03-19T00:00:00.000000Z"}, {"uuid": "e6a7c3e5-c883-412e-b976-aca71de30b3f", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2025-37920", "type": "seen", "source": "https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0316/", "content": "", "creation_timestamp": "2026-03-19T00:00:00.000000Z"}, {"uuid": "24a9bd04-0068-4906-ab0b-ddc3e18e2f80", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2025-37854", "type": "seen", "source": "https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0316/", "content": "", "creation_timestamp": "2026-03-19T00:00:00.000000Z"}, {"uuid": "ae0a75d7-fbc2-4049-973f-7cdff3652757", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2025-37776", "type": "seen", "source": "https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0316/", "content": "", "creation_timestamp": "2026-03-19T00:00:00.000000Z"}, {"uuid": "7e851236-110f-4c84-9294-698405aa681c", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "c933734a-9be8-4142-889e-26e95c752803", "vulnerability": "CVE-2025-37849", "type": "seen", "source": "https://vulnerability.circl.lu/bundle/816dcc8e-f25a-4895-9b59-1bbd9caeccb8", "content": "", "creation_timestamp": "2025-12-03T14:14:49.267740Z"}, {"uuid": "01dd36b4-287b-4b71-b52f-8ffea2fe1048", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2025-37984", "type": "seen", "source": "https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0316/", "content": "", "creation_timestamp": "2026-03-19T00:00:00.000000Z"}, {"uuid": "997cbb2b-63f7-40e5-a6da-b486af1fe547", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2025-37926", "type": "seen", "source": "https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0316/", "content": "", "creation_timestamp": "2026-03-19T00:00:00.000000Z"}, {"uuid": "1a3bb6a8-1e78-4769-94eb-22fce372a960", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2025-37924", "type": "seen", "source": "https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0316/", "content": "", "creation_timestamp": "2026-03-19T00:00:00.000000Z"}, {"uuid": "aaacd0ee-0465-4b71-b7bb-d8c1ae6f1c9a", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "c933734a-9be8-4142-889e-26e95c752803", "vulnerability": "CVE-2025-37882", "type": "seen", "source": "https://vulnerability.circl.lu/bundle/816dcc8e-f25a-4895-9b59-1bbd9caeccb8", "content": "", "creation_timestamp": "2025-12-03T14:14:49.267740Z"}, {"uuid": "c2b92d0e-658a-4e84-aba0-d2b3f22aae39", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "c933734a-9be8-4142-889e-26e95c752803", "vulnerability": "CVE-2025-37830", "type": "seen", "source": "https://vulnerability.circl.lu/bundle/816dcc8e-f25a-4895-9b59-1bbd9caeccb8", "content": "", "creation_timestamp": "2025-12-03T14:14:49.267740Z"}, {"uuid": "c280a92d-1f71-41ff-a630-3bf9153fc306", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "c933734a-9be8-4142-889e-26e95c752803", "vulnerability": "CVE-2025-37801", "type": "seen", "source": "https://vulnerability.circl.lu/bundle/816dcc8e-f25a-4895-9b59-1bbd9caeccb8", "content": "", "creation_timestamp": "2025-12-03T14:14:49.267740Z"}, {"uuid": "e09e49eb-1639-4517-b5f0-812b8773209d", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2025-37928", "type": "seen", "source": "https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0316/", "content": "", "creation_timestamp": "2026-03-19T00:00:00.000000Z"}, {"uuid": "e43a3fcc-5c6e-4500-baf2-a2ebe97ead1b", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2025-37931", "type": "seen", "source": "https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0316/", "content": "", "creation_timestamp": "2026-03-19T00:00:00.000000Z"}, {"uuid": "b68f7a1d-bd63-4404-9972-505e97932462", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2025-37882", "type": "seen", "source": "https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0316/", "content": "", "creation_timestamp": "2026-03-19T00:00:00.000000Z"}, {"uuid": "84887c8e-77bf-4fd9-8590-b90f91496608", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2025-37899", "type": "seen", "source": "https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0316/", "content": "", "creation_timestamp": "2026-03-19T00:00:00.000000Z"}, {"uuid": "69a249d1-0324-4745-ad8d-b6e45adc386d", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "c933734a-9be8-4142-889e-26e95c752803", "vulnerability": "CVE-2025-37880", "type": "seen", "source": "https://vulnerability.circl.lu/bundle/816dcc8e-f25a-4895-9b59-1bbd9caeccb8", "content": "", "creation_timestamp": "2025-12-03T14:14:49.267740Z"}, {"uuid": "f491d864-a6f9-4b54-8e1b-e9296e34fc2d", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "c933734a-9be8-4142-889e-26e95c752803", "vulnerability": "CVE-2025-37742", "type": "seen", "source": "https://vulnerability.circl.lu/bundle/816dcc8e-f25a-4895-9b59-1bbd9caeccb8", "content": "", "creation_timestamp": "2025-12-03T14:14:49.267740Z"}, {"uuid": "299174d9-779d-4c7b-ab74-847193c2bdb2", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2025-37947", "type": "seen", "source": "https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0316/", "content": "", "creation_timestamp": "2026-03-19T00:00:00.000000Z"}, {"uuid": "559c5563-0481-4569-a07a-cba50bb06c5d", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2025-37853", "type": "seen", "source": "https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0316/", "content": "", "creation_timestamp": "2026-03-19T00:00:00.000000Z"}, {"uuid": "27e8b690-a2ef-4b86-81a2-69e8e13171ee", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "c933734a-9be8-4142-889e-26e95c752803", "vulnerability": "CVE-2025-37853", "type": "seen", "source": "https://vulnerability.circl.lu/bundle/816dcc8e-f25a-4895-9b59-1bbd9caeccb8", "content": "", "creation_timestamp": "2025-12-03T14:14:49.267740Z"}, {"uuid": "27f59613-6b16-4872-9d0c-a009fef5c654", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2025-37956", "type": "seen", "source": "https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0316/", "content": "", "creation_timestamp": "2026-03-19T00:00:00.000000Z"}, {"uuid": "87b6befa-bf12-44ce-b799-1a386f155ec8", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2025-37954", "type": "seen", "source": "https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0316/", "content": "", "creation_timestamp": "2026-03-19T00:00:00.000000Z"}, {"uuid": "13bfea83-2a61-4e89-99a4-b77211a88420", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2025-37959", "type": "seen", "source": "https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0316/", "content": "", "creation_timestamp": "2026-03-19T00:00:00.000000Z"}, {"uuid": "d640284d-09b1-4b18-a501-1bbfe41c25a6", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2025-37877", "type": "seen", "source": "https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0316/", "content": "", "creation_timestamp": "2026-03-19T00:00:00.000000Z"}, {"uuid": "6e7813ff-ca53-4aa6-8222-405cdd58ebf4", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2025-37884", "type": "seen", "source": "https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0316/", "content": "", "creation_timestamp": "2026-03-19T00:00:00.000000Z"}, {"uuid": "7395e48d-7db7-4680-a3d7-7806945711d4", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2025-37880", "type": "seen", "source": "https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0316/", "content": "", "creation_timestamp": "2026-03-19T00:00:00.000000Z"}, {"uuid": "9b6eca3a-7a65-4aa7-ac89-ab714b41696d", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2025-37944", "type": "seen", "source": "https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0316/", "content": "", "creation_timestamp": "2026-03-19T00:00:00.000000Z"}, {"uuid": "a67cda47-ffc6-404d-9010-9d6a51616f1e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "c933734a-9be8-4142-889e-26e95c752803", "vulnerability": "CVE-2025-37833", "type": "seen", "source": "https://vulnerability.circl.lu/bundle/816dcc8e-f25a-4895-9b59-1bbd9caeccb8", "content": "", "creation_timestamp": "2025-12-03T14:14:49.267740Z"}, {"uuid": "bd123e17-939b-4d1f-98dc-f47387bfcefc", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2025-37878", "type": "seen", "source": "https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0316/", "content": "", "creation_timestamp": "2026-03-19T00:00:00.000000Z"}, {"uuid": "08723fe1-0466-44e3-948d-4de1765cd3bf", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2025-37907", "type": "seen", "source": "https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0316/", "content": "", "creation_timestamp": "2026-03-19T00:00:00.000000Z"}, {"uuid": "a843ce99-1782-4e91-ad8f-9a63d7bb15a4", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "c933734a-9be8-4142-889e-26e95c752803", "vulnerability": "CVE-2025-37961", "type": "seen", "source": "https://vulnerability.circl.lu/bundle/816dcc8e-f25a-4895-9b59-1bbd9caeccb8", "content": "", "creation_timestamp": "2025-12-03T14:14:49.267740Z"}, {"uuid": "6807c0af-01a6-4ff5-973d-bc1017e014d1", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2025-37849", "type": "seen", "source": "https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0316/", "content": "", "creation_timestamp": "2026-03-19T00:00:00.000000Z"}, {"uuid": "b84d0af8-e020-45a7-8344-c422223540ae", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2025-37903", "type": "seen", "source": "https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0316/", "content": "", "creation_timestamp": "2026-03-19T00:00:00.000000Z"}, {"uuid": "31ad4ec7-3f17-4952-a5d9-e64ca1ac9845", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2025-37879", "type": "seen", "source": "https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0316/", "content": "", "creation_timestamp": "2026-03-19T00:00:00.000000Z"}, {"uuid": "905f5b50-1d4e-401d-8271-bc540684fab2", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2025-37876", "type": "seen", "source": "https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0316/", "content": "", "creation_timestamp": "2026-03-19T00:00:00.000000Z"}, {"uuid": "b7e41180-c94f-4606-8dde-7826d36c3439", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "c933734a-9be8-4142-889e-26e95c752803", "vulnerability": "CVE-2025-37800", "type": "seen", "source": "https://vulnerability.circl.lu/bundle/816dcc8e-f25a-4895-9b59-1bbd9caeccb8", "content": "", "creation_timestamp": "2025-12-03T14:14:49.267740Z"}, {"uuid": "c4cb92a0-61ee-4af7-b25b-781d48cd41ce", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2025-37855", "type": "seen", "source": "https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0316/", "content": "", "creation_timestamp": "2026-03-19T00:00:00.000000Z"}, {"uuid": "2ff62fff-1bc4-45ba-8069-5d3389ae5b3e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "c933734a-9be8-4142-889e-26e95c752803", "vulnerability": "CVE-2025-37768", "type": "seen", "source": "https://vulnerability.circl.lu/bundle/816dcc8e-f25a-4895-9b59-1bbd9caeccb8", "content": "", "creation_timestamp": "2025-12-03T14:14:49.267740Z"}, {"uuid": "066b95cb-d8d5-4c40-b1fd-8f644263b7f9", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2025-37852", "type": "seen", "source": "https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0316/", "content": "", "creation_timestamp": "2026-03-19T00:00:00.000000Z"}, {"uuid": "614ac5c8-1229-413c-bb5b-a2155053c496", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2025-37856", "type": "seen", "source": "https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0316/", "content": "", "creation_timestamp": "2026-03-19T00:00:00.000000Z"}, {"uuid": "590a9b06-549f-4d78-8a6a-b6b55a1057a7", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2025-37870", "type": "seen", "source": "https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0316/", "content": "", "creation_timestamp": "2026-03-19T00:00:00.000000Z"}, {"uuid": "0a51d58d-e7ab-4bba-af20-fa2a28e87f9d", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "c933734a-9be8-4142-889e-26e95c752803", "vulnerability": "CVE-2025-37911", "type": "seen", "source": "https://vulnerability.circl.lu/bundle/816dcc8e-f25a-4895-9b59-1bbd9caeccb8", "content": "", "creation_timestamp": "2025-12-03T14:14:49.267740Z"}, {"uuid": "f0af671c-0375-4784-9f1a-e3188098b93f", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2025-37861", "type": "seen", "source": "https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0316/", "content": "", "creation_timestamp": "2026-03-19T00:00:00.000000Z"}, {"uuid": "079faeb9-7f52-4de5-beec-699ed88c32cc", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "c933734a-9be8-4142-889e-26e95c752803", "vulnerability": "CVE-2025-37856", "type": "seen", "source": "https://vulnerability.circl.lu/bundle/816dcc8e-f25a-4895-9b59-1bbd9caeccb8", "content": "", "creation_timestamp": "2025-12-03T14:14:49.267740Z"}, {"uuid": "206366a4-4ece-4273-b8d5-8a73062405c9", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "c933734a-9be8-4142-889e-26e95c752803", "vulnerability": "CVE-2025-37928", "type": "seen", "source": "https://vulnerability.circl.lu/bundle/816dcc8e-f25a-4895-9b59-1bbd9caeccb8", "content": "", "creation_timestamp": "2025-12-03T14:14:49.267740Z"}, {"uuid": "7c3503cb-b7a2-4746-bbdb-84e1a9fc6f5d", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "c933734a-9be8-4142-889e-26e95c752803", "vulnerability": "CVE-2025-37836", "type": "seen", "source": "https://vulnerability.circl.lu/bundle/816dcc8e-f25a-4895-9b59-1bbd9caeccb8", "content": "", "creation_timestamp": "2025-12-03T14:14:49.267740Z"}, {"uuid": "c76ee038-efe1-43af-bb81-910eb876bf24", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "c933734a-9be8-4142-889e-26e95c752803", "vulnerability": "CVE-2025-37842", "type": "seen", "source": "https://vulnerability.circl.lu/bundle/816dcc8e-f25a-4895-9b59-1bbd9caeccb8", "content": "", "creation_timestamp": "2025-12-03T14:14:49.267740Z"}, {"uuid": "63b7ad9e-02e8-43f9-a7ae-7c25cbffa30c", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37164", "type": "seen", "source": "https://bsky.app/profile/mynameisv.bsky.social/post/3mcu4z4yj322r", "content": "", "creation_timestamp": "2026-01-20T12:14:06.274951Z"}, {"uuid": "32268d9c-d3cd-494d-8268-9ce1d50e88b6", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37164", "type": "seen", "source": "https://bsky.app/profile/blackhatnews.tokyo/post/3mcuhya66tp2s", "content": "", "creation_timestamp": "2026-01-20T15:30:23.323511Z"}, {"uuid": "c73f41ef-3e61-4937-b6fa-9e7ce7a536da", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "c933734a-9be8-4142-889e-26e95c752803", "vulnerability": "CVE-2025-37770", "type": "seen", "source": "https://vulnerability.circl.lu/bundle/816dcc8e-f25a-4895-9b59-1bbd9caeccb8", "content": "", "creation_timestamp": "2025-12-03T14:14:49.267740Z"}, {"uuid": "edd38d7a-cec1-42fd-b856-b84c1dbf6fea", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "c933734a-9be8-4142-889e-26e95c752803", "vulnerability": "CVE-2025-37807", "type": "seen", "source": "https://vulnerability.circl.lu/bundle/816dcc8e-f25a-4895-9b59-1bbd9caeccb8", "content": "", "creation_timestamp": "2025-12-03T14:14:49.267740Z"}, {"uuid": "828e048a-dd3b-44d3-8e4d-d9c6f9b597dd", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2025-37777", "type": "seen", "source": "https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0316/", "content": "", "creation_timestamp": "2026-03-19T00:00:00.000000Z"}, {"uuid": "7a1dde73-cfe4-439d-87d5-e7818d5c93ad", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "c933734a-9be8-4142-889e-26e95c752803", "vulnerability": "CVE-2025-37920", "type": "seen", "source": "https://vulnerability.circl.lu/bundle/816dcc8e-f25a-4895-9b59-1bbd9caeccb8", "content": "", "creation_timestamp": "2025-12-03T14:14:49.267740Z"}, {"uuid": "d8e71b33-d285-4f0f-a132-7815daab322b", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "c933734a-9be8-4142-889e-26e95c752803", "vulnerability": "CVE-2025-37948", "type": "seen", "source": "https://vulnerability.circl.lu/bundle/816dcc8e-f25a-4895-9b59-1bbd9caeccb8", "content": "", "creation_timestamp": "2025-12-03T14:14:49.267740Z"}, {"uuid": "a7232cb2-c23a-482b-a081-c0d11f5f0197", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "cve-2025-37164", "type": "seen", "source": "https://social.tchncs.de/users/gborn/statuses/115933867940959396", "content": "", "creation_timestamp": "2026-01-21T15:47:17.001184Z"}, {"uuid": "3ea32ac5-407e-4a97-a94b-0069c067be86", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37164", "type": "seen", "source": "https://bsky.app/profile/etguenni.bsky.social/post/3mcwzgwghjs27", "content": "", "creation_timestamp": "2026-01-21T15:48:11.456755Z"}, {"uuid": "ba5fc29e-d4df-40cf-85bd-be60bd38068c", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "c933734a-9be8-4142-889e-26e95c752803", "vulnerability": "CVE-2025-37879", "type": "seen", "source": "https://vulnerability.circl.lu/bundle/816dcc8e-f25a-4895-9b59-1bbd9caeccb8", "content": "", "creation_timestamp": "2025-12-03T14:14:49.267740Z"}, {"uuid": "cb3b1674-8b64-44bb-ac19-e0ced55abf50", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "c933734a-9be8-4142-889e-26e95c752803", "vulnerability": "CVE-2025-37883", "type": "seen", "source": "https://vulnerability.circl.lu/bundle/816dcc8e-f25a-4895-9b59-1bbd9caeccb8", "content": "", "creation_timestamp": "2025-12-03T14:14:49.267740Z"}, {"uuid": "4fcecafc-ad07-4686-a4f2-f92ea55fe598", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2025-37834", "type": "seen", "source": "https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0316/", "content": "", "creation_timestamp": "2026-03-19T00:00:00.000000Z"}, {"uuid": "ed7f8c6b-492b-468c-9fda-4f62238ff4c2", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2025-37743", "type": "seen", "source": "https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0316/", "content": "", "creation_timestamp": "2026-03-19T00:00:00.000000Z"}, {"uuid": "ea4ba696-2acb-4ba9-9ac0-692183a12ea8", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2025-37744", "type": "seen", "source": "https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0316/", "content": "", "creation_timestamp": "2026-03-19T00:00:00.000000Z"}, {"uuid": "c4734227-09de-4efb-8322-bfbf7e5e059e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2025-37745", "type": "seen", "source": "https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0316/", "content": "", "creation_timestamp": "2026-03-19T00:00:00.000000Z"}, {"uuid": "6a7c9e64-bfe7-4a4c-b8ec-594c8b405d91", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2025-37746", "type": "seen", "source": "https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0316/", "content": "", "creation_timestamp": "2026-03-19T00:00:00.000000Z"}, {"uuid": "7346f0d7-3c63-4f4b-929d-caaacb8f639d", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2025-37775", "type": "seen", "source": "https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0316/", "content": "", "creation_timestamp": "2026-03-19T00:00:00.000000Z"}, {"uuid": "b3adc692-2725-4933-a299-b48a986fde35", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2025-37786", "type": "seen", "source": "https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0316/", "content": "", "creation_timestamp": "2026-03-19T00:00:00.000000Z"}, {"uuid": "77cd48d7-b99e-49e0-b4e4-26bce46d6ba4", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2025-37800", "type": "seen", "source": "https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0316/", "content": "", "creation_timestamp": "2026-03-19T00:00:00.000000Z"}, {"uuid": "49a144b6-367b-4aa9-95f2-55968631c201", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2025-37806", "type": "seen", "source": "https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0316/", "content": "", "creation_timestamp": "2026-03-19T00:00:00.000000Z"}, {"uuid": "82f731fd-b815-409f-b26c-08226041cd01", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2025-37807", "type": "seen", "source": "https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0316/", "content": "", "creation_timestamp": "2026-03-19T00:00:00.000000Z"}, {"uuid": "90b6eb96-c718-4746-96b1-7aa19d4100b2", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2025-37842", "type": "seen", "source": "https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0316/", "content": "", "creation_timestamp": "2026-03-19T00:00:00.000000Z"}, {"uuid": "93973e4a-3255-486c-825f-bddff1c56311", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2025-37820", "type": "seen", "source": "https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0316/", "content": "", "creation_timestamp": "2026-03-19T00:00:00.000000Z"}, {"uuid": "ddbc7f52-492f-4915-8289-e63b2245f6aa", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2025-37822", "type": "seen", "source": "https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0316/", "content": "", "creation_timestamp": "2026-03-19T00:00:00.000000Z"}, {"uuid": "14472b5b-328b-4643-b81f-a0e62a224e4c", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2025-37833", "type": "seen", "source": "https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0316/", "content": "", "creation_timestamp": "2026-03-19T00:00:00.000000Z"}, {"uuid": "afbffb1c-cdf2-4d00-a490-420a347ecafe", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "cve-2025-37164", "type": "seen", "source": "https://gist.github.com/alon710/1d6a209c5e9f256491dd30dd45eae1d5", "content": "", "creation_timestamp": "2026-01-24T21:26:23.000000Z"}, {"uuid": "502ea892-1ef9-4bec-a2f2-187a8335f5b1", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "cve-2025-37164", "type": "seen", "source": "https://gist.github.com/alon710/60a6d951d1dc8fa6dac26c3dac24d7a7", "content": "", "creation_timestamp": "2026-01-24T22:41:45.000000Z"}, {"uuid": "643cbd6d-99c9-4350-9b25-73ca387f12f3", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2025-37822", "type": "seen", "source": "https://www.hkcert.org/security-bulletin/debian-linux-kernel-multiple-vulnerabilities_20260316", "content": "", "creation_timestamp": "2026-03-16T03:00:00.000000Z"}, {"uuid": "9a1a0cfc-da2d-489a-b6bf-eddf2ae9790c", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2025-37786", "type": "seen", "source": "https://www.hkcert.org/security-bulletin/debian-linux-kernel-multiple-vulnerabilities_20260316", "content": "", "creation_timestamp": "2026-03-16T03:00:00.000000Z"}, {"uuid": "da9012cc-9c0c-4592-a1ef-ad6a947f3b2e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2025-37920", "type": "seen", "source": "https://www.hkcert.org/security-bulletin/debian-linux-kernel-multiple-vulnerabilities_20260316", "content": "", "creation_timestamp": "2026-03-16T03:00:00.000000Z"}, {"uuid": "9fda7c32-a4de-4cc1-a73c-cf1d9eb3ca58", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37164", "type": "seen", "source": "https://bsky.app/profile/newsen.bsky.social/post/3mdcgl5ygwi2h", "content": "", "creation_timestamp": "2026-01-26T04:42:27.701892Z"}, {"uuid": "82955093-938a-4c68-b985-20b8e60baa8d", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "af0120d0-3dac-4a6a-974b-a9f33d2a9846", "vulnerability": "CVE-2025-37164", "type": "exploited", "source": "https://vulnerability.circl.lu/known-exploited-vulnerabilities-catalog/b1f9ef7b-1037-40d8-aae1-ea6b0c3ed483", "content": "", "creation_timestamp": "2026-02-02T12:25:43.387104Z"}, {"uuid": "baf3007f-7b0c-44b4-a00b-9136af9c6026", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37849", "type": "seen", "source": "https://bsky.app/profile/o2cloud.bsky.social/post/3miltukybcz26", "content": "", "creation_timestamp": "2026-04-03T13:40:17.184326Z"}, {"uuid": "d727afc1-82c7-40af-903c-7e4f7bf08e47", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37164", "type": "published-proof-of-concept", "source": "Telegram/shQsG5TFmMrzus3uWOqA-vjUO4oHdrJHZ6Xu7ifps-_tm5s", "content": "", "creation_timestamp": "2026-01-07T20:04:13.000000Z"}, {"uuid": "c9d3d321-316b-4c99-b0b3-f0c13fced51f", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37164", "type": "published-proof-of-concept", "source": "Telegram/3pBq5cR6IlqeDtmbK0wx8m04HXDRqV_g5yEoTFBTOYd5yjQ", "content": "", "creation_timestamp": "2026-01-07T03:00:06.000000Z"}, {"uuid": "27ae0c14-088a-4a74-8454-9f03531a0738", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37164", "type": "published-proof-of-concept", "source": "Telegram/utdOlXrxtJhuzozgREzDNv0wfeU39jR5jsj_GoqbUxaQLcM", "content": "", "creation_timestamp": "2025-12-18T21:00:04.000000Z"}, {"uuid": "05d5073b-e5ee-4f1d-8f34-621c05b8a90b", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37164", "type": "published-proof-of-concept", "source": "Telegram/mLEOWN64VqKw_0VE78e17Gu1UFXBsQSVdJfNgYq3VLys3t4", "content": "", "creation_timestamp": "2025-12-20T21:00:05.000000Z"}, {"uuid": "1fdeb9d7-84ef-4531-97f8-afa068063e86", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37164", "type": "published-proof-of-concept", "source": "Telegram/7njGm26FnoUK1bQXzBTU_OZCWqcjQDOZaxwwz-bFB38oj9Y", "content": "", "creation_timestamp": "2025-12-20T03:00:05.000000Z"}, {"uuid": "14cc9cba-8cc2-4b28-92d5-364bda574067", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37899", "type": "published-proof-of-concept", "source": "https://t.me/orderofsixangles/2613", "content": "How I used o3 to find CVE-2025-37899, a remote zeroday vulnerability in the Linux kernel\u2019s SMB implementation\n\nhttps://sean.heelan.io/2025/05/22/how-i-used-o3-to-find-cve-2025-37899-a-remote-zeroday-vulnerability-in-the-linux-kernels-smb-implementation/", "creation_timestamp": "2025-05-22T11:27:17.000000Z"}, {"uuid": "d68c1f4f-c061-47de-ab51-b375b9a39ee2", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37947", "type": "seen", "source": "https://bsky.app/profile/r-netsec.bsky.social/post/3mixdxobrr42b", "content": "", "creation_timestamp": "2026-04-08T03:27:38.232104Z"}, {"uuid": "07843133-b133-4332-a284-cc8913f87c36", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2025-37849", "type": "seen", "source": "https://www.hkcert.org/security-bulletin/ubuntu-linux-kernel-multiple-vulnerabilities_20260408", "content": "", "creation_timestamp": "2026-04-07T18:00:00.000000Z"}, {"uuid": "b3c869bb-0925-44bf-b6a1-0b9b959b7317", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2025-37860", "type": "seen", "source": "https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0397/", "content": "", "creation_timestamp": "2026-04-02T17:00:00.000000Z"}, {"uuid": "ead45659-2762-4c78-b267-75214c2529d1", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2025-37849", "type": "seen", "source": "https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0397/", "content": "", "creation_timestamp": "2026-04-02T17:00:00.000000Z"}, {"uuid": "fa0133fe-f614-4fe5-bd50-27b982e9d193", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37100", "type": "published-proof-of-concept", "source": "Telegram/Cx1-p36APBve2ZXOx6JZQ1ihep0qwdXJ_nQmLSJI9jXODK8", "content": "", "creation_timestamp": "2025-06-10T16:01:27.000000Z"}, {"uuid": "0a93b5bd-62a1-466a-b9e4-12a7223e427e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3776", "type": "published-proof-of-concept", "source": "https://t.me/GithubRedTeam/33958", "content": "GitHub\u76d1\u63a7\u6d88\u606f\u63d0\u9192\uff01\uff01\uff01 \n\n\u66f4\u65b0\u4e86\uff1aCVE-2025\n\u63cf\u8ff0\uff1a WordPress Verification SMS with TargetSMS Plugin <= 1.5 is vulnerable to Remote Code Execution (RCE) \nURL\uff1ahttps://github.com/Nxploited/CVE-2025-3776\n\n\u6807\u7b7e\uff1a#CVE-2025", "creation_timestamp": "2025-04-24T01:22:24.000000Z"}, {"uuid": "e69415a6-4a87-4407-918a-bed6c5dd8be0", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2025-37849", "type": "seen", "source": "https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0396/", "content": "", "creation_timestamp": "2026-04-02T17:00:00.000000Z"}, {"uuid": "d0d9175a-0479-4b47-a5d2-49b8e62d8211", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2025-37860", "type": "seen", "source": "https://www.hkcert.org/security-bulletin/ubuntu-linux-kernel-multiple-vulnerabilities_20260408", "content": "", "creation_timestamp": "2026-04-07T18:00:00.000000Z"}, {"uuid": "901416c6-0ea9-462c-be25-8ae54a302577", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3782", "type": "published-proof-of-concept", "source": "https://t.me/GithubRedTeam/35814", "content": "GitHub\u76d1\u63a7\u6d88\u606f\u63d0\u9192\uff01\uff01\uff01 \n\n\u66f4\u65b0\u4e86\uff1aCVE-2025\n\u63cf\u8ff0\uff1aPoC for CVE-2025-2011 - SQLi in Depicter plugin <= 3.6.1\nURL\uff1ahttps://github.com/datagoboom/CVE-2025-3782\n\n\u6807\u7b7e\uff1a#CVE-2025", "creation_timestamp": "2025-05-06T20:18:23.000000Z"}, {"uuid": "c9c724e5-2346-4711-9662-3803c039496f", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3774", "type": "published-proof-of-concept", "source": "Telegram/yixXk03Px4jmK8hy8DNQOPYwyMdQ2hxkl47WHo8gYnS6T9E", "content": "", "creation_timestamp": "2025-06-17T03:02:49.000000Z"}, {"uuid": "e0b8365c-a501-4e19-ac99-6ce6dcff6e36", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3749", "type": "seen", "source": "https://t.me/DarkWebInformer_CVEAlerts/13365", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-3749\n\ud83d\udd25 CVSS Score: 6.4 (cvssV3_1, Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N)\n\ud83d\udd39 Description: The Breeze Display plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the \u2018cal_size\u2019 parameter in all versions up to, and including, 1.2.3 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with Contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.\n\ud83d\udccf Published: 2025-04-24T22:22:13.994Z\n\ud83d\udccf Modified: 2025-04-24T22:22:13.994Z\n\ud83d\udd17 References:\n1. https://www.wordfence.com/threat-intel/vulnerabilities/id/527dd2c7-5bbb-4c79-aa3c-7d70ddd26163?source=cve\n2. https://plugins.trac.wordpress.org/browser/wt-display-breeze/trunk/includes/shortcodes.php#L114\n3. https://wordpress.org/plugins/wt-display-breeze/#developers\n4. https://plugins.trac.wordpress.org/changeset/3280146/", "creation_timestamp": "2025-04-24T23:09:23.000000Z"}, {"uuid": "2c2f6d54-d4b8-4fc1-a147-a6da75a5ef06", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3775", "type": "seen", "source": "https://t.me/DarkWebInformer_CVEAlerts/13378", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-3775\n\ud83d\udd25 CVSS Score: 6.5 (cvssV3_1, Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N)\n\ud83d\udd39 Description: The ShopLentor \u2013 WooCommerce Builder for Elementor & Gutenberg +20 Modules \u2013 All in One Solution (formerly WooLentor) plugin for WordPress is vulnerable to Server-Side Request Forgery in all versions up to, and including, 3.1.2 via the woolentor_template_proxy function. This makes it possible for unauthenticated attackers to make web requests to arbitrary locations originating from the web application, and can be used to query and modify information from internal services.\n\ud83d\udccf Published: 2025-04-25T04:23:04.940Z\n\ud83d\udccf Modified: 2025-04-25T04:23:04.940Z\n\ud83d\udd17 References:\n1. https://www.wordfence.com/threat-intel/vulnerabilities/id/4dfc28ec-1411-43c3-833e-a6c85a3ed767?source=cve\n2. https://plugins.trac.wordpress.org/browser/woolentor-addons/tags/3.1.2/includes/admin-panel/includes/classes/Admin.php#L71", "creation_timestamp": "2025-04-25T05:08:58.000000Z"}, {"uuid": "473a5b92-9020-4f0d-a282-8881a23fdebd", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3752", "type": "seen", "source": "https://t.me/DarkWebInformer_CVEAlerts/13377", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-3752\n\ud83d\udd25 CVSS Score: 6.4 (cvssV3_1, Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N)\n\ud83d\udd39 Description: The Able Player, accessible HTML5 media player plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the \u2018preload\u2019 parameter in all versions up to, and including, 1.2.1 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with Contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.\n\ud83d\udccf Published: 2025-04-25T04:23:05.578Z\n\ud83d\udccf Modified: 2025-04-25T04:23:05.578Z\n\ud83d\udd17 References:\n1. https://www.wordfence.com/threat-intel/vulnerabilities/id/85c123ee-8de0-4800-b96b-68bb4d763560?source=cve\n2. https://plugins.trac.wordpress.org/browser/ableplayer/trunk/ableplayer.php#L375\n3. https://wordpress.org/plugins/ableplayer/#developers\n4. https://plugins.trac.wordpress.org/changeset?sfp_email=&sfph_mail=&reponame=&old=3281106%40ableplayer&new=3281106%40ableplayer", "creation_timestamp": "2025-04-25T05:08:57.000000Z"}, {"uuid": "21b4e5a8-33f0-4ebc-9a87-b0e76125dd98", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3743", "type": "seen", "source": "https://t.me/DarkWebInformer_CVEAlerts/13385", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-3743\n\ud83d\udd25 CVSS Score: 5.3 (cvssV3_1, Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N)\n\ud83d\udd39 Description: The Upsell Funnel Builder for WooCommerce plugin for WordPress is vulnerable to order manipulation in all versions up to, and including, 3.0.0. This is due to the plugin allowing the additional product ID and discount field to be manipulated prior to processing via the 'add_offer_in_cart' function. This makes it possible for unauthenticated attackers to arbitrarily update the product associated with any order bump, and arbitrarily update the discount applied to any order bump item, when adding it to the cart.\n\ud83d\udccf Published: 2025-04-25T06:45:29.320Z\n\ud83d\udccf Modified: 2025-04-25T06:45:29.320Z\n\ud83d\udd17 References:\n1. https://www.wordfence.com/threat-intel/vulnerabilities/id/b0e1546b-c8cc-4d57-9909-153209e3a9c6?source=cve\n2. https://plugins.trac.wordpress.org/browser/upsell-order-bump-offer-for-woocommerce/tags/3.0.0/public/class-upsell-order-bump-offer-for-woocommerce-public.php#L1773\n3. https://plugins.trac.wordpress.org/browser/upsell-order-bump-offer-for-woocommerce/tags/3.0.0/public/class-upsell-order-bump-offer-for-woocommerce-public.php#L1818\n4. https://plugins.trac.wordpress.org/browser/upsell-order-bump-offer-for-woocommerce/tags/3.0.0/public/class-upsell-order-bump-offer-for-woocommerce-public.php#L1829\n5. https://plugins.trac.wordpress.org/browser/upsell-order-bump-offer-for-woocommerce/tags/3.0.0/public/class-upsell-order-bump-offer-for-woocommerce-public.php#L1771\n6. https://plugins.trac.wordpress.org/changeset/3279944/", "creation_timestamp": "2025-04-25T07:07:12.000000Z"}, {"uuid": "d5e593d2-7421-4ce6-ae64-901841a7d911", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3708", "type": "seen", "source": "https://t.me/DarkWebInformer_CVEAlerts/14440", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-3708\n\ud83d\udd25 CVSS Score: 9.8 (cvssV3_1, Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H)\n\ud83d\udd39 Description: Le-show medical practice management system from Le-yan has a SQL Injection vulnerability, allowing unauthenticated remote attackers to inject arbitrary SQL commands to read, modify, and delete database contents.\n\ud83d\udccf Published: 2025-05-02T02:55:32.493Z\n\ud83d\udccf Modified: 2025-05-02T02:55:32.493Z\n\ud83d\udd17 References:\n1. https://www.twcert.org.tw/tw/cp-132-10085-69e16-1.html\n2. https://www.twcert.org.tw/en/cp-139-10086-dbfd0-2.html", "creation_timestamp": "2025-05-02T04:15:56.000000Z"}, {"uuid": "b272f46e-1a1c-4be6-8c10-7b64427fb5bb", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3709", "type": "seen", "source": "https://t.me/DarkWebInformer_CVEAlerts/14439", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-3709\n\ud83d\udd25 CVSS Score: 9.8 (cvssV3_1, Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H)\n\ud83d\udd39 Description: Agentflow from Flowring Technology has an Account Lockout Bypass vulnerability, allowing unauthenticated remote attackers to exploit this vulnerability to perform password brute force attack.\n\ud83d\udccf Published: 2025-05-02T03:13:32.971Z\n\ud83d\udccf Modified: 2025-05-02T03:13:32.971Z\n\ud83d\udd17 References:\n1. https://www.twcert.org.tw/tw/cp-132-10091-12462-1.html\n2. https://www.twcert.org.tw/en/cp-139-10090-112f7-2.html", "creation_timestamp": "2025-05-02T04:15:56.000000Z"}, {"uuid": "c9e9ab9f-9255-4beb-88a0-e25ccb378083", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2025-3756", "type": "seen", "source": "https://cyber.gc.ca/en/alerts-advisories/control-systems-abb-security-advisory-av26-346", "content": "", "creation_timestamp": "2026-04-13T12:44:04.000000Z"}, {"uuid": "5a8927e1-14e2-4a48-95d9-597ae9e56680", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3748", "type": "seen", "source": "https://t.me/DarkWebInformer_CVEAlerts/14437", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-3748\n\ud83d\udd25 CVSS Score: 6.4 (cvssV3_1, Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N)\n\ud83d\udd39 Description: The Taxonomy Chain Menu plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's pn_chain_menu shortcode in all versions up to, and including, 1.0.8 due to insufficient input sanitization and output escaping on user supplied attributes. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.\n\ud83d\udccf Published: 2025-05-02T03:21:17.556Z\n\ud83d\udccf Modified: 2025-05-02T03:21:17.556Z\n\ud83d\udd17 References:\n1. https://www.wordfence.com/threat-intel/vulnerabilities/id/25afc28c-2814-4b49-add5-1d0ce5ff3a07?source=cve\n2. https://plugins.trac.wordpress.org/browser/taxonomy-chain-menu/trunk/index.php#L190\n3. https://wordpress.org/plugins/taxonomy-chain-menu/#developers\n4. https://plugins.trac.wordpress.org/changeset/3284354/", "creation_timestamp": "2025-05-02T04:15:51.000000Z"}, {"uuid": "4bdfbe47-f63e-4084-9955-b6fe22e17843", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3707", "type": "seen", "source": "https://t.me/DarkWebInformer_CVEAlerts/14441", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-3707\n\ud83d\udd25 CVSS Score: 6.5 (cvssV3_1, Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N)\n\ud83d\udd39 Description: The eHDR CTMS from Sunnet has a SQL Injection vulnerability, allowing remote attackers with regular privileges to inject arbitrary SQL command to read database contents.\n\ud83d\udccf Published: 2025-05-02T02:50:33.346Z\n\ud83d\udccf Modified: 2025-05-02T02:50:33.346Z\n\ud83d\udd17 References:\n1. https://www.twcert.org.tw/tw/cp-132-10083-4ed7f-1.html\n2. https://www.twcert.org.tw/en/cp-139-10084-d7c47-2.html", "creation_timestamp": "2025-05-02T04:15:57.000000Z"}, {"uuid": "bbaf5316-c99c-47e6-b300-b093e0d86a4e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37789", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/14454", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-37789\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nnet: openvswitch: fix nested key length validation in the set() action\n\nIt's not safe to access nla_len(ovs_key) if the data is smaller than\nthe netlink header.  Check that the attribute is OK first.\n\ud83d\udccf Published: 2025-05-01T13:07:22.809Z\n\ud83d\udccf Modified: 2025-05-02T06:16:29.055Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/54c6957d1123a2032099b9eab51c314800f677ce\n2. https://git.kernel.org/stable/c/7fcaec0b2ab8fa5fbf0b45e5512364a168f445bd\n3. https://git.kernel.org/stable/c/a27526e6b48eee9e2d82efff502c4f272f1a91d4\n4. https://git.kernel.org/stable/c/1489c195c8eecd262aa6712761ba5288203e28ec\n5. https://git.kernel.org/stable/c/824a7c2df5127b2402b68a21a265d413e78dcad7\n6. https://git.kernel.org/stable/c/be80768d4f3b6fd13f421451cc3fee8778aba8bc\n7. https://git.kernel.org/stable/c/03d7262dd53e8c404da35cc81aaa887fd901f76b\n8. https://git.kernel.org/stable/c/65d91192aa66f05710cfddf6a14b5a25ee554dba", "creation_timestamp": "2025-05-02T07:16:23.000000Z"}, {"uuid": "70789968-da52-4195-ac70-24b0f2c9441e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37796", "type": "seen", "source": "https://t.me/DarkWebInformer_CVEAlerts/14451", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-37796\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nwifi: at76c50x: fix use after free access in at76_disconnect\n\nThe memory pointed to by priv is freed at the end of at76_delete_device\nfunction (using ieee80211_free_hw). But the code then accesses the udev\nfield of the freed object to put the USB device. This may also lead to a\nmemory leak of the usb device. Fix this by using udev from interface.\n\ud83d\udccf Published: 2025-05-01T13:07:27.694Z\n\ud83d\udccf Modified: 2025-05-02T06:16:35.629Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/c731cdfddcf1be1590d5ba8c9b508f98e3a2b3d6\n2. https://git.kernel.org/stable/c/6e4ab3e574c2a335b40fa1f70d1c54fcb58ab33f\n3. https://git.kernel.org/stable/c/3c619aec1f538333b56746d2f796aab1bca5c9a5\n4. https://git.kernel.org/stable/c/5e7df74745700f059dc117a620e566964a2e8f2c\n5. https://git.kernel.org/stable/c/7ca513631fa6ad3011b8b9197cdde0f351103704\n6. https://git.kernel.org/stable/c/a9682bfef2cf3802515a902e964d774e137be1b9\n7. https://git.kernel.org/stable/c/152721cbae42713ecfbca6847e0f102ee6b19546\n8. https://git.kernel.org/stable/c/27c7e63b3cb1a20bb78ed4a36c561ea4579fd7da", "creation_timestamp": "2025-05-02T07:16:20.000000Z"}, {"uuid": "76bf13cd-7423-48be-886d-84cb791422ca", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37770", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/14460", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-37770\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/amd/pm: Prevent division by zero\n\nThe user can set any speed value.\nIf speed is greater than UINT_MAX/8, division by zero is possible.\n\nFound by Linux Verification Center (linuxtesting.org) with SVACE.\n\ud83d\udccf Published: 2025-05-01T13:07:10.353Z\n\ud83d\udccf Modified: 2025-05-02T06:16:18.072Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/e109528bbf460e50074c156253d9080d223ee37f\n2. https://git.kernel.org/stable/c/0c02fcbe4a1393a3c02da6ae35e72493cfdb2155\n3. https://git.kernel.org/stable/c/836a189fb422e7efb81c51d5160e47ec7bc11500\n4. https://git.kernel.org/stable/c/587de3ca7875c06fe3c3aa4073a85c4eff46591f\n5. https://git.kernel.org/stable/c/bd4d90adbca1862d03e581e10e74ab73ec75e61b\n6. https://git.kernel.org/stable/c/05de66de280ea1bd0459c994bfd2dd332cfbc2a9\n7. https://git.kernel.org/stable/c/4b8c3c0d17c07f301011e2908fecd2ebdcfe3d1c", "creation_timestamp": "2025-05-02T07:16:31.000000Z"}, {"uuid": "355b5a13-b795-476b-a2b7-07e4b0d5b3c2", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37771", "type": "seen", "source": "https://t.me/DarkWebInformer_CVEAlerts/14459", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-37771\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/amd/pm: Prevent division by zero\n\nThe user can set any speed value.\nIf speed is greater than UINT_MAX/8, division by zero is possible.\n\nFound by Linux Verification Center (linuxtesting.org) with SVACE.\n\ud83d\udccf Published: 2025-05-01T13:07:11.517Z\n\ud83d\udccf Modified: 2025-05-02T06:16:19.073Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/b7c41df4913789ebfe73cc1e17c6401d4c5eab69\n2. https://git.kernel.org/stable/c/402964994e8ece29702383b234fabcf04791ff95\n3. https://git.kernel.org/stable/c/5096174074114f83c700a27869c54362cbb10f3e\n4. https://git.kernel.org/stable/c/6413fed016208171592c88b5df002af8a1387e24\n5. https://git.kernel.org/stable/c/baa54adb5e0599299b8f088efb5544d876a3eb62\n6. https://git.kernel.org/stable/c/7d641c2b83275d3b0424127b2e0d2d0f7dd82aef", "creation_timestamp": "2025-05-02T07:16:30.000000Z"}, {"uuid": "9b77719d-997a-4ad7-af65-d3627e397ba3", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37773", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/14458", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-37773\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nvirtiofs: add filesystem context source name check\n\nIn certain scenarios, for example, during fuzz testing, the source\nname may be NULL, which could lead to a kernel panic. Therefore, an\nextra check for the source name should be added.\n\ud83d\udccf Published: 2025-05-01T13:07:12.944Z\n\ud83d\udccf Modified: 2025-05-02T06:16:20.211Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/b84f13fdad10a543e2e65bab7e81b3f0bceabd67\n2. https://git.kernel.org/stable/c/9d6dcf18a1b49990295ac8a05fd9bdfd27ccbf88\n3. https://git.kernel.org/stable/c/5ee09cdaf3414f6c92960714af46d3d90eede2f3\n4. https://git.kernel.org/stable/c/599d1e2a6aecc44acf22fe7ea6f5e84a7e526abe\n5. https://git.kernel.org/stable/c/f6ec52710dc5e156b774cbef5d0f5c99b1c53a80\n6. https://git.kernel.org/stable/c/c3e31d613951c299487844c4d1686a933e8ee291\n7. https://git.kernel.org/stable/c/a648d80f8d9b208beee03a2d9aa690cfacf1d41e\n8. https://git.kernel.org/stable/c/a94fd938df2b1628da66b498aa0eeb89593bc7a2", "creation_timestamp": "2025-05-02T07:16:30.000000Z"}, {"uuid": "f305e63c-76dd-43e4-a244-e95cbea77582", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37777", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/14457", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-37777\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nksmbd: fix use-after-free in __smb2_lease_break_noti()\n\nMove tcp_transport free to ksmbd_conn_free. If ksmbd connection is\nreferenced when ksmbd server thread terminates, It will not be freed,\nbut conn->tcp_transport is freed. __smb2_lease_break_noti can be performed\nasynchronously when the connection is disconnected. __smb2_lease_break_noti\ncalls ksmbd_conn_write, which can cause use-after-free\nwhen conn->ksmbd_transport is already freed.\n\ud83d\udccf Published: 2025-05-01T13:07:15.741Z\n\ud83d\udccf Modified: 2025-05-02T06:16:21.642Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/1aec4d14cf81b7b3e7b69eb1cfa94144eed7138e\n2. https://git.kernel.org/stable/c/e59796fc80603bcd8569d4d2e10b213c1918edb4\n3. https://git.kernel.org/stable/c/21a4e47578d44c6b37c4fc4aba8ed7cc8dbb13de", "creation_timestamp": "2025-05-02T07:16:29.000000Z"}, {"uuid": "0fe2a569-998f-42fc-a69d-c3a394ee95dd", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3706", "type": "seen", "source": "https://t.me/DarkWebInformer_CVEAlerts/13652", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-3706\n\ud83d\udd25 CVSS Score: 6.1 (cvssV3_1, Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N)\n\ud83d\udd39 Description: The eHRMS from 104 Corporation has a Reflected Cross-site Scripting vulnerability, allowing unauthenticated remote attackers to execute arbitrary JavaScript codes in user's browser through phishing attacks.\n\ud83d\udccf Published: 2025-04-28T02:39:46.515Z\n\ud83d\udccf Modified: 2025-04-28T02:39:46.515Z\n\ud83d\udd17 References:\n1. https://www.twcert.org.tw/tw/cp-132-10079-f0958-1.html\n2. https://www.twcert.org.tw/en/cp-139-10080-31e4b-2.html", "creation_timestamp": "2025-04-28T03:10:47.000000Z"}, {"uuid": "04f95494-f2a2-4502-8367-8873172d1e5c", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37947", "type": "published-proof-of-concept", "source": "https://t.me/thebugbountyhunter/10279", "content": "ksmbd - Exploiting CVE-2025-37947 (3/3) · Doyensec's Blog\n\nhttps://blog.doyensec.com/2025/10/08/ksmbd-3.html", "creation_timestamp": "2025-10-16T08:28:23.000000Z"}, {"uuid": "4af47174-44d1-446a-8dc9-c08bbb84b82b", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37924", "type": "published-proof-of-concept", "source": "Telegram/PZyAgFdjcKEvAOmTbHs0GHmYTdWHIFdf5cfzSlA2BEGv440", "content": "", "creation_timestamp": "2026-04-02T11:19:52.000000Z"}, {"uuid": "7baa3aa7-dd0c-4d55-8d4a-cc02283f390e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37899", "type": "published-proof-of-concept", "source": "Telegram/13Au7FcqCdNlrGOoKeKFoA7_poXYfPBz0gw71j4APaWO7JM", "content": "", "creation_timestamp": "2025-05-25T09:09:54.000000Z"}, {"uuid": "fbcc6be6-6ae2-4050-8e3c-f10879cd1763", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37947", "type": "published-proof-of-concept", "source": "Telegram/P9a0Za8gE6K7y0i_gLeJFZNUx86CaXC4rY9Y1GIdbHAgOlM", "content": "", "creation_timestamp": "2025-10-24T12:28:34.000000Z"}, {"uuid": "8a8ab7e0-1837-4a69-87c0-b3dea54cbd1e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37787", "type": "seen", "source": "https://t.me/DarkWebInformer_CVEAlerts/14456", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-37787\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nnet: dsa: mv88e6xxx: avoid unregistering devlink regions which were never registered\n\nRussell King reports that a system with mv88e6xxx dereferences a NULL\npointer when unbinding this driver:\nhttps://lore.kernel.org/netdev/Z_lRkMlTJ1KQ0kVX@shell.armlinux.org.uk/\n\nThe crash seems to be in devlink_region_destroy(), which is not NULL\ntolerant but is given a NULL devlink global region pointer.\n\nAt least on some chips, some devlink regions are conditionally registered\nsince the blamed commit, see mv88e6xxx_setup_devlink_regions_global():\n\n  if (cond && !cond(chip))\n   continue;\n\nThese are MV88E6XXX_REGION_STU and MV88E6XXX_REGION_PVT. If the chip\ndoes not have an STU or PVT, it should crash like this.\n\nTo fix the issue, avoid unregistering those regions which are NULL, i.e.\nwere skipped at mv88e6xxx_setup_devlink_regions_global() time.\n\ud83d\udccf Published: 2025-05-01T13:07:21.593Z\n\ud83d\udccf Modified: 2025-05-02T06:16:26.935Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/8ccdf5e24b276848eefb2755e05ff0f005a0c4a1\n2. https://git.kernel.org/stable/c/b3c70dfe51f10df60db2646c08cebd24bcdc5247\n3. https://git.kernel.org/stable/c/bbb80f004f7a90c3dcaacc982c59967457254a05\n4. https://git.kernel.org/stable/c/3665695e3572239dc233216f06b41f40cc771889\n5. https://git.kernel.org/stable/c/5f5e95945bb1e08be7655da6acba648274db457d\n6. https://git.kernel.org/stable/c/c84f6ce918a9e6f4996597cbc62536bbf2247c96", "creation_timestamp": "2025-05-02T07:16:26.000000Z"}, {"uuid": "68a31c6b-ab32-4d80-ae05-0489420c6988", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37788", "type": "seen", "source": "https://t.me/DarkWebInformer_CVEAlerts/14455", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-37788\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\ncxgb4: fix memory leak in cxgb4_init_ethtool_filters() error path\n\nIn the for loop used to allocate the loc_array and bmap for each port, a\nmemory leak is possible when the allocation for loc_array succeeds,\nbut the allocation for bmap fails. This is because when the control flow\ngoes to the label free_eth_finfo, only the allocations starting from\n(i-1)th iteration are freed.\n\nFix that by freeing the loc_array in the bmap allocation error path.\n\ud83d\udccf Published: 2025-05-01T13:07:22.208Z\n\ud83d\udccf Modified: 2025-05-02T06:16:27.966Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/e9de08e15aee35b96064960f95997bb6c1209c4b\n2. https://git.kernel.org/stable/c/118d05b530343cd9322607b9719405ba254a4183\n3. https://git.kernel.org/stable/c/fa2d7708955e4f8212fd69bab1da604e60cb0b15\n4. https://git.kernel.org/stable/c/08aa59c0be768596467552c129e9f82166779a67\n5. https://git.kernel.org/stable/c/dafb6e433ab2333b67be05433dc9c6ccbc7b1284\n6. https://git.kernel.org/stable/c/76deedea08899885f076aba0bb80bd1276446822\n7. https://git.kernel.org/stable/c/00ffb3724ce743578163f5ade2884374554ca021", "creation_timestamp": "2025-05-02T07:16:24.000000Z"}, {"uuid": "eb37bb64-2a56-4774-b0dd-8b03a1424793", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3713", "type": "seen", "source": "https://t.me/true_secator/8008", "content": "\u0418\u0441\u0441\u043b\u0435\u0434\u043e\u0432\u0430\u0442\u0435\u043b\u0438 \u0440\u0430\u0441\u043a\u0440\u044b\u043b\u0438 9 \u043a\u0440\u0438\u0442\u0438\u0447\u0435\u0441\u043a\u0438\u0445 \u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u0435\u0439 IP KVM, \u043a\u043e\u0442\u043e\u0440\u044b\u0435 \u043f\u043e\u0437\u0432\u043e\u043b\u044f\u044e\u0442 \u043f\u043e\u043b\u0443\u0447\u0430\u0442\u044c \u043d\u0435\u0441\u0430\u043d\u043a\u0446\u0438\u043e\u043d\u0438\u0440\u043e\u0432\u0430\u043d\u043d\u044b\u0439 \u0434\u043e\u0441\u0442\u0443\u043f \u0441 \u043f\u0440\u0430\u0432\u0430\u043c\u0438 root \u0438 \u043a\u043e\u043d\u0442\u0440\u043e\u043b\u044c \u043d\u0430\u0434 \u0441\u043a\u043e\u043c\u043f\u0440\u043e\u043c\u0435\u0442\u0438\u0440\u043e\u0432\u0430\u043d\u043d\u044b\u043c\u0438 \u0445\u043e\u0441\u0442\u0430\u043c\u0438.\n\n\u0423\u0441\u0442\u0440\u043e\u0439\u0441\u0442\u0432\u0430 IP KVM \u043e\u0431\u0435\u0441\u043f\u0435\u0447\u0438\u0432\u0430\u044e\u0442 \u0443\u0434\u0430\u043b\u0435\u043d\u043d\u044b\u0439 \u0434\u043e\u0441\u0442\u0443\u043f \u043a \u043a\u043b\u0430\u0432\u0438\u0430\u0442\u0443\u0440\u0435, \u0432\u0438\u0434\u0435\u043e\u0432\u044b\u0445\u043e\u0434\u0443 \u0438 \u043c\u044b\u0448\u0438 \u0446\u0435\u043b\u0435\u0432\u043e\u0433\u043e \u043a\u043e\u043c\u043f\u044c\u044e\u0442\u0435\u0440\u0430 \u043d\u0430 \u0443\u0440\u043e\u0432\u043d\u0435 BIOS/UEFI.\n\n\u041e\u0431\u043d\u0430\u0440\u0443\u0436\u0435\u043d\u043d\u044b\u0435 Eclypsium \u043f\u0440\u043e\u0431\u043b\u0435\u043c\u044b \u0437\u0430\u0442\u0440\u0430\u0433\u0438\u0432\u0430\u044e\u0442 \u0447\u0435\u0442\u044b\u0440\u0435 \u0440\u0430\u0437\u043b\u0438\u0447\u043d\u044b\u0445 \u043f\u0440\u043e\u0434\u0443\u043a\u0442\u0430: GL-iNet Comet RM-1, Angeet/Yeeso ES3 KVM, Sipeed NanoKVM \u0438 JetKVM. \u041d\u0430\u0438\u0431\u043e\u043b\u0435\u0435 \u0441\u0435\u0440\u044c\u0435\u0437\u043d\u044b\u0435 \u0438\u0437 \u043d\u0438\u0445 \u043f\u043e\u0437\u0432\u043e\u043b\u044f\u044e\u0442 \u043d\u0435\u0430\u0432\u0442\u043e\u0440\u0438\u0437\u043e\u0432\u0430\u043d\u043d\u044b\u043c \u043f\u043e\u043b\u044c\u0437\u043e\u0432\u0430\u0442\u0435\u043b\u044f\u043c \u043f\u043e\u043b\u0443\u0447\u0438\u0442\u044c root-\u0434\u043e\u0441\u0442\u0443\u043f \u0438\u043b\u0438 \u0437\u0430\u043f\u0443\u0441\u0442\u0438\u0442\u044c \u0432\u0440\u0435\u0434\u043e\u043d\u043e\u0441\u043d\u044b\u0439 \u043a\u043e\u0434.\n\n\u0421\u0440\u0435\u0434\u0438 \u043e\u0431\u0449\u0438\u0445 \u0434\u0435\u0444\u0435\u043a\u0442\u043e\u0432 \u0438\u0441\u0441\u043b\u0435\u0434\u043e\u0432\u0430\u0442\u0435\u043b\u0438 \u0432\u044b\u0434\u0435\u043b\u0438\u043b\u0438: \u043e\u0442\u0441\u0443\u0442\u0441\u0442\u0432\u0438\u0435 \u043f\u0440\u043e\u0432\u0435\u0440\u043a\u0438 \u043f\u043e\u0434\u043f\u0438\u0441\u0438 \u043f\u0440\u043e\u0448\u0438\u0432\u043a\u0438, \u043e\u0442\u0441\u0443\u0442\u0441\u0442\u0432\u0438\u0435 \u0437\u0430\u0449\u0438\u0442\u044b \u043e\u0442 \u0431\u0440\u0443\u0442\u0430, \u043d\u0435\u0440\u0430\u0431\u043e\u0442\u0430\u044e\u0449\u0438\u0435 \u043c\u0435\u0445\u0430\u043d\u0438\u0437\u043c\u044b \u043a\u043e\u043d\u0442\u0440\u043e\u043b\u044f \u0434\u043e\u0441\u0442\u0443\u043f\u0430 \u0438 \u043e\u0442\u043a\u0440\u044b\u0442\u044b\u0435 \u0438\u043d\u0442\u0435\u0440\u0444\u0435\u0439\u0441\u044b \u043e\u0442\u043b\u0430\u0434\u043a\u0438, \u0430 \u0438\u0445 \u043f\u0435\u0440\u0435\u0447\u0435\u043d\u044c \u0432\u044b\u0433\u043b\u044f\u0434\u0438\u0442 \u0441\u043b\u0435\u0434\u0443\u044e\u0449\u0438\u043c \u043e\u0431\u0440\u0430\u0437\u043e\u043c:\n\n- CVE-2026-32290\u00a0(CVSS: 4.2): \u043d\u0435\u0434\u043e\u0441\u0442\u0430\u0442\u043e\u0447\u043d\u0430\u044f \u043f\u0440\u043e\u0432\u0435\u0440\u043a\u0430 \u043f\u043e\u0434\u043b\u0438\u043d\u043d\u043e\u0441\u0442\u0438 \u043f\u0440\u043e\u0448\u0438\u0432\u043a\u0438 \u0432 KVM-\u043f\u0435\u0440\u0435\u043a\u043b\u044e\u0447\u0430\u0442\u0435\u043b\u0435 GL-iNet Comet (\u043f\u043b\u0430\u043d\u0438\u0440\u0443\u0435\u0442\u0441\u044f \u0438\u0441\u043f\u0440\u0430\u0432\u043b\u0435\u043d\u0438\u0435);\n\n- CVE-2026-32291\u00a0(CVSS: 7.6): \u043f\u0440\u043e\u0431\u043b\u0435\u043c\u0430 \u0434\u043e\u0441\u0442\u0443\u043f\u0430 \u043a \u043a\u043e\u0440\u043d\u0435\u0432\u043e\u043c\u0443 \u043a\u0430\u0442\u0430\u043b\u043e\u0433\u0443 \u0443\u043d\u0438\u0432\u0435\u0440\u0441\u0430\u043b\u044c\u043d\u043e\u0433\u043e \u0430\u0441\u0438\u043d\u0445\u0440\u043e\u043d\u043d\u043e\u0433\u043e \u043f\u0440\u0438\u0435\u043c\u043e\u043f\u0435\u0440\u0435\u0434\u0430\u0442\u0447\u0438\u043a\u0430 (UART) \u0432 KVM-\u0441\u0435\u0440\u0432\u0435\u0440\u0435 GL-iNet Comet (\u043f\u043b\u0430\u043d\u0438\u0440\u0443\u0435\u0442\u0441\u044f \u0438\u0441\u043f\u0440\u0430\u0432\u043b\u0435\u043d\u0438\u0435);\n\n- CVE-2026-32292\u00a0(CVSS: 5.3): \u043d\u0435\u0434\u043e\u0441\u0442\u0430\u0442\u043e\u0447\u043d\u0430\u044f \u0437\u0430\u0449\u0438\u0442\u0430 \u043e\u0442 \u0431\u0440\u0443\u0442-\u0430\u0442\u0430\u043a \u0432 GL-iNet Comet KVM (\u0438\u0441\u043f\u0440\u0430\u0432\u043b\u0435\u043d\u043e \u0432 \u0432\u0435\u0440\u0441\u0438\u0438 1.8.1 BETA);\n\n- CVE-2026-32293\u00a0(CVSS: 3.1): \u043d\u0435\u0431\u0435\u0437\u043e\u043f\u0430\u0441\u043d\u043e\u0435 \u043f\u0435\u0440\u0432\u043e\u043d\u0430\u0447\u0430\u043b\u044c\u043d\u043e\u0435 \u0432\u044b\u0434\u0435\u043b\u0435\u043d\u0438\u0435 \u0440\u0435\u0441\u0443\u0440\u0441\u043e\u0432 \u0447\u0435\u0440\u0435\u0437 \u043d\u0435\u0430\u0443\u0442\u0435\u043d\u0442\u0438\u0444\u0438\u0446\u0438\u0440\u043e\u0432\u0430\u043d\u043d\u043e\u0435 \u043e\u0431\u043b\u0430\u0447\u043d\u043e\u0435 \u0441\u043e\u0435\u0434\u0438\u043d\u0435\u043d\u0438\u0435 \u0432 GL-iNet Comet KVM (\u0438\u0441\u043f\u0440\u0430\u0432\u043b\u0435\u043d\u043e \u0432 \u0432\u0435\u0440\u0441\u0438\u0438 1.8.1 BETA);\n\n- CVE-2026-32294\u00a0(CVSS: 6.7): \u043d\u0435\u0434\u043e\u0441\u0442\u0430\u0442\u043e\u0447\u043d\u0430\u044f \u043f\u0440\u043e\u0432\u0435\u0440\u043a\u0430 \u043e\u0431\u043d\u043e\u0432\u043b\u0435\u043d\u0438\u0439 \u0432 JetKVM (\u0438\u0441\u043f\u0440\u0430\u0432\u043b\u0435\u043d\u043e \u0432 \u0432\u0435\u0440\u0441\u0438\u0438 0.5.4);\n\n- CVE-2026-32295\u00a0(CVSS: 7.3): \u043d\u0435\u0434\u043e\u0441\u0442\u0430\u0442\u043e\u0447\u043d\u043e\u0435 \u043e\u0433\u0440\u0430\u043d\u0438\u0447\u0435\u043d\u0438\u0435 \u0441\u043a\u043e\u0440\u043e\u0441\u0442\u0438 \u0437\u0430\u043f\u0440\u043e\u0441\u043e\u0432 \u0432 JetKVM (\u0438\u0441\u043f\u0440\u0430\u0432\u043b\u0435\u043d\u043e \u0432 \u0432\u0435\u0440\u0441\u0438\u0438 0.5.4);\n\n- CVE-2026-32296\u00a0(CVSS: 5.4): \u0440\u0430\u0441\u043a\u0440\u044b\u0442\u0438\u0435 \u043a\u043e\u043d\u0444\u0438\u0433\u0443\u0440\u0430\u0446\u0438\u0438 \u043a\u043e\u043d\u0435\u0447\u043d\u043e\u0439 \u0442\u043e\u0447\u043a\u0438 \u0432 Sipeed NanoKVM (\u0438\u0441\u043f\u0440\u0430\u0432\u043b\u0435\u043d\u043e \u0432 NanoKVM \u0432\u0435\u0440\u0441\u0438\u0438 2.3.1 \u0438 Pro 1.2.4);\n\n- CVE-2026-32297\u00a0(CVSS: 9.8): \u043e\u0442\u0441\u0443\u0442\u0441\u0442\u0432\u0438\u0435 \u0430\u0443\u0442\u0435\u043d\u0442\u0438\u0444\u0438\u043a\u0430\u0446\u0438\u0438 \u0434\u043b\u044f \u043a\u0440\u0438\u0442\u0438\u0447\u0435\u0441\u043a\u043e\u0439 \u0444\u0443\u043d\u043a\u0446\u0438\u0438 \u0432 Angeet ES3 KVM, \u043f\u0440\u0438\u0432\u043e\u0434\u044f\u0449\u0430\u044f \u043a RCE (\u0438\u0441\u043f\u0440\u0430\u0432\u043b\u0435\u043d\u0438\u0435 \u043e\u0442\u0441\u0443\u0442\u0441\u0442\u0432\u0443\u0435\u0442);\n\n- CVE-2026-32298\u00a0(CVSS: 8.8): \u0432\u043d\u0435\u0434\u0440\u0435\u043d\u0438\u0435 \u043a\u043e\u043c\u0430\u043d\u0434 \u041e\u0421 \u0432 Angeet ES3 KVM (\u0438\u0441\u043f\u0440\u0430\u0432\u043b\u0435\u043d\u0438\u0435 \u043e\u0442\u0441\u0443\u0442\u0441\u0442\u0432\u0443\u0435\u0442).\n\n\u041a\u0430\u043a \u043e\u0442\u043c\u0435\u0447\u0430\u0435\u0442 \u0438\u0441\u0441\u043b\u0435\u0434\u043e\u0432\u0430\u0442\u0435\u043b\u0438, \u044d\u0442\u043e \u043d\u0435 \u043a\u0430\u043a\u0438\u0435-\u0442\u043e \u044d\u043a\u0437\u043e\u0442\u0438\u0447\u0435\u0441\u043a\u0438\u0435 0-day, \u0430 \u043f\u0440\u043e\u0441\u0447\u0435\u0442\u044b \u0432 \u0444\u0443\u043d\u0434\u0430\u043c\u0435\u043d\u0442\u0430\u043b\u044c\u043d\u044b\u0445 \u043c\u0435\u0440\u0430\u0445 \u0431\u0435\u0437\u043e\u043f\u0430\u0441\u043d\u043e\u0441\u0442\u0438, \u043a\u043e\u0442\u043e\u0440\u044b\u0435 \u0434\u043e\u043b\u0436\u043d\u044b \u0431\u044b\u0442\u044c \u0440\u0435\u0430\u043b\u0438\u0437\u043e\u0432\u0430\u043d\u044b \u043d\u0430 \u043b\u044e\u0431\u043e\u043c \u0441\u0435\u0442\u0435\u0432\u043e\u043c \u0443\u0441\u0442\u0440\u043e\u0439\u0441\u0442\u0432\u0435.\n\n\u0417\u043b\u043e\u0443\u043c\u044b\u0448\u043b\u0435\u043d\u043d\u0438\u043a \u043c\u043e\u0436\u0435\u0442 \u0438\u0441\u043f\u043e\u043b\u044c\u0437\u043e\u0432\u0430\u0442\u044c \u044d\u0442\u0438 \u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u0438 \u0434\u043b\u044f \u0432\u043d\u0435\u0434\u0440\u0435\u043d\u0438\u044f \u043d\u0430\u0436\u0430\u0442\u0438\u0439 \u043a\u043b\u0430\u0432\u0438\u0448, \u0437\u0430\u0433\u0440\u0443\u0437\u043a\u0438 \u0441\u043e \u0441\u044a\u0435\u043c\u043d\u044b\u0445 \u043d\u043e\u0441\u0438\u0442\u0435\u043b\u0435\u0439 \u0441 \u0446\u0435\u043b\u044c\u044e \u043e\u0431\u0445\u043e\u0434\u0430 \u0448\u0438\u0444\u0440\u043e\u0432\u0430\u043d\u0438\u044f \u0434\u0438\u0441\u043a\u0430 \u0438\u043b\u0438 \u0437\u0430\u0449\u0438\u0442\u044b Secure Boot, \u043e\u0431\u0445\u043e\u0434\u0430 \u044d\u043a\u0440\u0430\u043d\u043e\u0432 \u0431\u043b\u043e\u043a\u0438\u0440\u043e\u0432\u043a\u0438 \u0438 \u0434\u043e\u0441\u0442\u0443\u043f\u0430 \u043a \u0441\u0438\u0441\u0442\u0435\u043c\u0430\u043c, \u0438, \u0447\u0442\u043e \u0431\u043e\u043b\u0435\u0435 \u0432\u0430\u0436\u043d\u043e, \u043e\u0441\u0442\u0430\u0432\u0430\u0442\u044c\u0441\u044f \u043d\u0435\u0437\u0430\u043c\u0435\u0447\u0435\u043d\u043d\u044b\u043c \u041f\u041e \u0431\u0435\u0437\u043e\u043f\u0430\u0441\u043d\u043e\u0441\u0442\u0438, \u0443\u0441\u0442\u0430\u043d\u043e\u0432\u043b\u0435\u043d\u043d\u044b\u043c \u043d\u0430 \u0443\u0440\u043e\u0432\u043d\u0435 \u041e\u0421.\n\n\u041f\u0440\u0438\u0447\u0435\u043c, \u044d\u0442\u043e \u0443\u0436\u0435 \u043d\u0435 \u043f\u0435\u0440\u0432\u044b\u0439 \u0441\u043b\u0443\u0447\u0430\u0439 \u043e\u0431\u043d\u0430\u0440\u0443\u0436\u0435\u043d\u0438\u044f \u043f\u0440\u043e\u0431\u043b\u0435\u043c \u0432 IP KVM-\u0443\u0441\u0442\u0440\u043e\u0439\u0441\u0442\u0432\u0430\u0445. \u0422\u0430\u043a, \u0432 \u0438\u044e\u043b\u0435 2025 \u0433\u043e\u0434\u0430 Positive Technologies \u0432\u044b\u044f\u0432\u043b\u044f\u043b\u0430 \u043f\u044f\u0442\u044c \u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u0435\u0439\u00a0\u0432 \u043a\u043e\u043c\u043c\u0443\u0442\u0430\u0442\u043e\u0440\u0430\u0445 ATEN International (CVE-2025-3710, CVE-2025-3711, CVE-2025-3712, CVE-2025-3713 \u0438 CVE-2025-3714), \u043a\u043e\u0442\u043e\u0440\u044b\u0435 \u043c\u043e\u0433\u043b\u0438 \u043f\u0440\u0438\u0432\u0435\u0441\u0442\u0438 \u043a DoS \u0438 RCE.\n\n\u0412 \u043a\u0430\u0447\u0435\u0441\u0442\u0432\u0435 \u043c\u0435\u0440 \u043f\u043e \u0441\u043d\u0438\u0436\u0435\u043d\u0438\u044e \u0440\u0438\u0441\u043a\u043e\u0432 \u0440\u0435\u043a\u043e\u043c\u0435\u043d\u0434\u0443\u0435\u0442\u0441\u044f \u0432\u043d\u0435\u0434\u0440\u0438\u0442\u044c MFa \u0442\u0430\u043c, \u0433\u0434\u0435 \u044d\u0442\u043e \u043f\u043e\u0434\u0434\u0435\u0440\u0436\u0438\u0432\u0430\u0435\u0442\u0441\u044f, \u0438\u0437\u043e\u043b\u0438\u0440\u043e\u0432\u0430\u0442\u044c KVM-\u0443\u0441\u0442\u0440\u043e\u0439\u0441\u0442\u0432\u0430 \u0432 \u0432\u044b\u0434\u0435\u043b\u0435\u043d\u043d\u043e\u0439 \u0443\u043f\u0440\u0430\u0432\u043b\u044f\u044e\u0449\u0435\u0439 VLAN, \u043e\u0433\u0440\u0430\u043d\u0438\u0447\u0438\u0442\u044c \u0434\u043e\u0441\u0442\u0443\u043f \u0432 \u0418\u043d\u0442\u0435\u0440\u043d\u0435\u0442, \u0438\u0441\u043f\u043e\u043b\u044c\u0437\u043e\u0432\u0430\u0442\u044c \u0442\u0430\u043a\u0438\u0435 \u0438\u043d\u0441\u0442\u0440\u0443\u043c\u0435\u043d\u0442\u044b, \u043a\u0430\u043a Shodan, \u0434\u043b\u044f \u043f\u0440\u043e\u0432\u0435\u0440\u043a\u0438 \u043d\u0430 \u043d\u0430\u043b\u0438\u0447\u0438\u0435 \u0432\u043d\u0435\u0448\u043d\u0438\u0445 \u0443\u0433\u0440\u043e\u0437, \u043e\u0442\u0441\u043b\u0435\u0436\u0438\u0432\u0430\u0442\u044c \u043d\u0435\u043e\u0436\u0438\u0434\u0430\u043d\u043d\u044b\u0439 \u0441\u0435\u0442\u0435\u0432\u043e\u0439 \u0442\u0440\u0430\u0444\u0438\u043a \u043a/\u043e\u0442 \u0443\u0441\u0442\u0440\u043e\u0439\u0441\u0442\u0432 \u0438 \u043f\u043e\u0434\u0434\u0435\u0440\u0436\u0438\u0432\u0430\u0442\u044c \u043f\u0440\u043e\u0448\u0438\u0432\u043a\u0443 \u0432 \u0430\u043a\u0442\u0443\u0430\u043b\u044c\u043d\u043e\u043c \u0441\u043e\u0441\u0442\u043e\u044f\u043d\u0438\u0438.\n\n\u0412\u0435\u0434\u044c, \u043a\u0430\u043a \u0437\u0430\u044f\u0432\u043b\u044f\u044e\u0442 \u0432 Eclypsium, \u0437\u043b\u043e\u0443\u043c\u044b\u0448\u043b\u0435\u043d\u043d\u0438\u043a, \u0432\u0437\u043b\u043e\u043c\u0430\u0432\u0448\u0438\u0439 KVM-\u043f\u0435\u0440\u0435\u043a\u043b\u044e\u0447\u0430\u0442\u0435\u043b\u044c, \u0441\u043f\u043e\u0441\u043e\u0431\u0435\u043d \u0441\u043a\u0440\u044b\u0432\u0430\u0442\u044c \u0438\u043d\u0441\u0442\u0440\u0443\u043c\u0435\u043d\u0442\u044b \u0438 \u0431\u044d\u043a\u0434\u043e\u0440\u044b \u043d\u0430 \u0441\u0430\u043c\u043e\u043c \u0443\u0441\u0442\u0440\u043e\u0439\u0441\u0442\u0432\u0435, \u043f\u043e\u0432\u0442\u043e\u0440\u043d\u043e \u0437\u0430\u0440\u0430\u0436\u0430\u044f \u0445\u043e\u0441\u0442-\u0441\u0438\u0441\u0442\u0435\u043c\u044b \u0434\u0430\u0436\u0435 \u043f\u043e\u0441\u043b\u0435 \u0443\u0441\u0442\u0440\u0430\u043d\u0435\u043d\u0438\u044f \u043f\u0440\u043e\u0431\u043b\u0435\u043c\u044b.", "creation_timestamp": "2026-03-18T17:04:14.000000Z"}, {"uuid": "af008b17-b5aa-433f-89f7-f5812af3fd5e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3712", "type": "seen", "source": "https://t.me/true_secator/8008", "content": "\u0418\u0441\u0441\u043b\u0435\u0434\u043e\u0432\u0430\u0442\u0435\u043b\u0438 \u0440\u0430\u0441\u043a\u0440\u044b\u043b\u0438 9 \u043a\u0440\u0438\u0442\u0438\u0447\u0435\u0441\u043a\u0438\u0445 \u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u0435\u0439 IP KVM, \u043a\u043e\u0442\u043e\u0440\u044b\u0435 \u043f\u043e\u0437\u0432\u043e\u043b\u044f\u044e\u0442 \u043f\u043e\u043b\u0443\u0447\u0430\u0442\u044c \u043d\u0435\u0441\u0430\u043d\u043a\u0446\u0438\u043e\u043d\u0438\u0440\u043e\u0432\u0430\u043d\u043d\u044b\u0439 \u0434\u043e\u0441\u0442\u0443\u043f \u0441 \u043f\u0440\u0430\u0432\u0430\u043c\u0438 root \u0438 \u043a\u043e\u043d\u0442\u0440\u043e\u043b\u044c \u043d\u0430\u0434 \u0441\u043a\u043e\u043c\u043f\u0440\u043e\u043c\u0435\u0442\u0438\u0440\u043e\u0432\u0430\u043d\u043d\u044b\u043c\u0438 \u0445\u043e\u0441\u0442\u0430\u043c\u0438.\n\n\u0423\u0441\u0442\u0440\u043e\u0439\u0441\u0442\u0432\u0430 IP KVM \u043e\u0431\u0435\u0441\u043f\u0435\u0447\u0438\u0432\u0430\u044e\u0442 \u0443\u0434\u0430\u043b\u0435\u043d\u043d\u044b\u0439 \u0434\u043e\u0441\u0442\u0443\u043f \u043a \u043a\u043b\u0430\u0432\u0438\u0430\u0442\u0443\u0440\u0435, \u0432\u0438\u0434\u0435\u043e\u0432\u044b\u0445\u043e\u0434\u0443 \u0438 \u043c\u044b\u0448\u0438 \u0446\u0435\u043b\u0435\u0432\u043e\u0433\u043e \u043a\u043e\u043c\u043f\u044c\u044e\u0442\u0435\u0440\u0430 \u043d\u0430 \u0443\u0440\u043e\u0432\u043d\u0435 BIOS/UEFI.\n\n\u041e\u0431\u043d\u0430\u0440\u0443\u0436\u0435\u043d\u043d\u044b\u0435 Eclypsium \u043f\u0440\u043e\u0431\u043b\u0435\u043c\u044b \u0437\u0430\u0442\u0440\u0430\u0433\u0438\u0432\u0430\u044e\u0442 \u0447\u0435\u0442\u044b\u0440\u0435 \u0440\u0430\u0437\u043b\u0438\u0447\u043d\u044b\u0445 \u043f\u0440\u043e\u0434\u0443\u043a\u0442\u0430: GL-iNet Comet RM-1, Angeet/Yeeso ES3 KVM, Sipeed NanoKVM \u0438 JetKVM. \u041d\u0430\u0438\u0431\u043e\u043b\u0435\u0435 \u0441\u0435\u0440\u044c\u0435\u0437\u043d\u044b\u0435 \u0438\u0437 \u043d\u0438\u0445 \u043f\u043e\u0437\u0432\u043e\u043b\u044f\u044e\u0442 \u043d\u0435\u0430\u0432\u0442\u043e\u0440\u0438\u0437\u043e\u0432\u0430\u043d\u043d\u044b\u043c \u043f\u043e\u043b\u044c\u0437\u043e\u0432\u0430\u0442\u0435\u043b\u044f\u043c \u043f\u043e\u043b\u0443\u0447\u0438\u0442\u044c root-\u0434\u043e\u0441\u0442\u0443\u043f \u0438\u043b\u0438 \u0437\u0430\u043f\u0443\u0441\u0442\u0438\u0442\u044c \u0432\u0440\u0435\u0434\u043e\u043d\u043e\u0441\u043d\u044b\u0439 \u043a\u043e\u0434.\n\n\u0421\u0440\u0435\u0434\u0438 \u043e\u0431\u0449\u0438\u0445 \u0434\u0435\u0444\u0435\u043a\u0442\u043e\u0432 \u0438\u0441\u0441\u043b\u0435\u0434\u043e\u0432\u0430\u0442\u0435\u043b\u0438 \u0432\u044b\u0434\u0435\u043b\u0438\u043b\u0438: \u043e\u0442\u0441\u0443\u0442\u0441\u0442\u0432\u0438\u0435 \u043f\u0440\u043e\u0432\u0435\u0440\u043a\u0438 \u043f\u043e\u0434\u043f\u0438\u0441\u0438 \u043f\u0440\u043e\u0448\u0438\u0432\u043a\u0438, \u043e\u0442\u0441\u0443\u0442\u0441\u0442\u0432\u0438\u0435 \u0437\u0430\u0449\u0438\u0442\u044b \u043e\u0442 \u0431\u0440\u0443\u0442\u0430, \u043d\u0435\u0440\u0430\u0431\u043e\u0442\u0430\u044e\u0449\u0438\u0435 \u043c\u0435\u0445\u0430\u043d\u0438\u0437\u043c\u044b \u043a\u043e\u043d\u0442\u0440\u043e\u043b\u044f \u0434\u043e\u0441\u0442\u0443\u043f\u0430 \u0438 \u043e\u0442\u043a\u0440\u044b\u0442\u044b\u0435 \u0438\u043d\u0442\u0435\u0440\u0444\u0435\u0439\u0441\u044b \u043e\u0442\u043b\u0430\u0434\u043a\u0438, \u0430 \u0438\u0445 \u043f\u0435\u0440\u0435\u0447\u0435\u043d\u044c \u0432\u044b\u0433\u043b\u044f\u0434\u0438\u0442 \u0441\u043b\u0435\u0434\u0443\u044e\u0449\u0438\u043c \u043e\u0431\u0440\u0430\u0437\u043e\u043c:\n\n- CVE-2026-32290\u00a0(CVSS: 4.2): \u043d\u0435\u0434\u043e\u0441\u0442\u0430\u0442\u043e\u0447\u043d\u0430\u044f \u043f\u0440\u043e\u0432\u0435\u0440\u043a\u0430 \u043f\u043e\u0434\u043b\u0438\u043d\u043d\u043e\u0441\u0442\u0438 \u043f\u0440\u043e\u0448\u0438\u0432\u043a\u0438 \u0432 KVM-\u043f\u0435\u0440\u0435\u043a\u043b\u044e\u0447\u0430\u0442\u0435\u043b\u0435 GL-iNet Comet (\u043f\u043b\u0430\u043d\u0438\u0440\u0443\u0435\u0442\u0441\u044f \u0438\u0441\u043f\u0440\u0430\u0432\u043b\u0435\u043d\u0438\u0435);\n\n- CVE-2026-32291\u00a0(CVSS: 7.6): \u043f\u0440\u043e\u0431\u043b\u0435\u043c\u0430 \u0434\u043e\u0441\u0442\u0443\u043f\u0430 \u043a \u043a\u043e\u0440\u043d\u0435\u0432\u043e\u043c\u0443 \u043a\u0430\u0442\u0430\u043b\u043e\u0433\u0443 \u0443\u043d\u0438\u0432\u0435\u0440\u0441\u0430\u043b\u044c\u043d\u043e\u0433\u043e \u0430\u0441\u0438\u043d\u0445\u0440\u043e\u043d\u043d\u043e\u0433\u043e \u043f\u0440\u0438\u0435\u043c\u043e\u043f\u0435\u0440\u0435\u0434\u0430\u0442\u0447\u0438\u043a\u0430 (UART) \u0432 KVM-\u0441\u0435\u0440\u0432\u0435\u0440\u0435 GL-iNet Comet (\u043f\u043b\u0430\u043d\u0438\u0440\u0443\u0435\u0442\u0441\u044f \u0438\u0441\u043f\u0440\u0430\u0432\u043b\u0435\u043d\u0438\u0435);\n\n- CVE-2026-32292\u00a0(CVSS: 5.3): \u043d\u0435\u0434\u043e\u0441\u0442\u0430\u0442\u043e\u0447\u043d\u0430\u044f \u0437\u0430\u0449\u0438\u0442\u0430 \u043e\u0442 \u0431\u0440\u0443\u0442-\u0430\u0442\u0430\u043a \u0432 GL-iNet Comet KVM (\u0438\u0441\u043f\u0440\u0430\u0432\u043b\u0435\u043d\u043e \u0432 \u0432\u0435\u0440\u0441\u0438\u0438 1.8.1 BETA);\n\n- CVE-2026-32293\u00a0(CVSS: 3.1): \u043d\u0435\u0431\u0435\u0437\u043e\u043f\u0430\u0441\u043d\u043e\u0435 \u043f\u0435\u0440\u0432\u043e\u043d\u0430\u0447\u0430\u043b\u044c\u043d\u043e\u0435 \u0432\u044b\u0434\u0435\u043b\u0435\u043d\u0438\u0435 \u0440\u0435\u0441\u0443\u0440\u0441\u043e\u0432 \u0447\u0435\u0440\u0435\u0437 \u043d\u0435\u0430\u0443\u0442\u0435\u043d\u0442\u0438\u0444\u0438\u0446\u0438\u0440\u043e\u0432\u0430\u043d\u043d\u043e\u0435 \u043e\u0431\u043b\u0430\u0447\u043d\u043e\u0435 \u0441\u043e\u0435\u0434\u0438\u043d\u0435\u043d\u0438\u0435 \u0432 GL-iNet Comet KVM (\u0438\u0441\u043f\u0440\u0430\u0432\u043b\u0435\u043d\u043e \u0432 \u0432\u0435\u0440\u0441\u0438\u0438 1.8.1 BETA);\n\n- CVE-2026-32294\u00a0(CVSS: 6.7): \u043d\u0435\u0434\u043e\u0441\u0442\u0430\u0442\u043e\u0447\u043d\u0430\u044f \u043f\u0440\u043e\u0432\u0435\u0440\u043a\u0430 \u043e\u0431\u043d\u043e\u0432\u043b\u0435\u043d\u0438\u0439 \u0432 JetKVM (\u0438\u0441\u043f\u0440\u0430\u0432\u043b\u0435\u043d\u043e \u0432 \u0432\u0435\u0440\u0441\u0438\u0438 0.5.4);\n\n- CVE-2026-32295\u00a0(CVSS: 7.3): \u043d\u0435\u0434\u043e\u0441\u0442\u0430\u0442\u043e\u0447\u043d\u043e\u0435 \u043e\u0433\u0440\u0430\u043d\u0438\u0447\u0435\u043d\u0438\u0435 \u0441\u043a\u043e\u0440\u043e\u0441\u0442\u0438 \u0437\u0430\u043f\u0440\u043e\u0441\u043e\u0432 \u0432 JetKVM (\u0438\u0441\u043f\u0440\u0430\u0432\u043b\u0435\u043d\u043e \u0432 \u0432\u0435\u0440\u0441\u0438\u0438 0.5.4);\n\n- CVE-2026-32296\u00a0(CVSS: 5.4): \u0440\u0430\u0441\u043a\u0440\u044b\u0442\u0438\u0435 \u043a\u043e\u043d\u0444\u0438\u0433\u0443\u0440\u0430\u0446\u0438\u0438 \u043a\u043e\u043d\u0435\u0447\u043d\u043e\u0439 \u0442\u043e\u0447\u043a\u0438 \u0432 Sipeed NanoKVM (\u0438\u0441\u043f\u0440\u0430\u0432\u043b\u0435\u043d\u043e \u0432 NanoKVM \u0432\u0435\u0440\u0441\u0438\u0438 2.3.1 \u0438 Pro 1.2.4);\n\n- CVE-2026-32297\u00a0(CVSS: 9.8): \u043e\u0442\u0441\u0443\u0442\u0441\u0442\u0432\u0438\u0435 \u0430\u0443\u0442\u0435\u043d\u0442\u0438\u0444\u0438\u043a\u0430\u0446\u0438\u0438 \u0434\u043b\u044f \u043a\u0440\u0438\u0442\u0438\u0447\u0435\u0441\u043a\u043e\u0439 \u0444\u0443\u043d\u043a\u0446\u0438\u0438 \u0432 Angeet ES3 KVM, \u043f\u0440\u0438\u0432\u043e\u0434\u044f\u0449\u0430\u044f \u043a RCE (\u0438\u0441\u043f\u0440\u0430\u0432\u043b\u0435\u043d\u0438\u0435 \u043e\u0442\u0441\u0443\u0442\u0441\u0442\u0432\u0443\u0435\u0442);\n\n- CVE-2026-32298\u00a0(CVSS: 8.8): \u0432\u043d\u0435\u0434\u0440\u0435\u043d\u0438\u0435 \u043a\u043e\u043c\u0430\u043d\u0434 \u041e\u0421 \u0432 Angeet ES3 KVM (\u0438\u0441\u043f\u0440\u0430\u0432\u043b\u0435\u043d\u0438\u0435 \u043e\u0442\u0441\u0443\u0442\u0441\u0442\u0432\u0443\u0435\u0442).\n\n\u041a\u0430\u043a \u043e\u0442\u043c\u0435\u0447\u0430\u0435\u0442 \u0438\u0441\u0441\u043b\u0435\u0434\u043e\u0432\u0430\u0442\u0435\u043b\u0438, \u044d\u0442\u043e \u043d\u0435 \u043a\u0430\u043a\u0438\u0435-\u0442\u043e \u044d\u043a\u0437\u043e\u0442\u0438\u0447\u0435\u0441\u043a\u0438\u0435 0-day, \u0430 \u043f\u0440\u043e\u0441\u0447\u0435\u0442\u044b \u0432 \u0444\u0443\u043d\u0434\u0430\u043c\u0435\u043d\u0442\u0430\u043b\u044c\u043d\u044b\u0445 \u043c\u0435\u0440\u0430\u0445 \u0431\u0435\u0437\u043e\u043f\u0430\u0441\u043d\u043e\u0441\u0442\u0438, \u043a\u043e\u0442\u043e\u0440\u044b\u0435 \u0434\u043e\u043b\u0436\u043d\u044b \u0431\u044b\u0442\u044c \u0440\u0435\u0430\u043b\u0438\u0437\u043e\u0432\u0430\u043d\u044b \u043d\u0430 \u043b\u044e\u0431\u043e\u043c \u0441\u0435\u0442\u0435\u0432\u043e\u043c \u0443\u0441\u0442\u0440\u043e\u0439\u0441\u0442\u0432\u0435.\n\n\u0417\u043b\u043e\u0443\u043c\u044b\u0448\u043b\u0435\u043d\u043d\u0438\u043a \u043c\u043e\u0436\u0435\u0442 \u0438\u0441\u043f\u043e\u043b\u044c\u0437\u043e\u0432\u0430\u0442\u044c \u044d\u0442\u0438 \u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u0438 \u0434\u043b\u044f \u0432\u043d\u0435\u0434\u0440\u0435\u043d\u0438\u044f \u043d\u0430\u0436\u0430\u0442\u0438\u0439 \u043a\u043b\u0430\u0432\u0438\u0448, \u0437\u0430\u0433\u0440\u0443\u0437\u043a\u0438 \u0441\u043e \u0441\u044a\u0435\u043c\u043d\u044b\u0445 \u043d\u043e\u0441\u0438\u0442\u0435\u043b\u0435\u0439 \u0441 \u0446\u0435\u043b\u044c\u044e \u043e\u0431\u0445\u043e\u0434\u0430 \u0448\u0438\u0444\u0440\u043e\u0432\u0430\u043d\u0438\u044f \u0434\u0438\u0441\u043a\u0430 \u0438\u043b\u0438 \u0437\u0430\u0449\u0438\u0442\u044b Secure Boot, \u043e\u0431\u0445\u043e\u0434\u0430 \u044d\u043a\u0440\u0430\u043d\u043e\u0432 \u0431\u043b\u043e\u043a\u0438\u0440\u043e\u0432\u043a\u0438 \u0438 \u0434\u043e\u0441\u0442\u0443\u043f\u0430 \u043a \u0441\u0438\u0441\u0442\u0435\u043c\u0430\u043c, \u0438, \u0447\u0442\u043e \u0431\u043e\u043b\u0435\u0435 \u0432\u0430\u0436\u043d\u043e, \u043e\u0441\u0442\u0430\u0432\u0430\u0442\u044c\u0441\u044f \u043d\u0435\u0437\u0430\u043c\u0435\u0447\u0435\u043d\u043d\u044b\u043c \u041f\u041e \u0431\u0435\u0437\u043e\u043f\u0430\u0441\u043d\u043e\u0441\u0442\u0438, \u0443\u0441\u0442\u0430\u043d\u043e\u0432\u043b\u0435\u043d\u043d\u044b\u043c \u043d\u0430 \u0443\u0440\u043e\u0432\u043d\u0435 \u041e\u0421.\n\n\u041f\u0440\u0438\u0447\u0435\u043c, \u044d\u0442\u043e \u0443\u0436\u0435 \u043d\u0435 \u043f\u0435\u0440\u0432\u044b\u0439 \u0441\u043b\u0443\u0447\u0430\u0439 \u043e\u0431\u043d\u0430\u0440\u0443\u0436\u0435\u043d\u0438\u044f \u043f\u0440\u043e\u0431\u043b\u0435\u043c \u0432 IP KVM-\u0443\u0441\u0442\u0440\u043e\u0439\u0441\u0442\u0432\u0430\u0445. \u0422\u0430\u043a, \u0432 \u0438\u044e\u043b\u0435 2025 \u0433\u043e\u0434\u0430 Positive Technologies \u0432\u044b\u044f\u0432\u043b\u044f\u043b\u0430 \u043f\u044f\u0442\u044c \u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u0435\u0439\u00a0\u0432 \u043a\u043e\u043c\u043c\u0443\u0442\u0430\u0442\u043e\u0440\u0430\u0445 ATEN International (CVE-2025-3710, CVE-2025-3711, CVE-2025-3712, CVE-2025-3713 \u0438 CVE-2025-3714), \u043a\u043e\u0442\u043e\u0440\u044b\u0435 \u043c\u043e\u0433\u043b\u0438 \u043f\u0440\u0438\u0432\u0435\u0441\u0442\u0438 \u043a DoS \u0438 RCE.\n\n\u0412 \u043a\u0430\u0447\u0435\u0441\u0442\u0432\u0435 \u043c\u0435\u0440 \u043f\u043e \u0441\u043d\u0438\u0436\u0435\u043d\u0438\u044e \u0440\u0438\u0441\u043a\u043e\u0432 \u0440\u0435\u043a\u043e\u043c\u0435\u043d\u0434\u0443\u0435\u0442\u0441\u044f \u0432\u043d\u0435\u0434\u0440\u0438\u0442\u044c MFa \u0442\u0430\u043c, \u0433\u0434\u0435 \u044d\u0442\u043e \u043f\u043e\u0434\u0434\u0435\u0440\u0436\u0438\u0432\u0430\u0435\u0442\u0441\u044f, \u0438\u0437\u043e\u043b\u0438\u0440\u043e\u0432\u0430\u0442\u044c KVM-\u0443\u0441\u0442\u0440\u043e\u0439\u0441\u0442\u0432\u0430 \u0432 \u0432\u044b\u0434\u0435\u043b\u0435\u043d\u043d\u043e\u0439 \u0443\u043f\u0440\u0430\u0432\u043b\u044f\u044e\u0449\u0435\u0439 VLAN, \u043e\u0433\u0440\u0430\u043d\u0438\u0447\u0438\u0442\u044c \u0434\u043e\u0441\u0442\u0443\u043f \u0432 \u0418\u043d\u0442\u0435\u0440\u043d\u0435\u0442, \u0438\u0441\u043f\u043e\u043b\u044c\u0437\u043e\u0432\u0430\u0442\u044c \u0442\u0430\u043a\u0438\u0435 \u0438\u043d\u0441\u0442\u0440\u0443\u043c\u0435\u043d\u0442\u044b, \u043a\u0430\u043a Shodan, \u0434\u043b\u044f \u043f\u0440\u043e\u0432\u0435\u0440\u043a\u0438 \u043d\u0430 \u043d\u0430\u043b\u0438\u0447\u0438\u0435 \u0432\u043d\u0435\u0448\u043d\u0438\u0445 \u0443\u0433\u0440\u043e\u0437, \u043e\u0442\u0441\u043b\u0435\u0436\u0438\u0432\u0430\u0442\u044c \u043d\u0435\u043e\u0436\u0438\u0434\u0430\u043d\u043d\u044b\u0439 \u0441\u0435\u0442\u0435\u0432\u043e\u0439 \u0442\u0440\u0430\u0444\u0438\u043a \u043a/\u043e\u0442 \u0443\u0441\u0442\u0440\u043e\u0439\u0441\u0442\u0432 \u0438 \u043f\u043e\u0434\u0434\u0435\u0440\u0436\u0438\u0432\u0430\u0442\u044c \u043f\u0440\u043e\u0448\u0438\u0432\u043a\u0443 \u0432 \u0430\u043a\u0442\u0443\u0430\u043b\u044c\u043d\u043e\u043c \u0441\u043e\u0441\u0442\u043e\u044f\u043d\u0438\u0438.\n\n\u0412\u0435\u0434\u044c, \u043a\u0430\u043a \u0437\u0430\u044f\u0432\u043b\u044f\u044e\u0442 \u0432 Eclypsium, \u0437\u043b\u043e\u0443\u043c\u044b\u0448\u043b\u0435\u043d\u043d\u0438\u043a, \u0432\u0437\u043b\u043e\u043c\u0430\u0432\u0448\u0438\u0439 KVM-\u043f\u0435\u0440\u0435\u043a\u043b\u044e\u0447\u0430\u0442\u0435\u043b\u044c, \u0441\u043f\u043e\u0441\u043e\u0431\u0435\u043d \u0441\u043a\u0440\u044b\u0432\u0430\u0442\u044c \u0438\u043d\u0441\u0442\u0440\u0443\u043c\u0435\u043d\u0442\u044b \u0438 \u0431\u044d\u043a\u0434\u043e\u0440\u044b \u043d\u0430 \u0441\u0430\u043c\u043e\u043c \u0443\u0441\u0442\u0440\u043e\u0439\u0441\u0442\u0432\u0435, \u043f\u043e\u0432\u0442\u043e\u0440\u043d\u043e \u0437\u0430\u0440\u0430\u0436\u0430\u044f \u0445\u043e\u0441\u0442-\u0441\u0438\u0441\u0442\u0435\u043c\u044b \u0434\u0430\u0436\u0435 \u043f\u043e\u0441\u043b\u0435 \u0443\u0441\u0442\u0440\u0430\u043d\u0435\u043d\u0438\u044f \u043f\u0440\u043e\u0431\u043b\u0435\u043c\u044b.", "creation_timestamp": "2026-03-18T17:04:14.000000Z"}, {"uuid": "e943db2c-9d5f-40eb-9275-bbb4dce08092", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3710", "type": "seen", "source": "https://t.me/true_secator/8008", "content": "\u0418\u0441\u0441\u043b\u0435\u0434\u043e\u0432\u0430\u0442\u0435\u043b\u0438 \u0440\u0430\u0441\u043a\u0440\u044b\u043b\u0438 9 \u043a\u0440\u0438\u0442\u0438\u0447\u0435\u0441\u043a\u0438\u0445 \u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u0435\u0439 IP KVM, \u043a\u043e\u0442\u043e\u0440\u044b\u0435 \u043f\u043e\u0437\u0432\u043e\u043b\u044f\u044e\u0442 \u043f\u043e\u043b\u0443\u0447\u0430\u0442\u044c \u043d\u0435\u0441\u0430\u043d\u043a\u0446\u0438\u043e\u043d\u0438\u0440\u043e\u0432\u0430\u043d\u043d\u044b\u0439 \u0434\u043e\u0441\u0442\u0443\u043f \u0441 \u043f\u0440\u0430\u0432\u0430\u043c\u0438 root \u0438 \u043a\u043e\u043d\u0442\u0440\u043e\u043b\u044c \u043d\u0430\u0434 \u0441\u043a\u043e\u043c\u043f\u0440\u043e\u043c\u0435\u0442\u0438\u0440\u043e\u0432\u0430\u043d\u043d\u044b\u043c\u0438 \u0445\u043e\u0441\u0442\u0430\u043c\u0438.\n\n\u0423\u0441\u0442\u0440\u043e\u0439\u0441\u0442\u0432\u0430 IP KVM \u043e\u0431\u0435\u0441\u043f\u0435\u0447\u0438\u0432\u0430\u044e\u0442 \u0443\u0434\u0430\u043b\u0435\u043d\u043d\u044b\u0439 \u0434\u043e\u0441\u0442\u0443\u043f \u043a \u043a\u043b\u0430\u0432\u0438\u0430\u0442\u0443\u0440\u0435, \u0432\u0438\u0434\u0435\u043e\u0432\u044b\u0445\u043e\u0434\u0443 \u0438 \u043c\u044b\u0448\u0438 \u0446\u0435\u043b\u0435\u0432\u043e\u0433\u043e \u043a\u043e\u043c\u043f\u044c\u044e\u0442\u0435\u0440\u0430 \u043d\u0430 \u0443\u0440\u043e\u0432\u043d\u0435 BIOS/UEFI.\n\n\u041e\u0431\u043d\u0430\u0440\u0443\u0436\u0435\u043d\u043d\u044b\u0435 Eclypsium \u043f\u0440\u043e\u0431\u043b\u0435\u043c\u044b \u0437\u0430\u0442\u0440\u0430\u0433\u0438\u0432\u0430\u044e\u0442 \u0447\u0435\u0442\u044b\u0440\u0435 \u0440\u0430\u0437\u043b\u0438\u0447\u043d\u044b\u0445 \u043f\u0440\u043e\u0434\u0443\u043a\u0442\u0430: GL-iNet Comet RM-1, Angeet/Yeeso ES3 KVM, Sipeed NanoKVM \u0438 JetKVM. \u041d\u0430\u0438\u0431\u043e\u043b\u0435\u0435 \u0441\u0435\u0440\u044c\u0435\u0437\u043d\u044b\u0435 \u0438\u0437 \u043d\u0438\u0445 \u043f\u043e\u0437\u0432\u043e\u043b\u044f\u044e\u0442 \u043d\u0435\u0430\u0432\u0442\u043e\u0440\u0438\u0437\u043e\u0432\u0430\u043d\u043d\u044b\u043c \u043f\u043e\u043b\u044c\u0437\u043e\u0432\u0430\u0442\u0435\u043b\u044f\u043c \u043f\u043e\u043b\u0443\u0447\u0438\u0442\u044c root-\u0434\u043e\u0441\u0442\u0443\u043f \u0438\u043b\u0438 \u0437\u0430\u043f\u0443\u0441\u0442\u0438\u0442\u044c \u0432\u0440\u0435\u0434\u043e\u043d\u043e\u0441\u043d\u044b\u0439 \u043a\u043e\u0434.\n\n\u0421\u0440\u0435\u0434\u0438 \u043e\u0431\u0449\u0438\u0445 \u0434\u0435\u0444\u0435\u043a\u0442\u043e\u0432 \u0438\u0441\u0441\u043b\u0435\u0434\u043e\u0432\u0430\u0442\u0435\u043b\u0438 \u0432\u044b\u0434\u0435\u043b\u0438\u043b\u0438: \u043e\u0442\u0441\u0443\u0442\u0441\u0442\u0432\u0438\u0435 \u043f\u0440\u043e\u0432\u0435\u0440\u043a\u0438 \u043f\u043e\u0434\u043f\u0438\u0441\u0438 \u043f\u0440\u043e\u0448\u0438\u0432\u043a\u0438, \u043e\u0442\u0441\u0443\u0442\u0441\u0442\u0432\u0438\u0435 \u0437\u0430\u0449\u0438\u0442\u044b \u043e\u0442 \u0431\u0440\u0443\u0442\u0430, \u043d\u0435\u0440\u0430\u0431\u043e\u0442\u0430\u044e\u0449\u0438\u0435 \u043c\u0435\u0445\u0430\u043d\u0438\u0437\u043c\u044b \u043a\u043e\u043d\u0442\u0440\u043e\u043b\u044f \u0434\u043e\u0441\u0442\u0443\u043f\u0430 \u0438 \u043e\u0442\u043a\u0440\u044b\u0442\u044b\u0435 \u0438\u043d\u0442\u0435\u0440\u0444\u0435\u0439\u0441\u044b \u043e\u0442\u043b\u0430\u0434\u043a\u0438, \u0430 \u0438\u0445 \u043f\u0435\u0440\u0435\u0447\u0435\u043d\u044c \u0432\u044b\u0433\u043b\u044f\u0434\u0438\u0442 \u0441\u043b\u0435\u0434\u0443\u044e\u0449\u0438\u043c \u043e\u0431\u0440\u0430\u0437\u043e\u043c:\n\n- CVE-2026-32290\u00a0(CVSS: 4.2): \u043d\u0435\u0434\u043e\u0441\u0442\u0430\u0442\u043e\u0447\u043d\u0430\u044f \u043f\u0440\u043e\u0432\u0435\u0440\u043a\u0430 \u043f\u043e\u0434\u043b\u0438\u043d\u043d\u043e\u0441\u0442\u0438 \u043f\u0440\u043e\u0448\u0438\u0432\u043a\u0438 \u0432 KVM-\u043f\u0435\u0440\u0435\u043a\u043b\u044e\u0447\u0430\u0442\u0435\u043b\u0435 GL-iNet Comet (\u043f\u043b\u0430\u043d\u0438\u0440\u0443\u0435\u0442\u0441\u044f \u0438\u0441\u043f\u0440\u0430\u0432\u043b\u0435\u043d\u0438\u0435);\n\n- CVE-2026-32291\u00a0(CVSS: 7.6): \u043f\u0440\u043e\u0431\u043b\u0435\u043c\u0430 \u0434\u043e\u0441\u0442\u0443\u043f\u0430 \u043a \u043a\u043e\u0440\u043d\u0435\u0432\u043e\u043c\u0443 \u043a\u0430\u0442\u0430\u043b\u043e\u0433\u0443 \u0443\u043d\u0438\u0432\u0435\u0440\u0441\u0430\u043b\u044c\u043d\u043e\u0433\u043e \u0430\u0441\u0438\u043d\u0445\u0440\u043e\u043d\u043d\u043e\u0433\u043e \u043f\u0440\u0438\u0435\u043c\u043e\u043f\u0435\u0440\u0435\u0434\u0430\u0442\u0447\u0438\u043a\u0430 (UART) \u0432 KVM-\u0441\u0435\u0440\u0432\u0435\u0440\u0435 GL-iNet Comet (\u043f\u043b\u0430\u043d\u0438\u0440\u0443\u0435\u0442\u0441\u044f \u0438\u0441\u043f\u0440\u0430\u0432\u043b\u0435\u043d\u0438\u0435);\n\n- CVE-2026-32292\u00a0(CVSS: 5.3): \u043d\u0435\u0434\u043e\u0441\u0442\u0430\u0442\u043e\u0447\u043d\u0430\u044f \u0437\u0430\u0449\u0438\u0442\u0430 \u043e\u0442 \u0431\u0440\u0443\u0442-\u0430\u0442\u0430\u043a \u0432 GL-iNet Comet KVM (\u0438\u0441\u043f\u0440\u0430\u0432\u043b\u0435\u043d\u043e \u0432 \u0432\u0435\u0440\u0441\u0438\u0438 1.8.1 BETA);\n\n- CVE-2026-32293\u00a0(CVSS: 3.1): \u043d\u0435\u0431\u0435\u0437\u043e\u043f\u0430\u0441\u043d\u043e\u0435 \u043f\u0435\u0440\u0432\u043e\u043d\u0430\u0447\u0430\u043b\u044c\u043d\u043e\u0435 \u0432\u044b\u0434\u0435\u043b\u0435\u043d\u0438\u0435 \u0440\u0435\u0441\u0443\u0440\u0441\u043e\u0432 \u0447\u0435\u0440\u0435\u0437 \u043d\u0435\u0430\u0443\u0442\u0435\u043d\u0442\u0438\u0444\u0438\u0446\u0438\u0440\u043e\u0432\u0430\u043d\u043d\u043e\u0435 \u043e\u0431\u043b\u0430\u0447\u043d\u043e\u0435 \u0441\u043e\u0435\u0434\u0438\u043d\u0435\u043d\u0438\u0435 \u0432 GL-iNet Comet KVM (\u0438\u0441\u043f\u0440\u0430\u0432\u043b\u0435\u043d\u043e \u0432 \u0432\u0435\u0440\u0441\u0438\u0438 1.8.1 BETA);\n\n- CVE-2026-32294\u00a0(CVSS: 6.7): \u043d\u0435\u0434\u043e\u0441\u0442\u0430\u0442\u043e\u0447\u043d\u0430\u044f \u043f\u0440\u043e\u0432\u0435\u0440\u043a\u0430 \u043e\u0431\u043d\u043e\u0432\u043b\u0435\u043d\u0438\u0439 \u0432 JetKVM (\u0438\u0441\u043f\u0440\u0430\u0432\u043b\u0435\u043d\u043e \u0432 \u0432\u0435\u0440\u0441\u0438\u0438 0.5.4);\n\n- CVE-2026-32295\u00a0(CVSS: 7.3): \u043d\u0435\u0434\u043e\u0441\u0442\u0430\u0442\u043e\u0447\u043d\u043e\u0435 \u043e\u0433\u0440\u0430\u043d\u0438\u0447\u0435\u043d\u0438\u0435 \u0441\u043a\u043e\u0440\u043e\u0441\u0442\u0438 \u0437\u0430\u043f\u0440\u043e\u0441\u043e\u0432 \u0432 JetKVM (\u0438\u0441\u043f\u0440\u0430\u0432\u043b\u0435\u043d\u043e \u0432 \u0432\u0435\u0440\u0441\u0438\u0438 0.5.4);\n\n- CVE-2026-32296\u00a0(CVSS: 5.4): \u0440\u0430\u0441\u043a\u0440\u044b\u0442\u0438\u0435 \u043a\u043e\u043d\u0444\u0438\u0433\u0443\u0440\u0430\u0446\u0438\u0438 \u043a\u043e\u043d\u0435\u0447\u043d\u043e\u0439 \u0442\u043e\u0447\u043a\u0438 \u0432 Sipeed NanoKVM (\u0438\u0441\u043f\u0440\u0430\u0432\u043b\u0435\u043d\u043e \u0432 NanoKVM \u0432\u0435\u0440\u0441\u0438\u0438 2.3.1 \u0438 Pro 1.2.4);\n\n- CVE-2026-32297\u00a0(CVSS: 9.8): \u043e\u0442\u0441\u0443\u0442\u0441\u0442\u0432\u0438\u0435 \u0430\u0443\u0442\u0435\u043d\u0442\u0438\u0444\u0438\u043a\u0430\u0446\u0438\u0438 \u0434\u043b\u044f \u043a\u0440\u0438\u0442\u0438\u0447\u0435\u0441\u043a\u043e\u0439 \u0444\u0443\u043d\u043a\u0446\u0438\u0438 \u0432 Angeet ES3 KVM, \u043f\u0440\u0438\u0432\u043e\u0434\u044f\u0449\u0430\u044f \u043a RCE (\u0438\u0441\u043f\u0440\u0430\u0432\u043b\u0435\u043d\u0438\u0435 \u043e\u0442\u0441\u0443\u0442\u0441\u0442\u0432\u0443\u0435\u0442);\n\n- CVE-2026-32298\u00a0(CVSS: 8.8): \u0432\u043d\u0435\u0434\u0440\u0435\u043d\u0438\u0435 \u043a\u043e\u043c\u0430\u043d\u0434 \u041e\u0421 \u0432 Angeet ES3 KVM (\u0438\u0441\u043f\u0440\u0430\u0432\u043b\u0435\u043d\u0438\u0435 \u043e\u0442\u0441\u0443\u0442\u0441\u0442\u0432\u0443\u0435\u0442).\n\n\u041a\u0430\u043a \u043e\u0442\u043c\u0435\u0447\u0430\u0435\u0442 \u0438\u0441\u0441\u043b\u0435\u0434\u043e\u0432\u0430\u0442\u0435\u043b\u0438, \u044d\u0442\u043e \u043d\u0435 \u043a\u0430\u043a\u0438\u0435-\u0442\u043e \u044d\u043a\u0437\u043e\u0442\u0438\u0447\u0435\u0441\u043a\u0438\u0435 0-day, \u0430 \u043f\u0440\u043e\u0441\u0447\u0435\u0442\u044b \u0432 \u0444\u0443\u043d\u0434\u0430\u043c\u0435\u043d\u0442\u0430\u043b\u044c\u043d\u044b\u0445 \u043c\u0435\u0440\u0430\u0445 \u0431\u0435\u0437\u043e\u043f\u0430\u0441\u043d\u043e\u0441\u0442\u0438, \u043a\u043e\u0442\u043e\u0440\u044b\u0435 \u0434\u043e\u043b\u0436\u043d\u044b \u0431\u044b\u0442\u044c \u0440\u0435\u0430\u043b\u0438\u0437\u043e\u0432\u0430\u043d\u044b \u043d\u0430 \u043b\u044e\u0431\u043e\u043c \u0441\u0435\u0442\u0435\u0432\u043e\u043c \u0443\u0441\u0442\u0440\u043e\u0439\u0441\u0442\u0432\u0435.\n\n\u0417\u043b\u043e\u0443\u043c\u044b\u0448\u043b\u0435\u043d\u043d\u0438\u043a \u043c\u043e\u0436\u0435\u0442 \u0438\u0441\u043f\u043e\u043b\u044c\u0437\u043e\u0432\u0430\u0442\u044c \u044d\u0442\u0438 \u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u0438 \u0434\u043b\u044f \u0432\u043d\u0435\u0434\u0440\u0435\u043d\u0438\u044f \u043d\u0430\u0436\u0430\u0442\u0438\u0439 \u043a\u043b\u0430\u0432\u0438\u0448, \u0437\u0430\u0433\u0440\u0443\u0437\u043a\u0438 \u0441\u043e \u0441\u044a\u0435\u043c\u043d\u044b\u0445 \u043d\u043e\u0441\u0438\u0442\u0435\u043b\u0435\u0439 \u0441 \u0446\u0435\u043b\u044c\u044e \u043e\u0431\u0445\u043e\u0434\u0430 \u0448\u0438\u0444\u0440\u043e\u0432\u0430\u043d\u0438\u044f \u0434\u0438\u0441\u043a\u0430 \u0438\u043b\u0438 \u0437\u0430\u0449\u0438\u0442\u044b Secure Boot, \u043e\u0431\u0445\u043e\u0434\u0430 \u044d\u043a\u0440\u0430\u043d\u043e\u0432 \u0431\u043b\u043e\u043a\u0438\u0440\u043e\u0432\u043a\u0438 \u0438 \u0434\u043e\u0441\u0442\u0443\u043f\u0430 \u043a \u0441\u0438\u0441\u0442\u0435\u043c\u0430\u043c, \u0438, \u0447\u0442\u043e \u0431\u043e\u043b\u0435\u0435 \u0432\u0430\u0436\u043d\u043e, \u043e\u0441\u0442\u0430\u0432\u0430\u0442\u044c\u0441\u044f \u043d\u0435\u0437\u0430\u043c\u0435\u0447\u0435\u043d\u043d\u044b\u043c \u041f\u041e \u0431\u0435\u0437\u043e\u043f\u0430\u0441\u043d\u043e\u0441\u0442\u0438, \u0443\u0441\u0442\u0430\u043d\u043e\u0432\u043b\u0435\u043d\u043d\u044b\u043c \u043d\u0430 \u0443\u0440\u043e\u0432\u043d\u0435 \u041e\u0421.\n\n\u041f\u0440\u0438\u0447\u0435\u043c, \u044d\u0442\u043e \u0443\u0436\u0435 \u043d\u0435 \u043f\u0435\u0440\u0432\u044b\u0439 \u0441\u043b\u0443\u0447\u0430\u0439 \u043e\u0431\u043d\u0430\u0440\u0443\u0436\u0435\u043d\u0438\u044f \u043f\u0440\u043e\u0431\u043b\u0435\u043c \u0432 IP KVM-\u0443\u0441\u0442\u0440\u043e\u0439\u0441\u0442\u0432\u0430\u0445. \u0422\u0430\u043a, \u0432 \u0438\u044e\u043b\u0435 2025 \u0433\u043e\u0434\u0430 Positive Technologies \u0432\u044b\u044f\u0432\u043b\u044f\u043b\u0430 \u043f\u044f\u0442\u044c \u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u0435\u0439\u00a0\u0432 \u043a\u043e\u043c\u043c\u0443\u0442\u0430\u0442\u043e\u0440\u0430\u0445 ATEN International (CVE-2025-3710, CVE-2025-3711, CVE-2025-3712, CVE-2025-3713 \u0438 CVE-2025-3714), \u043a\u043e\u0442\u043e\u0440\u044b\u0435 \u043c\u043e\u0433\u043b\u0438 \u043f\u0440\u0438\u0432\u0435\u0441\u0442\u0438 \u043a DoS \u0438 RCE.\n\n\u0412 \u043a\u0430\u0447\u0435\u0441\u0442\u0432\u0435 \u043c\u0435\u0440 \u043f\u043e \u0441\u043d\u0438\u0436\u0435\u043d\u0438\u044e \u0440\u0438\u0441\u043a\u043e\u0432 \u0440\u0435\u043a\u043e\u043c\u0435\u043d\u0434\u0443\u0435\u0442\u0441\u044f \u0432\u043d\u0435\u0434\u0440\u0438\u0442\u044c MFa \u0442\u0430\u043c, \u0433\u0434\u0435 \u044d\u0442\u043e \u043f\u043e\u0434\u0434\u0435\u0440\u0436\u0438\u0432\u0430\u0435\u0442\u0441\u044f, \u0438\u0437\u043e\u043b\u0438\u0440\u043e\u0432\u0430\u0442\u044c KVM-\u0443\u0441\u0442\u0440\u043e\u0439\u0441\u0442\u0432\u0430 \u0432 \u0432\u044b\u0434\u0435\u043b\u0435\u043d\u043d\u043e\u0439 \u0443\u043f\u0440\u0430\u0432\u043b\u044f\u044e\u0449\u0435\u0439 VLAN, \u043e\u0433\u0440\u0430\u043d\u0438\u0447\u0438\u0442\u044c \u0434\u043e\u0441\u0442\u0443\u043f \u0432 \u0418\u043d\u0442\u0435\u0440\u043d\u0435\u0442, \u0438\u0441\u043f\u043e\u043b\u044c\u0437\u043e\u0432\u0430\u0442\u044c \u0442\u0430\u043a\u0438\u0435 \u0438\u043d\u0441\u0442\u0440\u0443\u043c\u0435\u043d\u0442\u044b, \u043a\u0430\u043a Shodan, \u0434\u043b\u044f \u043f\u0440\u043e\u0432\u0435\u0440\u043a\u0438 \u043d\u0430 \u043d\u0430\u043b\u0438\u0447\u0438\u0435 \u0432\u043d\u0435\u0448\u043d\u0438\u0445 \u0443\u0433\u0440\u043e\u0437, \u043e\u0442\u0441\u043b\u0435\u0436\u0438\u0432\u0430\u0442\u044c \u043d\u0435\u043e\u0436\u0438\u0434\u0430\u043d\u043d\u044b\u0439 \u0441\u0435\u0442\u0435\u0432\u043e\u0439 \u0442\u0440\u0430\u0444\u0438\u043a \u043a/\u043e\u0442 \u0443\u0441\u0442\u0440\u043e\u0439\u0441\u0442\u0432 \u0438 \u043f\u043e\u0434\u0434\u0435\u0440\u0436\u0438\u0432\u0430\u0442\u044c \u043f\u0440\u043e\u0448\u0438\u0432\u043a\u0443 \u0432 \u0430\u043a\u0442\u0443\u0430\u043b\u044c\u043d\u043e\u043c \u0441\u043e\u0441\u0442\u043e\u044f\u043d\u0438\u0438.\n\n\u0412\u0435\u0434\u044c, \u043a\u0430\u043a \u0437\u0430\u044f\u0432\u043b\u044f\u044e\u0442 \u0432 Eclypsium, \u0437\u043b\u043e\u0443\u043c\u044b\u0448\u043b\u0435\u043d\u043d\u0438\u043a, \u0432\u0437\u043b\u043e\u043c\u0430\u0432\u0448\u0438\u0439 KVM-\u043f\u0435\u0440\u0435\u043a\u043b\u044e\u0447\u0430\u0442\u0435\u043b\u044c, \u0441\u043f\u043e\u0441\u043e\u0431\u0435\u043d \u0441\u043a\u0440\u044b\u0432\u0430\u0442\u044c \u0438\u043d\u0441\u0442\u0440\u0443\u043c\u0435\u043d\u0442\u044b \u0438 \u0431\u044d\u043a\u0434\u043e\u0440\u044b \u043d\u0430 \u0441\u0430\u043c\u043e\u043c \u0443\u0441\u0442\u0440\u043e\u0439\u0441\u0442\u0432\u0435, \u043f\u043e\u0432\u0442\u043e\u0440\u043d\u043e \u0437\u0430\u0440\u0430\u0436\u0430\u044f \u0445\u043e\u0441\u0442-\u0441\u0438\u0441\u0442\u0435\u043c\u044b \u0434\u0430\u0436\u0435 \u043f\u043e\u0441\u043b\u0435 \u0443\u0441\u0442\u0440\u0430\u043d\u0435\u043d\u0438\u044f \u043f\u0440\u043e\u0431\u043b\u0435\u043c\u044b.", "creation_timestamp": "2026-03-18T17:04:14.000000Z"}, {"uuid": "9a167529-0c63-4749-ad53-9862bb9522c0", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3711", "type": "seen", "source": "https://t.me/true_secator/8008", "content": "\u0418\u0441\u0441\u043b\u0435\u0434\u043e\u0432\u0430\u0442\u0435\u043b\u0438 \u0440\u0430\u0441\u043a\u0440\u044b\u043b\u0438 9 \u043a\u0440\u0438\u0442\u0438\u0447\u0435\u0441\u043a\u0438\u0445 \u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u0435\u0439 IP KVM, \u043a\u043e\u0442\u043e\u0440\u044b\u0435 \u043f\u043e\u0437\u0432\u043e\u043b\u044f\u044e\u0442 \u043f\u043e\u043b\u0443\u0447\u0430\u0442\u044c \u043d\u0435\u0441\u0430\u043d\u043a\u0446\u0438\u043e\u043d\u0438\u0440\u043e\u0432\u0430\u043d\u043d\u044b\u0439 \u0434\u043e\u0441\u0442\u0443\u043f \u0441 \u043f\u0440\u0430\u0432\u0430\u043c\u0438 root \u0438 \u043a\u043e\u043d\u0442\u0440\u043e\u043b\u044c \u043d\u0430\u0434 \u0441\u043a\u043e\u043c\u043f\u0440\u043e\u043c\u0435\u0442\u0438\u0440\u043e\u0432\u0430\u043d\u043d\u044b\u043c\u0438 \u0445\u043e\u0441\u0442\u0430\u043c\u0438.\n\n\u0423\u0441\u0442\u0440\u043e\u0439\u0441\u0442\u0432\u0430 IP KVM \u043e\u0431\u0435\u0441\u043f\u0435\u0447\u0438\u0432\u0430\u044e\u0442 \u0443\u0434\u0430\u043b\u0435\u043d\u043d\u044b\u0439 \u0434\u043e\u0441\u0442\u0443\u043f \u043a \u043a\u043b\u0430\u0432\u0438\u0430\u0442\u0443\u0440\u0435, \u0432\u0438\u0434\u0435\u043e\u0432\u044b\u0445\u043e\u0434\u0443 \u0438 \u043c\u044b\u0448\u0438 \u0446\u0435\u043b\u0435\u0432\u043e\u0433\u043e \u043a\u043e\u043c\u043f\u044c\u044e\u0442\u0435\u0440\u0430 \u043d\u0430 \u0443\u0440\u043e\u0432\u043d\u0435 BIOS/UEFI.\n\n\u041e\u0431\u043d\u0430\u0440\u0443\u0436\u0435\u043d\u043d\u044b\u0435 Eclypsium \u043f\u0440\u043e\u0431\u043b\u0435\u043c\u044b \u0437\u0430\u0442\u0440\u0430\u0433\u0438\u0432\u0430\u044e\u0442 \u0447\u0435\u0442\u044b\u0440\u0435 \u0440\u0430\u0437\u043b\u0438\u0447\u043d\u044b\u0445 \u043f\u0440\u043e\u0434\u0443\u043a\u0442\u0430: GL-iNet Comet RM-1, Angeet/Yeeso ES3 KVM, Sipeed NanoKVM \u0438 JetKVM. \u041d\u0430\u0438\u0431\u043e\u043b\u0435\u0435 \u0441\u0435\u0440\u044c\u0435\u0437\u043d\u044b\u0435 \u0438\u0437 \u043d\u0438\u0445 \u043f\u043e\u0437\u0432\u043e\u043b\u044f\u044e\u0442 \u043d\u0435\u0430\u0432\u0442\u043e\u0440\u0438\u0437\u043e\u0432\u0430\u043d\u043d\u044b\u043c \u043f\u043e\u043b\u044c\u0437\u043e\u0432\u0430\u0442\u0435\u043b\u044f\u043c \u043f\u043e\u043b\u0443\u0447\u0438\u0442\u044c root-\u0434\u043e\u0441\u0442\u0443\u043f \u0438\u043b\u0438 \u0437\u0430\u043f\u0443\u0441\u0442\u0438\u0442\u044c \u0432\u0440\u0435\u0434\u043e\u043d\u043e\u0441\u043d\u044b\u0439 \u043a\u043e\u0434.\n\n\u0421\u0440\u0435\u0434\u0438 \u043e\u0431\u0449\u0438\u0445 \u0434\u0435\u0444\u0435\u043a\u0442\u043e\u0432 \u0438\u0441\u0441\u043b\u0435\u0434\u043e\u0432\u0430\u0442\u0435\u043b\u0438 \u0432\u044b\u0434\u0435\u043b\u0438\u043b\u0438: \u043e\u0442\u0441\u0443\u0442\u0441\u0442\u0432\u0438\u0435 \u043f\u0440\u043e\u0432\u0435\u0440\u043a\u0438 \u043f\u043e\u0434\u043f\u0438\u0441\u0438 \u043f\u0440\u043e\u0448\u0438\u0432\u043a\u0438, \u043e\u0442\u0441\u0443\u0442\u0441\u0442\u0432\u0438\u0435 \u0437\u0430\u0449\u0438\u0442\u044b \u043e\u0442 \u0431\u0440\u0443\u0442\u0430, \u043d\u0435\u0440\u0430\u0431\u043e\u0442\u0430\u044e\u0449\u0438\u0435 \u043c\u0435\u0445\u0430\u043d\u0438\u0437\u043c\u044b \u043a\u043e\u043d\u0442\u0440\u043e\u043b\u044f \u0434\u043e\u0441\u0442\u0443\u043f\u0430 \u0438 \u043e\u0442\u043a\u0440\u044b\u0442\u044b\u0435 \u0438\u043d\u0442\u0435\u0440\u0444\u0435\u0439\u0441\u044b \u043e\u0442\u043b\u0430\u0434\u043a\u0438, \u0430 \u0438\u0445 \u043f\u0435\u0440\u0435\u0447\u0435\u043d\u044c \u0432\u044b\u0433\u043b\u044f\u0434\u0438\u0442 \u0441\u043b\u0435\u0434\u0443\u044e\u0449\u0438\u043c \u043e\u0431\u0440\u0430\u0437\u043e\u043c:\n\n- CVE-2026-32290\u00a0(CVSS: 4.2): \u043d\u0435\u0434\u043e\u0441\u0442\u0430\u0442\u043e\u0447\u043d\u0430\u044f \u043f\u0440\u043e\u0432\u0435\u0440\u043a\u0430 \u043f\u043e\u0434\u043b\u0438\u043d\u043d\u043e\u0441\u0442\u0438 \u043f\u0440\u043e\u0448\u0438\u0432\u043a\u0438 \u0432 KVM-\u043f\u0435\u0440\u0435\u043a\u043b\u044e\u0447\u0430\u0442\u0435\u043b\u0435 GL-iNet Comet (\u043f\u043b\u0430\u043d\u0438\u0440\u0443\u0435\u0442\u0441\u044f \u0438\u0441\u043f\u0440\u0430\u0432\u043b\u0435\u043d\u0438\u0435);\n\n- CVE-2026-32291\u00a0(CVSS: 7.6): \u043f\u0440\u043e\u0431\u043b\u0435\u043c\u0430 \u0434\u043e\u0441\u0442\u0443\u043f\u0430 \u043a \u043a\u043e\u0440\u043d\u0435\u0432\u043e\u043c\u0443 \u043a\u0430\u0442\u0430\u043b\u043e\u0433\u0443 \u0443\u043d\u0438\u0432\u0435\u0440\u0441\u0430\u043b\u044c\u043d\u043e\u0433\u043e \u0430\u0441\u0438\u043d\u0445\u0440\u043e\u043d\u043d\u043e\u0433\u043e \u043f\u0440\u0438\u0435\u043c\u043e\u043f\u0435\u0440\u0435\u0434\u0430\u0442\u0447\u0438\u043a\u0430 (UART) \u0432 KVM-\u0441\u0435\u0440\u0432\u0435\u0440\u0435 GL-iNet Comet (\u043f\u043b\u0430\u043d\u0438\u0440\u0443\u0435\u0442\u0441\u044f \u0438\u0441\u043f\u0440\u0430\u0432\u043b\u0435\u043d\u0438\u0435);\n\n- CVE-2026-32292\u00a0(CVSS: 5.3): \u043d\u0435\u0434\u043e\u0441\u0442\u0430\u0442\u043e\u0447\u043d\u0430\u044f \u0437\u0430\u0449\u0438\u0442\u0430 \u043e\u0442 \u0431\u0440\u0443\u0442-\u0430\u0442\u0430\u043a \u0432 GL-iNet Comet KVM (\u0438\u0441\u043f\u0440\u0430\u0432\u043b\u0435\u043d\u043e \u0432 \u0432\u0435\u0440\u0441\u0438\u0438 1.8.1 BETA);\n\n- CVE-2026-32293\u00a0(CVSS: 3.1): \u043d\u0435\u0431\u0435\u0437\u043e\u043f\u0430\u0441\u043d\u043e\u0435 \u043f\u0435\u0440\u0432\u043e\u043d\u0430\u0447\u0430\u043b\u044c\u043d\u043e\u0435 \u0432\u044b\u0434\u0435\u043b\u0435\u043d\u0438\u0435 \u0440\u0435\u0441\u0443\u0440\u0441\u043e\u0432 \u0447\u0435\u0440\u0435\u0437 \u043d\u0435\u0430\u0443\u0442\u0435\u043d\u0442\u0438\u0444\u0438\u0446\u0438\u0440\u043e\u0432\u0430\u043d\u043d\u043e\u0435 \u043e\u0431\u043b\u0430\u0447\u043d\u043e\u0435 \u0441\u043e\u0435\u0434\u0438\u043d\u0435\u043d\u0438\u0435 \u0432 GL-iNet Comet KVM (\u0438\u0441\u043f\u0440\u0430\u0432\u043b\u0435\u043d\u043e \u0432 \u0432\u0435\u0440\u0441\u0438\u0438 1.8.1 BETA);\n\n- CVE-2026-32294\u00a0(CVSS: 6.7): \u043d\u0435\u0434\u043e\u0441\u0442\u0430\u0442\u043e\u0447\u043d\u0430\u044f \u043f\u0440\u043e\u0432\u0435\u0440\u043a\u0430 \u043e\u0431\u043d\u043e\u0432\u043b\u0435\u043d\u0438\u0439 \u0432 JetKVM (\u0438\u0441\u043f\u0440\u0430\u0432\u043b\u0435\u043d\u043e \u0432 \u0432\u0435\u0440\u0441\u0438\u0438 0.5.4);\n\n- CVE-2026-32295\u00a0(CVSS: 7.3): \u043d\u0435\u0434\u043e\u0441\u0442\u0430\u0442\u043e\u0447\u043d\u043e\u0435 \u043e\u0433\u0440\u0430\u043d\u0438\u0447\u0435\u043d\u0438\u0435 \u0441\u043a\u043e\u0440\u043e\u0441\u0442\u0438 \u0437\u0430\u043f\u0440\u043e\u0441\u043e\u0432 \u0432 JetKVM (\u0438\u0441\u043f\u0440\u0430\u0432\u043b\u0435\u043d\u043e \u0432 \u0432\u0435\u0440\u0441\u0438\u0438 0.5.4);\n\n- CVE-2026-32296\u00a0(CVSS: 5.4): \u0440\u0430\u0441\u043a\u0440\u044b\u0442\u0438\u0435 \u043a\u043e\u043d\u0444\u0438\u0433\u0443\u0440\u0430\u0446\u0438\u0438 \u043a\u043e\u043d\u0435\u0447\u043d\u043e\u0439 \u0442\u043e\u0447\u043a\u0438 \u0432 Sipeed NanoKVM (\u0438\u0441\u043f\u0440\u0430\u0432\u043b\u0435\u043d\u043e \u0432 NanoKVM \u0432\u0435\u0440\u0441\u0438\u0438 2.3.1 \u0438 Pro 1.2.4);\n\n- CVE-2026-32297\u00a0(CVSS: 9.8): \u043e\u0442\u0441\u0443\u0442\u0441\u0442\u0432\u0438\u0435 \u0430\u0443\u0442\u0435\u043d\u0442\u0438\u0444\u0438\u043a\u0430\u0446\u0438\u0438 \u0434\u043b\u044f \u043a\u0440\u0438\u0442\u0438\u0447\u0435\u0441\u043a\u043e\u0439 \u0444\u0443\u043d\u043a\u0446\u0438\u0438 \u0432 Angeet ES3 KVM, \u043f\u0440\u0438\u0432\u043e\u0434\u044f\u0449\u0430\u044f \u043a RCE (\u0438\u0441\u043f\u0440\u0430\u0432\u043b\u0435\u043d\u0438\u0435 \u043e\u0442\u0441\u0443\u0442\u0441\u0442\u0432\u0443\u0435\u0442);\n\n- CVE-2026-32298\u00a0(CVSS: 8.8): \u0432\u043d\u0435\u0434\u0440\u0435\u043d\u0438\u0435 \u043a\u043e\u043c\u0430\u043d\u0434 \u041e\u0421 \u0432 Angeet ES3 KVM (\u0438\u0441\u043f\u0440\u0430\u0432\u043b\u0435\u043d\u0438\u0435 \u043e\u0442\u0441\u0443\u0442\u0441\u0442\u0432\u0443\u0435\u0442).\n\n\u041a\u0430\u043a \u043e\u0442\u043c\u0435\u0447\u0430\u0435\u0442 \u0438\u0441\u0441\u043b\u0435\u0434\u043e\u0432\u0430\u0442\u0435\u043b\u0438, \u044d\u0442\u043e \u043d\u0435 \u043a\u0430\u043a\u0438\u0435-\u0442\u043e \u044d\u043a\u0437\u043e\u0442\u0438\u0447\u0435\u0441\u043a\u0438\u0435 0-day, \u0430 \u043f\u0440\u043e\u0441\u0447\u0435\u0442\u044b \u0432 \u0444\u0443\u043d\u0434\u0430\u043c\u0435\u043d\u0442\u0430\u043b\u044c\u043d\u044b\u0445 \u043c\u0435\u0440\u0430\u0445 \u0431\u0435\u0437\u043e\u043f\u0430\u0441\u043d\u043e\u0441\u0442\u0438, \u043a\u043e\u0442\u043e\u0440\u044b\u0435 \u0434\u043e\u043b\u0436\u043d\u044b \u0431\u044b\u0442\u044c \u0440\u0435\u0430\u043b\u0438\u0437\u043e\u0432\u0430\u043d\u044b \u043d\u0430 \u043b\u044e\u0431\u043e\u043c \u0441\u0435\u0442\u0435\u0432\u043e\u043c \u0443\u0441\u0442\u0440\u043e\u0439\u0441\u0442\u0432\u0435.\n\n\u0417\u043b\u043e\u0443\u043c\u044b\u0448\u043b\u0435\u043d\u043d\u0438\u043a \u043c\u043e\u0436\u0435\u0442 \u0438\u0441\u043f\u043e\u043b\u044c\u0437\u043e\u0432\u0430\u0442\u044c \u044d\u0442\u0438 \u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u0438 \u0434\u043b\u044f \u0432\u043d\u0435\u0434\u0440\u0435\u043d\u0438\u044f \u043d\u0430\u0436\u0430\u0442\u0438\u0439 \u043a\u043b\u0430\u0432\u0438\u0448, \u0437\u0430\u0433\u0440\u0443\u0437\u043a\u0438 \u0441\u043e \u0441\u044a\u0435\u043c\u043d\u044b\u0445 \u043d\u043e\u0441\u0438\u0442\u0435\u043b\u0435\u0439 \u0441 \u0446\u0435\u043b\u044c\u044e \u043e\u0431\u0445\u043e\u0434\u0430 \u0448\u0438\u0444\u0440\u043e\u0432\u0430\u043d\u0438\u044f \u0434\u0438\u0441\u043a\u0430 \u0438\u043b\u0438 \u0437\u0430\u0449\u0438\u0442\u044b Secure Boot, \u043e\u0431\u0445\u043e\u0434\u0430 \u044d\u043a\u0440\u0430\u043d\u043e\u0432 \u0431\u043b\u043e\u043a\u0438\u0440\u043e\u0432\u043a\u0438 \u0438 \u0434\u043e\u0441\u0442\u0443\u043f\u0430 \u043a \u0441\u0438\u0441\u0442\u0435\u043c\u0430\u043c, \u0438, \u0447\u0442\u043e \u0431\u043e\u043b\u0435\u0435 \u0432\u0430\u0436\u043d\u043e, \u043e\u0441\u0442\u0430\u0432\u0430\u0442\u044c\u0441\u044f \u043d\u0435\u0437\u0430\u043c\u0435\u0447\u0435\u043d\u043d\u044b\u043c \u041f\u041e \u0431\u0435\u0437\u043e\u043f\u0430\u0441\u043d\u043e\u0441\u0442\u0438, \u0443\u0441\u0442\u0430\u043d\u043e\u0432\u043b\u0435\u043d\u043d\u044b\u043c \u043d\u0430 \u0443\u0440\u043e\u0432\u043d\u0435 \u041e\u0421.\n\n\u041f\u0440\u0438\u0447\u0435\u043c, \u044d\u0442\u043e \u0443\u0436\u0435 \u043d\u0435 \u043f\u0435\u0440\u0432\u044b\u0439 \u0441\u043b\u0443\u0447\u0430\u0439 \u043e\u0431\u043d\u0430\u0440\u0443\u0436\u0435\u043d\u0438\u044f \u043f\u0440\u043e\u0431\u043b\u0435\u043c \u0432 IP KVM-\u0443\u0441\u0442\u0440\u043e\u0439\u0441\u0442\u0432\u0430\u0445. \u0422\u0430\u043a, \u0432 \u0438\u044e\u043b\u0435 2025 \u0433\u043e\u0434\u0430 Positive Technologies \u0432\u044b\u044f\u0432\u043b\u044f\u043b\u0430 \u043f\u044f\u0442\u044c \u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u0435\u0439\u00a0\u0432 \u043a\u043e\u043c\u043c\u0443\u0442\u0430\u0442\u043e\u0440\u0430\u0445 ATEN International (CVE-2025-3710, CVE-2025-3711, CVE-2025-3712, CVE-2025-3713 \u0438 CVE-2025-3714), \u043a\u043e\u0442\u043e\u0440\u044b\u0435 \u043c\u043e\u0433\u043b\u0438 \u043f\u0440\u0438\u0432\u0435\u0441\u0442\u0438 \u043a DoS \u0438 RCE.\n\n\u0412 \u043a\u0430\u0447\u0435\u0441\u0442\u0432\u0435 \u043c\u0435\u0440 \u043f\u043e \u0441\u043d\u0438\u0436\u0435\u043d\u0438\u044e \u0440\u0438\u0441\u043a\u043e\u0432 \u0440\u0435\u043a\u043e\u043c\u0435\u043d\u0434\u0443\u0435\u0442\u0441\u044f \u0432\u043d\u0435\u0434\u0440\u0438\u0442\u044c MFa \u0442\u0430\u043c, \u0433\u0434\u0435 \u044d\u0442\u043e \u043f\u043e\u0434\u0434\u0435\u0440\u0436\u0438\u0432\u0430\u0435\u0442\u0441\u044f, \u0438\u0437\u043e\u043b\u0438\u0440\u043e\u0432\u0430\u0442\u044c KVM-\u0443\u0441\u0442\u0440\u043e\u0439\u0441\u0442\u0432\u0430 \u0432 \u0432\u044b\u0434\u0435\u043b\u0435\u043d\u043d\u043e\u0439 \u0443\u043f\u0440\u0430\u0432\u043b\u044f\u044e\u0449\u0435\u0439 VLAN, \u043e\u0433\u0440\u0430\u043d\u0438\u0447\u0438\u0442\u044c \u0434\u043e\u0441\u0442\u0443\u043f \u0432 \u0418\u043d\u0442\u0435\u0440\u043d\u0435\u0442, \u0438\u0441\u043f\u043e\u043b\u044c\u0437\u043e\u0432\u0430\u0442\u044c \u0442\u0430\u043a\u0438\u0435 \u0438\u043d\u0441\u0442\u0440\u0443\u043c\u0435\u043d\u0442\u044b, \u043a\u0430\u043a Shodan, \u0434\u043b\u044f \u043f\u0440\u043e\u0432\u0435\u0440\u043a\u0438 \u043d\u0430 \u043d\u0430\u043b\u0438\u0447\u0438\u0435 \u0432\u043d\u0435\u0448\u043d\u0438\u0445 \u0443\u0433\u0440\u043e\u0437, \u043e\u0442\u0441\u043b\u0435\u0436\u0438\u0432\u0430\u0442\u044c \u043d\u0435\u043e\u0436\u0438\u0434\u0430\u043d\u043d\u044b\u0439 \u0441\u0435\u0442\u0435\u0432\u043e\u0439 \u0442\u0440\u0430\u0444\u0438\u043a \u043a/\u043e\u0442 \u0443\u0441\u0442\u0440\u043e\u0439\u0441\u0442\u0432 \u0438 \u043f\u043e\u0434\u0434\u0435\u0440\u0436\u0438\u0432\u0430\u0442\u044c \u043f\u0440\u043e\u0448\u0438\u0432\u043a\u0443 \u0432 \u0430\u043a\u0442\u0443\u0430\u043b\u044c\u043d\u043e\u043c \u0441\u043e\u0441\u0442\u043e\u044f\u043d\u0438\u0438.\n\n\u0412\u0435\u0434\u044c, \u043a\u0430\u043a \u0437\u0430\u044f\u0432\u043b\u044f\u044e\u0442 \u0432 Eclypsium, \u0437\u043b\u043e\u0443\u043c\u044b\u0448\u043b\u0435\u043d\u043d\u0438\u043a, \u0432\u0437\u043b\u043e\u043c\u0430\u0432\u0448\u0438\u0439 KVM-\u043f\u0435\u0440\u0435\u043a\u043b\u044e\u0447\u0430\u0442\u0435\u043b\u044c, \u0441\u043f\u043e\u0441\u043e\u0431\u0435\u043d \u0441\u043a\u0440\u044b\u0432\u0430\u0442\u044c \u0438\u043d\u0441\u0442\u0440\u0443\u043c\u0435\u043d\u0442\u044b \u0438 \u0431\u044d\u043a\u0434\u043e\u0440\u044b \u043d\u0430 \u0441\u0430\u043c\u043e\u043c \u0443\u0441\u0442\u0440\u043e\u0439\u0441\u0442\u0432\u0435, \u043f\u043e\u0432\u0442\u043e\u0440\u043d\u043e \u0437\u0430\u0440\u0430\u0436\u0430\u044f \u0445\u043e\u0441\u0442-\u0441\u0438\u0441\u0442\u0435\u043c\u044b \u0434\u0430\u0436\u0435 \u043f\u043e\u0441\u043b\u0435 \u0443\u0441\u0442\u0440\u0430\u043d\u0435\u043d\u0438\u044f \u043f\u0440\u043e\u0431\u043b\u0435\u043c\u044b.", "creation_timestamp": "2026-03-18T17:04:14.000000Z"}, {"uuid": "17a3da97-3189-454f-b18f-7457858e3386", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3714", "type": "seen", "source": "https://t.me/true_secator/8008", "content": "\u0418\u0441\u0441\u043b\u0435\u0434\u043e\u0432\u0430\u0442\u0435\u043b\u0438 \u0440\u0430\u0441\u043a\u0440\u044b\u043b\u0438 9 \u043a\u0440\u0438\u0442\u0438\u0447\u0435\u0441\u043a\u0438\u0445 \u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u0435\u0439 IP KVM, \u043a\u043e\u0442\u043e\u0440\u044b\u0435 \u043f\u043e\u0437\u0432\u043e\u043b\u044f\u044e\u0442 \u043f\u043e\u043b\u0443\u0447\u0430\u0442\u044c \u043d\u0435\u0441\u0430\u043d\u043a\u0446\u0438\u043e\u043d\u0438\u0440\u043e\u0432\u0430\u043d\u043d\u044b\u0439 \u0434\u043e\u0441\u0442\u0443\u043f \u0441 \u043f\u0440\u0430\u0432\u0430\u043c\u0438 root \u0438 \u043a\u043e\u043d\u0442\u0440\u043e\u043b\u044c \u043d\u0430\u0434 \u0441\u043a\u043e\u043c\u043f\u0440\u043e\u043c\u0435\u0442\u0438\u0440\u043e\u0432\u0430\u043d\u043d\u044b\u043c\u0438 \u0445\u043e\u0441\u0442\u0430\u043c\u0438.\n\n\u0423\u0441\u0442\u0440\u043e\u0439\u0441\u0442\u0432\u0430 IP KVM \u043e\u0431\u0435\u0441\u043f\u0435\u0447\u0438\u0432\u0430\u044e\u0442 \u0443\u0434\u0430\u043b\u0435\u043d\u043d\u044b\u0439 \u0434\u043e\u0441\u0442\u0443\u043f \u043a \u043a\u043b\u0430\u0432\u0438\u0430\u0442\u0443\u0440\u0435, \u0432\u0438\u0434\u0435\u043e\u0432\u044b\u0445\u043e\u0434\u0443 \u0438 \u043c\u044b\u0448\u0438 \u0446\u0435\u043b\u0435\u0432\u043e\u0433\u043e \u043a\u043e\u043c\u043f\u044c\u044e\u0442\u0435\u0440\u0430 \u043d\u0430 \u0443\u0440\u043e\u0432\u043d\u0435 BIOS/UEFI.\n\n\u041e\u0431\u043d\u0430\u0440\u0443\u0436\u0435\u043d\u043d\u044b\u0435 Eclypsium \u043f\u0440\u043e\u0431\u043b\u0435\u043c\u044b \u0437\u0430\u0442\u0440\u0430\u0433\u0438\u0432\u0430\u044e\u0442 \u0447\u0435\u0442\u044b\u0440\u0435 \u0440\u0430\u0437\u043b\u0438\u0447\u043d\u044b\u0445 \u043f\u0440\u043e\u0434\u0443\u043a\u0442\u0430: GL-iNet Comet RM-1, Angeet/Yeeso ES3 KVM, Sipeed NanoKVM \u0438 JetKVM. \u041d\u0430\u0438\u0431\u043e\u043b\u0435\u0435 \u0441\u0435\u0440\u044c\u0435\u0437\u043d\u044b\u0435 \u0438\u0437 \u043d\u0438\u0445 \u043f\u043e\u0437\u0432\u043e\u043b\u044f\u044e\u0442 \u043d\u0435\u0430\u0432\u0442\u043e\u0440\u0438\u0437\u043e\u0432\u0430\u043d\u043d\u044b\u043c \u043f\u043e\u043b\u044c\u0437\u043e\u0432\u0430\u0442\u0435\u043b\u044f\u043c \u043f\u043e\u043b\u0443\u0447\u0438\u0442\u044c root-\u0434\u043e\u0441\u0442\u0443\u043f \u0438\u043b\u0438 \u0437\u0430\u043f\u0443\u0441\u0442\u0438\u0442\u044c \u0432\u0440\u0435\u0434\u043e\u043d\u043e\u0441\u043d\u044b\u0439 \u043a\u043e\u0434.\n\n\u0421\u0440\u0435\u0434\u0438 \u043e\u0431\u0449\u0438\u0445 \u0434\u0435\u0444\u0435\u043a\u0442\u043e\u0432 \u0438\u0441\u0441\u043b\u0435\u0434\u043e\u0432\u0430\u0442\u0435\u043b\u0438 \u0432\u044b\u0434\u0435\u043b\u0438\u043b\u0438: \u043e\u0442\u0441\u0443\u0442\u0441\u0442\u0432\u0438\u0435 \u043f\u0440\u043e\u0432\u0435\u0440\u043a\u0438 \u043f\u043e\u0434\u043f\u0438\u0441\u0438 \u043f\u0440\u043e\u0448\u0438\u0432\u043a\u0438, \u043e\u0442\u0441\u0443\u0442\u0441\u0442\u0432\u0438\u0435 \u0437\u0430\u0449\u0438\u0442\u044b \u043e\u0442 \u0431\u0440\u0443\u0442\u0430, \u043d\u0435\u0440\u0430\u0431\u043e\u0442\u0430\u044e\u0449\u0438\u0435 \u043c\u0435\u0445\u0430\u043d\u0438\u0437\u043c\u044b \u043a\u043e\u043d\u0442\u0440\u043e\u043b\u044f \u0434\u043e\u0441\u0442\u0443\u043f\u0430 \u0438 \u043e\u0442\u043a\u0440\u044b\u0442\u044b\u0435 \u0438\u043d\u0442\u0435\u0440\u0444\u0435\u0439\u0441\u044b \u043e\u0442\u043b\u0430\u0434\u043a\u0438, \u0430 \u0438\u0445 \u043f\u0435\u0440\u0435\u0447\u0435\u043d\u044c \u0432\u044b\u0433\u043b\u044f\u0434\u0438\u0442 \u0441\u043b\u0435\u0434\u0443\u044e\u0449\u0438\u043c \u043e\u0431\u0440\u0430\u0437\u043e\u043c:\n\n- CVE-2026-32290\u00a0(CVSS: 4.2): \u043d\u0435\u0434\u043e\u0441\u0442\u0430\u0442\u043e\u0447\u043d\u0430\u044f \u043f\u0440\u043e\u0432\u0435\u0440\u043a\u0430 \u043f\u043e\u0434\u043b\u0438\u043d\u043d\u043e\u0441\u0442\u0438 \u043f\u0440\u043e\u0448\u0438\u0432\u043a\u0438 \u0432 KVM-\u043f\u0435\u0440\u0435\u043a\u043b\u044e\u0447\u0430\u0442\u0435\u043b\u0435 GL-iNet Comet (\u043f\u043b\u0430\u043d\u0438\u0440\u0443\u0435\u0442\u0441\u044f \u0438\u0441\u043f\u0440\u0430\u0432\u043b\u0435\u043d\u0438\u0435);\n\n- CVE-2026-32291\u00a0(CVSS: 7.6): \u043f\u0440\u043e\u0431\u043b\u0435\u043c\u0430 \u0434\u043e\u0441\u0442\u0443\u043f\u0430 \u043a \u043a\u043e\u0440\u043d\u0435\u0432\u043e\u043c\u0443 \u043a\u0430\u0442\u0430\u043b\u043e\u0433\u0443 \u0443\u043d\u0438\u0432\u0435\u0440\u0441\u0430\u043b\u044c\u043d\u043e\u0433\u043e \u0430\u0441\u0438\u043d\u0445\u0440\u043e\u043d\u043d\u043e\u0433\u043e \u043f\u0440\u0438\u0435\u043c\u043e\u043f\u0435\u0440\u0435\u0434\u0430\u0442\u0447\u0438\u043a\u0430 (UART) \u0432 KVM-\u0441\u0435\u0440\u0432\u0435\u0440\u0435 GL-iNet Comet (\u043f\u043b\u0430\u043d\u0438\u0440\u0443\u0435\u0442\u0441\u044f \u0438\u0441\u043f\u0440\u0430\u0432\u043b\u0435\u043d\u0438\u0435);\n\n- CVE-2026-32292\u00a0(CVSS: 5.3): \u043d\u0435\u0434\u043e\u0441\u0442\u0430\u0442\u043e\u0447\u043d\u0430\u044f \u0437\u0430\u0449\u0438\u0442\u0430 \u043e\u0442 \u0431\u0440\u0443\u0442-\u0430\u0442\u0430\u043a \u0432 GL-iNet Comet KVM (\u0438\u0441\u043f\u0440\u0430\u0432\u043b\u0435\u043d\u043e \u0432 \u0432\u0435\u0440\u0441\u0438\u0438 1.8.1 BETA);\n\n- CVE-2026-32293\u00a0(CVSS: 3.1): \u043d\u0435\u0431\u0435\u0437\u043e\u043f\u0430\u0441\u043d\u043e\u0435 \u043f\u0435\u0440\u0432\u043e\u043d\u0430\u0447\u0430\u043b\u044c\u043d\u043e\u0435 \u0432\u044b\u0434\u0435\u043b\u0435\u043d\u0438\u0435 \u0440\u0435\u0441\u0443\u0440\u0441\u043e\u0432 \u0447\u0435\u0440\u0435\u0437 \u043d\u0435\u0430\u0443\u0442\u0435\u043d\u0442\u0438\u0444\u0438\u0446\u0438\u0440\u043e\u0432\u0430\u043d\u043d\u043e\u0435 \u043e\u0431\u043b\u0430\u0447\u043d\u043e\u0435 \u0441\u043e\u0435\u0434\u0438\u043d\u0435\u043d\u0438\u0435 \u0432 GL-iNet Comet KVM (\u0438\u0441\u043f\u0440\u0430\u0432\u043b\u0435\u043d\u043e \u0432 \u0432\u0435\u0440\u0441\u0438\u0438 1.8.1 BETA);\n\n- CVE-2026-32294\u00a0(CVSS: 6.7): \u043d\u0435\u0434\u043e\u0441\u0442\u0430\u0442\u043e\u0447\u043d\u0430\u044f \u043f\u0440\u043e\u0432\u0435\u0440\u043a\u0430 \u043e\u0431\u043d\u043e\u0432\u043b\u0435\u043d\u0438\u0439 \u0432 JetKVM (\u0438\u0441\u043f\u0440\u0430\u0432\u043b\u0435\u043d\u043e \u0432 \u0432\u0435\u0440\u0441\u0438\u0438 0.5.4);\n\n- CVE-2026-32295\u00a0(CVSS: 7.3): \u043d\u0435\u0434\u043e\u0441\u0442\u0430\u0442\u043e\u0447\u043d\u043e\u0435 \u043e\u0433\u0440\u0430\u043d\u0438\u0447\u0435\u043d\u0438\u0435 \u0441\u043a\u043e\u0440\u043e\u0441\u0442\u0438 \u0437\u0430\u043f\u0440\u043e\u0441\u043e\u0432 \u0432 JetKVM (\u0438\u0441\u043f\u0440\u0430\u0432\u043b\u0435\u043d\u043e \u0432 \u0432\u0435\u0440\u0441\u0438\u0438 0.5.4);\n\n- CVE-2026-32296\u00a0(CVSS: 5.4): \u0440\u0430\u0441\u043a\u0440\u044b\u0442\u0438\u0435 \u043a\u043e\u043d\u0444\u0438\u0433\u0443\u0440\u0430\u0446\u0438\u0438 \u043a\u043e\u043d\u0435\u0447\u043d\u043e\u0439 \u0442\u043e\u0447\u043a\u0438 \u0432 Sipeed NanoKVM (\u0438\u0441\u043f\u0440\u0430\u0432\u043b\u0435\u043d\u043e \u0432 NanoKVM \u0432\u0435\u0440\u0441\u0438\u0438 2.3.1 \u0438 Pro 1.2.4);\n\n- CVE-2026-32297\u00a0(CVSS: 9.8): \u043e\u0442\u0441\u0443\u0442\u0441\u0442\u0432\u0438\u0435 \u0430\u0443\u0442\u0435\u043d\u0442\u0438\u0444\u0438\u043a\u0430\u0446\u0438\u0438 \u0434\u043b\u044f \u043a\u0440\u0438\u0442\u0438\u0447\u0435\u0441\u043a\u043e\u0439 \u0444\u0443\u043d\u043a\u0446\u0438\u0438 \u0432 Angeet ES3 KVM, \u043f\u0440\u0438\u0432\u043e\u0434\u044f\u0449\u0430\u044f \u043a RCE (\u0438\u0441\u043f\u0440\u0430\u0432\u043b\u0435\u043d\u0438\u0435 \u043e\u0442\u0441\u0443\u0442\u0441\u0442\u0432\u0443\u0435\u0442);\n\n- CVE-2026-32298\u00a0(CVSS: 8.8): \u0432\u043d\u0435\u0434\u0440\u0435\u043d\u0438\u0435 \u043a\u043e\u043c\u0430\u043d\u0434 \u041e\u0421 \u0432 Angeet ES3 KVM (\u0438\u0441\u043f\u0440\u0430\u0432\u043b\u0435\u043d\u0438\u0435 \u043e\u0442\u0441\u0443\u0442\u0441\u0442\u0432\u0443\u0435\u0442).\n\n\u041a\u0430\u043a \u043e\u0442\u043c\u0435\u0447\u0430\u0435\u0442 \u0438\u0441\u0441\u043b\u0435\u0434\u043e\u0432\u0430\u0442\u0435\u043b\u0438, \u044d\u0442\u043e \u043d\u0435 \u043a\u0430\u043a\u0438\u0435-\u0442\u043e \u044d\u043a\u0437\u043e\u0442\u0438\u0447\u0435\u0441\u043a\u0438\u0435 0-day, \u0430 \u043f\u0440\u043e\u0441\u0447\u0435\u0442\u044b \u0432 \u0444\u0443\u043d\u0434\u0430\u043c\u0435\u043d\u0442\u0430\u043b\u044c\u043d\u044b\u0445 \u043c\u0435\u0440\u0430\u0445 \u0431\u0435\u0437\u043e\u043f\u0430\u0441\u043d\u043e\u0441\u0442\u0438, \u043a\u043e\u0442\u043e\u0440\u044b\u0435 \u0434\u043e\u043b\u0436\u043d\u044b \u0431\u044b\u0442\u044c \u0440\u0435\u0430\u043b\u0438\u0437\u043e\u0432\u0430\u043d\u044b \u043d\u0430 \u043b\u044e\u0431\u043e\u043c \u0441\u0435\u0442\u0435\u0432\u043e\u043c \u0443\u0441\u0442\u0440\u043e\u0439\u0441\u0442\u0432\u0435.\n\n\u0417\u043b\u043e\u0443\u043c\u044b\u0448\u043b\u0435\u043d\u043d\u0438\u043a \u043c\u043e\u0436\u0435\u0442 \u0438\u0441\u043f\u043e\u043b\u044c\u0437\u043e\u0432\u0430\u0442\u044c \u044d\u0442\u0438 \u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u0438 \u0434\u043b\u044f \u0432\u043d\u0435\u0434\u0440\u0435\u043d\u0438\u044f \u043d\u0430\u0436\u0430\u0442\u0438\u0439 \u043a\u043b\u0430\u0432\u0438\u0448, \u0437\u0430\u0433\u0440\u0443\u0437\u043a\u0438 \u0441\u043e \u0441\u044a\u0435\u043c\u043d\u044b\u0445 \u043d\u043e\u0441\u0438\u0442\u0435\u043b\u0435\u0439 \u0441 \u0446\u0435\u043b\u044c\u044e \u043e\u0431\u0445\u043e\u0434\u0430 \u0448\u0438\u0444\u0440\u043e\u0432\u0430\u043d\u0438\u044f \u0434\u0438\u0441\u043a\u0430 \u0438\u043b\u0438 \u0437\u0430\u0449\u0438\u0442\u044b Secure Boot, \u043e\u0431\u0445\u043e\u0434\u0430 \u044d\u043a\u0440\u0430\u043d\u043e\u0432 \u0431\u043b\u043e\u043a\u0438\u0440\u043e\u0432\u043a\u0438 \u0438 \u0434\u043e\u0441\u0442\u0443\u043f\u0430 \u043a \u0441\u0438\u0441\u0442\u0435\u043c\u0430\u043c, \u0438, \u0447\u0442\u043e \u0431\u043e\u043b\u0435\u0435 \u0432\u0430\u0436\u043d\u043e, \u043e\u0441\u0442\u0430\u0432\u0430\u0442\u044c\u0441\u044f \u043d\u0435\u0437\u0430\u043c\u0435\u0447\u0435\u043d\u043d\u044b\u043c \u041f\u041e \u0431\u0435\u0437\u043e\u043f\u0430\u0441\u043d\u043e\u0441\u0442\u0438, \u0443\u0441\u0442\u0430\u043d\u043e\u0432\u043b\u0435\u043d\u043d\u044b\u043c \u043d\u0430 \u0443\u0440\u043e\u0432\u043d\u0435 \u041e\u0421.\n\n\u041f\u0440\u0438\u0447\u0435\u043c, \u044d\u0442\u043e \u0443\u0436\u0435 \u043d\u0435 \u043f\u0435\u0440\u0432\u044b\u0439 \u0441\u043b\u0443\u0447\u0430\u0439 \u043e\u0431\u043d\u0430\u0440\u0443\u0436\u0435\u043d\u0438\u044f \u043f\u0440\u043e\u0431\u043b\u0435\u043c \u0432 IP KVM-\u0443\u0441\u0442\u0440\u043e\u0439\u0441\u0442\u0432\u0430\u0445. \u0422\u0430\u043a, \u0432 \u0438\u044e\u043b\u0435 2025 \u0433\u043e\u0434\u0430 Positive Technologies \u0432\u044b\u044f\u0432\u043b\u044f\u043b\u0430 \u043f\u044f\u0442\u044c \u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u0435\u0439\u00a0\u0432 \u043a\u043e\u043c\u043c\u0443\u0442\u0430\u0442\u043e\u0440\u0430\u0445 ATEN International (CVE-2025-3710, CVE-2025-3711, CVE-2025-3712, CVE-2025-3713 \u0438 CVE-2025-3714), \u043a\u043e\u0442\u043e\u0440\u044b\u0435 \u043c\u043e\u0433\u043b\u0438 \u043f\u0440\u0438\u0432\u0435\u0441\u0442\u0438 \u043a DoS \u0438 RCE.\n\n\u0412 \u043a\u0430\u0447\u0435\u0441\u0442\u0432\u0435 \u043c\u0435\u0440 \u043f\u043e \u0441\u043d\u0438\u0436\u0435\u043d\u0438\u044e \u0440\u0438\u0441\u043a\u043e\u0432 \u0440\u0435\u043a\u043e\u043c\u0435\u043d\u0434\u0443\u0435\u0442\u0441\u044f \u0432\u043d\u0435\u0434\u0440\u0438\u0442\u044c MFa \u0442\u0430\u043c, \u0433\u0434\u0435 \u044d\u0442\u043e \u043f\u043e\u0434\u0434\u0435\u0440\u0436\u0438\u0432\u0430\u0435\u0442\u0441\u044f, \u0438\u0437\u043e\u043b\u0438\u0440\u043e\u0432\u0430\u0442\u044c KVM-\u0443\u0441\u0442\u0440\u043e\u0439\u0441\u0442\u0432\u0430 \u0432 \u0432\u044b\u0434\u0435\u043b\u0435\u043d\u043d\u043e\u0439 \u0443\u043f\u0440\u0430\u0432\u043b\u044f\u044e\u0449\u0435\u0439 VLAN, \u043e\u0433\u0440\u0430\u043d\u0438\u0447\u0438\u0442\u044c \u0434\u043e\u0441\u0442\u0443\u043f \u0432 \u0418\u043d\u0442\u0435\u0440\u043d\u0435\u0442, \u0438\u0441\u043f\u043e\u043b\u044c\u0437\u043e\u0432\u0430\u0442\u044c \u0442\u0430\u043a\u0438\u0435 \u0438\u043d\u0441\u0442\u0440\u0443\u043c\u0435\u043d\u0442\u044b, \u043a\u0430\u043a Shodan, \u0434\u043b\u044f \u043f\u0440\u043e\u0432\u0435\u0440\u043a\u0438 \u043d\u0430 \u043d\u0430\u043b\u0438\u0447\u0438\u0435 \u0432\u043d\u0435\u0448\u043d\u0438\u0445 \u0443\u0433\u0440\u043e\u0437, \u043e\u0442\u0441\u043b\u0435\u0436\u0438\u0432\u0430\u0442\u044c \u043d\u0435\u043e\u0436\u0438\u0434\u0430\u043d\u043d\u044b\u0439 \u0441\u0435\u0442\u0435\u0432\u043e\u0439 \u0442\u0440\u0430\u0444\u0438\u043a \u043a/\u043e\u0442 \u0443\u0441\u0442\u0440\u043e\u0439\u0441\u0442\u0432 \u0438 \u043f\u043e\u0434\u0434\u0435\u0440\u0436\u0438\u0432\u0430\u0442\u044c \u043f\u0440\u043e\u0448\u0438\u0432\u043a\u0443 \u0432 \u0430\u043a\u0442\u0443\u0430\u043b\u044c\u043d\u043e\u043c \u0441\u043e\u0441\u0442\u043e\u044f\u043d\u0438\u0438.\n\n\u0412\u0435\u0434\u044c, \u043a\u0430\u043a \u0437\u0430\u044f\u0432\u043b\u044f\u044e\u0442 \u0432 Eclypsium, \u0437\u043b\u043e\u0443\u043c\u044b\u0448\u043b\u0435\u043d\u043d\u0438\u043a, \u0432\u0437\u043b\u043e\u043c\u0430\u0432\u0448\u0438\u0439 KVM-\u043f\u0435\u0440\u0435\u043a\u043b\u044e\u0447\u0430\u0442\u0435\u043b\u044c, \u0441\u043f\u043e\u0441\u043e\u0431\u0435\u043d \u0441\u043a\u0440\u044b\u0432\u0430\u0442\u044c \u0438\u043d\u0441\u0442\u0440\u0443\u043c\u0435\u043d\u0442\u044b \u0438 \u0431\u044d\u043a\u0434\u043e\u0440\u044b \u043d\u0430 \u0441\u0430\u043c\u043e\u043c \u0443\u0441\u0442\u0440\u043e\u0439\u0441\u0442\u0432\u0435, \u043f\u043e\u0432\u0442\u043e\u0440\u043d\u043e \u0437\u0430\u0440\u0430\u0436\u0430\u044f \u0445\u043e\u0441\u0442-\u0441\u0438\u0441\u0442\u0435\u043c\u044b \u0434\u0430\u0436\u0435 \u043f\u043e\u0441\u043b\u0435 \u0443\u0441\u0442\u0440\u0430\u043d\u0435\u043d\u0438\u044f \u043f\u0440\u043e\u0431\u043b\u0435\u043c\u044b.", "creation_timestamp": "2026-03-18T17:04:14.000000Z"}, {"uuid": "e684d57b-977a-4658-8e26-6850a5bb25b1", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37750", "type": "seen", "source": "https://t.me/cvedetector/24223", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-37750 - Linux SMB Client UAF in Decryption with Multichannel\", \n  \"Content\": \"CVE ID : CVE-2025-37750 \nPublished : May 1, 2025, 1:15 p.m. | 1\u00a0hour, 5\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nsmb: client: fix UAF in decryption with multichannel  \n  \nAfter commit f7025d861694 (\"smb: client: allocate crypto only for  \nprimary server\") and commit b0abcd65ec54 (\"smb: client: fix UAF in  \nasync decryption\"), the channels started reusing AEAD TFM from primary  \nchannel to perform synchronous decryption, but that can't done as  \nthere could be multiple cifsd threads (one per channel) simultaneously  \naccessing it to perform decryption.  \n  \nThis fixes the following KASAN splat when running fstest generic/249  \nwith 'vers=3.1.1,multichannel,max_channels=4,seal' against Windows  \nServer 2022:  \n  \nBUG: KASAN: slab-use-after-free in gf128mul_4k_lle+0xba/0x110  \nRead of size 8 at addr ffff8881046c18a0 by task cifsd/986  \nCPU: 3 UID: 0 PID: 986 Comm: cifsd Not tainted 6.15.0-rc1 #1  \nPREEMPT(voluntary)  \nHardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-3.fc41  \n04/01/2014  \nCall Trace:  \n   \n dump_stack_lvl+0x5d/0x80  \n print_report+0x156/0x528  \n ? gf128mul_4k_lle+0xba/0x110  \n ? __virt_addr_valid+0x145/0x300  \n ? __phys_addr+0x46/0x90  \n ? gf128mul_4k_lle+0xba/0x110  \n kasan_report+0xdf/0x1a0  \n ? gf128mul_4k_lle+0xba/0x110  \n gf128mul_4k_lle+0xba/0x110  \n ghash_update+0x189/0x210  \n shash_ahash_update+0x295/0x370  \n ? __pfx_shash_ahash_update+0x10/0x10  \n ? __pfx_shash_ahash_update+0x10/0x10  \n ? __pfx_extract_iter_to_sg+0x10/0x10  \n ? ___kmalloc_large_node+0x10e/0x180  \n ? __asan_memset+0x23/0x50  \n crypto_ahash_update+0x3c/0xc0  \n gcm_hash_assoc_remain_continue+0x93/0xc0  \n crypt_message+0xe09/0xec0 [cifs]  \n ? __pfx_crypt_message+0x10/0x10 [cifs]  \n ? _raw_spin_unlock+0x23/0x40  \n ? __pfx_cifs_readv_from_socket+0x10/0x10 [cifs]  \n decrypt_raw_data+0x229/0x380 [cifs]  \n ? __pfx_decrypt_raw_data+0x10/0x10 [cifs]  \n ? __pfx_cifs_read_iter_from_socket+0x10/0x10 [cifs]  \n smb3_receive_transform+0x837/0xc80 [cifs]  \n ? __pfx_smb3_receive_transform+0x10/0x10 [cifs]  \n ? __pfx___might_resched+0x10/0x10  \n ? __pfx_smb3_is_transform_hdr+0x10/0x10 [cifs]  \n cifs_demultiplex_thread+0x692/0x1570 [cifs]  \n ? __pfx_cifs_demultiplex_thread+0x10/0x10 [cifs]  \n ? rcu_is_watching+0x20/0x50  \n ? rcu_lockdep_current_cpu_online+0x62/0xb0  \n ? find_held_lock+0x32/0x90  \n ? kvm_sched_clock_read+0x11/0x20  \n ? local_clock_noinstr+0xd/0xd0  \n ? trace_irq_enable.constprop.0+0xa8/0xe0  \n ? __pfx_cifs_demultiplex_thread+0x10/0x10 [cifs]  \n kthread+0x1fe/0x380  \n ? kthread+0x10f/0x380  \n ? __pfx_kthread+0x10/0x10  \n ? local_clock_noinstr+0xd/0xd0  \n ? ret_from_fork+0x1b/0x60  \n ? local_clock+0x15/0x30  \n ? lock_release+0x29b/0x390  \n ? rcu_is_watching+0x20/0x50  \n ? __pfx_kthread+0x10/0x10  \n ret_from_fork+0x31/0x60  \n ? __pfx_kthread+0x10/0x10  \n ret_from_fork_asm+0x1a/0x30 \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"01 May 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-05-01T16:30:19.000000Z"}, {"uuid": "2d4f7f6b-b9b0-483b-89cc-cd26d393c38e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37164", "type": "published-proof-of-concept", "source": "https://t.me/xakep_ru/18695", "content": "\u0412 HPE OneView \u0438\u0441\u043f\u0440\u0430\u0432\u0438\u043b\u0438 \u043a\u0440\u0438\u0442\u0438\u0447\u0435\u0441\u043a\u0438\u0439 RCE-\u0431\u0430\u0433\n\n\u0420\u0430\u0437\u0440\u0430\u0431\u043e\u0442\u0447\u0438\u043a\u0438 Hewlett Packard Enterprise (HPE) \u0432\u044b\u043f\u0443\u0441\u0442\u0438\u043b\u0438 \u0438\u0441\u043f\u0440\u0430\u0432\u043b\u0435\u043d\u0438\u044f \u0434\u043b\u044f \u043a\u0440\u0438\u0442\u0438\u0447\u0435\u0441\u043a\u043e\u0439 \u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u0438 \u0443\u0434\u0430\u043b\u0435\u043d\u043d\u043e\u0433\u043e \u0432\u044b\u043f\u043e\u043b\u043d\u0435\u043d\u0438\u044f \u043a\u043e\u0434\u0430, \u043e\u0431\u043d\u0430\u0440\u0443\u0436\u0435\u043d\u043d\u043e\u0439 \u0432 \u041f\u041e \u0434\u043b\u044f \u0443\u043f\u0440\u0430\u0432\u043b\u0435\u043d\u0438\u044f \u0418\u0422-\u0438\u043d\u0444\u0440\u0430\u0441\u0442\u0440\u0443\u043a\u0442\u0443\u0440\u043e\u0439 OneView. \u041f\u0440\u043e\u0431\u043b\u0435\u043c\u0430 \u043f\u043e\u043b\u0443\u0447\u0438\u043b\u0430 \u0438\u0434\u0435\u043d\u0442\u0438\u0444\u0438\u043a\u0430\u0442\u043e\u0440 CVE-2025-37164 (\u043c\u0430\u043a\u0441\u0438\u043c\u0430\u043b\u044c\u043d\u044b\u0435 10 \u0431\u0430\u043b\u043b\u043e\u0432 \u043f\u043e \u0448\u043a\u0430\u043b\u0435 CVSS) \u0438 \u043c\u043e\u0436\u0435\u0442 \u0438\u0441\u043f\u043e\u043b\u044c\u0437\u043e\u0432\u0430\u0442\u044c\u0441\u044f \u0431\u0435\u0437 \u0430\u0443\u0442\u0435\u043d\u0442\u0438\u0444\u0438\u043a\u0430\u0446\u0438\u0438.\n\nhttps://xakep.ru/2025/12/23/cve-2025-37164/", "creation_timestamp": "2025-12-23T17:36:23.000000Z"}, {"uuid": "78dae314-f634-4165-84e2-b26b2b08bd57", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37164", "type": "published-proof-of-concept", "source": "https://t.me/ics_cert/1369", "content": "\u0622\u0633\u06cc\u0628\u200c\u067e\u0630\u06cc\u0631\u06cc \u062f\u0631 \u0633\u06cc\u0633\u062a\u0645 \u0645\u062f\u06cc\u0631\u06cc\u062a \u0632\u06cc\u0631\u0633\u0627\u062e\u062a \u0641\u0646\u0627\u0648\u0631\u06cc \u0627\u0637\u0644\u0627\u0639\u0627\u062a HPE OneView \u0628\u0647 \u062f\u0644\u06cc\u0644 \u0645\u062f\u06cc\u0631\u06cc\u062a \u0646\u0627\u062f\u0631\u0633\u062a \u062a\u0648\u0644\u06cc\u062f \u06a9\u062f \u0631\u062e \u062f\u0627\u062f\u0647 \u0627\u0633\u062a. \u0628\u0647\u0631\u0647\u200c\u0628\u0631\u062f\u0627\u0631\u06cc \u0627\u0632 \u0627\u06cc\u0646 \u0622\u0633\u06cc\u0628\u200c\u067e\u0630\u06cc\u0631\u06cc \u0645\u06cc\u200c\u062a\u0648\u0627\u0646\u062f \u0628\u0647 \u0646\u0641\u0648\u0630\u06af\u0631\u06cc \u06a9\u0647 \u0628\u0647 \u0635\u0648\u0631\u062a \u0627\u0632 \u0631\u0627\u0647 \u062f\u0648\u0631 \u0639\u0645\u0644 \u0645\u06cc\u200c\u06a9\u0646\u062f \u0627\u062c\u0627\u0632\u0647 \u062f\u0647\u062f \u06a9\u062f \u062f\u0644\u062e\u0648\u0627\u0647 \u062e\u0648\u062f \u0631\u0627 \u0627\u062c\u0631\u0627 \u06a9\u0646\u062f.\n\nBDU:2025-16117\nCVE-2025-37164\n\n\u0646\u0635\u0628 \u0628\u0647\u200c\u0631\u0648\u0632\u0631\u0633\u0627\u0646\u06cc\u200c\u0647\u0627 \u0627\u0632 \u0645\u0646\u0627\u0628\u0639 \u0645\u0639\u062a\u0628\u0631. \u0628\u0627 \u062a\u0648\u062c\u0647 \u0628\u0647 \u0634\u0631\u0627\u06cc\u0637 \u0645\u0648\u062c\u0648\u062f\u060c \u062a\u0648\u0635\u06cc\u0647 \u0645\u06cc\u200c\u0634\u0648\u062f \u0628\u0647\u200c\u0631\u0648\u0632\u0631\u0633\u0627\u0646\u06cc\u200c\u0647\u0627\u06cc \u0646\u0631\u0645\u200c\u0627\u0641\u0632\u0627\u0631\u06cc \u062a\u0646\u0647\u0627 \u067e\u0633 \u0627\u0632 \u0627\u0631\u0632\u06cc\u0627\u0628\u06cc \u062a\u0645\u0627\u0645\u06cc \u0631\u06cc\u0633\u06a9\u200c\u0647\u0627\u06cc \u0645\u0631\u062a\u0628\u0637 \u0646\u0635\u0628 \u0634\u0648\u0646\u062f.\n\n\u0627\u0642\u062f\u0627\u0645\u0627\u062a \u062c\u0628\u0631\u0627\u0646\u06cc:\n- \u0627\u0633\u062a\u0641\u0627\u062f\u0647 \u0627\u0632 \u0627\u0628\u0632\u0627\u0631\u0647\u0627\u06cc \u0641\u0627\u06cc\u0631\u0648\u0627\u0644 \u0628\u0631\u0627\u06cc \u0645\u062d\u062f\u0648\u062f \u06a9\u0631\u062f\u0646 \u062f\u0633\u062a\u0631\u0633\u06cc \u0627\u0632 \u0631\u0627\u0647 \u062f\u0648\u0631 \u0628\u0647 \u0646\u0631\u0645\u200c\u0627\u0641\u0632\u0627\u0631 \u0622\u0633\u06cc\u0628\u200c\u067e\u0630\u06cc\u0631\u061b\n- \u0645\u062d\u062f\u0648\u062f \u06a9\u0631\u062f\u0646 \u062f\u0633\u062a\u0631\u0633\u06cc \u0628\u0647 \u0646\u0631\u0645\u200c\u0627\u0641\u0632\u0627\u0631 \u0622\u0633\u06cc\u0628\u200c\u067e\u0630\u06cc\u0631 \u0628\u0627 \u0627\u0633\u062a\u0641\u0627\u062f\u0647 \u0627\u0632 \u0637\u0631\u062d \u062f\u0633\u062a\u0631\u0633\u06cc \u0628\u0631 \u0627\u0633\u0627\u0633 \u00ab\u0641\u0647\u0631\u0633\u062a\u200c\u0647\u0627\u06cc \u0633\u0641\u06cc\u062f\u00bb\u061b\n- \u0627\u0633\u062a\u0641\u0627\u062f\u0647 \u0627\u0632 \u0633\u06cc\u0633\u062a\u0645\u200c\u0647\u0627\u06cc \u062a\u0634\u062e\u06cc\u0635 \u0648 \u067e\u06cc\u0634\u06af\u06cc\u0631\u06cc \u0627\u0632 \u0646\u0641\u0648\u0630 \u0628\u0631\u0627\u06cc \u0634\u0646\u0627\u0633\u0627\u06cc\u06cc (\u06a9\u0634\u0641\u060c \u062b\u0628\u062a) \u0648 \u0648\u0627\u06a9\u0646\u0634 \u0628\u0647 \u062a\u0644\u0627\u0634\u200c\u0647\u0627\u06cc \u0628\u0647\u0631\u0647\u200c\u0628\u0631\u062f\u0627\u0631\u06cc \u0627\u0632 \u0622\u0633\u06cc\u0628\u200c\u067e\u0630\u06cc\u0631\u06cc\u200c\u0647\u0627\u061b\n- \u0627\u0633\u062a\u0641\u0627\u062f\u0647 \u0627\u0632 \u0634\u0628\u06a9\u0647\u200c\u0647\u0627\u06cc \u062e\u0635\u0648\u0635\u06cc \u0645\u062c\u0627\u0632\u06cc \u0628\u0631\u0627\u06cc \u0633\u0627\u0632\u0645\u0627\u0646\u062f\u0647\u06cc \u062f\u0633\u062a\u0631\u0633\u06cc \u0627\u0632 \u0631\u0627\u0647 \u062f\u0648\u0631 (VPN)\u061b\n- \u0645\u062d\u062f\u0648\u062f \u06a9\u0631\u062f\u0646 \u062f\u0633\u062a\u0631\u0633\u06cc \u0628\u0647 \u062f\u0633\u062a\u06af\u0627\u0647 \u0627\u0632 \u0634\u0628\u06a9\u0647\u200c\u0647\u0627\u06cc \u062e\u0627\u0631\u062c\u06cc (\u0627\u06cc\u0646\u062a\u0631\u0646\u062a).\n\n\u0627\u0633\u062a\u0641\u0627\u062f\u0647 \u0627\u0632 \u062a\u0648\u0635\u06cc\u0647\u200c\u0647\u0627\u06cc \u062a\u0648\u0644\u06cc\u062f\u06a9\u0646\u0646\u062f\u0647:\nhttps://support.hpe.com/hpesc/public/docDisplay?docId=hpesbgn04985en_us&docLocale=en_US#vulnerability-summary-1\n\ud83d\udca1\u0627\u06af\u0631 \u0627\u06cc\u0646 \u0645\u062a\u0646 \u062f\u06cc\u062f\u06af\u0627\u0647 \u0634\u0645\u0627 \u0631\u0627 \u062a\u063a\u06cc\u06cc\u0631 \u062f\u0627\u062f\u060c \u0628\u0627\u0630\u06a9\u0631 \u0645\u0646\u0628\u0639 \u0628\u0647 \u0627\u0634\u062a\u0631\u0627\u06a9 \u0628\u06af\u0630\u0627\u0631\u06cc\u062f. \n\ud83c\udfed\u00a0 \u06a9\u0627\u0646\u0627\u0644 \u062a\u062e\u0635\u0635\u06cc \u0627\u0645\u0646\u06cc\u062a \u0632\u06cc\u0631\u0633\u0627\u062e\u062a\u0647\u0627\u06cc \u0627\u062a\u0648\u0645\u0627\u0633\u06cc\u0648\u0646 \u0648 \u06a9\u0646\u062a\u0631\u0644 \u0635\u0646\u0639\u062a\u06cc\n@pedram_kiani\n\u06a9\u0627\u0646\u0627\u0644 \u062a\u0644\u06af\u0631\u0627\u0645:\nhttps://t.me/ics_cert\n\u06af\u0631\u0648\u0647 \u062a\u0644\u06af\u0631\u0627\u0645 :\nhttps://t.me/ICSCERT_IR", "creation_timestamp": "2025-12-29T15:31:39.000000Z"}, {"uuid": "5079c3b1-e76f-4246-b230-f34dc315bd7e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37766", "type": "seen", "source": "https://t.me/DarkWebInformer_CVEAlerts/14463", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-37766\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/amd/pm: Prevent division by zero\n\nThe user can set any speed value.\nIf speed is greater than UINT_MAX/8, division by zero is possible.\n\nFound by Linux Verification Center (linuxtesting.org) with SVACE.\n\ud83d\udccf Published: 2025-05-01T13:07:07.168Z\n\ud83d\udccf Modified: 2025-05-02T06:16:14.896Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/6b9f9b998b107c7539f148a013d789ddb860c3b9\n2. https://git.kernel.org/stable/c/ce773dd844ee19a605af27f11470887e0f2044a9\n3. https://git.kernel.org/stable/c/80814924260cea431a8fc6137d11cc8cb331a10c\n4. https://git.kernel.org/stable/c/ffd688804425579a472fbd2525bedb58b1d28bd9\n5. https://git.kernel.org/stable/c/068091b796480819bf70b159f17e222ad8bea900\n6. https://git.kernel.org/stable/c/42f7b5d12c28b2a601a98d10a80c6db1fe1a2900\n7. https://git.kernel.org/stable/c/affd2241927a1e74c0aecd50c2d920dc4213c56d\n8. https://git.kernel.org/stable/c/4e3d9508c056d7e0a56b58d5c81253e2a0d22b6c", "creation_timestamp": "2025-05-02T07:16:37.000000Z"}, {"uuid": "18045761-7623-46a5-af69-6ef8d68e4a37", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37767", "type": "seen", "source": "https://t.me/DarkWebInformer_CVEAlerts/14462", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-37767\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/amd/pm: Prevent division by zero\n\nThe user can set any speed value.\nIf speed is greater than UINT_MAX/8, division by zero is possible.\n\nFound by Linux Verification Center (linuxtesting.org) with SVACE.\n\ud83d\udccf Published: 2025-05-01T13:07:07.861Z\n\ud83d\udccf Modified: 2025-05-02T06:16:15.942Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/f2904fa2b9da943db6bef7c0f8b3fb4fc14acbc4\n2. https://git.kernel.org/stable/c/8f7b5987e21e003cafac28f0e4d323e6496f83ba\n3. https://git.kernel.org/stable/c/c3ff73e3bddf1a6c30d7effe4018d12ba0cadd2e\n4. https://git.kernel.org/stable/c/fb803d4bb9ea0a61c21c4987505e4d4ae18f9fdc\n5. https://git.kernel.org/stable/c/327107bd7f052f4ee2d0c966c7ae879822f1814f\n6. https://git.kernel.org/stable/c/f23e9116ebb71b63fe9cec0dcac792aa9af30b0c", "creation_timestamp": "2025-05-02T07:16:36.000000Z"}, {"uuid": "4d3c8ea3-9713-496a-93b0-9354190f4e97", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37768", "type": "seen", "source": "https://t.me/DarkWebInformer_CVEAlerts/14461", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-37768\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/amd/pm: Prevent division by zero\n\nThe user can set any speed value.\nIf speed is greater than UINT_MAX/8, division by zero is possible.\n\nFound by Linux Verification Center (linuxtesting.org) with SVACE.\n\ud83d\udccf Published: 2025-05-01T13:07:08.680Z\n\ud83d\udccf Modified: 2025-05-02T06:16:16.990Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/3cdd02cb70682d7d205ca6dc02a4d1eb76758d24\n2. https://git.kernel.org/stable/c/be0fffc4152aac4f0291ed2d793f3cfee788449d\n3. https://git.kernel.org/stable/c/5fc4fb54f6f064c25bfbbfd443aa861d3422dd4c\n4. https://git.kernel.org/stable/c/b0742a709be7979c7a480772046a1f36d09dab00\n5. https://git.kernel.org/stable/c/8e9c4f8d197d5709c75effa5d58e80b4fa01981a\n6. https://git.kernel.org/stable/c/9e4f1e21fe7b93a8ef57db433071266c2590e260\n7. https://git.kernel.org/stable/c/7c246a05df51c52fe0852ce56ba10c41e6ed1f39", "creation_timestamp": "2025-05-02T07:16:32.000000Z"}, {"uuid": "f70abf12-c308-4001-b944-64018b50606b", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37929", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/19687", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-37929\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\narm64: errata: Add missing sentinels to Spectre-BHB MIDR arrays\n\nCommit a5951389e58d (\"arm64: errata: Add newer ARM cores to the\nspectre_bhb_loop_affected() lists\") added some additional CPUs to the\nSpectre-BHB workaround, including some new arrays for designs that\nrequire new 'k' values for the workaround to be effective.\n\nUnfortunately, the new arrays omitted the sentinel entry and so\nis_midr_in_range_list() will walk off the end when it doesn't find a\nmatch. With UBSAN enabled, this leads to a crash during boot when\nis_midr_in_range_list() is inlined (which was more common prior to\nc8c2647e69be (\"arm64: Make \u00a0_midr_in_range_list() an exported\nfunction\")):\n\n |  Internal error: aarch64 BRK: 00000000f2000001 [#1] PREEMPT SMP\n |  pstate: 804000c5 (Nzcv daIF +PAN -UAO -TCO -DIT -SSBS BTYPE=--)\n |  pc : spectre_bhb_loop_affected+0x28/0x30\n |  lr : is_spectre_bhb_affected+0x170/0x190\n | [...]\n |  Call trace:\n |   spectre_bhb_loop_affected+0x28/0x30\n |   update_cpu_capabilities+0xc0/0x184\n |   init_cpu_features+0x188/0x1a4\n |   cpuinfo_store_boot_cpu+0x4c/0x60\n |   smp_prepare_boot_cpu+0x38/0x54\n |   start_kernel+0x8c/0x478\n |   __primary_switched+0xc8/0xd4\n |  Code: 6b09011f 54000061 52801080 d65f03c0 (d4200020)\n |  ---[ end trace 0000000000000000 ]---\n |  Kernel panic - not syncing: aarch64 BRK: Fatal exception\n\nAdd the missing sentinel entries.\n\ud83d\udccf Published: 2025-05-20T15:21:55.253Z\n\ud83d\udccf Modified: 2025-06-27T10:21:19.345Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/e68da90ac00d8b681561aeb8f5d6c47af3a04861\n2. https://git.kernel.org/stable/c/6266b3509b2c6ebf2f9daf2239ff8eb60c5f5bd3\n3. https://git.kernel.org/stable/c/446289b8b36b2ee98dabf6388acbddcc33ed41be\n4. https://git.kernel.org/stable/c/3821cae9bd5a99a42d3d0be1b58e41f072cd4c4c\n5. https://git.kernel.org/stable/c/090c8714efe1c3c470301cc2f794c1ee2a57746c\n6. https://git.kernel.org/stable/c/333579202f09e260e8116321df4c55f80a19b160\n7. https://git.kernel.org/stable/c/fee4d171451c1ad9e8aaf65fc0ab7d143a33bd72", "creation_timestamp": "2025-06-27T10:49:53.000000Z"}, {"uuid": "74cd214f-ecdb-4482-9c9e-ab58ea30d8e6", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37755", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/14269", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-37755\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nnet: libwx: handle page_pool_dev_alloc_pages error\n\npage_pool_dev_alloc_pages could return NULL. There was a WARN_ON(!page)\nbut it would still proceed to use the NULL pointer and then crash.\n\nThis is similar to commit 001ba0902046\n(\"net: fec: handle page_pool_dev_alloc_pages error\").\n\nThis is found by our static analysis tool KNighter.\n\ud83d\udccf Published: 2025-05-01T12:55:59.499Z\n\ud83d\udccf Modified: 2025-05-01T12:55:59.499Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/c17ef974bfcf1a50818168b47c4606b425a957c4\n2. https://git.kernel.org/stable/c/ad81d666e114ebf989fc9994d4c93d451dc60056\n3. https://git.kernel.org/stable/c/1dd13c60348f515acd8c6f25a561b9c4e3b04fea\n4. https://git.kernel.org/stable/c/90bec7cef8805f9a23145e070dff28a02bb584eb\n5. https://git.kernel.org/stable/c/7f1ff1b38a7c8b872382b796023419d87d78c47e", "creation_timestamp": "2025-05-01T13:14:39.000000Z"}, {"uuid": "30abf82f-2070-4aa8-adce-5985d5755591", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37757", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/14268", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-37757\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\ntipc: fix memory leak in tipc_link_xmit\n\nIn case the backlog transmit queue for system-importance messages is overloaded,\ntipc_link_xmit() returns -ENOBUFS but the skb list is not purged. This leads to\nmemory leak and failure when a skb is allocated.\n\nThis commit fixes this issue by purging the skb list before tipc_link_xmit()\nreturns.\n\ud83d\udccf Published: 2025-05-01T12:56:01.195Z\n\ud83d\udccf Modified: 2025-05-01T12:56:01.195Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/24e6280cdd7f8d01fc6b9b365fb800c2fb7ea9bb\n2. https://git.kernel.org/stable/c/09c2dcda2c551bba30710c33f6ac678ae7395389\n3. https://git.kernel.org/stable/c/7c5957f7905b4aede9d7a559d271438f3ca9e852\n4. https://git.kernel.org/stable/c/d0e02d3d27a0b4dcb13f954f537ca1dd8f282dcf\n5. https://git.kernel.org/stable/c/a40cbfbb8f95c325430f017883da669b2aa927d4\n6. https://git.kernel.org/stable/c/69ae94725f4fc9e75219d2d69022029c5b24bc9a", "creation_timestamp": "2025-05-01T13:14:38.000000Z"}, {"uuid": "0f1fd078-d843-4573-a35c-0dbcb5414dec", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37758", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/14267", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-37758\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nata: pata_pxa: Fix potential NULL pointer dereference in pxa_ata_probe()\n\ndevm_ioremap() returns NULL on error. Currently, pxa_ata_probe() does\nnot check for this case, which can result in a NULL pointer dereference.\n\nAdd NULL check after devm_ioremap() to prevent this issue.\n\ud83d\udccf Published: 2025-05-01T12:56:02.520Z\n\ud83d\udccf Modified: 2025-05-01T12:56:02.520Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/2dc53c7a0c1f57b082931facafa804a7ca32a9a6\n2. https://git.kernel.org/stable/c/5b09bf6243b0bc0ae58bd9efdf6f0de5546f8d06\n3. https://git.kernel.org/stable/c/ee2b0301d6bfe16b35d57947687c664ecb815775\n4. https://git.kernel.org/stable/c/c022287f6e599422511aa227dc6da37b58d9ceac\n5. https://git.kernel.org/stable/c/2ba9e4c69207777bb0775c7c091800ecd69de144\n6. https://git.kernel.org/stable/c/ad320e408a8c95a282ab9c05cdf0c9b95e317985", "creation_timestamp": "2025-05-01T13:14:37.000000Z"}, {"uuid": "20a675cd-62cc-40d8-8962-315baade0ece", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37759", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/14266", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-37759\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nublk: fix handling recovery & reissue in ublk_abort_queue()\n\nCommit 8284066946e6 (\"ublk: grab request reference when the request is handled\nby userspace\") doesn't grab request reference in case of recovery reissue.\nThen the request can be requeued & re-dispatch & failed when canceling\nuring command.\n\nIf it is one zc request, the request can be freed before io_uring\nreturns the zc buffer back, then cause kernel panic:\n\n[  126.773061] BUG: kernel NULL pointer dereference, address: 00000000000000c8\n[  126.773657] #PF: supervisor read access in kernel mode\n[  126.774052] #PF: error_code(0x0000) - not-present page\n[  126.774455] PGD 0 P4D 0\n[  126.774698] Oops: Oops: 0000 [#1] SMP NOPTI\n[  126.775034] CPU: 13 UID: 0 PID: 1612 Comm: kworker/u64:55 Not tainted 6.14.0_blk+ #182 PREEMPT(full)\n[  126.775676] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-1.fc39 04/01/2014\n[  126.776275] Workqueue: iou_exit io_ring_exit_work\n[  126.776651] RIP: 0010:ublk_io_release+0x14/0x130 [ublk_drv]\n\nFixes it by always grabbing request reference for aborting the request.\n\ud83d\udccf Published: 2025-05-01T12:56:03.462Z\n\ud83d\udccf Modified: 2025-05-01T12:56:03.462Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/caa5c8a2358604f38bf0a4afaa5eacda13763067\n2. https://git.kernel.org/stable/c/5d34a30efac9c9c93e150130caa940c0df6053c1\n3. https://git.kernel.org/stable/c/0a21d259ca4d6310fdfcc0284ebbc000e66cbf70\n4. https://git.kernel.org/stable/c/6ee6bd5d4fce502a5b5a2ea805e9ff16e6aa890f", "creation_timestamp": "2025-05-01T13:14:36.000000Z"}, {"uuid": "ed2c5a37-3385-4ba0-9764-cafcc3430c83", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37743", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/14274", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-37743\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nwifi: ath12k: Avoid memory leak while enabling statistics\n\nDriver uses monitor destination rings for extended statistics mode and\nstandalone monitor mode. In extended statistics mode, TLVs are parsed from\nthe buffer received from the monitor destination ring and assigned to the\nppdu_info structure to update per-packet statistics. In standalone monitor\nmode, along with per-packet statistics, the packet data (payload) is\ncaptured, and the driver updates per MSDU to mac80211.\n\nWhen the AP interface is enabled, only extended statistics mode is\nactivated. As part of enabling monitor rings for collecting statistics,\nthe driver subscribes to HAL_RX_MPDU_START TLV in the filter\nconfiguration. This TLV is received from the monitor destination ring, and\nkzalloc for the mon_mpdu object occurs, which is not freed, leading to a\nmemory leak. The kzalloc for the mon_mpdu object is only required while\nenabling the standalone monitor interface. This causes a memory leak while\nenabling extended statistics mode in the driver.\n\nFix this memory leak by removing the kzalloc for the mon_mpdu object in\nthe HAL_RX_MPDU_START TLV handling. Additionally, remove the standalone\nmonitor mode handlings in the HAL_MON_BUF_ADDR and HAL_RX_MSDU_END TLVs.\nThese TLV tags will be handled properly when enabling standalone monitor\nmode in the future.\n\nTested-on: QCN9274 hw2.0 PCI WLAN.WBE.1.3.1-00173-QCAHKSWPL_SILICONZ-1\nTested-on: WCN7850 hw2.0 PCI WLAN.HMT.1.0.c5-00481-QCAHMTSWPL_V1.0_V2.0_SILICONZ-3\n\ud83d\udccf Published: 2025-05-01T12:55:51.312Z\n\ud83d\udccf Modified: 2025-05-01T12:55:51.312Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/286bab0fc7b9db728dab8c63cadf6be9b3facf8c\n2. https://git.kernel.org/stable/c/ecfc131389923405be8e7a6f4408fd9321e4d19b", "creation_timestamp": "2025-05-01T13:14:48.000000Z"}, {"uuid": "dccb66b7-130a-4c5b-8f97-075245d25a0b", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37746", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/14273", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-37746\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nperf/dwc_pcie: fix duplicate pci_dev devices\n\nDuring platform_device_register, wrongly using struct device\npci_dev as platform_data caused a kmemdup copy of pci_dev. Worse\nstill, accessing the duplicated device leads to list corruption as its\nmutex content (e.g., list, magic) remains the same as the original.\n\ud83d\udccf Published: 2025-05-01T12:55:53.385Z\n\ud83d\udccf Modified: 2025-05-01T12:55:53.385Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/a71c6fc87b2b9905dc2e38887fe4122287216be9\n2. https://git.kernel.org/stable/c/7f35b429802a8065aa61e2a3f567089649f4d98e", "creation_timestamp": "2025-05-01T13:14:45.000000Z"}, {"uuid": "6f47d962-b1d6-4bd0-a2f0-f4444985896d", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37748", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/14272", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-37748\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\niommu/mediatek: Fix NULL pointer deference in mtk_iommu_device_group\n\nCurrently, mtk_iommu calls during probe iommu_device_register before\nthe hw_list from driver data is initialized. Since iommu probing issue\nfix, it leads to NULL pointer dereference in mtk_iommu_device_group when\nhw_list is accessed with list_first_entry (not null safe).\n\nSo, change the call order to ensure iommu_device_register is called\nafter the driver data are initialized.\n\ud83d\udccf Published: 2025-05-01T12:55:54.660Z\n\ud83d\udccf Modified: 2025-05-01T12:55:54.660Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/2f75cb27bef43c8692b0f5e471e5632f6a9beb99\n2. https://git.kernel.org/stable/c/6abd09bed43b8d83d461e0fb5b9a200a06aa8a27\n3. https://git.kernel.org/stable/c/a0842539e8ef9386c070156103aff888e558a60c\n4. https://git.kernel.org/stable/c/ce7d3b2f6f393fa35f0ea12861b83a1ca28b295c\n5. https://git.kernel.org/stable/c/69f9d2d37d1207c5a73dac52a4ce1361ead707f5\n6. https://git.kernel.org/stable/c/38e8844005e6068f336a3ad45451a562a0040ca1", "creation_timestamp": "2025-05-01T13:14:44.000000Z"}, {"uuid": "1e7723c5-3aad-4547-b077-d932f29903fc", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37749", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/14271", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-37749\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nnet: ppp: Add bound checking for skb data on ppp_sync_txmung\n\nEnsure we have enough data in linear buffer from skb before accessing\ninitial bytes. This prevents potential out-of-bounds accesses\nwhen processing short packets.\n\nWhen ppp_sync_txmung receives an incoming package with an empty\npayload:\n(remote) gef\u27a4  p *(struct pppoe_hdr *) (skb->head + skb->network_header)\n$18 = {\n type = 0x1,\n ver = 0x1,\n code = 0x0,\n sid = 0x2,\n        length = 0x0,\n tag = 0xffff8880371cdb96\n}\n\nfrom the skb struct (trimmed)\n      tail = 0x16,\n      end = 0x140,\n      head = 0xffff88803346f400 \"4\",\n      data = 0xffff88803346f416 \":\\377\",\n      truesize = 0x380,\n      len = 0x0,\n      data_len = 0x0,\n      mac_len = 0xe,\n      hdr_len = 0x0,\n\nit is not safe to access data[2].\n\n[pabeni@redhat.com: fixed subj typo]\n\ud83d\udccf Published: 2025-05-01T12:55:55.316Z\n\ud83d\udccf Modified: 2025-05-01T12:55:55.316Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/b78f2b458f56a5a4d976c8e01c43dbf58d3ea2ca\n2. https://git.kernel.org/stable/c/fbaffe8bccf148ece8ad67eb5d7aa852cabf59c8\n3. https://git.kernel.org/stable/c/b4c836d33ca888695b2f2665f948bc1b34fbd533\n4. https://git.kernel.org/stable/c/1f6eb9fa87a781d5370c0de7794ae242f1a95ee5\n5. https://git.kernel.org/stable/c/6e8a6bf43cea4347121ab21bb1ed8d7bef7e732e\n6. https://git.kernel.org/stable/c/aabc6596ffb377c4c9c8f335124b92ea282c9821", "creation_timestamp": "2025-05-01T13:14:43.000000Z"}, {"uuid": "75b8f6a2-800c-4f0c-af7a-7f3acb6ef1b0", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37751", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/14270", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-37751\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nx86/cpu: Avoid running off the end of an AMD erratum table\n\nThe NULL array terminator at the end of erratum_1386_microcode was\nremoved during the switch from x86_cpu_desc to x86_cpu_id. This\ncauses readers to run off the end of the array.\n\nReplace the NULL.\n\ud83d\udccf Published: 2025-05-01T12:55:56.624Z\n\ud83d\udccf Modified: 2025-05-01T12:55:56.624Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/1b518f73f1b6f59e083ec33dea22d9a1a275a970\n2. https://git.kernel.org/stable/c/f0df00ebc57f803603f2a2e0df197e51f06fbe90", "creation_timestamp": "2025-05-01T13:14:42.000000Z"}, {"uuid": "2464350b-a0d0-4514-a230-75021d3ae75a", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37740", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/14276", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-37740\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\njfs: add sanity check for agwidth in dbMount\n\nThe width in dmapctl of the AG is zero, it trigger a divide error when\ncalculating the control page level in dbAllocAG.\n\nTo avoid this issue, add a check for agwidth in dbAllocAG.\n\ud83d\udccf Published: 2025-05-01T12:55:49.287Z\n\ud83d\udccf Modified: 2025-05-01T12:55:49.287Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/a260bf14cd347878f01f70739ba829442a474a16\n2. https://git.kernel.org/stable/c/cc0bc4cb62ce5fa0c383e3bf0765d01f46bd49ac\n3. https://git.kernel.org/stable/c/ccd97c8a4f90810f228ee40d1055148fa146dd57\n4. https://git.kernel.org/stable/c/c8c96a9e7660e5e5eea445978fe8f2e432d91c1f\n5. https://git.kernel.org/stable/c/e3f85edb03183fb06539e5b50dd2c4bb42b869f0\n6. https://git.kernel.org/stable/c/ddf2846f22e8575d6b4b6a66f2100f168b8cd73d", "creation_timestamp": "2025-05-01T13:14:50.000000Z"}, {"uuid": "245432c4-ed7b-408d-b064-99a4de8faf3d", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37742", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/14275", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-37742\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\njfs: Fix uninit-value access of imap allocated in the diMount() function\n\nsyzbot reports that hex_dump_to_buffer is using uninit-value:\n\n=====================================================\nBUG: KMSAN: uninit-value in hex_dump_to_buffer+0x888/0x1100 lib/hexdump.c:171\nhex_dump_to_buffer+0x888/0x1100 lib/hexdump.c:171\nprint_hex_dump+0x13d/0x3e0 lib/hexdump.c:276\ndiFree+0x5ba/0x4350 fs/jfs/jfs_imap.c:876\njfs_evict_inode+0x510/0x550 fs/jfs/inode.c:156\nevict+0x723/0xd10 fs/inode.c:796\niput_final fs/inode.c:1946 [inline]\niput+0x97b/0xdb0 fs/inode.c:1972\ntxUpdateMap+0xf3e/0x1150 fs/jfs/jfs_txnmgr.c:2367\ntxLazyCommit fs/jfs/jfs_txnmgr.c:2664 [inline]\njfs_lazycommit+0x627/0x11d0 fs/jfs/jfs_txnmgr.c:2733\nkthread+0x6b9/0xef0 kernel/kthread.c:464\nret_from_fork+0x6d/0x90 arch/x86/kernel/process.c:148\nret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244\n\nUninit was created at:\nslab_post_alloc_hook mm/slub.c:4121 [inline]\nslab_alloc_node mm/slub.c:4164 [inline]\n__kmalloc_cache_noprof+0x8e3/0xdf0 mm/slub.c:4320\nkmalloc_noprof include/linux/slab.h:901 [inline]\ndiMount+0x61/0x7f0 fs/jfs/jfs_imap.c:105\njfs_mount+0xa8e/0x11d0 fs/jfs/jfs_mount.c:176\njfs_fill_super+0xa47/0x17c0 fs/jfs/super.c:523\nget_tree_bdev_flags+0x6ec/0x910 fs/super.c:1636\nget_tree_bdev+0x37/0x50 fs/super.c:1659\njfs_get_tree+0x34/0x40 fs/jfs/super.c:635\nvfs_get_tree+0xb1/0x5a0 fs/super.c:1814\ndo_new_mount+0x71f/0x15e0 fs/namespace.c:3560\npath_mount+0x742/0x1f10 fs/namespace.c:3887\ndo_mount fs/namespace.c:3900 [inline]\n__do_sys_mount fs/namespace.c:4111 [inline]\n__se_sys_mount+0x71f/0x800 fs/namespace.c:4088\n__x64_sys_mount+0xe4/0x150 fs/namespace.c:4088\nx64_sys_call+0x39bf/0x3c30 arch/x86/include/generated/asm/syscalls_64.h:166\ndo_syscall_x64 arch/x86/entry/common.c:52 [inline]\ndo_syscall_64+0xcd/0x1e0 arch/x86/entry/common.c:83\nentry_SYSCALL_64_after_hwframe+0x77/0x7f\n=====================================================\n\nThe reason is that imap is not properly initialized after memory\nallocation. It will cause the snprintf() function to write uninitialized\ndata into linebuf within hex_dump_to_buffer().\n\nFix this by using kzalloc instead of kmalloc to clear its content at the\nbeginning in diMount().\n\ud83d\udccf Published: 2025-05-01T12:55:50.603Z\n\ud83d\udccf Modified: 2025-05-01T12:55:50.603Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/cab1852368dd74d629ee02abdbc559218ca64dde\n2. https://git.kernel.org/stable/c/067347e00a3a7d04afed93f080c6c131e5dd15ee\n3. https://git.kernel.org/stable/c/63148ce4904faa668daffdd1d3c1199ae315ef2c\n4. https://git.kernel.org/stable/c/7057f3aab47629d38e54eae83505813cf0da1e4b\n5. https://git.kernel.org/stable/c/d0d7eca253ccd0619b3d2b683ffe32218ebca9ac\n6. https://git.kernel.org/stable/c/9629d7d66c621671d9a47afe27ca9336bfc8a9ea", "creation_timestamp": "2025-05-01T13:14:48.000000Z"}, {"uuid": "a668dc36-af98-4c45-b6e5-c1ea0c1ef182", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37790", "type": "seen", "source": "https://t.me/DarkWebInformer_CVEAlerts/14453", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-37790\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nnet: mctp: Set SOCK_RCU_FREE\n\nBind lookup runs under RCU, so ensure that a socket doesn't go away in\nthe middle of a lookup.\n\ud83d\udccf Published: 2025-05-01T13:07:23.416Z\n\ud83d\udccf Modified: 2025-05-02T06:16:30.506Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/5c1313b93c8c2e3904a48aa88e2fa1db28c607ae\n2. https://git.kernel.org/stable/c/b9764ebebb007249fb733a131b6110ff333b6616\n3. https://git.kernel.org/stable/c/a8a3b61ce140e2b0a72a779e8d70f60c0cf1e47a\n4. https://git.kernel.org/stable/c/3f899bd6dd56ddc46509b526e23a8f0a97712a6d\n5. https://git.kernel.org/stable/c/e3b5edbdb45924a7d4206d13868a2aac71f1e53d\n6. https://git.kernel.org/stable/c/52024cd6ec71a6ca934d0cc12452bd8d49850679", "creation_timestamp": "2025-05-02T07:16:22.000000Z"}, {"uuid": "1e2b8e6d-1cb2-4c66-ae8c-6557382357c2", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37792", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/14452", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-37792\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: btrtl: Prevent potential NULL dereference\n\nThe btrtl_initialize() function checks that rtl_load_file() either\nhad an error or it loaded a zero length file.  However, if it loaded\na zero length file then the error code is not set correctly.  It\nresults in an error pointer vs NULL bug, followed by a NULL pointer\ndereference.  This was detected by Smatch:\n\ndrivers/bluetooth/btrtl.c:592 btrtl_initialize() warn: passing zero to 'ERR_PTR'\n\ud83d\udccf Published: 2025-05-01T13:07:24.882Z\n\ud83d\udccf Modified: 2025-05-02T06:16:31.893Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/c3e9717276affe59fd8213706db021b493e81e34\n2. https://git.kernel.org/stable/c/73dc99c0ea94abd22379b2d82cacbc73f3e18ec1\n3. https://git.kernel.org/stable/c/2d7c60c2a38b4b461fa960ad0995136a6bfe0756\n4. https://git.kernel.org/stable/c/d8441818690d795232331bd8358545c5c95b6b72\n5. https://git.kernel.org/stable/c/3db6605043b50c8bb768547b23e0222f67ceef3e\n6. https://git.kernel.org/stable/c/aaf356f872a60db1e96fb762a62c4607fd22741f\n7. https://git.kernel.org/stable/c/53ceef799dcfc22c734d600811bfc9dd32eaea0a\n8. https://git.kernel.org/stable/c/324dddea321078a6eeb535c2bff5257be74c9799", "creation_timestamp": "2025-05-02T07:16:21.000000Z"}, {"uuid": "4beb11b6-691b-42b8-86be-a64e4c24d0e7", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3763", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/12544", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-3763\n\ud83d\udd25 CVSS Score: 4.8 (cvssV4_0, Vector: CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N)\n\ud83d\udd39 Description: A vulnerability classified as critical has been found in SourceCodester Phone Management System 1.0. This affects the function main of the component Password Handler. The manipulation of the argument s leads to buffer overflow. Local access is required to approach this attack. The exploit has been disclosed to the public and may be used.\n\ud83d\udccf Published: 2025-04-17T18:31:07.035Z\n\ud83d\udccf Modified: 2025-04-18T20:33:29.970Z\n\ud83d\udd17 References:\n1. https://vuldb.com/?id.305397\n2. https://vuldb.com/?ctiid.305397\n3. https://vuldb.com/?submit.553650\n4. https://github.com/eeeee-vul/CVE/issues/4\n5. https://www.sourcecodester.com/", "creation_timestamp": "2025-04-18T20:59:26.000000Z"}, {"uuid": "0f19cb79-79a9-46dd-9ee1-db0a885f15e9", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3723", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/12145", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-3723\n\ud83d\udd25 CVSS Score: 6.9 (cvssV4_0, Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N)\n\ud83d\udd39 Description: A vulnerability was found in PCMan FTP Server 2.0.7 and classified as critical. This issue affects some unknown processing of the component MDTM Command Handler. The manipulation leads to buffer overflow. The attack may be initiated remotely. The exploit has been disclosed to the public and may be used.\n\ud83d\udccf Published: 2025-04-16T19:31:03.798Z\n\ud83d\udccf Modified: 2025-04-16T19:31:03.798Z\n\ud83d\udd17 References:\n1. https://vuldb.com/?id.305069\n2. https://vuldb.com/?ctiid.305069\n3. https://vuldb.com/?submit.552796\n4. https://fitoxs.com/exploit/exploit-d41d8cd98f00b204e9800998ecf8427e.txt", "creation_timestamp": "2025-04-16T19:56:30.000000Z"}, {"uuid": "1936df7b-e9c7-485d-8c69-079afc8574bf", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3724", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/12144", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-3724\n\ud83d\udd25 CVSS Score: 6.9 (cvssV4_0, Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N)\n\ud83d\udd39 Description: A vulnerability was found in PCMan FTP Server 2.0.7. It has been classified as critical. Affected is an unknown function of the component DIR Command Handler. The manipulation leads to buffer overflow. It is possible to launch the attack remotely. The exploit has been disclosed to the public and may be used.\n\ud83d\udccf Published: 2025-04-16T19:31:04.955Z\n\ud83d\udccf Modified: 2025-04-16T19:31:04.955Z\n\ud83d\udd17 References:\n1. https://vuldb.com/?id.305070\n2. https://vuldb.com/?ctiid.305070\n3. https://vuldb.com/?submit.552808\n4. https://fitoxs.com/exploit/exploit-21232f297a57a5a743894a0e4a801fc3.txt", "creation_timestamp": "2025-04-16T19:56:29.000000Z"}, {"uuid": "93e73327-a6ad-4060-bcf5-270cb0f03e73", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3765", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/12332", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-3765\n\ud83d\udd25 CVSS Score: 5.3 (cvssV4_0, Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N)\n\ud83d\udd39 Description: A vulnerability, which was classified as critical, has been found in SourceCodester Web-based Pharmacy Product Management System 1.0. This issue affects some unknown processing of the file /edit-photo.php. The manipulation of the argument Avatar leads to unrestricted upload. The attack may be initiated remotely. The exploit has been disclosed to the public and may be used.\n\ud83d\udccf Published: 2025-04-17T19:31:07.368Z\n\ud83d\udccf Modified: 2025-04-17T19:42:17.226Z\n\ud83d\udd17 References:\n1. https://vuldb.com/?id.305399\n2. https://vuldb.com/?ctiid.305399\n3. https://vuldb.com/?submit.553722\n4. https://github.com/yaklang/IRifyScanResult/blob/main/Web-based%20Pharmacy%20Product%20Management%20System/upload_in_edit-photo.md\n5. https://www.sourcecodester.com/", "creation_timestamp": "2025-04-17T19:58:07.000000Z"}, {"uuid": "e9a41660-c930-4971-94e2-c41b809c5fb9", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3736", "type": "seen", "source": "https://t.me/DarkWebInformer_CVEAlerts/12335", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-3736\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: Vulnerability in Drupal Simple GTM.This issue affects Simple GTM: *.*.\n\ud83d\udccf Published: 2025-04-16T16:32:08.593Z\n\ud83d\udccf Modified: 2025-04-17T19:40:22.032Z\n\ud83d\udd17 References:\n1. https://www.drupal.org/sa-contrib-2025-037", "creation_timestamp": "2025-04-17T19:58:10.000000Z"}, {"uuid": "fcccdacb-54ab-4724-a578-d35b142bb7e4", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3737", "type": "seen", "source": "https://t.me/DarkWebInformer_CVEAlerts/12336", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-3737\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: Vulnerability in Drupal Google Maps: Store Locator.This issue affects Google Maps: Store Locator: *.*.\n\ud83d\udccf Published: 2025-04-16T16:32:22.119Z\n\ud83d\udccf Modified: 2025-04-17T19:40:13.391Z\n\ud83d\udd17 References:\n1. https://www.drupal.org/sa-contrib-2025-038", "creation_timestamp": "2025-04-17T19:58:12.000000Z"}, {"uuid": "9862df9e-8049-4162-8cfe-4317e76bd8f7", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3783", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/12390", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-3783\n\ud83d\udd25 CVSS Score: 5.3 (cvssV4_0, Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N)\n\ud83d\udd39 Description: A vulnerability classified as critical was found in SourceCodester Web-based Pharmacy Product Management System 1.0. Affected by this vulnerability is an unknown functionality of the file /add-product.php. The manipulation of the argument Avatar leads to unrestricted upload. The attack can be launched remotely. The exploit has been disclosed to the public and may be used.\n\ud83d\udccf Published: 2025-04-18T05:31:05.055Z\n\ud83d\udccf Modified: 2025-04-18T05:31:05.055Z\n\ud83d\udd17 References:\n1. https://vuldb.com/?id.305605\n2. https://vuldb.com/?ctiid.305605\n3. https://vuldb.com/?submit.553723\n4. https://github.com/yaklang/IRifyScanResult/blob/main/Web-based%20Pharmacy%20Product%20Management%20System/upload_in_add-product.md\n5. https://www.sourcecodester.com/", "creation_timestamp": "2025-04-18T05:58:43.000000Z"}, {"uuid": "27979bc3-a550-428e-b21d-ee6f3036ae4e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3764", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/12327", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-3764\n\ud83d\udd25 CVSS Score: 5.3 (cvssV4_0, Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N)\n\ud83d\udd39 Description: A vulnerability classified as critical was found in SourceCodester Web-based Pharmacy Product Management System 1.0. This vulnerability affects unknown code of the file /edit-product.php. The manipulation of the argument Avatar leads to unrestricted upload. The attack can be initiated remotely. The exploit has been disclosed to the public and may be used.\n\ud83d\udccf Published: 2025-04-17T19:31:04.968Z\n\ud83d\udccf Modified: 2025-04-17T19:49:55.511Z\n\ud83d\udd17 References:\n1. https://vuldb.com/?id.305398\n2. https://vuldb.com/?ctiid.305398\n3. https://vuldb.com/?submit.553721\n4. https://github.com/yaklang/IRifyScanResult/blob/main/Web-based%20Pharmacy%20Product%20Management%20System/upload_in_edit-product.md\n5. https://www.sourcecodester.com/", "creation_timestamp": "2025-04-17T19:57:59.000000Z"}, {"uuid": "87809e99-311c-4abb-ab99-3a45d2ddf7c3", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3738", "type": "seen", "source": "https://t.me/DarkWebInformer_CVEAlerts/12337", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-3738\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: Vulnerability in Drupal Google Optimize.This issue affects Google Optimize: *.*.\n\ud83d\udccf Published: 2025-04-16T16:32:31.214Z\n\ud83d\udccf Modified: 2025-04-17T19:40:04.588Z\n\ud83d\udd17 References:\n1. https://www.drupal.org/sa-contrib-2025-039", "creation_timestamp": "2025-04-17T19:58:13.000000Z"}, {"uuid": "435e99ad-f373-4ae8-873f-6ea3e041b836", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3735", "type": "seen", "source": "https://t.me/DarkWebInformer_CVEAlerts/12334", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-3735\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: Vulnerability in Drupal Panelizer (obsolete).This issue affects Panelizer (obsolete): *.*.\n\ud83d\udccf Published: 2025-04-16T16:31:34.331Z\n\ud83d\udccf Modified: 2025-04-17T19:40:31.402Z\n\ud83d\udd17 References:\n1. https://www.drupal.org/sa-contrib-2025-036", "creation_timestamp": "2025-04-17T19:58:09.000000Z"}, {"uuid": "9c339d27-262c-4ae8-9467-2adec7e494f1", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37893", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/12406", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-37893\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nLoongArch: BPF: Fix off-by-one error in build_prologue()\n\nVincent reported that running BPF progs with tailcalls on LoongArch\ncauses kernel hard lockup. Debugging the issues shows that the JITed\nimage missing a jirl instruction at the end of the epilogue.\n\nThere are two passes in JIT compiling, the first pass set the flags and\nthe second pass generates JIT code based on those flags. With BPF progs\nmixing bpf2bpf and tailcalls, build_prologue() generates N insns in the\nfirst pass and then generates N+1 insns in the second pass. This makes\nepilogue_offset off by one and we will jump to some unexpected insn and\ncause lockup. Fix this by inserting a nop insn.\n\ud83d\udccf Published: 2025-04-18T07:01:28.856Z\n\ud83d\udccf Modified: 2025-04-18T07:01:28.856Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/e9ccb262b39ab01a5ac2e485b7996b8498e7b373\n2. https://git.kernel.org/stable/c/b3ffad2f02db4aace6799fe0049508b8925eae45\n3. https://git.kernel.org/stable/c/205a2182c51ffebaef54d643e3745e720cded08b\n4. https://git.kernel.org/stable/c/c74d95a5679741ef428974ab788f5b0758dc78ae\n5. https://git.kernel.org/stable/c/48b904de2408af5f936f0e03f48dfcddeab58aa0\n6. https://git.kernel.org/stable/c/7e2586991e36663c9bc48c828b83eab180ad30a9", "creation_timestamp": "2025-04-18T07:59:22.000000Z"}, {"uuid": "a2b749e1-6edb-4c71-81af-fb41bcbc6484", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3787", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/12411", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-3787\n\ud83d\udd25 CVSS Score: 5.1 (cvssV4_0, Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N)\n\ud83d\udd39 Description: A vulnerability was found in PbootCMS 3.2.5. It has been classified as problematic. Affected is an unknown function of the component Image Handler. The manipulation leads to server-side request forgery. It is possible to launch the attack remotely. The exploit has been disclosed to the public and may be used.\n\ud83d\udccf Published: 2025-04-18T09:31:04.227Z\n\ud83d\udccf Modified: 2025-04-18T09:31:04.227Z\n\ud83d\udd17 References:\n1. https://vuldb.com/?id.305610\n2. https://vuldb.com/?ctiid.305610\n3. https://vuldb.com/?submit.553731\n4. https://github.com/KKDT12138/CVE/blob/main/cve6.pdf", "creation_timestamp": "2025-04-18T09:58:58.000000Z"}, {"uuid": "fe951684-da11-4b5d-aea4-e72468863bd7", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3785", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/12408", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-3785\n\ud83d\udd25 CVSS Score: 8.7 (cvssV4_0, Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N)\n\ud83d\udd39 Description: A vulnerability has been found in D-Link DWR-M961 1.1.36 and classified as critical. This vulnerability affects unknown code of the file /boafrm/formStaticDHCP of the component Authorization Interface. The manipulation of the argument Hostname leads to stack-based buffer overflow. The attack can be initiated remotely. The exploit has been disclosed to the public and may be used. Upgrading to version 1.1.49 is able to address this issue. It is recommended to upgrade the affected component.\n\ud83d\udccf Published: 2025-04-18T08:31:05.721Z\n\ud83d\udccf Modified: 2025-04-18T08:31:05.721Z\n\ud83d\udd17 References:\n1. https://vuldb.com/?id.305608\n2. https://vuldb.com/?ctiid.305608\n3. https://vuldb.com/?submit.553547\n4. https://github.com/ZOKEYE/CVE/blob/main/D-link.md\n5. https://www.dlink.com/", "creation_timestamp": "2025-04-18T08:59:06.000000Z"}, {"uuid": "e57e1881-1c32-40e7-90a5-38ee727d62e4", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37860", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/12407", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-37860\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nsfc: fix NULL dereferences in ef100_process_design_param()\n\nSince cited commit, ef100_probe_main() and hence also\n ef100_check_design_params() run before efx->net_dev is created;\n consequently, we cannot netif_set_tso_max_size() or _segs() at this\n point.\nMove those netif calls to ef100_probe_netdev(), and also replace\n netif_err within the design params code with pci_err.\n\ud83d\udccf Published: 2025-04-18T07:01:28.132Z\n\ud83d\udccf Modified: 2025-04-18T07:01:28.132Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/e56391011381d6d029da377a65ac314cb3d5def2\n2. https://git.kernel.org/stable/c/8241ecec1cdc6699ae197d52d58e76bddd995fa5", "creation_timestamp": "2025-04-18T07:59:23.000000Z"}, {"uuid": "b5c2373f-b36d-433e-953f-3fd109e010f2", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3786", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/12413", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-3786\n\ud83d\udd25 CVSS Score: 8.7 (cvssV4_0, Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N)\n\ud83d\udd39 Description: A vulnerability was found in Tenda AC15 up to 15.03.05.19 and classified as critical. This issue affects the function fromSetWirelessRepeat of the file /goform/WifiExtraSet. The manipulation of the argument mac leads to buffer overflow. The attack may be initiated remotely. The exploit has been disclosed to the public and may be used.\n\ud83d\udccf Published: 2025-04-18T09:00:23.217Z\n\ud83d\udccf Modified: 2025-04-18T09:00:23.217Z\n\ud83d\udd17 References:\n1. https://vuldb.com/?id.305609\n2. https://vuldb.com/?ctiid.305609\n3. https://vuldb.com/?submit.553703\n4. https://github.com/CH13hh/cve/tree/AC15WifiExtraSet\n5. https://www.tenda.com.cn/", "creation_timestamp": "2025-04-18T09:59:00.000000Z"}, {"uuid": "ec8fbae5-4856-4bdc-8ba9-b3f403582cee", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3789", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/12421", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-3789\n\ud83d\udd25 CVSS Score: 5.1 (cvssV4_0, Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N)\n\ud83d\udd39 Description: A vulnerability was found in baseweb JSite 1.0. It has been rated as problematic. Affected by this issue is some unknown functionality of the file /a/sys/area/save. The manipulation of the argument Name leads to cross site scripting. The attack may be launched remotely. The exploit has been disclosed to the public and may be used.\n\ud83d\udccf Published: 2025-04-18T12:31:04.563Z\n\ud83d\udccf Modified: 2025-04-18T12:31:04.563Z\n\ud83d\udd17 References:\n1. https://vuldb.com/?id.305612\n2. https://vuldb.com/?ctiid.305612\n3. https://vuldb.com/?submit.554566\n4. https://github.com/caigo8/CVE-md/blob/main/JSite/XSS3.md", "creation_timestamp": "2025-04-18T12:58:24.000000Z"}, {"uuid": "72531715-4f94-4e02-b618-c22e202aa014", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3762", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/12541", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-3762\n\ud83d\udd25 CVSS Score: 6.9 (cvssV4_0, Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N)\n\ud83d\udd39 Description: A vulnerability was found in PCMan FTP Server 2.0.7. It has been rated as critical. Affected by this issue is some unknown functionality of the component MPUT Command Handler. The manipulation leads to buffer overflow. The attack may be launched remotely. The exploit has been disclosed to the public and may be used.\n\ud83d\udccf Published: 2025-04-17T18:31:04.442Z\n\ud83d\udccf Modified: 2025-04-18T20:36:41.481Z\n\ud83d\udd17 References:\n1. https://vuldb.com/?id.305396\n2. https://vuldb.com/?ctiid.305396\n3. https://vuldb.com/?submit.553567\n4. https://fitoxs.com/exploit/exploit-8d31b9e55c1c3d8f2cbf62e3e218f50b.txt", "creation_timestamp": "2025-04-18T20:59:24.000000Z"}, {"uuid": "91c42b35-0f26-438d-a503-7ff8a905362c", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3795", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/12543", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-3795\n\ud83d\udd25 CVSS Score: 4.8 (cvssV4_0, Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N)\n\ud83d\udd39 Description: A vulnerability was found in DaiCuo 1.3.13. It has been rated as problematic. Affected by this issue is some unknown functionality of the component SEO Optimization Settings Section. The manipulation leads to cross site scripting. The attack may be launched remotely. The exploit has been disclosed to the public and may be used.\n\ud83d\udccf Published: 2025-04-18T20:00:10.780Z\n\ud83d\udccf Modified: 2025-04-18T20:34:00.287Z\n\ud83d\udd17 References:\n1. https://vuldb.com/?id.305648\n2. https://vuldb.com/?ctiid.305648\n3. https://vuldb.com/?submit.554639\n4. https://github.com/daicuo/cms/issues/1", "creation_timestamp": "2025-04-18T20:59:25.000000Z"}, {"uuid": "17cf84a4-1ab2-4baa-99dc-188419c251a2", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3796", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/12551", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-3796\n\ud83d\udd25 CVSS Score: 5.3 (cvssV4_0, Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N)\n\ud83d\udd39 Description: A vulnerability classified as critical has been found in PHPGurukul Men Salon Management System 1.0. This affects an unknown part of the file /admin/contact-us.php. The manipulation of the argument pagetitle/pagedes/email/mobnumber/timing leads to sql injection. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used.\n\ud83d\udccf Published: 2025-04-18T21:00:11.403Z\n\ud83d\udccf Modified: 2025-04-18T21:00:11.403Z\n\ud83d\udd17 References:\n1. https://vuldb.com/?id.305649\n2. https://vuldb.com/?ctiid.305649\n3. https://vuldb.com/?submit.554659\n4. https://github.com/yaklang/IRifyScanResult/blob/main/Men-Salon-Management-System/sql_inject_in_contact_us.md\n5. https://phpgurukul.com/", "creation_timestamp": "2025-04-18T21:59:29.000000Z"}, {"uuid": "92407acf-358f-4224-a2b0-372151fcb5c1", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3798", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/12581", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-3798\n\ud83d\udd25 CVSS Score: 5.1 (cvssV4_0, Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N)\n\ud83d\udd39 Description: A vulnerability, which was classified as critical, has been found in WCMS 11. This issue affects the function sub of the file app/admin/AdvadminController.php of the component Advertisement Image Handler. The manipulation leads to unrestricted upload. The attack may be initiated remotely. The exploit has been disclosed to the public and may be used.\n\ud83d\udccf Published: 2025-04-19T10:00:07.289Z\n\ud83d\udccf Modified: 2025-04-19T10:00:07.289Z\n\ud83d\udd17 References:\n1. https://vuldb.com/?id.305651\n2. https://vuldb.com/?ctiid.305651\n3. https://vuldb.com/?submit.554696\n4. https://github.com/IceFoxH/VULN/issues/16", "creation_timestamp": "2025-04-19T11:02:06.000000Z"}, {"uuid": "1bae24a7-18a1-4ae6-a590-b2da97bf45f0", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3799", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/12580", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-3799\n\ud83d\udd25 CVSS Score: 6.9 (cvssV4_0, Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N)\n\ud83d\udd39 Description: A vulnerability, which was classified as critical, was found in WCMS 11. Affected is an unknown function of the file app/controllers/AnonymousController.php. The manipulation of the argument email/username leads to sql injection. It is possible to launch the attack remotely. The exploit has been disclosed to the public and may be used. Other parameters might be affected as well.\n\ud83d\udccf Published: 2025-04-19T10:31:04.389Z\n\ud83d\udccf Modified: 2025-04-19T10:31:04.389Z\n\ud83d\udd17 References:\n1. https://vuldb.com/?id.305652\n2. https://vuldb.com/?ctiid.305652\n3. https://vuldb.com/?submit.554697\n4. https://github.com/IceFoxH/VULN/issues/15", "creation_timestamp": "2025-04-19T11:02:05.000000Z"}, {"uuid": "429dcafc-e18a-4cbe-8d18-c8eae3c14e6b", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37838", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/12609", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-37838\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nHSI: ssi_protocol: Fix use after free vulnerability in ssi_protocol Driver Due to Race Condition\n\nIn the ssi_protocol_probe() function, &ssi->work is bound with\nssip_xmit_work(), In ssip_pn_setup(), the ssip_pn_xmit() function\nwithin the ssip_pn_ops structure is capable of starting the\nwork.\n\nIf we remove the module which will call ssi_protocol_remove()\nto make a cleanup, it will free ssi through kfree(ssi),\nwhile the work mentioned above will be used. The sequence\nof operations that may lead to a UAF bug is as follows:\n\nCPU0                                    CPU1\n\n                        | ssip_xmit_work\nssi_protocol_remove     |\nkfree(ssi);             |\n                        | struct hsi_client *cl = ssi->cl;\n                        | // use ssi\n\nFix it by ensuring that the work is canceled before proceeding\nwith the cleanup in ssi_protocol_remove().\n\ud83d\udccf Published: 2025-04-18T14:20:55.389Z\n\ud83d\udccf Modified: 2025-04-20T08:31:57.492Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/ae5a6a0b425e8f76a9f0677e50796e494e89b088\n2. https://git.kernel.org/stable/c/834e602d0cc7c743bfce734fad4a46cefc0f9ab1\n3. https://git.kernel.org/stable/c/4b4194c9a7a8f92db39e8e86c85f4fb12ebbec4f\n4. https://git.kernel.org/stable/c/e3f88665a78045fe35c7669d2926b8d97b892c11", "creation_timestamp": "2025-04-20T09:03:21.000000Z"}, {"uuid": "658602e6-b739-40a4-96f7-eb98d9fed5b6", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3797", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/12632", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-3797\n\ud83d\udd25 CVSS Score: 5.1 (cvssV4_0, Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N)\n\ud83d\udd39 Description: A vulnerability classified as critical was found in SeaCMS up to 13.3. This vulnerability affects unknown code of the file /admin_topic.php?action=delall. The manipulation of the argument e_id leads to sql injection. The attack can be initiated remotely. The exploit has been disclosed to the public and may be used.\n\ud83d\udccf Published: 2025-04-19T07:00:12.724Z\n\ud83d\udccf Modified: 2025-04-21T02:36:52.642Z\n\ud83d\udd17 References:\n1. https://vuldb.com/?id.305650\n2. https://vuldb.com/?ctiid.305650\n3. https://vuldb.com/?submit.554660\n4. https://github.com/FSRM1/CVE/blob/main/seacms_sql2.md", "creation_timestamp": "2025-04-21T03:01:54.000000Z"}, {"uuid": "3038629f-bc52-4b4a-aef1-7a69263907d5", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37087", "type": "seen", "source": "https://t.me/DarkWebInformer_CVEAlerts/12973", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-37087\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: A vulnerability in the cmdb service of the HPE Performance Cluster Manager (HPCM) could allow an attacker to gain access to an arbitrary file on the server host.\n\ud83d\udccf Published: 2025-04-22T20:58:58.516Z\n\ud83d\udccf Modified: 2025-04-22T20:59:34.714Z\n\ud83d\udd17 References:\n1. https://support.hpe.com/hpesc/docDisplay?docLocale=en_US&docId=a00146087en_us", "creation_timestamp": "2025-04-22T21:04:11.000000Z"}, {"uuid": "495a671f-095e-4ce4-aa6c-f9e26b844cd9", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37088", "type": "seen", "source": "https://t.me/DarkWebInformer_CVEAlerts/12993", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-37088\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: A security vulnerability has been identified in HPE Cray Data Virtualization Service (DVS). Depending on race conditions and configuration, this vulnerability may lead to local/cluster unauthorized access.\n\ud83d\udccf Published: 2025-04-22T21:55:32.657Z\n\ud83d\udccf Modified: 2025-04-22T21:55:32.657Z\n\ud83d\udd17 References:\n1. https://support.hpe.com/hpesc/public/docDisplay?docId=hpesbcr04749en_us&docLocale=en_US", "creation_timestamp": "2025-04-22T22:04:01.000000Z"}, {"uuid": "a73e9325-aaa7-4e1a-8cfc-3565a5e42d27", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3761", "type": "seen", "source": "https://t.me/DarkWebInformer_CVEAlerts/13192", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-3761\n\ud83d\udd25 CVSS Score: 8.8 (cvssV3_1, Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H)\n\ud83d\udd39 Description: The My Tickets \u2013 Accessible Event Ticketing plugin for WordPress is vulnerable to Privilege Escalation in all versions up to, and including, 2.0.16. This is due to the mt_save_profile() function not appropriately restricting access to unauthorized users to update roles. This makes it possible for authenticated attackers, with Subscriber-level access and above, to update their role to that of an administrator.\n\ud83d\udccf Published: 2025-04-24T06:57:06.438Z\n\ud83d\udccf Modified: 2025-04-24T06:57:06.438Z\n\ud83d\udd17 References:\n1. https://www.wordfence.com/threat-intel/vulnerabilities/id/6d875c23-3d8a-4f82-bea3-1c46b5045d94?source=cve\n2. https://plugins.trac.wordpress.org/changeset/3280248/my-tickets/trunk/my-tickets.php", "creation_timestamp": "2025-04-24T07:19:21.000000Z"}, {"uuid": "0cae5cba-3800-4d59-a907-a8df55e91ff4", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3776", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/13197", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-3776\n\ud83d\udd25 CVSS Score: 8.3 (cvssV3_1, Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:L)\n\ud83d\udd39 Description: The Verification SMS with TargetSMS plugin for WordPress is vulnerable to limited Remote Code Execution in all versions up to, and including, 1.5 via the 'targetvr_ajax_handler' function. This is due to a lack of validation on the type of function that can be called. This makes it possible for unauthenticated attackers to execute any callable function on the site, such as phpinfo().\n\ud83d\udccf Published: 2025-04-24T08:23:52.626Z\n\ud83d\udccf Modified: 2025-04-24T08:23:52.626Z\n\ud83d\udd17 References:\n1. https://www.wordfence.com/threat-intel/vulnerabilities/id/ed08d248-7467-4a3b-91a2-4286d91b9c50?source=cve\n2. https://plugins.trac.wordpress.org/browser/verification-sms-targetsms/trunk/inc/ajax.php#L7\n3. https://plugins.trac.wordpress.org/browser/verification-sms-targetsms/trunk/inc/ajax.php#L9", "creation_timestamp": "2025-04-24T09:12:10.000000Z"}, {"uuid": "0cddd61d-ed1e-4e28-b303-e2937dcaa7a5", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3793", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/13198", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-3793\n\ud83d\udd25 CVSS Score: 4.2 (cvssV3_1, Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N)\n\ud83d\udd39 Description: The Buddypress Force Password Change plugin for WordPress is vulnerable to authenticated account takeover due to the plugin not properly validating a user's identity prior to updating their password through the 'bp_force_password_ajax' function in all versions up to, and including, 0.1. This makes it possible for authenticated attackers, with subscriber-level access and above and under certain prerequisites, to change arbitrary user's passwords, including administrators, and leverage that to gain access to their accounts.\n\ud83d\udccf Published: 2025-04-24T08:23:52.234Z\n\ud83d\udccf Modified: 2025-04-24T08:23:52.234Z\n\ud83d\udd17 References:\n1. https://www.wordfence.com/threat-intel/vulnerabilities/id/e3048c4c-77b1-4778-a5d0-b532df777d06?source=cve\n2. https://plugins.trac.wordpress.org/browser/buddy-press-force-password-change/trunk/bp-force-password-change.php#L93", "creation_timestamp": "2025-04-24T09:12:11.000000Z"}, {"uuid": "a88eb9b7-95c0-4c98-816c-da99d48b95e3", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37799", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/14693", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-37799\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nvmxnet3: Fix malformed packet sizing in vmxnet3_process_xdp\n\nvmxnet3 driver's XDP handling is buggy for packet sizes using ring0 (that\nis, packet sizes between 128 - 3k bytes).\n\nWe noticed MTU-related connectivity issues with Cilium's service load-\nbalancing in case of vmxnet3 as NIC underneath. A simple curl to a HTTP\nbackend service where the XDP LB was doing IPIP encap led to overly large\npacket sizes but only for *some* of the packets (e.g. HTTP GET request)\nwhile others (e.g. the prior TCP 3WHS) looked completely fine on the wire.\n\nIn fact, the pcap recording on the backend node actually revealed that the\nnode with the XDP LB was leaking uninitialized kernel data onto the wire\nfor the affected packets, for example, while the packets should have been\n152 bytes their actual size was 1482 bytes, so the remainder after 152 bytes\nwas padded with whatever other data was in that page at the time (e.g. we\nsaw user/payload data from prior processed packets).\n\nWe only noticed this through an MTU issue, e.g. when the XDP LB node and\nthe backend node both had the same MTU (e.g. 1500) then the curl request\ngot dropped on the backend node's NIC given the packet was too large even\nthough the IPIP-encapped packet normally would never even come close to\nthe MTU limit. Lowering the MTU on the XDP LB (e.g. 1480) allowed to let\nthe curl request succeed (which also indicates that the kernel ignored the\npadding, and thus the issue wasn't very user-visible).\n\nCommit e127ce7699c1 (\"vmxnet3: Fix missing reserved tailroom\") was too eager\nto also switch xdp_prepare_buff() from rcd->len to rbi->len. It really needs\nto stick to rcd->len which is the actual packet length from the descriptor.\nThe latter we also feed into vmxnet3_process_xdp_small(), by the way, and\nit indicates the correct length needed to initialize the xdp->{data,data_end}\nparts. For e127ce7699c1 (\"vmxnet3: Fix missing reserved tailroom\") the\nrelevant part was adapting xdp_init_buff() to address the warning given the\nxdp_data_hard_end() depends on xdp->frame_sz. With that fixed, traffic on\nthe wire looks good again.\n\ud83d\udccf Published: 2025-05-03T11:39:51.924Z\n\ud83d\udccf Modified: 2025-05-03T11:39:51.924Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/4c2227656d9003f4d77afc76f34dd81b95e4c2c4", "creation_timestamp": "2025-05-03T12:17:14.000000Z"}, {"uuid": "6f749204-35fc-44c7-8916-8df503747bf7", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37760", "type": "seen", "source": "https://t.me/DarkWebInformer_CVEAlerts/14797", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-37760\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nmm/vma: add give_up_on_oom option on modify/merge, use in uffd release\n\nCurrently, if a VMA merge fails due to an OOM condition arising on commit\nmerge or a failure to duplicate anon_vma's, we report this so the caller\ncan handle it.\n\nHowever there are cases where the caller is only ostensibly trying a\nmerge, and doesn't mind if it fails due to this condition.\n\nSince we do not want to introduce an implicit assumption that we only\nactually modify VMAs after OOM conditions might arise, add a 'give up on\noom' option and make an explicit contract that, should this flag be set, we\nabsolutely will not modify any VMAs should OOM arise and just bail out.\n\nSince it'd be very unusual for a user to try to vma_modify() with this flag\nset but be specifying a range within a VMA which ends up being split (which\ncan fail due to rlimit issues, not only OOM), we add a debug warning for\nthis condition.\n\nThe motivating reason for this is uffd release - syzkaller (and Pedro\nFalcato's VERY astute analysis) found a way in which an injected fault on\nallocation, triggering an OOM condition on commit merge, would result in\nuffd code becoming confused and treating an error value as if it were a VMA\npointer.\n\nTo avoid this, we make use of this new VMG flag to ensure that this never\noccurs, utilising the fact that, should we be clearing entire VMAs, we do\nnot wish an OOM event to be reported to us.\n\nMany thanks to Pedro Falcato for his excellent analysis and Jann Horn for\nhis insightful and intelligent analysis of the situation, both of whom were\ninstrumental in this fix.\n\ud83d\udccf Published: 2025-05-01T13:07:02.617Z\n\ud83d\udccf Modified: 2025-05-04T13:07:17.678Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/b906c1ad25adce6ff35be19b65a1aa7d960fe1d7\n2. https://git.kernel.org/stable/c/c103a75c61648203d731e3b97a6fbeea4003cb15\n3. https://git.kernel.org/stable/c/41e6ddcaa0f18dda4c3fadf22533775a30d6f72f", "creation_timestamp": "2025-05-04T13:18:39.000000Z"}, {"uuid": "62e57a23-ef2f-4562-9ab6-a37a87bb76cb", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37874", "type": "seen", "source": "https://t.me/DarkWebInformer_CVEAlerts/15697", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-37874\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nnet: ngbe: fix memory leak in ngbe_probe() error path\n\nWhen ngbe_sw_init() is called, memory is allocated for wx->rss_key\nin wx_init_rss_key(). However, in ngbe_probe() function, the subsequent\nerror paths after ngbe_sw_init() don't free the rss_key. Fix that by\nfreeing it in error path along with wx->mac_table.\n\nAlso change the label to which execution jumps when ngbe_sw_init()\nfails, because otherwise, it could lead to a double free for rss_key,\nwhen the mac_table allocation fails in wx_sw_init().\n\ud83d\udccf Published: 2025-05-09T06:44:02.314Z\n\ud83d\udccf Modified: 2025-05-09T06:44:02.314Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/7c2b66a31c7a4866400f7e6fb43cb32021bfca01\n2. https://git.kernel.org/stable/c/8335a3feb9d0d97e5e8f76d38b6bb8573d5b4a29\n3. https://git.kernel.org/stable/c/397487338eff1891c4654ce7deaafbf72a1688b2\n4. https://git.kernel.org/stable/c/88fa80021b77732bc98f73fb69d69c7cc37b9f0d", "creation_timestamp": "2025-05-09T07:25:43.000000Z"}, {"uuid": "93a84e9e-fe4b-4ad9-892b-26a41e665acb", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3782", "type": "seen", "source": "https://t.me/DarkWebInformer_CVEAlerts/15083", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-3782\n\ud83d\udd25 CVSS Score: 6.4 (cvssV3_1, Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N)\n\ud83d\udd39 Description: The Cision Block plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the \u2018id\u2019 parameter in all versions up to, and including, 4.3.0 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with Contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.\n\ud83d\udccf Published: 2025-05-06T09:21:49.867Z\n\ud83d\udccf Modified: 2025-05-06T09:21:49.867Z\n\ud83d\udd17 References:\n1. https://www.wordfence.com/threat-intel/vulnerabilities/id/c5b8268a-f3a3-4576-b235-962de37cc388?source=cve\n2. https://plugins.trac.wordpress.org/browser/cision-block/tags/4.3.0/src/Frontend/templates/cision-block.php#L51\n3. https://wordpress.org/plugins/cision-block/#developers\n4. https://plugins.trac.wordpress.org/changeset/3288041/", "creation_timestamp": "2025-05-06T10:21:03.000000Z"}, {"uuid": "ec08808b-1d40-4fd7-acc9-1cc030efbfb5", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3771", "type": "seen", "source": "https://t.me/DarkWebInformer_CVEAlerts/19587", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-3771\n\ud83d\udd25 CVSS Score: 7.2 (cvssV4_0, Vector: CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:N/VC:L/VI:H/VA:H/SC:L/SI:H/SA:H)\n\ud83d\udd39 Description: A path or symbolic link manipulation vulnerability in SIR 1.0.3 and prior versions allows an authenticated non-admin local user to overwrite system files with SIR backup files, which can potentially cause a system crash. This was achieved by adding a malicious entry to the registry under the Trellix SIR registry folder or via policy or with a junction symbolic link to files that the user would not normally have permission to acces\n\ud83d\udccf Published: 2025-06-26T11:05:18.669Z\n\ud83d\udccf Modified: 2025-06-26T11:13:57.691Z\n\ud83d\udd17 References:\n1. https://thrive.trellix.com/s/article/000014635", "creation_timestamp": "2025-06-26T11:51:19.000000Z"}, {"uuid": "75c7795d-717b-4957-bb23-3bbf406f97be", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37730", "type": "seen", "source": "https://t.me/DarkWebInformer_CVEAlerts/15174", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-37730\n\ud83d\udd25 CVSS Score: 6.5 (cvssV3_1, Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N)\n\ud83d\udd39 Description: Improper certificate validation in Logstash's TCP output could lead to a man-in-the-middle (MitM) attack in \u201cclient\u201d mode, as hostname verification in TCP output was not being performed when the ssl_verification_mode => full was set.\n\ud83d\udccf Published: 2025-05-06T17:29:07.189Z\n\ud83d\udccf Modified: 2025-05-06T17:51:59.631Z\n\ud83d\udd17 References:\n1. https://discuss.elastic.co/t/logstash-8-17-6-8-18-1-and-9-0-1-security-update-esa-2025-08/377869", "creation_timestamp": "2025-05-06T18:21:30.000000Z"}, {"uuid": "d4560db2-8530-4b6d-a566-056f6244f3dc", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3773", "type": "seen", "source": "https://t.me/DarkWebInformer_CVEAlerts/19588", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-3773\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: A sensitive  information exposure vulnerability in System Information Reporter (SIR) 1.0.3 and prior allows an authenticated non-admin local user to extract sensitive information stored in a registry backup folder.\n\ud83d\udccf Published: 2025-06-26T11:11:26.881Z\n\ud83d\udccf Modified: 2025-06-26T11:11:26.881Z\n\ud83d\udd17 References:\n1. https://thrive.trellix.com/s/article/000014635", "creation_timestamp": "2025-06-26T11:51:21.000000Z"}, {"uuid": "db03d653-6d20-4f65-9d90-7a075d58cb42", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3766", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/15269", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-3766\n\ud83d\udd25 CVSS Score: 5.4 (cvssV3_1, Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N)\n\ud83d\udd39 Description: The Login Lockdown & Protection plugin for WordPress is vulnerable to unauthorized nonce access due to a missing capability check on the ajax_run_tool function in all versions up to, and including, 2.11. This makes it possible for authenticated attackers, with Subscriber-level access and above, to obtain a valid nonce that can be used to generate a global unlock key, which can in turn be used to add arbitrary IP address to the plugin allowlist. This can only by exploited on new installations where the site administrator hasn't visited the loginlockdown page yet.\n\ud83d\udccf Published: 2025-05-07T04:22:54.046Z\n\ud83d\udccf Modified: 2025-05-07T04:22:54.046Z\n\ud83d\udd17 References:\n1. https://www.wordfence.com/threat-intel/vulnerabilities/id/ac9a3848-f486-475b-b2c7-ea1007bb30d3?source=cve\n2. https://plugins.trac.wordpress.org/browser/login-lockdown/trunk/libs/ajax.php#L17\n3. https://plugins.trac.wordpress.org/changeset/3286814/login-lockdown", "creation_timestamp": "2025-05-07T05:21:49.000000Z"}, {"uuid": "19f1d80f-59c8-4a79-818b-970a659fe275", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37823", "type": "seen", "source": "https://t.me/DarkWebInformer_CVEAlerts/15486", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-37823\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nnet_sched: hfsc: Fix a potential UAF in hfsc_dequeue() too\n\nSimilarly to the previous patch, we need to safe guard hfsc_dequeue()\ntoo. But for this one, we don't have a reliable reproducer.\n\ud83d\udccf Published: 2025-05-08T06:26:16.839Z\n\ud83d\udccf Modified: 2025-05-08T06:26:16.839Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/68f256305ceb426d545a0dc31f83c2ab1d211a1e\n2. https://git.kernel.org/stable/c/2f46d14919c39528c6e540ebc43f90055993eedc\n3. https://git.kernel.org/stable/c/da7936518996d290e2fcfcaf6cd7e15bfd87804a\n4. https://git.kernel.org/stable/c/11bccb054c1462fb069219f8e98e97a5a730758e\n5. https://git.kernel.org/stable/c/76c4c22c2437d3d3880efc0f62eca06ef078d290\n6. https://git.kernel.org/stable/c/c6f035044104c6ff656f4565cd22938dc892528c\n7. https://git.kernel.org/stable/c/c6936266f8bf98a53f28ef9a820e6a501e946d09\n8. https://git.kernel.org/stable/c/6ccbda44e2cc3d26fd22af54c650d6d5d801addf", "creation_timestamp": "2025-05-08T07:23:11.000000Z"}, {"uuid": "562bd785-17bf-4a7d-92cb-e188ccb0f637", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37831", "type": "seen", "source": "https://t.me/DarkWebInformer_CVEAlerts/15480", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-37831\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\ncpufreq: apple-soc: Fix null-ptr-deref in apple_soc_cpufreq_get_rate()\n\ncpufreq_cpu_get_raw() can return NULL when the target CPU is not present\nin the policy->cpus mask. apple_soc_cpufreq_get_rate() does not check\nfor this case, which results in a NULL pointer dereference.\n\ud83d\udccf Published: 2025-05-08T06:26:22.328Z\n\ud83d\udccf Modified: 2025-05-08T06:26:22.328Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/1053dcf8a504d4933bb3f73df22bc363298d194b\n2. https://git.kernel.org/stable/c/fbdba5f37413dbc09d82ad7235e5b7a2fb8e0f75\n3. https://git.kernel.org/stable/c/01e86ea22610d98ae6141e428019a6916e79f725\n4. https://git.kernel.org/stable/c/9992649f6786921873a9b89dafa5e04d8c5fef2b", "creation_timestamp": "2025-05-08T07:23:05.000000Z"}, {"uuid": "818f24a5-34a6-4767-b9e8-c7e989ee5b72", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37817", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/15492", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-37817\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nmcb: fix a double free bug in chameleon_parse_gdd()\n\nIn chameleon_parse_gdd(), if mcb_device_register() fails, 'mdev'\nwould be released in mcb_device_register() via put_device().\nThus, goto 'err' label and free 'mdev' again causes a double free.\nJust return if mcb_device_register() fails.\n\ud83d\udccf Published: 2025-05-08T06:26:12.683Z\n\ud83d\udccf Modified: 2025-05-08T06:26:12.683Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/d70184958b0ea8c0fd52e2b456654b503e769fc8\n2. https://git.kernel.org/stable/c/4ffe8c9fb561e4427dd1a3056cd5b3685b74f78d\n3. https://git.kernel.org/stable/c/59f993cd36b6e28a394ba3d977e8ffe5c9884e3b\n4. https://git.kernel.org/stable/c/c5b8a549ef1fcc6066b037a3962c79d60465ba0b\n5. https://git.kernel.org/stable/c/96838eb1836fd372e42be5db84f0b333b65146a6\n6. https://git.kernel.org/stable/c/df1a5d5c6134224f9298e5189230f9d29ae50cac\n7. https://git.kernel.org/stable/c/bcc7d58ee5173e34306026bd01e1fbf75e169d37\n8. https://git.kernel.org/stable/c/7c7f1bfdb2249f854a736d9b79778c7e5a29a150", "creation_timestamp": "2025-05-08T07:23:20.000000Z"}, {"uuid": "0be01f55-47a6-4157-8204-0b28b0e6e75b", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3758", "type": "seen", "source": "https://t.me/DarkWebInformer_CVEAlerts/15528", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-3758\n\ud83d\udd25 CVSS Score: 8.7 (cvssV4_0, Vector: CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N)\n\ud83d\udd39 Description: WF2220 exposes endpoint\u00a0/cgi-bin-igd/netcore_get.cgi\u00a0that returns configuration of the device to unauthorized users. Returned configuration includes cleartext password.\nThe vendor was contacted early about this disclosure but did not respond in any way.\n\ud83d\udccf Published: 2025-05-08T10:05:00.716Z\n\ud83d\udccf Modified: 2025-05-08T13:48:47.390Z\n\ud83d\udd17 References:\n1. https://cert.pl/posts/2025/05/CVE-2025-3758\n2. https://cert.pl/en/posts/2025/05/CVE-2025-3758", "creation_timestamp": "2025-05-08T14:23:26.000000Z"}, {"uuid": "561b170e-2419-4907-b2eb-7a232173cfe4", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37834", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/15478", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-37834\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nmm/vmscan: don't try to reclaim hwpoison folio\n\nSyzkaller reports a bug as follows:\n\nInjecting memory failure for pfn 0x18b00e at process virtual address 0x20ffd000\nMemory failure: 0x18b00e: dirty swapcache page still referenced by 2 users\nMemory failure: 0x18b00e: recovery action for dirty swapcache page: Failed\npage: refcount:2 mapcount:0 mapping:0000000000000000 index:0x20ffd pfn:0x18b00e\nmemcg:ffff0000dd6d9000\nanon flags: 0x5ffffe00482011(locked|dirty|arch_1|swapbacked|hwpoison|node=0|zone=2|lastcpupid=0xfffff)\nraw: 005ffffe00482011 dead000000000100 dead000000000122 ffff0000e232a7c9\nraw: 0000000000020ffd 0000000000000000 00000002ffffffff ffff0000dd6d9000\npage dumped because: VM_BUG_ON_FOLIO(!folio_test_uptodate(folio))\n------------[ cut here ]------------\nkernel BUG at mm/swap_state.c:184!\nInternal error: Oops - BUG: 00000000f2000800 [#1] SMP\nModules linked in:\nCPU: 0 PID: 60 Comm: kswapd0 Not tainted 6.6.0-gcb097e7de84e #3\nHardware name: linux,dummy-virt (DT)\npstate: 80400005 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)\npc : add_to_swap+0xbc/0x158\nlr : add_to_swap+0xbc/0x158\nsp : ffff800087f37340\nx29: ffff800087f37340 x28: fffffc00052c0380 x27: ffff800087f37780\nx26: ffff800087f37490 x25: ffff800087f37c78 x24: ffff800087f377a0\nx23: ffff800087f37c50 x22: 0000000000000000 x21: fffffc00052c03b4\nx20: 0000000000000000 x19: fffffc00052c0380 x18: 0000000000000000\nx17: 296f696c6f662865 x16: 7461646f7470755f x15: 747365745f6f696c\nx14: 6f6621284f494c4f x13: 0000000000000001 x12: ffff600036d8b97b\nx11: 1fffe00036d8b97a x10: ffff600036d8b97a x9 : dfff800000000000\nx8 : 00009fffc9274686 x7 : ffff0001b6c5cbd3 x6 : 0000000000000001\nx5 : ffff0000c25896c0 x4 : 0000000000000000 x3 : 0000000000000000\nx2 : 0000000000000000 x1 : ffff0000c25896c0 x0 : 0000000000000000\nCall trace:\n add_to_swap+0xbc/0x158\n shrink_folio_list+0x12ac/0x2648\n shrink_inactive_list+0x318/0x948\n shrink_lruvec+0x450/0x720\n shrink_node_memcgs+0x280/0x4a8\n shrink_node+0x128/0x978\n balance_pgdat+0x4f0/0xb20\n kswapd+0x228/0x438\n kthread+0x214/0x230\n ret_from_fork+0x10/0x20\n\nI can reproduce this issue with the following steps:\n\n1) When a dirty swapcache page is isolated by reclaim process and the\n   page isn't locked, inject memory failure for the page. \n   me_swapcache_dirty() clears uptodate flag and tries to delete from lru,\n   but fails.  Reclaim process will put the hwpoisoned page back to lru.\n\n2) The process that maps the hwpoisoned page exits, the page is deleted\n   the page will never be freed and will be in the lru forever.\n\n3) If we trigger a reclaim again and tries to reclaim the page,\n   add_to_swap() will trigger VM_BUG_ON_FOLIO due to the uptodate flag is\n   cleared.\n\nTo fix it, skip the hwpoisoned page in shrink_folio_list().  Besides, the\nhwpoison folio may not be unmapped by hwpoison_user_mappings() yet, unmap\nit in shrink_folio_list(), otherwise the folio will fail to be unmaped by\nhwpoison_user_mappings() since the folio isn't in lru list.\n\ud83d\udccf Published: 2025-05-08T06:26:24.463Z\n\ud83d\udccf Modified: 2025-05-08T06:26:24.463Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/1c9798bf8145a92abf45aa9d38a6406d9eb8bdf0\n2. https://git.kernel.org/stable/c/912e9f0300c3564b72a8808db406e313193a37ad\n3. https://git.kernel.org/stable/c/1b0449544c6482179ac84530b61fc192a6527bfd", "creation_timestamp": "2025-05-08T07:23:03.000000Z"}, {"uuid": "67dbbe53-6913-4f88-9f5f-dc3d2f5350d5", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37828", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/15483", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-37828\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nscsi: ufs: mcq: Add NULL check in ufshcd_mcq_abort()\n\nA race can occur between the MCQ completion path and the abort handler:\nonce a request completes, __blk_mq_free_request() sets rq->mq_hctx to\nNULL, meaning the subsequent ufshcd_mcq_req_to_hwq() call in\nufshcd_mcq_abort() can return a NULL pointer. If this NULL pointer is\ndereferenced, the kernel will crash.\n\nAdd a NULL check for the returned hwq pointer. If hwq is NULL, log an\nerror and return FAILED, preventing a potential NULL-pointer\ndereference.  As suggested by Bart, the ufshcd_cmd_inflight() check is\nremoved.\n\nThis is similar to the fix in commit 74736103fb41 (\"scsi: ufs: core: Fix\nufshcd_abort_one racing issue\").\n\nThis is found by our static analysis tool KNighter.\n\ud83d\udccf Published: 2025-05-08T06:26:20.135Z\n\ud83d\udccf Modified: 2025-05-08T06:26:20.135Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/d6979fabe812a168d5053e5a41d5a2e9b8afd7bf\n2. https://git.kernel.org/stable/c/7d002f591486f5ef4bc02eb02025a53f931f0eb5\n3. https://git.kernel.org/stable/c/47eec518aef3814f64a5da43df81bdd74d8c0041\n4. https://git.kernel.org/stable/c/4c324085062919d4e21c69e5e78456dcec0052fe", "creation_timestamp": "2025-05-08T07:23:08.000000Z"}, {"uuid": "c7f8631f-7e16-4884-a0c3-5c809f7768b1", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37829", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/15482", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-37829\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\ncpufreq: scpi: Fix null-ptr-deref in scpi_cpufreq_get_rate()\n\ncpufreq_cpu_get_raw() can return NULL when the target CPU is not present\nin the policy->cpus mask. scpi_cpufreq_get_rate() does not check for\nthis case, which results in a NULL pointer dereference.\n\ud83d\udccf Published: 2025-05-08T06:26:21.061Z\n\ud83d\udccf Modified: 2025-05-08T06:26:21.061Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/ad4796f2da495b2cbbd0fccccbcbf63f2aeee613\n2. https://git.kernel.org/stable/c/fdf035d9c5436536ffcfea0ac6adeb5dda3c3a23\n3. https://git.kernel.org/stable/c/8fbaa76690f67a7cbad315f89d607b46e3e06ede\n4. https://git.kernel.org/stable/c/da8ee91e532486055ecf88478d38c2f3dc234182\n5. https://git.kernel.org/stable/c/19e0eaa62e8831f2bc0285fef3bf8faaa7f3e09b\n6. https://git.kernel.org/stable/c/28fbd7b13b4d3074b16db913aedc9d8d37ab41e7\n7. https://git.kernel.org/stable/c/124bddf123311cd1f18bffd63a5d974468d59c67\n8. https://git.kernel.org/stable/c/73b24dc731731edf762f9454552cb3a5b7224949", "creation_timestamp": "2025-05-08T07:23:07.000000Z"}, {"uuid": "156f7553-682b-4fd0-8a02-16a3843c677b", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37830", "type": "seen", "source": "https://t.me/DarkWebInformer_CVEAlerts/15481", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-37830\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\ncpufreq: scmi: Fix null-ptr-deref in scmi_cpufreq_get_rate()\n\ncpufreq_cpu_get_raw() can return NULL when the target CPU is not present\nin the policy->cpus mask. scmi_cpufreq_get_rate() does not check for\nthis case, which results in a NULL pointer dereference.\n\nAdd NULL check after cpufreq_cpu_get_raw() to prevent this issue.\n\ud83d\udccf Published: 2025-05-08T06:26:21.736Z\n\ud83d\udccf Modified: 2025-05-08T06:26:21.736Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/4e3d1c1925d8e752992cd893d03d974e6807ac16\n2. https://git.kernel.org/stable/c/f9c5423855e3687262d881aeee5cfb3bc8577bff\n3. https://git.kernel.org/stable/c/ea834c90aa7cc80a1b456f7a91432734d5087d16\n4. https://git.kernel.org/stable/c/7ccfadfb2562337b4f0462a86a9746a6eea89718\n5. https://git.kernel.org/stable/c/cfaca93b8fe317b7faa9af732e0ba8c9081fa018\n6. https://git.kernel.org/stable/c/484d3f15cc6cbaa52541d6259778e715b2c83c54", "creation_timestamp": "2025-05-08T07:23:06.000000Z"}, {"uuid": "0f0fe4aa-ee23-431d-ba0a-b5fd0b206d87", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37832", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/15479", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-37832\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\ncpufreq: sun50i: prevent out-of-bounds access\n\nA KASAN enabled kernel reports an out-of-bounds access when handling the\nnvmem cell in the sun50i cpufreq driver:\n==================================================================\nBUG: KASAN: slab-out-of-bounds in sun50i_cpufreq_nvmem_probe+0x180/0x3d4\nRead of size 4 at addr ffff000006bf31e0 by task kworker/u16:1/38\n\nThis is because the DT specifies the nvmem cell as covering only two\nbytes, but we use a u32 pointer to read the value. DTs for other SoCs\nindeed specify 4 bytes, so we cannot just shorten the variable to a u16.\n\nFortunately nvmem_cell_read() allows to return the length of the nvmem\ncell, in bytes, so we can use that information to only access the valid\nportion of the data.\nTo cover multiple cell sizes, use memcpy() to copy the information into a\nzeroed u32 buffer, then also make sure we always read the data in little\nendian fashion, as this is how the data is stored in the SID efuses.\n\ud83d\udccf Published: 2025-05-08T06:26:22.965Z\n\ud83d\udccf Modified: 2025-05-08T06:26:22.965Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/40bf7f560ca4c2468d518cebf14561bc864f58f8\n2. https://git.kernel.org/stable/c/dba5a1f963cf781c0b60f4b7f07465a6c687c27e\n3. https://git.kernel.org/stable/c/14c8a418159e541d70dbf8fc71225d1623beaf0f", "creation_timestamp": "2025-05-08T07:23:04.000000Z"}, {"uuid": "d3896b10-c5be-4e06-90ea-24ddb2d03400", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37812", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/15496", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-37812\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nusb: cdns3: Fix deadlock when using NCM gadget\n\nThe cdns3 driver has the same NCM deadlock as fixed in cdnsp by commit\n58f2fcb3a845 (\"usb: cdnsp: Fix deadlock issue during using NCM gadget\").\n\nUnder PREEMPT_RT the deadlock can be readily triggered by heavy network\ntraffic, for example using \"iperf --bidir\" over NCM ethernet link.\n\nThe deadlock occurs because the threaded interrupt handler gets\npreempted by a softirq, but both are protected by the same spinlock.\nPrevent deadlock by disabling softirq during threaded irq handler.\n\ud83d\udccf Published: 2025-05-08T06:26:09.355Z\n\ud83d\udccf Modified: 2025-05-08T06:26:09.355Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/eebfb64c624fc738b669100173344fb441c5e719\n2. https://git.kernel.org/stable/c/59a760e4796a3cd88d8b9d7706e0a638de677751\n3. https://git.kernel.org/stable/c/b96239582531775f2fdcb14de29bdb6870fd4c8c\n4. https://git.kernel.org/stable/c/c27db84ed44e50ff90d9e3a2a25fae2e0a0fa015\n5. https://git.kernel.org/stable/c/48a62deb857f0694f611949015e70ad194d97159\n6. https://git.kernel.org/stable/c/74cd6e408a4c010e404832f0e4609d29bf1d0c41\n7. https://git.kernel.org/stable/c/09e90a9689a4aac7a2f726dc2aa472b0b37937b7\n8. https://git.kernel.org/stable/c/a1059896f2bfdcebcdc7153c3be2307ea319501f", "creation_timestamp": "2025-05-08T07:23:24.000000Z"}, {"uuid": "7edfa7ef-4243-4383-ab90-b19690f4af72", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37813", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/15495", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-37813\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nusb: xhci: Fix invalid pointer dereference in Etron workaround\n\nThis check is performed before prepare_transfer() and prepare_ring(), so\nenqueue can already point at the final link TRB of a segment. And indeed\nit will, some 0.4% of times this code is called.\n\nThen enqueue + 1 is an invalid pointer. It will crash the kernel right\naway or load some junk which may look like a link TRB and cause the real\nlink TRB to be replaced with a NOOP. This wouldn't end well.\n\nUse a functionally equivalent test which doesn't dereference the pointer\nand always gives correct result.\n\nSomething has crashed my machine twice in recent days while playing with\nan Etron HC, and a control transfer stress test ran for confirmation has\njust crashed it again. The same test passes with this patch applied.\n\ud83d\udccf Published: 2025-05-08T06:26:10.000Z\n\ud83d\udccf Modified: 2025-05-08T06:26:10.000Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/142273a49f2c315eabdbdf5a71c15e479b75ca91\n2. https://git.kernel.org/stable/c/bce3055b08e303e28a8751f6073066f5c33a0744\n3. https://git.kernel.org/stable/c/0624e29c595b05e7a0e6d1c368f0a05799928e30\n4. https://git.kernel.org/stable/c/1ea050da5562af9b930d17cbbe9632d30f5df43a", "creation_timestamp": "2025-05-08T07:23:23.000000Z"}, {"uuid": "db26d3a0-05d5-4b40-b0af-9e7e65bdf3cf", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37815", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/15494", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-37815\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nmisc: microchip: pci1xxxx: Fix Kernel panic during IRQ handler registration\n\nResolve kernel panic while accessing IRQ handler associated with the\ngenerated IRQ. This is done by acquiring the spinlock and storing the\ncurrent interrupt state before handling the interrupt request using\ngeneric_handle_irq.\n\nA previous fix patch was submitted where 'generic_handle_irq' was\nreplaced with 'handle_nested_irq'. However, this change also causes\nthe kernel panic where after determining which GPIO triggered the\ninterrupt and attempting to call handle_nested_irq with the mapped\nIRQ number, leads to a failure in locating the registered handler.\n\ud83d\udccf Published: 2025-05-08T06:26:11.402Z\n\ud83d\udccf Modified: 2025-05-08T06:26:11.402Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/1263d5f581908602c618c6665e683c4436383a09\n2. https://git.kernel.org/stable/c/62957f58ab3aa7fa792dc6ff3575624062539a4d\n3. https://git.kernel.org/stable/c/12cc2193f2b9548e8ea5fbce8201b44158222edf\n4. https://git.kernel.org/stable/c/4e02059dc91068bc5017b8546f9ec3b930f6d6a6\n5. https://git.kernel.org/stable/c/18eb77c75ed01439f96ae5c0f33461eb5134b907", "creation_timestamp": "2025-05-08T07:23:22.000000Z"}, {"uuid": "4203b9e5-d8bd-493e-ad66-780ad7f56d8c", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37816", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/15493", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-37816\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nmei: vsc: Fix fortify-panic caused by invalid counted_by() use\n\ngcc 15 honors the __counted_by(len) attribute on vsc_tp_packet.buf[]\nand the vsc-tp.c code is using this in a wrong way. len does not contain\nthe available size in the buffer, it contains the actual packet length\n*without* the crc. So as soon as vsc_tp_xfer() tries to add the crc to\nbuf[] the fortify-panic handler gets triggered:\n\n[   80.842193] memcpy: detected buffer overflow: 4 byte write of buffer size 0\n[   80.842243] WARNING: CPU: 4 PID: 272 at lib/string_helpers.c:1032 __fortify_report+0x45/0x50\n...\n[   80.843175]  __fortify_panic+0x9/0xb\n[   80.843186]  vsc_tp_xfer.cold+0x67/0x67 [mei_vsc_hw]\n[   80.843210]  ? seqcount_lockdep_reader_access.constprop.0+0x82/0x90\n[   80.843229]  ? lockdep_hardirqs_on+0x7c/0x110\n[   80.843250]  mei_vsc_hw_start+0x98/0x120 [mei_vsc]\n[   80.843270]  mei_reset+0x11d/0x420 [mei]\n\nThe easiest fix would be to just drop the counted-by but with the exception\nof the ack buffer in vsc_tp_xfer_helper() which only contains enough room\nfor the packet-header, all other uses of vsc_tp_packet always use a buffer\nof VSC_TP_MAX_XFER_SIZE bytes for the packet.\n\nInstead of just dropping the counted-by, split the vsc_tp_packet struct\ndefinition into a header and a full-packet definition and use a fixed\nsize buf[] in the packet definition, this way fortify-source buffer\noverrun checking still works when enabled.\n\ud83d\udccf Published: 2025-05-08T06:26:12.063Z\n\ud83d\udccf Modified: 2025-05-08T06:26:12.063Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/3e243378f27cc7d11682a3ad720228b0723affa5\n2. https://git.kernel.org/stable/c/ac04663c67f244810b3492e9ecd9f7cdbefeca2d\n3. https://git.kernel.org/stable/c/00f1cc14da0f06d2897b8c528df7c7dcf1b8da50", "creation_timestamp": "2025-05-08T07:23:21.000000Z"}, {"uuid": "edb823a0-89e4-4a7b-8ff4-28dcc0e59370", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37821", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/15488", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-37821\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nsched/eevdf: Fix se->slice being set to U64_MAX and resulting crash\n\nThere is a code path in dequeue_entities() that can set the slice of a\nsched_entity to U64_MAX, which sometimes results in a crash.\n\nThe offending case is when dequeue_entities() is called to dequeue a\ndelayed group entity, and then the entity's parent's dequeue is delayed.\nIn that case:\n\n1. In the if (entity_is_task(se)) else block at the beginning of\n   dequeue_entities(), slice is set to\n   cfs_rq_min_slice(group_cfs_rq(se)). If the entity was delayed, then\n   it has no queued tasks, so cfs_rq_min_slice() returns U64_MAX.\n2. The first for_each_sched_entity() loop dequeues the entity.\n3. If the entity was its parent's only child, then the next iteration\n   tries to dequeue the parent.\n4. If the parent's dequeue needs to be delayed, then it breaks from the\n   first for_each_sched_entity() loop _without updating slice_.\n5. The second for_each_sched_entity() loop sets the parent's ->slice to\n   the saved slice, which is still U64_MAX.\n\nThis throws off subsequent calculations with potentially catastrophic\nresults. A manifestation we saw in production was:\n\n6. In update_entity_lag(), se->slice is used to calculate limit, which\n   ends up as a huge negative number.\n7. limit is used in se->vlag = clamp(vlag, -limit, limit). Because limit\n   is negative, vlag > limit, so se->vlag is set to the same huge\n   negative number.\n8. In place_entity(), se->vlag is scaled, which overflows and results in\n   another huge (positive or negative) number.\n9. The adjusted lag is subtracted from se->vruntime, which increases or\n   decreases se->vruntime by a huge number.\n10. pick_eevdf() calls entity_eligible()/vruntime_eligible(), which\n    incorrectly returns false because the vruntime is so far from the\n    other vruntimes on the queue, causing the\n    (vruntime - cfs_rq->min_vruntime) * load calulation to overflow.\n11. Nothing appears to be eligible, so pick_eevdf() returns NULL.\n12. pick_next_entity() tries to dereference the return value of\n    pick_eevdf() and crashes.\n\nDumping the cfs_rq states from the core dumps with drgn showed tell-tale\nhuge vruntime ranges and bogus vlag values, and I also traced se->slice\nbeing set to U64_MAX on live systems (which was usually \"benign\" since\nthe rest of the runqueue needed to be in a particular state to crash).\n\nFix it in dequeue_entities() by always setting slice from the first\nnon-empty cfs_rq.\n\ud83d\udccf Published: 2025-05-08T06:26:15.535Z\n\ud83d\udccf Modified: 2025-05-08T06:26:15.535Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/50a665496881262519f115f1bfe5822f30580eb0\n2. https://git.kernel.org/stable/c/bbce3de72be56e4b5f68924b7da9630cc89aa1a8", "creation_timestamp": "2025-05-08T07:23:13.000000Z"}, {"uuid": "0f5f4104-e3d7-484b-8a14-4640331c12f4", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37822", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/15487", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-37822\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nriscv: uprobes: Add missing fence.i after building the XOL buffer\n\nThe XOL (execute out-of-line) buffer is used to single-step the\nreplaced instruction(s) for uprobes. The RISC-V port was missing a\nproper fence.i (i$ flushing) after constructing the XOL buffer, which\ncan result in incorrect execution of stale/broken instructions.\n\nThis was found running the BPF selftests \"test_progs:\nuprobe_autoattach, attach_probe\" on the Spacemit K1/X60, where the\nuprobes tests randomly blew up.\n\ud83d\udccf Published: 2025-05-08T06:26:16.209Z\n\ud83d\udccf Modified: 2025-05-08T06:26:16.209Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/bcf6d3158c5902d92b6d62335af4422b7bf7c4e2\n2. https://git.kernel.org/stable/c/1dbb95a36499374c51b47ee8ae258a8862c20978\n3. https://git.kernel.org/stable/c/7d1d19a11cfbfd8bae1d89cc010b2cc397cd0c48", "creation_timestamp": "2025-05-08T07:23:12.000000Z"}, {"uuid": "6783f321-3956-4649-94f0-77e8c71b0198", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37825", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/15485", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-37825\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nnvmet: fix out-of-bounds access in nvmet_enable_port\n\nWhen trying to enable a port that has no transport configured yet,\nnvmet_enable_port() uses NVMF_TRTYPE_MAX (255) to query the transports\narray, causing an out-of-bounds access:\n\n[  106.058694] BUG: KASAN: global-out-of-bounds in nvmet_enable_port+0x42/0x1da\n[  106.058719] Read of size 8 at addr ffffffff89dafa58 by task ln/632\n[...]\n[  106.076026] nvmet: transport type 255 not supported\n\nSince commit 200adac75888, NVMF_TRTYPE_MAX is the default state as configured by\nnvmet_ports_make().\nAvoid this by checking for NVMF_TRTYPE_MAX before proceeding.\n\ud83d\udccf Published: 2025-05-08T06:26:18.094Z\n\ud83d\udccf Modified: 2025-05-08T06:26:18.094Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/83c00860a37b3fcba8026cb344101f1b8af547cf\n2. https://git.kernel.org/stable/c/3d7aa0c7b4e96cd460826d932e44710cdeb3378b", "creation_timestamp": "2025-05-08T07:23:10.000000Z"}, {"uuid": "6c3d425f-ff56-4d6d-90c2-932016b6d586", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37826", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/15484", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-37826\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nscsi: ufs: core: Add NULL check in ufshcd_mcq_compl_pending_transfer()\n\nAdd a NULL check for the returned hwq pointer by ufshcd_mcq_req_to_hwq().\n\nThis is similar to the fix in commit 74736103fb41 (\"scsi: ufs: core: Fix\nufshcd_abort_one racing issue\").\n\ud83d\udccf Published: 2025-05-08T06:26:18.694Z\n\ud83d\udccf Modified: 2025-05-08T06:26:18.694Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/eeab6618037be84e438e9d6ed5d9a53502faf81f\n2. https://git.kernel.org/stable/c/700128d67d57bb1de4251e563ab85202def36c50\n3. https://git.kernel.org/stable/c/08a966a917fe3d92150fa3cc15793ad5e57051eb", "creation_timestamp": "2025-05-08T07:23:09.000000Z"}, {"uuid": "d19c2ce4-dbfa-47a0-a967-6367fe99d926", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37818", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/15491", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-37818\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nLoongArch: Return NULL from huge_pte_offset() for invalid PMD\n\nLoongArch's huge_pte_offset() currently returns a pointer to a PMD slot\neven if the underlying entry points to invalid_pte_table (indicating no\nmapping). Callers like smaps_hugetlb_range() fetch this invalid entry\nvalue (the address of invalid_pte_table) via this pointer.\n\nThe generic is_swap_pte() check then incorrectly identifies this address\nas a swap entry on LoongArch, because it satisfies the \"!pte_present()\n&& !pte_none()\" conditions. This misinterpretation, combined with a\ncoincidental match by is_migration_entry() on the address bits, leads to\nkernel crashes in pfn_swap_entry_to_page().\n\nFix this at the architecture level by modifying huge_pte_offset() to\ncheck the PMD entry's content using pmd_none() before returning. If the\nentry is invalid (i.e., it points to invalid_pte_table), return NULL\ninstead of the pointer to the slot.\n\ud83d\udccf Published: 2025-05-08T06:26:13.322Z\n\ud83d\udccf Modified: 2025-05-08T06:26:13.322Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/34256805720993e37adf6127371a1265aea8376a\n2. https://git.kernel.org/stable/c/2ca9380b12711afe95b3589bd82b59623b3c96b3\n3. https://git.kernel.org/stable/c/51424fd171cee6a33f01f7c66b8eb23ac42289d4\n4. https://git.kernel.org/stable/c/b49f085cd671addbda4802d6b9382513f7dd0f30\n5. https://git.kernel.org/stable/c/bd51834d1cf65a2c801295d230c220aeebf87a73", "creation_timestamp": "2025-05-08T07:23:16.000000Z"}, {"uuid": "a81cebb4-7c9e-48a7-8ca2-d78ba880f526", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37819", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/15490", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-37819\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nirqchip/gic-v2m: Prevent use after free of gicv2m_get_fwnode()\n\nWith ACPI in place, gicv2m_get_fwnode() is registered with the pci\nsubsystem as pci_msi_get_fwnode_cb(), which may get invoked at runtime\nduring a PCI host bridge probe. But, the call back is wrongly marked as\n__init, causing it to be freed, while being registered with the PCI\nsubsystem and could trigger:\n\n Unable to handle kernel paging request at virtual address ffff8000816c0400\n  gicv2m_get_fwnode+0x0/0x58 (P)\n  pci_set_bus_msi_domain+0x74/0x88\n  pci_register_host_bridge+0x194/0x548\n\nThis is easily reproducible on a Juno board with ACPI boot.\n\nRetain the function for later use.\n\ud83d\udccf Published: 2025-05-08T06:26:13.975Z\n\ud83d\udccf Modified: 2025-05-08T06:26:13.975Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/2f2803e4b5e4df2b08d378deaab78b1681ef9b30\n2. https://git.kernel.org/stable/c/3939d6f29d34cdb60e3f68b76e39e00a964a1d51\n3. https://git.kernel.org/stable/c/47bee0081b483b077c7560bc5358ad101f89c8ef\n4. https://git.kernel.org/stable/c/3318dc299b072a0511d6dfd8367f3304fb6d9827", "creation_timestamp": "2025-05-08T07:23:15.000000Z"}, {"uuid": "f1f53f49-9639-4f6d-8ee5-67f9c73f44b6", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37820", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/15489", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-37820\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nxen-netfront: handle NULL returned by xdp_convert_buff_to_frame()\n\nThe function xdp_convert_buff_to_frame() may return NULL if it fails\nto correctly convert the XDP buffer into an XDP frame due to memory\nconstraints, internal errors, or invalid data. Failing to check for NULL\nmay lead to a NULL pointer dereference if the result is used later in\nprocessing, potentially causing crashes, data corruption, or undefined\nbehavior.\n\nOn XDP redirect failure, the associated page must be released explicitly\nif it was previously retained via get_page(). Failing to do so may result\nin a memory leak, as the pages reference count is not decremented.\n\ud83d\udccf Published: 2025-05-08T06:26:14.602Z\n\ud83d\udccf Modified: 2025-05-08T06:26:14.602Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/5b83d30c63f9964acb1bc63eb8e670b9e0d2c240\n2. https://git.kernel.org/stable/c/cefd8a2e2de46209ce66e6d30c237eb59b6c5bfa\n3. https://git.kernel.org/stable/c/d6a9c4e6f9b3ec3ad98468c950ad214af8a2efb9\n4. https://git.kernel.org/stable/c/eefccd889df3b49d92e7349d94c4aa7e1ba19f6c\n5. https://git.kernel.org/stable/c/cc3628dcd851ddd8d418bf0c897024b4621ddc92", "creation_timestamp": "2025-05-08T07:23:14.000000Z"}, {"uuid": "d6aca02c-dbe8-41da-be9a-9ec1e9e7be43", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37877", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/15695", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-37877\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\niommu: Clear iommu-dma ops on cleanup\n\nIf iommu_device_register() encounters an error, it can end up tearing\ndown already-configured groups and default domains, however this\ncurrently still leaves devices hooked up to iommu-dma (and even\nhistorically the behaviour in this area was at best inconsistent across\narchitectures/drivers...) Although in the case that an IOMMU is present\nwhose driver has failed to probe, users cannot necessarily expect DMA to\nwork anyway, it's still arguable that we should do our best to put\nthings back as if the IOMMU driver was never there at all, and certainly\nthe potential for crashing in iommu-dma itself is undesirable. Make sure\nwe clean up the dev->dma_iommu flag along with everything else.\n\ud83d\udccf Published: 2025-05-09T06:45:41.751Z\n\ud83d\udccf Modified: 2025-05-09T06:45:41.751Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/b14d98641312d972bb3f38e82eddf92898522389\n2. https://git.kernel.org/stable/c/104a84276821aed0ed241ce0d82d6c3267e3fcb8\n3. https://git.kernel.org/stable/c/280e5a30100578106a4305ce0118e0aa9b866f12", "creation_timestamp": "2025-05-09T07:25:40.000000Z"}, {"uuid": "0dc82b9c-8467-4695-93a1-e7a59f861487", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37878", "type": "seen", "source": "https://t.me/DarkWebInformer_CVEAlerts/15694", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-37878\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nperf/core: Fix WARN_ON(!ctx) in __free_event() for partial init\n\nMove the get_ctx(child_ctx) call and the child_event->ctx assignment to\noccur immediately after the child event is allocated. Ensure that\nchild_event->ctx is non-NULL before any subsequent error path within\ninherit_event calls free_event(), satisfying the assumptions of the\ncleanup code.\n\nDetails:\n\nThere's no clear Fixes tag, because this bug is a side-effect of\nmultiple interacting commits over time (up to 15 years old), not\na single regression.\n\nThe code initially incremented refcount then assigned context\nimmediately after the child_event was created. Later, an early\nvalidity check for child_event was added before the\nrefcount/assignment. Even later, a WARN_ON_ONCE() cleanup check was\nadded, assuming event->ctx is valid if the pmu_ctx is valid.\nThe problem is that the WARN_ON_ONCE() could trigger after the initial\ncheck passed but before child_event->ctx was assigned, violating its\nprecondition. The solution is to assign child_event->ctx right after\nits initial validation. This ensures the context exists for any\nsubsequent checks or cleanup routines, resolving the WARN_ON_ONCE().\n\nTo resolve it, defer the refcount update and child_event->ctx assignment\ndirectly after child_event->pmu_ctx is set but before checking if the\nparent event is orphaned. The cleanup routine depends on\nevent->pmu_ctx being non-NULL before it verifies event->ctx is\nnon-NULL. This also maintains the author's original intent of passing\nin child_ctx to find_get_pmu_context before its refcount/assignment.\n\n[ mingo: Expanded the changelog from another email by Gabriel Shahrouzi. ]\n\ud83d\udccf Published: 2025-05-09T06:45:42.459Z\n\ud83d\udccf Modified: 2025-05-09T06:45:42.459Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/1fe9b92eede32574dbe05b5bdb6ad666b350bed0\n2. https://git.kernel.org/stable/c/90dc6c1e3b200812da8d0aa030e1b7fda8226d0e\n3. https://git.kernel.org/stable/c/cb56cd11feabf99e08bc18960700a53322ffcea7\n4. https://git.kernel.org/stable/c/0ba3a4ab76fd3367b9cb680cad70182c896c795c", "creation_timestamp": "2025-05-09T07:25:40.000000Z"}, {"uuid": "4073bf82-6407-4098-8592-ca9e6eb9470b", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37880", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/15693", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-37880\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\num: work around sched_yield not yielding in time-travel mode\n\nsched_yield by a userspace may not actually cause scheduling in\ntime-travel mode as no time has passed. In the case seen it appears to\nbe a badly implemented userspace spinlock in ASAN. Unfortunately, with\ntime-travel it causes an extreme slowdown or even deadlock depending on\nthe kernel configuration (CONFIG_UML_MAX_USERSPACE_ITERATIONS).\n\nWork around it by accounting time to the process whenever it executes a\nsched_yield syscall.\n\ud83d\udccf Published: 2025-05-09T06:45:44.117Z\n\ud83d\udccf Modified: 2025-05-09T06:45:44.117Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/da780c4a075ba2deb05ae29f0af4a990578c7901\n2. https://git.kernel.org/stable/c/990ddc65173776f1e01e7135d8c1fd5f8fd4d5d2\n3. https://git.kernel.org/stable/c/887c5c12e80c8424bd471122d2e8b6b462e12874", "creation_timestamp": "2025-05-09T07:25:38.000000Z"}, {"uuid": "32b90a80-c26a-4cc5-a8b1-a282f25a5a1e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37881", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/15692", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-37881\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nusb: gadget: aspeed: Add NULL pointer check in ast_vhub_init_dev()\n\nThe variable d->name, returned by devm_kasprintf(), could be NULL.\nA pointer check is added to prevent potential NULL pointer dereference.\nThis is similar to the fix in commit 3027e7b15b02\n(\"ice: Fix some null pointer dereference issues in ice_ptp.c\").\n\nThis issue is found by our static analysis tool\n\ud83d\udccf Published: 2025-05-09T06:45:45.205Z\n\ud83d\udccf Modified: 2025-05-09T06:45:45.205Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/a777ccfb9ba8d43f745e41b69ba39d4a506a081e\n2. https://git.kernel.org/stable/c/c8d4faf452a627f9b09c3a5c366133a19e5b7a28\n3. https://git.kernel.org/stable/c/d26a6093d52904cacdbb75424c323c19b443a890\n4. https://git.kernel.org/stable/c/36d68151712e525450f0fbb3045e7110f0d9b610\n5. https://git.kernel.org/stable/c/cfa7984f69359761b07a7831c1258c0fde1e0389\n6. https://git.kernel.org/stable/c/052fb65335befeae8500e88d69ea022266baaf6d\n7. https://git.kernel.org/stable/c/61006ca381b4d65d2b8ca695ea8da1ce18d6dee3\n8. https://git.kernel.org/stable/c/8c75f3e6a433d92084ad4e78b029ae680865420f", "creation_timestamp": "2025-05-09T07:25:35.000000Z"}, {"uuid": "1dbd66f3-fdbd-4607-95d2-98211f424337", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37886", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/15687", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-37886\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\npds_core: make wait_context part of q_info\n\nMake the wait_context a full part of the q_info struct rather\nthan a stack variable that goes away after pdsc_adminq_post()\nis done so that the context is still available after the wait\nloop has given up.\n\nThere was a case where a slow development firmware caused\nthe adminq request to time out, but then later the FW finally\nfinished the request and sent the interrupt.  The handler tried\nto complete_all() the completion context that had been created\non the stack in pdsc_adminq_post() but no longer existed.\nThis caused bad pointer usage, kernel crashes, and much wailing\nand gnashing of teeth.\n\ud83d\udccf Published: 2025-05-09T06:45:48.810Z\n\ud83d\udccf Modified: 2025-05-09T06:45:48.810Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/1d7c4b2b0bbfb09b55b2dc0e2355d7936bf89381\n2. https://git.kernel.org/stable/c/66d7702b42ffdf0dce4808626088268a4e905ca6\n3. https://git.kernel.org/stable/c/520f012fe75fb8efc9f16a57ef929a7a2115d892\n4. https://git.kernel.org/stable/c/3f77c3dfffc7063428b100c4945ca2a7a8680380", "creation_timestamp": "2025-05-09T07:25:28.000000Z"}, {"uuid": "ffa31f00-a989-47fb-aa25-bc20be106166", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37887", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/15686", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-37887\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\npds_core: handle unsupported PDS_CORE_CMD_FW_CONTROL result\n\nIf the FW doesn't support the PDS_CORE_CMD_FW_CONTROL command\nthe driver might at the least print garbage and at the worst\ncrash when the user runs the \"devlink dev info\" devlink command.\n\nThis happens because the stack variable fw_list is not 0\ninitialized which results in fw_list.num_fw_slots being a\ngarbage value from the stack.  Then the driver tries to access\nfw_list.fw_names[i] with i >= ARRAY_SIZE and runs off the end\nof the array.\n\nFix this by initializing the fw_list and by not failing\ncompletely if the devcmd fails because other useful information\nis printed via devlink dev info even if the devcmd fails.\n\ud83d\udccf Published: 2025-05-09T06:45:49.492Z\n\ud83d\udccf Modified: 2025-05-09T06:45:49.492Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/cdd784c96fe2e5edbf0ed9b3e96fe776e8092385\n2. https://git.kernel.org/stable/c/6702f5c6b22deaa95bf84f526148174a160a02cb\n3. https://git.kernel.org/stable/c/12a4651a80dbe4589a84e26785fbbe1ed4d043b7\n4. https://git.kernel.org/stable/c/2567daad69cd1107fc0ec29b1615f110d7cf7385", "creation_timestamp": "2025-05-09T07:25:27.000000Z"}, {"uuid": "56c414d7-0b20-4a27-b99c-a6ad549737e1", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37888", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/15685", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-37888\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nnet/mlx5: Fix null-ptr-deref in mlx5_create_{inner_,}ttc_table()\n\nAdd NULL check for mlx5_get_flow_namespace() returns in\nmlx5_create_inner_ttc_table() and mlx5_create_ttc_table() to prevent\nNULL pointer dereference.\n\ud83d\udccf Published: 2025-05-09T06:45:50.128Z\n\ud83d\udccf Modified: 2025-05-09T06:45:50.128Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/0b682680b12b08cd62b113ea92b2938195de1dfe\n2. https://git.kernel.org/stable/c/ecd9d2647ddb4f42a121de648e48659ae1856c39\n3. https://git.kernel.org/stable/c/91037037ee3d611ce17f39d75f79c7de394b122a", "creation_timestamp": "2025-05-09T07:25:25.000000Z"}, {"uuid": "69fc8a5a-03fb-48e4-8352-f524bde3c6b2", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37889", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/15684", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-37889\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nPCI/MSI: Handle the NOMASK flag correctly for all PCI/MSI backends\n\nThe conversion of the XEN specific global variable pci_msi_ignore_mask to a\nMSI domain flag, missed the facts that:\n\n    1) Legacy architectures do not provide a interrupt domain\n    2) Parent MSI domains do not necessarily have a domain info attached\n   \nBoth cases result in an unconditional NULL pointer dereference. This was\nunfortunatly missed in review and testing revealed it late.\n\nCure this by using the existing pci_msi_domain_supports() helper, which\nhandles all possible cases correctly.\n\ud83d\udccf Published: 2025-05-09T06:45:50.868Z\n\ud83d\udccf Modified: 2025-05-09T06:45:50.868Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/46d357520934eef99fa121889f8ebbf46a6eddb8\n2. https://git.kernel.org/stable/c/2e3ad60b8f72a95e3a32ddd9d70ea129aa3fcfb7\n3. https://git.kernel.org/stable/c/3ece3e8e5976c49c3f887e5923f998eabd54ff40", "creation_timestamp": "2025-05-09T07:25:24.000000Z"}, {"uuid": "a39a967a-c843-4ce2-ac71-3b65a1d84a2f", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3713", "type": "seen", "source": "https://t.me/DarkWebInformer_CVEAlerts/15662", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-3713\n\ud83d\udd25 CVSS Score: 7.5 (cvssV3_1, Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H)\n\ud83d\udd39 Description: The LCD KVM over IP Switch CL5708IM has a Heap-based Buffer Overflow vulnerability, allowing unauthenticated remote attackers to exploit this vulnerability to perform a denial-of-service attack.\n\ud83d\udccf Published: 2025-05-09T04:03:13.030Z\n\ud83d\udccf Modified: 2025-05-09T04:03:13.030Z\n\ud83d\udd17 References:\n1. https://www.twcert.org.tw/tw/cp-132-10098-1a66d-1.html\n2. https://www.twcert.org.tw/en/cp-139-10106-9080f-2.html", "creation_timestamp": "2025-05-09T04:24:53.000000Z"}, {"uuid": "718fdd30-b545-427c-9c5c-b64ee1a33856", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3714", "type": "seen", "source": "https://t.me/DarkWebInformer_CVEAlerts/15661", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-3714\n\ud83d\udd25 CVSS Score: 9.8 (cvssV3_1, Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H)\n\ud83d\udd39 Description: The LCD KVM over IP Switch CL5708IM has a Stack-based Buffer Overflow vulnerability, allowing unauthenticated remote attackers to exploit this vulnerability to execute arbitrary code on the device.\n\ud83d\udccf Published: 2025-05-09T04:08:57.461Z\n\ud83d\udccf Modified: 2025-05-09T04:08:57.461Z\n\ud83d\udd17 References:\n1. https://www.twcert.org.tw/tw/cp-132-10099-0ad69-1.html\n2. https://www.twcert.org.tw/en/cp-139-10107-26b24-2.html", "creation_timestamp": "2025-05-09T04:24:51.000000Z"}, {"uuid": "6107e335-e694-41a2-ae13-285055d8f988", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3710", "type": "seen", "source": "https://t.me/DarkWebInformer_CVEAlerts/15667", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-3710\n\ud83d\udd25 CVSS Score: 9.8 (cvssV3_1, Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H)\n\ud83d\udd39 Description: The LCD KVM over IP Switch CL5708IM has a Stack-based Buffer Overflow vulnerability, allowing unauthenticated remote attackers to exploit this vulnerability to execute arbitrary code on the device.\n\ud83d\udccf Published: 2025-05-09T03:53:55.759Z\n\ud83d\udccf Modified: 2025-05-09T03:53:55.759Z\n\ud83d\udd17 References:\n1. https://www.twcert.org.tw/tw/cp-132-10095-a0f57-1.html\n2. https://www.twcert.org.tw/en/cp-139-10103-32121-2.html", "creation_timestamp": "2025-05-09T04:24:58.000000Z"}, {"uuid": "242442b7-d9a5-4583-8aea-79d6d5960a5a", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3711", "type": "seen", "source": "https://t.me/DarkWebInformer_CVEAlerts/15666", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-3711\n\ud83d\udd25 CVSS Score: 9.8 (cvssV3_1, Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H)\n\ud83d\udd39 Description: The LCD KVM over IP Switch CL5708IM has a Stack-based Buffer Overflow vulnerability, allowing unauthenticated remote attackers to exploit this vulnerability to execute arbitrary code on the device.\n\ud83d\udccf Published: 2025-05-09T03:56:50.320Z\n\ud83d\udccf Modified: 2025-05-09T03:56:50.320Z\n\ud83d\udd17 References:\n1. https://www.twcert.org.tw/tw/cp-132-10096-60a81-1.html\n2. https://www.twcert.org.tw/en/cp-139-10104-63bf4-2.html", "creation_timestamp": "2025-05-09T04:24:57.000000Z"}, {"uuid": "0043881a-defd-4cf0-a52b-6dd1de831ea8", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3712", "type": "seen", "source": "https://t.me/DarkWebInformer_CVEAlerts/15663", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-3712\n\ud83d\udd25 CVSS Score: 7.5 (cvssV3_1, Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H)\n\ud83d\udd39 Description: The LCD KVM over IP Switch CL5708IM has a Heap-based Buffer Overflow vulnerability, allowing unauthenticated remote attackers to exploit this vulnerability to perform a denial-of-service attack.\n\ud83d\udccf Published: 2025-05-09T04:00:11.812Z\n\ud83d\udccf Modified: 2025-05-09T04:00:11.812Z\n\ud83d\udd17 References:\n1. https://www.twcert.org.tw/tw/cp-132-10097-326fa-1.html\n2. https://www.twcert.org.tw/en/cp-139-10105-1e8b5-2.html", "creation_timestamp": "2025-05-09T04:24:53.000000Z"}, {"uuid": "cc1445ee-1885-4bd0-a0a1-cd01abfc8283", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37885", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/15688", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-37885\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nKVM: x86: Reset IRTE to host control if *new* route isn't postable\n\nRestore an IRTE back to host control (remapped or posted MSI mode) if the\n*new* GSI route prevents posting the IRQ directly to a vCPU, regardless of\nthe GSI routing type.  Updating the IRTE if and only if the new GSI is an\nMSI results in KVM leaving an IRTE posting to a vCPU.\n\nThe dangling IRTE can result in interrupts being incorrectly delivered to\nthe guest, and in the worst case scenario can result in use-after-free,\ne.g. if the VM is torn down, but the underlying host IRQ isn't freed.\n\ud83d\udccf Published: 2025-05-09T06:45:48.150Z\n\ud83d\udccf Modified: 2025-05-09T06:45:48.150Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/e5f2dee9f7fcd2ff4b97869f3c66a0d89c167769\n2. https://git.kernel.org/stable/c/116c7d35b8f72eac383b9fd371d7c1a8ffc2968b\n3. https://git.kernel.org/stable/c/023816bd5fa46fab94d1e7917fe131b79ed1fb41\n4. https://git.kernel.org/stable/c/3481fd96d801715942b6f69fe251133128156f30\n5. https://git.kernel.org/stable/c/b5de7ac74f69603ad803c524b840bffd36368fc3\n6. https://git.kernel.org/stable/c/3066ec21d1a33896125747f68638725f456308db\n7. https://git.kernel.org/stable/c/9bcac97dc42d2f4da8229d18feb0fe2b1ce523a2", "creation_timestamp": "2025-05-09T07:25:29.000000Z"}, {"uuid": "7c25face-5398-419b-bb7c-20aa0a12bc14", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37882", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/15691", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-37882\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nusb: xhci: Fix isochronous Ring Underrun/Overrun event handling\n\nThe TRB pointer of these events points at enqueue at the time of error\noccurrence on xHCI 1.1+ HCs or it's NULL on older ones. By the time we\nare handling the event, a new TD may be queued at this ring position.\n\nI can trigger this race by rising interrupt moderation to increase IRQ\nhandling delay. Similar delay may occur naturally due to system load.\n\nIf this ever happens after a Missed Service Error, missed TDs will be\nskipped and the new TD processed as if it matched the event. It could\nbe given back prematurely, risking data loss or buffer UAF by the xHC.\n\nDon't complete TDs on xrun events and don't warn if queued TDs don't\nmatch the event's TRB pointer, which can be NULL or a link/no-op TRB.\nDon't warn if there are no queued TDs at all.\n\nNow that it's safe, also handle xrun events if the skip flag is clear.\nThis ensures completion of any TD stuck in 'error mid TD' state right\nbefore the xrun event, which could happen if a driver submits a finite\nnumber of URBs to a buggy HC and then an error occurs on the last TD.\n\ud83d\udccf Published: 2025-05-09T06:45:45.936Z\n\ud83d\udccf Modified: 2025-05-09T06:45:45.936Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/16a7a8e6c47fea5c847beb696c8c21a7a44c1915\n2. https://git.kernel.org/stable/c/39a080a2925c81b0f1da0add44722ef2b78e5454\n3. https://git.kernel.org/stable/c/906dec15b9b321b546fd31a3c99ffc13724c7af4", "creation_timestamp": "2025-05-09T07:25:31.000000Z"}, {"uuid": "1f2a8268-7736-47b3-82e9-076fd7ce7ffd", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37883", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/15690", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-37883\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\ns390/sclp: Add check for get_zeroed_page()\n\nAdd check for the return value of get_zeroed_page() in\nsclp_console_init() to prevent null pointer dereference.\nFurthermore, to solve the memory leak caused by the loop\nallocation, add a free helper to do the free job.\n\ud83d\udccf Published: 2025-05-09T06:45:46.716Z\n\ud83d\udccf Modified: 2025-05-09T06:45:46.716Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/e1e00dc45648125ef7cb87ebc3b581ac224e7b39\n2. https://git.kernel.org/stable/c/397254706eba9d8f99fd237feede7ab3169a7f9a\n3. https://git.kernel.org/stable/c/28e5a867aa542e369e211c2baba7044228809a99\n4. https://git.kernel.org/stable/c/3b3aa72636a6205933609ec274a8747720c1ee3f\n5. https://git.kernel.org/stable/c/f69f8a93aacf6e99af7b1cc992d8ca2cc07b96fb\n6. https://git.kernel.org/stable/c/3db42c75a921854a99db0a2775814fef97415bac", "creation_timestamp": "2025-05-09T07:25:30.000000Z"}, {"uuid": "597f713b-0c1c-4f4b-a594-09aff167b268", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37884", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/15689", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-37884\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Fix deadlock between rcu_tasks_trace and event_mutex.\n\nFix the following deadlock:\nCPU A\n_free_event()\n  perf_kprobe_destroy()\n    mutex_lock(&event_mutex)\n      perf_trace_event_unreg()\n        synchronize_rcu_tasks_trace()\n\nThere are several paths where _free_event() grabs event_mutex\nand calls sync_rcu_tasks_trace. Above is one such case.\n\nCPU B\nbpf_prog_test_run_syscall()\n  rcu_read_lock_trace()\n    bpf_prog_run_pin_on_cpu()\n      bpf_prog_load()\n        bpf_tracing_func_proto()\n          trace_set_clr_event()\n            mutex_lock(&event_mutex)\n\nDelegate trace_set_clr_event() to workqueue to avoid\nsuch lock dependency.\n\ud83d\udccf Published: 2025-05-09T06:45:47.462Z\n\ud83d\udccf Modified: 2025-05-09T06:45:47.462Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/255cbc9db7067a83713fd2f4b31034ddd266549a\n2. https://git.kernel.org/stable/c/b5a528a34e1f613565115a7a6016862ccbfcb9ac\n3. https://git.kernel.org/stable/c/c5c833f6375f8ecf9254dd27946c927c7d645421\n4. https://git.kernel.org/stable/c/45286680b385f2592db3003554872388dee66d68\n5. https://git.kernel.org/stable/c/4580f4e0ebdf8dc8d506ae926b88510395a0c1d1", "creation_timestamp": "2025-05-09T07:25:29.000000Z"}, {"uuid": "0dd40af9-ce8a-40b6-a716-cdf16bd1bb39", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37873", "type": "seen", "source": "https://t.me/DarkWebInformer_CVEAlerts/15698", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-37873\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\neth: bnxt: fix missing ring index trim on error path\n\nCommit under Fixes converted tx_prod to be free running but missed\nmasking it on the Tx error path. This crashes on error conditions,\nfor example when DMA mapping fails.\n\ud83d\udccf Published: 2025-05-09T06:44:01.394Z\n\ud83d\udccf Modified: 2025-05-09T06:44:01.394Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/21e70f694bc0dcb40174b0940cc52a7769fc19e0\n2. https://git.kernel.org/stable/c/3742c55de00266fa7c8fd2c5d61a453d223a9cd1\n3. https://git.kernel.org/stable/c/12f2d033fae957d84c2c0ce604d2a077e61fa2c0", "creation_timestamp": "2025-05-09T07:25:44.000000Z"}, {"uuid": "38076f65-83ea-4725-89ad-dbaad0d398e6", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37875", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/15696", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-37875\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nigc: fix PTM cycle trigger logic\n\nWriting to clear the PTM status 'valid' bit while the PTM cycle is\ntriggered results in unreliable PTM operation. To fix this, clear the\nPTM 'trigger' and status after each PTM transaction.\n\nThe issue can be reproduced with the following:\n\n$ sudo phc2sys -R 1000 -O 0 -i tsn0 -m\n\nNote: 1000 Hz (-R 1000) is unrealistically large, but provides a way to\nquickly reproduce the issue.\n\nPHC2SYS exits with:\n\n\"ioctl PTP_OFFSET_PRECISE: Connection timed out\" when the PTM transaction\n  fails\n\nThis patch also fixes a hang in igc_probe() when loading the igc\ndriver in the kdump kernel on systems supporting PTM.\n\nThe igc driver running in the base kernel enables PTM trigger in\nigc_probe().  Therefore the driver is always in PTM trigger mode,\nexcept in brief periods when manually triggering a PTM cycle.\n\nWhen a crash occurs, the NIC is reset while PTM trigger is enabled.\nDue to a hardware problem, the NIC is subsequently in a bad busmaster\nstate and doesn't handle register reads/writes.  When running\nigc_probe() in the kdump kernel, the first register access to a NIC\nregister hangs driver probing and ultimately breaks kdump.\n\nWith this patch, igc has PTM trigger disabled most of the time,\nand the trigger is only enabled for very brief (10 - 100 us) periods\nwhen manually triggering a PTM cycle.  Chances that a crash occurs\nduring a PTM trigger are not 0, but extremely reduced.\n\ud83d\udccf Published: 2025-05-09T06:44:03.368Z\n\ud83d\udccf Modified: 2025-05-09T06:44:03.368Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/c1f174edaccc5a00f8e218c42a0aa9156efd5f76\n2. https://git.kernel.org/stable/c/0c03e4fbe1321697d9d04587e21e416705e1b19f\n3. https://git.kernel.org/stable/c/16194ca3f3b4448a062650c869a7b3b206c6f5d3\n4. https://git.kernel.org/stable/c/f3516229cd12dcd45f23ed01adab17e8772b1bd5\n5. https://git.kernel.org/stable/c/31959e06143692f7e02b8eef7d7d6ac645637906\n6. https://git.kernel.org/stable/c/8e404ad95d2c10c261e2ef6992c7c12dde03df0e", "creation_timestamp": "2025-05-09T07:25:43.000000Z"}, {"uuid": "57c553c8-97a9-4c48-befc-83b1d37ebe8e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37870", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/15701", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-37870\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/amd/display: prevent hang on link training fail\n\n[Why]\nWhen link training fails, the phy clock will be disabled. However, in\nenable_streams, it is assumed that link training succeeded and the\nmux selects the phy clock, causing a hang when a register write is made.\n\n[How]\nWhen enable_stream is hit, check if link training failed. If it did, fall\nback to the ref clock to avoid a hang and keep the system in a recoverable\nstate.\n\ud83d\udccf Published: 2025-05-09T06:43:59.074Z\n\ud83d\udccf Modified: 2025-05-09T06:43:59.074Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/0363c03672cd3191f037905bf981eb523a3b71b1\n2. https://git.kernel.org/stable/c/04bf4f2a497e9877c425c5124652e61fb8a1a0aa\n3. https://git.kernel.org/stable/c/8058061ed9d6bc259d1e678607b07d259342c08f", "creation_timestamp": "2025-05-09T07:25:50.000000Z"}, {"uuid": "08aae369-dda4-4033-b7d9-389090e04278", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37871", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/15700", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-37871\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nnfsd: decrease sc_count directly if fail to queue dl_recall\n\nA deadlock warning occurred when invoking nfs4_put_stid following a failed\ndl_recall queue operation:\n            T1                            T2\n                                nfs4_laundromat\n                                 nfs4_get_client_reaplist\n                                  nfs4_anylock_blockers\n__break_lease\n spin_lock // ctx->flc_lock\n                                   spin_lock // clp->cl_lock\n                                   nfs4_lockowner_has_blockers\n                                    locks_owner_has_blockers\n                                     spin_lock // flctx->flc_lock\n nfsd_break_deleg_cb\n  nfsd_break_one_deleg\n   nfs4_put_stid\n    refcount_dec_and_lock\n     spin_lock // clp->cl_lock\n\nWhen a file is opened, an nfs4_delegation is allocated with sc_count\ninitialized to 1, and the file_lease holds a reference to the delegation.\nThe file_lease is then associated with the file through kernel_setlease.\n\nThe disassociation is performed in nfsd4_delegreturn via the following\ncall chain:\nnfsd4_delegreturn --> destroy_delegation --> destroy_unhashed_deleg -->\nnfs4_unlock_deleg_lease --> kernel_setlease --> generic_delete_lease\nThe corresponding sc_count reference will be released after this\ndisassociation.\n\nSince nfsd_break_one_deleg executes while holding the flc_lock, the\ndisassociation process becomes blocked when attempting to acquire flc_lock\nin generic_delete_lease. This means:\n1) sc_count in nfsd_break_one_deleg will not be decremented to 0;\n2) The nfs4_put_stid called by nfsd_break_one_deleg will not attempt to\nacquire cl_lock;\n3) Consequently, no deadlock condition is created.\n\nGiven that sc_count in nfsd_break_one_deleg remains non-zero, we can\nsafely perform refcount_dec on sc_count directly. This approach\neffectively avoids triggering deadlock warnings.\n\ud83d\udccf Published: 2025-05-09T06:43:59.720Z\n\ud83d\udccf Modified: 2025-05-09T06:43:59.720Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/b9bbe8f9d5663311d06667ce36d6ed255ead1a26\n2. https://git.kernel.org/stable/c/a70832d3555987035fc430ccd703acd89393eadb\n3. https://git.kernel.org/stable/c/ba903539fff745d592d893c71b30e5e268a95413\n4. https://git.kernel.org/stable/c/7d192e27a431026c58d60edf66dc6cd98d0c01fc\n5. https://git.kernel.org/stable/c/a7fce086f6ca84db409b9d58493ea77c1978897c\n6. https://git.kernel.org/stable/c/14985d66b9b99c12995dd99d1c6c8dec4114c2a5\n7. https://git.kernel.org/stable/c/a1d14d931bf700c1025db8c46d6731aa5cf440f9", "creation_timestamp": "2025-05-09T07:25:47.000000Z"}, {"uuid": "4eb9f106-c2e3-4c3a-9e41-2171acbc1599", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37872", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/15699", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-37872\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nnet: txgbe: fix memory leak in txgbe_probe() error path\n\nWhen txgbe_sw_init() is called, memory is allocated for wx->rss_key\nin wx_init_rss_key(). However, in txgbe_probe() function, the subsequent\nerror paths after txgbe_sw_init() don't free the rss_key. Fix that by\nfreeing it in error path along with wx->mac_table.\n\nAlso change the label to which execution jumps when txgbe_sw_init()\nfails, because otherwise, it could lead to a double free for rss_key,\nwhen the mac_table allocation fails in wx_sw_init().\n\ud83d\udccf Published: 2025-05-09T06:44:00.570Z\n\ud83d\udccf Modified: 2025-05-09T06:44:00.570Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/635863d93deb8e352d63a8eba852efeaf1ac3539\n2. https://git.kernel.org/stable/c/837197a722919f5b0eeb967fe7cb0cc1e83173b9\n3. https://git.kernel.org/stable/c/b2727326d0a53709380aa147018085d71a6d4843", "creation_timestamp": "2025-05-09T07:25:45.000000Z"}, {"uuid": "3264810f-d899-434c-80ef-20862f80eb15", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3794", "type": "seen", "source": "https://t.me/DarkWebInformer_CVEAlerts/15857", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-3794\n\ud83d\udd25 CVSS Score: 5.4 (cvssV3_1, Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N)\n\ud83d\udd39 Description: The WPForms \u2013 Easy Form Builder for WordPress \u2013 Contact Forms, Payment Forms, Surveys, & More plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the start_timestamp parameter in all versions up to, and including, 1.9.5 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with Contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.\n\ud83d\udccf Published: 2025-05-09T22:22:12.702Z\n\ud83d\udccf Modified: 2025-05-09T22:22:12.702Z\n\ud83d\udd17 References:\n1. https://www.wordfence.com/threat-intel/vulnerabilities/id/179eb680-e8d8-4918-96e3-e67217771c29?source=cve\n2. https://plugins.trac.wordpress.org/browser/wpforms-lite/tags/1.9.4.2/assets/js/frontend/wpforms.js#L3154", "creation_timestamp": "2025-05-09T23:25:48.000000Z"}, {"uuid": "13fd473e-dde4-41d3-b593-1d5efee84ff7", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3744", "type": "seen", "source": "https://t.me/DarkWebInformer_CVEAlerts/16200", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-3744\n\ud83d\udd25 CVSS Score: 7.6 (cvssV3_1, Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:L)\n\ud83d\udd39 Description: Nomad Enterprise (\u201cNomad\u201d) jobs using the policy override option are bypassing the mandatory sentinel policies. This vulnerability, identified as CVE-2025-3744, is fixed in Nomad Enterprise 1.10.1, 1.9.9, and 1.8.13.\n\ud83d\udccf Published: 2025-05-13T18:40:08.281Z\n\ud83d\udccf Modified: 2025-05-13T19:21:33.581Z\n\ud83d\udd17 References:\n1. https://discuss.hashicorp.com/t/hcsec-2025-08-nomad-enterprise-vulnerable-to-violation-of-mandatory-sentinel-policies-in-job-submissions-via-policy-override/74935", "creation_timestamp": "2025-05-13T19:30:54.000000Z"}, {"uuid": "8866bc36-9c52-41db-b45a-9fe7d6121214", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3769", "type": "seen", "source": "https://t.me/DarkWebInformer_CVEAlerts/16296", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-3769\n\ud83d\udd25 CVSS Score: 5.3 (cvssV3_1, Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N)\n\ud83d\udd39 Description: The LatePoint \u2013 Calendar Booking Plugin for Appointments and Events plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 5.1.92 via the 'view_booking_summary_in_lightbox' due to missing validation on a user controlled key. This makes it possible for unauthenticated attackers to retrieve appointment details such as customer names and email addresses.\n\ud83d\udccf Published: 2025-05-14T11:12:25.594Z\n\ud83d\udccf Modified: 2025-05-14T11:12:25.594Z\n\ud83d\udd17 References:\n1. https://www.wordfence.com/threat-intel/vulnerabilities/id/7e9acd26-c341-4ece-bcf1-102f953a4b4f?source=cve\n2. https://plugins.trac.wordpress.org/browser/latepoint/trunk/lib/controllers/customer_cabinet_controller.php\n3. https://plugins.trac.wordpress.org/changeset/3291162/", "creation_timestamp": "2025-05-14T11:31:17.000000Z"}, {"uuid": "28bd198a-c000-4dd5-bc1a-f5d11849f0d8", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37098", "type": "seen", "source": "https://t.me/DarkWebInformer_CVEAlerts/20040", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-37098\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: A path traversal vulnerability exists in HPE Insight Remote Support (IRS) prior to v7.15.0.646.\n\ud83d\udccf Published: 2025-07-01T14:39:11.831Z\n\ud83d\udccf Modified: 2025-07-01T14:55:36.836Z\n\ud83d\udd17 References:\n1. https://support.hpe.com/hpesc/public/docDisplay?docId=hpesbgn04878en_us&docLocale=en_US", "creation_timestamp": "2025-07-01T15:07:54.000000Z"}, {"uuid": "d1dad388-b8fe-4329-9004-a2241d0bfc06", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3742", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/16455", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-3742\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: The Responsive Lightbox & Gallery WordPress plugin before 2.5.1 does not validate and escape some of its attributes before outputting them back in a page/post, which could allow users with the contributor role and above to perform Stored Cross-Site Scripting attacks.\n\ud83d\udccf Published: 2025-05-15T06:00:02.551Z\n\ud83d\udccf Modified: 2025-05-15T06:00:02.551Z\n\ud83d\udd17 References:\n1. https://wpscan.com/vulnerability/5b8f487b-63a5-4d2a-9b61-ed4d97f18320/", "creation_timestamp": "2025-05-15T06:33:25.000000Z"}, {"uuid": "c1a098e6-15be-4d1e-b07b-4a755da659e5", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37890", "type": "seen", "source": "https://t.me/DarkWebInformer_CVEAlerts/16685", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-37890\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nnet_sched: hfsc: Fix a UAF vulnerability in class with netem as child qdisc\n\nAs described in Gerrard's report [1], we have a UAF case when an hfsc class\nhas a netem child qdisc. The crux of the issue is that hfsc is assuming\nthat checking for cl->qdisc->q.qlen == 0 guarantees that it hasn't inserted\nthe class in the vttree or eltree (which is not true for the netem\nduplicate case).\n\nThis patch checks the n_active class variable to make sure that the code\nwon't insert the class in the vttree or eltree twice, catering for the\nreentrant case.\n\n[1] https://lore.kernel.org/netdev/CAHcdcOm+03OD2j6R0=YHKqmy=VgJ8xEOKuP6c7mSgnp-TEJJbw@mail.gmail.com/\n\ud83d\udccf Published: 2025-05-16T13:01:12.798Z\n\ud83d\udccf Modified: 2025-05-16T13:01:12.798Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/e3e949a39a91d1f829a4890e7dfe9417ac72e4d0\n2. https://git.kernel.org/stable/c/8df7d37d626430035b413b97cee18396b3450bef\n3. https://git.kernel.org/stable/c/6082a87af4c52f58150d40dec1716011d871ac21\n4. https://git.kernel.org/stable/c/2e7093c7a8aba5d4f8809f271488e5babe75e202\n5. https://git.kernel.org/stable/c/ac39fd4a757584d78ed062d4f6fd913f83bd98b5\n6. https://git.kernel.org/stable/c/141d34391abbb315d68556b7c67ad97885407547", "creation_timestamp": "2025-05-16T13:35:49.000000Z"}, {"uuid": "16554a86-ed2a-42ff-8869-a6a7b81c97e8", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37891", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/16813", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-37891\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nALSA: ump: Fix buffer overflow at UMP SysEx message conversion\n\nThe conversion function from MIDI 1.0 to UMP packet contains an\ninternal buffer to keep the incoming MIDI bytes, and its size is 4, as\nit was supposed to be the max size for a MIDI1 UMP packet data.\nHowever, the implementation overlooked that SysEx is handled in a\ndifferent format, and it can be up to 6 bytes, as found in\ndo_convert_to_ump().  It leads eventually to a buffer overflow, and\nmay corrupt the memory when a longer SysEx message is received.\n\nThe fix is simply to extend the buffer size to 6 to fit with the SysEx\nUMP message.\n\ud83d\udccf Published: 2025-05-19T07:19:04.583Z\n\ud83d\udccf Modified: 2025-05-19T07:19:04.583Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/ce4f77bef276e7d2eb7ab03a5d08bcbaa40710ec\n2. https://git.kernel.org/stable/c/226beac5605afbb33f8782148d188b64396145a4\n3. https://git.kernel.org/stable/c/42ef48dd4ebb082a1a90b5c3feeda2e68a9e32fe\n4. https://git.kernel.org/stable/c/56f1f30e6795b890463d9b20b11e576adf5a2f77", "creation_timestamp": "2025-05-19T07:38:15.000000Z"}, {"uuid": "9e99a36d-ae69-473b-9b70-3a595fa851ba", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37978", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/17037", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-37978\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nblock: integrity: Do not call set_page_dirty_lock()\n\nPlacing multiple protection information buffers inside the same page\ncan lead to oopses because set_page_dirty_lock() can't be called from\ninterrupt context.\n\nSince a protection information buffer is not backed by a file there is\nno point in setting its page dirty, there is nothing to synchronize.\nDrop the call to set_page_dirty_lock() and remove the last argument to\nbio_integrity_unpin_bvec().\n\ud83d\udccf Published: 2025-05-20T16:58:21.422Z\n\ud83d\udccf Modified: 2025-05-20T16:58:21.422Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/c38a005e6efb9ddfa06bd8353b82379d6fd5d6c4\n2. https://git.kernel.org/stable/c/9487fc1a10b3aa89feb24e7cedeccaaf63074617\n3. https://git.kernel.org/stable/c/39e160505198ff8c158f11bce2ba19809a756e8b", "creation_timestamp": "2025-05-20T17:46:53.000000Z"}, {"uuid": "b46a8287-6058-4e0d-aaca-d0a3757c6960", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37980", "type": "seen", "source": "https://t.me/DarkWebInformer_CVEAlerts/17036", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-37980\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nblock: fix resource leak in blk_register_queue() error path\n\nWhen registering a queue fails after blk_mq_sysfs_register() is\nsuccessful but the function later encounters an error, we need\nto clean up the blk_mq_sysfs resources.\n\nAdd the missing blk_mq_sysfs_unregister() call in the error path\nto properly clean up these resources and prevent a memory leak.\n\ud83d\udccf Published: 2025-05-20T16:58:22.720Z\n\ud83d\udccf Modified: 2025-05-20T16:58:22.720Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/549cbbd14bbec12469ceb279b79c763c8a24224e\n2. https://git.kernel.org/stable/c/41e43134ddda35949974be40520460a12dda3502\n3. https://git.kernel.org/stable/c/55a7bb2708f7c7c5b366d4e40916113168a3824c\n4. https://git.kernel.org/stable/c/40f2eb9b531475dd01b683fdaf61ca3cfd03a51e", "creation_timestamp": "2025-05-20T17:45:52.000000Z"}, {"uuid": "34063cd9-6867-4b22-9558-3c2f931b7f47", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37982", "type": "seen", "source": "https://t.me/DarkWebInformer_CVEAlerts/17034", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-37982\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nwifi: wl1251: fix memory leak in wl1251_tx_work\n\nThe skb dequeued from tx_queue is lost when wl1251_ps_elp_wakeup fails\nwith a -ETIMEDOUT error. Fix that by queueing the skb back to tx_queue.\n\ud83d\udccf Published: 2025-05-20T16:58:23.861Z\n\ud83d\udccf Modified: 2025-05-20T16:58:23.861Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/13c9744c1bcdb5de4e7dc1a78784788ecec52add\n2. https://git.kernel.org/stable/c/f08448a885403722c5c77dae51964badfcb69495\n3. https://git.kernel.org/stable/c/2996144be660d930d5e394652abe08fe89dbe00e\n4. https://git.kernel.org/stable/c/8fd4b9551af214d037fbc9d8e179840b8b917841\n5. https://git.kernel.org/stable/c/4a43fd36710669d67dbb5c16287a58412582ca26\n6. https://git.kernel.org/stable/c/52f224009ce1e44805e6ff3ffc2a06af9c1c3c5b\n7. https://git.kernel.org/stable/c/5a90c29d0204c5ffc45b43b4eced6eef0e19a33a\n8. https://git.kernel.org/stable/c/a0f0dc96de03ffeefc2a177b7f8acde565cb77f4", "creation_timestamp": "2025-05-20T17:45:45.000000Z"}, {"uuid": "d889df41-5c1d-4acd-a561-a4ec265512ce", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37983", "type": "seen", "source": "https://t.me/DarkWebInformer_CVEAlerts/17032", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-37983\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nqibfs: fix _another_ leak\n\nfailure to allocate inode => leaked dentry...\n\nthis one had been there since the initial merge; to be fair,\nif we are that far OOM, the odds of failing at that particular\nallocation are low...\n\ud83d\udccf Published: 2025-05-20T17:09:17.666Z\n\ud83d\udccf Modified: 2025-05-20T17:09:17.666Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/5e280cce3a29b7fe7b828c6ccd5aa5ba87ceb6b6\n2. https://git.kernel.org/stable/c/3c2fde33e3e505dfd1a895d1f24bad650c655e14\n3. https://git.kernel.org/stable/c/5fe708c5e3c8b2152c6caaa67243e431a5d6cca3\n4. https://git.kernel.org/stable/c/545defa656568c74590317cd30068f85134a8216\n5. https://git.kernel.org/stable/c/5d53e88d8370b9ab14dd830abb410d9a2671edb6\n6. https://git.kernel.org/stable/c/47ab2caba495c1d6a899d284e541a8df656dcfe9\n7. https://git.kernel.org/stable/c/24faa6ea274a2b96d0a78a0996c3137c2b2a65f0\n8. https://git.kernel.org/stable/c/bdb43af4fdb39f844ede401bdb1258f67a580a27", "creation_timestamp": "2025-05-20T17:45:43.000000Z"}, {"uuid": "170b38c2-6c8d-4830-ab95-7bd7c2f1062e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37987", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/17029", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-37987\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\npds_core: Prevent possible adminq overflow/stuck condition\n\nThe pds_core's adminq is protected by the adminq_lock, which prevents\nmore than 1 command to be posted onto it at any one time. This makes it\nso the client drivers cannot simultaneously post adminq commands.\nHowever, the completions happen in a different context, which means\nmultiple adminq commands can be posted sequentially and all waiting\non completion.\n\nOn the FW side, the backing adminq request queue is only 16 entries\nlong and the retry mechanism and/or overflow/stuck prevention is\nlacking. This can cause the adminq to get stuck, so commands are no\nlonger processed and completions are no longer sent by the FW.\n\nAs an initial fix, prevent more than 16 outstanding adminq commands so\nthere's no way to cause the adminq from getting stuck. This works\nbecause the backing adminq request queue will never have more than 16\npending adminq commands, so it will never overflow. This is done by\nreducing the adminq depth to 16.\n\ud83d\udccf Published: 2025-05-20T17:09:20.166Z\n\ud83d\udccf Modified: 2025-05-20T17:09:20.166Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/2982e07ad72b48eb12c29a87a3f2126ea552688c\n2. https://git.kernel.org/stable/c/5e3dc65675faad846420d24762e4faadc12d9392\n3. https://git.kernel.org/stable/c/d9e2f070d8af60f2c8c02b2ddf0a9e90b4e9220c", "creation_timestamp": "2025-05-20T17:45:15.000000Z"}, {"uuid": "3ae69017-8280-40d1-8c49-00e19a91a8d9", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37988", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/17028", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-37988\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nfix a couple of races in MNT_TREE_BENEATH handling by do_move_mount()\n\nNormally do_lock_mount(path, _) is locking a mountpoint pinned by\n*path and at the time when matching unlock_mount() unlocks that\nlocation it is still pinned by the same thing.\n\nUnfortunately, for 'beneath' case it's no longer that simple -\nthe object being locked is not the one *path points to.  It's the\nmountpoint of path->mnt.  The thing is, without sufficient locking\n->mnt_parent may change under us and none of the locks are held\nat that point.  The rules are\n * mount_lock stabilizes m->mnt_parent for any mount m.\n * namespace_sem stabilizes m->mnt_parent, provided that\nm is mounted.\n * if either of the above holds and refcount of m is positive,\nwe are guaranteed the same for refcount of m->mnt_parent.\n\nnamespace_sem nests inside inode_lock(), so do_lock_mount() has\nto take inode_lock() before grabbing namespace_sem.  It does\nrecheck that path->mnt is still mounted in the same place after\ngetting namespace_sem, and it does take care to pin the dentry.\nIt is needed, since otherwise we might end up with racing mount --move\n(or umount) happening while we were getting locks; in that case\ndentry would no longer be a mountpoint and could've been evicted\non memory pressure along with its inode - not something you want\nwhen grabbing lock on that inode.\n\nHowever, pinning a dentry is not enough - the matching mount is\nalso pinned only by the fact that path->mnt is mounted on top it\nand at that point we are not holding any locks whatsoever, so\nthe same kind of races could end up with all references to\nthat mount gone just as we are about to enter inode_lock().\nIf that happens, we are left with filesystem being shut down while\nwe are holding a dentry reference on it; results are not pretty.\n\nWhat we need to do is grab both dentry and mount at the same time;\nthat makes inode_lock() safe *and* avoids the problem with fs getting\nshut down under us.  After taking namespace_sem we verify that\npath->mnt is still mounted (which stabilizes its ->mnt_parent) and\ncheck that it's still mounted at the same place.  From that point\non to the matching namespace_unlock() we are guaranteed that\nmount/dentry pair we'd grabbed are also pinned by being the mountpoint\nof path->mnt, so we can quietly drop both the dentry reference (as\nthe current code does) and mnt one - it's OK to do under namespace_sem,\nsince we are not dropping the final refs.\n\nThat solves the problem on do_lock_mount() side; unlock_mount()\nalso has one, since dentry is guaranteed to stay pinned only until\nthe namespace_unlock().  That's easy to fix - just have inode_unlock()\ndone earlier, while it's still pinned by mp->m_dentry.\n\ud83d\udccf Published: 2025-05-20T17:09:20.765Z\n\ud83d\udccf Modified: 2025-05-20T17:09:20.765Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/4f435c1f4c48ff84968e2d9159f6fa41f46cf998\n2. https://git.kernel.org/stable/c/a61afd54826ac24c2c93845c4f441dbc344875b1\n3. https://git.kernel.org/stable/c/d4b21e8cd3d7efa2deb9cff534f0133e84f35086\n4. https://git.kernel.org/stable/c/0d039eac6e5950f9d1ecc9e410c2fd1feaeab3b6", "creation_timestamp": "2025-05-20T17:44:48.000000Z"}, {"uuid": "5aa478f2-13bf-4d2c-a6d7-3804d42c1045", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37989", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/17027", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-37989\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nnet: phy: leds: fix memory leak\n\nA network restart test on a router led to an out-of-memory condition,\nwhich was traced to a memory leak in the PHY LED trigger code.\n\nThe root cause is misuse of the devm API. The registration function\n(phy_led_triggers_register) is called from phy_attach_direct, not\nphy_probe, and the unregister function (phy_led_triggers_unregister)\nis called from phy_detach, not phy_remove. This means the register and\nunregister functions can be called multiple times for the same PHY\ndevice, but devm-allocated memory is not freed until the driver is\nunbound.\n\nThis also prevents kmemleak from detecting the leak, as the devm API\ninternally stores the allocated pointer.\n\nFix this by replacing devm_kzalloc/devm_kcalloc with standard\nkzalloc/kcalloc, and add the corresponding kfree calls in the unregister\npath.\n\ud83d\udccf Published: 2025-05-20T17:09:21.419Z\n\ud83d\udccf Modified: 2025-05-20T17:09:21.419Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/966d6494e2ed9be9052fcd9815afba830896aaf8\n2. https://git.kernel.org/stable/c/95bed65cc0eb2a610550abf849a8b94374da80a7\n3. https://git.kernel.org/stable/c/663c3da86e807c6c07ed48f911c7526fad6fe1ff\n4. https://git.kernel.org/stable/c/f41f097f68a33d392579885426d0734a81219501\n5. https://git.kernel.org/stable/c/618541a6cc1511064dfa58c89b3445e21844092f\n6. https://git.kernel.org/stable/c/41143e71052a00d654c15dc924fda50c1e7357d0\n7. https://git.kernel.org/stable/c/7f3d5880800f962c347777c4f8358f29f5fc403c\n8. https://git.kernel.org/stable/c/b7f0ee992adf601aa00c252418266177eb7ac2bc", "creation_timestamp": "2025-05-20T17:44:42.000000Z"}, {"uuid": "0230fc4b-cb84-4d60-af37-3cc410444366", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3715", "type": "seen", "source": "https://t.me/DarkWebInformer_CVEAlerts/16857", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-3715\n\ud83d\udd25 CVSS Score: 6.4 (cvssV3_1, Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N)\n\ud83d\udd39 Description: The Bold Page Builder plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the data-text parameter in all versions up to, and including, 5.3.5 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with Contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.\n\ud83d\udccf Published: 2025-05-18T05:22:39.619Z\n\ud83d\udccf Modified: 2025-05-19T14:24:56.083Z\n\ud83d\udd17 References:\n1. https://www.wordfence.com/threat-intel/vulnerabilities/id/a2452dd7-2bb9-4a0c-81db-6699a9b049ae?source=cve\n2. https://plugins.trac.wordpress.org/browser/bold-page-builder/tags/5.3.5/content_elements_misc/js/content_elements.js\n3. https://plugins.trac.wordpress.org/changeset/3292512/", "creation_timestamp": "2025-05-19T14:38:46.000000Z"}, {"uuid": "3b120a0e-2c73-4ad6-b95f-fab3d19a91cf", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37984", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/17031", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-37984\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\ncrypto: ecdsa - Harden against integer overflows in DIV_ROUND_UP()\n\nHerbert notes that DIV_ROUND_UP() may overflow unnecessarily if an ecdsa\nimplementation's ->key_size() callback returns an unusually large value.\nHerbert instead suggests (for a division by 8):\n\n  X / 8 + !!(X & 7)\n\nBased on this formula, introduce a generic DIV_ROUND_UP_POW2() macro and\nuse it in lieu of DIV_ROUND_UP() for ->key_size() return values.\n\nAdditionally, use the macro in ecc_digits_from_bytes(), whose \"nbytes\"\nparameter is a ->key_size() return value in some instances, or a\nuser-specified ASN.1 length in the case of ecdsa_get_signature_rs().\n\ud83d\udccf Published: 2025-05-20T17:09:18.321Z\n\ud83d\udccf Modified: 2025-05-20T17:09:18.321Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/921b8167f10708e38080f84e195cdc68a7a561f1\n2. https://git.kernel.org/stable/c/b16510a530d1e6ab9683f04f8fb34f2e0f538275", "creation_timestamp": "2025-05-20T17:45:42.000000Z"}, {"uuid": "f6752a6f-892b-4def-ae7d-ae39b7498c45", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37985", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/17030", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-37985\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nUSB: wdm: close race between wdm_open and wdm_wwan_port_stop\n\nClearing WDM_WWAN_IN_USE must be the last action or\nwe can open a chardev whose URBs are still poisoned\n\ud83d\udccf Published: 2025-05-20T17:09:18.963Z\n\ud83d\udccf Modified: 2025-05-20T17:09:18.963Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/b02a3fef3e8c8fe5a0a266f7a14f38cc608fb167\n2. https://git.kernel.org/stable/c/217fe1fc7d112595a793e02b306710e702eac492\n3. https://git.kernel.org/stable/c/54f7f8978af19f899dec80bcc71c8d4855dfbd72\n4. https://git.kernel.org/stable/c/52ae15c665b5fe5876655aaccc3ef70560b0e314\n5. https://git.kernel.org/stable/c/e3c9adc69357fcbe6253a2bc2588ee4bbaaedbe9\n6. https://git.kernel.org/stable/c/c1846ed4eb527bdfe6b3b7dd2c78e2af4bf98f4f", "creation_timestamp": "2025-05-20T17:45:41.000000Z"}, {"uuid": "8ffba2ed-fb0c-4a2f-933f-6e83815964e4", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37964", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/17019", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-37964\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nx86/mm: Eliminate window where TLB flushes may be inadvertently skipped\n\ntl;dr: There is a window in the mm switching code where the new CR3 is\nset and the CPU should be getting TLB flushes for the new mm.  But\nshould_flush_tlb() has a bug and suppresses the flush.  Fix it by\nwidening the window where should_flush_tlb() sends an IPI.\n\nLong Version:\n\n=== History ===\n\nThere were a few things leading up to this.\n\nFirst, updating mm_cpumask() was observed to be too expensive, so it was\nmade lazier.  But being lazy caused too many unnecessary IPIs to CPUs\ndue to the now-lazy mm_cpumask().  So code was added to cull\nmm_cpumask() periodically[2].  But that culling was a bit too aggressive\nand skipped sending TLB flushes to CPUs that need them.  So here we are\nagain.\n\n=== Problem ===\n\nThe too-aggressive code in should_flush_tlb() strikes in this window:\n\n // Turn on IPIs for this CPU/mm combination, but only\n // if should_flush_tlb() agrees:\n cpumask_set_cpu(cpu, mm_cpumask(next));\n\n next_tlb_gen = atomic64_read(&next->context.tlb_gen);\n choose_new_asid(next, next_tlb_gen, &new_asid, &need_flush);\n load_new_mm_cr3(need_flush);\n // ^ After 'need_flush' is set to false, IPIs *MUST*\n // be sent to this CPU and not be ignored.\n\n        this_cpu_write(cpu_tlbstate.loaded_mm, next);\n // ^ Not until this point does should_flush_tlb()\n // become true!\n\nshould_flush_tlb() will suppress TLB flushes between load_new_mm_cr3()\nand writing to 'loaded_mm', which is a window where they should not be\nsuppressed.  Whoops.\n\n=== Solution ===\n\nThankfully, the fuzzy \"just about to write CR3\" window is already marked\nwith loaded_mm==LOADED_MM_SWITCHING.  Simply checking for that state in\nshould_flush_tlb() is sufficient to ensure that the CPU is targeted with\nan IPI.\n\nThis will cause more TLB flush IPIs.  But the window is relatively small\nand I do not expect this to cause any kind of measurable performance\nimpact.\n\nUpdate the comment where LOADED_MM_SWITCHING is written since it grew\nyet another user.\n\nPeter Z also raised a concern that should_flush_tlb() might not observe\n'loaded_mm' and 'is_lazy' in the same order that switch_mm_irqs_off()\nwrites them.  Add a barrier to ensure that they are observed in the\norder they are written.\n\ud83d\udccf Published: 2025-05-20T16:01:56.013Z\n\ud83d\udccf Modified: 2025-05-20T16:01:56.013Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/12f703811af043d32b1c8a30001b2fa04d5cd0ac\n2. https://git.kernel.org/stable/c/02ad4ce144bd27f71f583f667fdf3b3ba0753477\n3. https://git.kernel.org/stable/c/d41072906abec8bb8e01ed16afefbaa558908c89\n4. https://git.kernel.org/stable/c/d87392094f96e162fa5fa5a8640d70cc0952806f\n5. https://git.kernel.org/stable/c/399ec9ca8fc4999e676ff89a90184ec40031cf59\n6. https://git.kernel.org/stable/c/fea4e317f9e7e1f449ce90dedc27a2d2a95bee5a", "creation_timestamp": "2025-05-20T16:41:12.000000Z"}, {"uuid": "bd49b49c-b65d-4256-aed7-6bd10a452617", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37892", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/16967", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-37892\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nmtd: inftlcore: Add error check for inftl_read_oob()\n\nIn INFTL_findwriteunit(), the return value of inftl_read_oob()\nneed to be checked. A proper implementation can be\nfound in INFTL_deleteblock(). The status will be set as\nSECTOR_IGNORE to break from the while-loop correctly\nif the inftl_read_oob() fails.\n\ud83d\udccf Published: 2025-05-20T11:00:26.977Z\n\ud83d\udccf Modified: 2025-05-20T11:00:26.977Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/b828d394308e8e00df0a6f57e7dabae609bb8b7b\n2. https://git.kernel.org/stable/c/0300e751170cf80c05ca1a762a7b449e8ca6b693\n3. https://git.kernel.org/stable/c/e7d6ceff95c55297f0ee8f9dbc4da5c558f30e9e\n4. https://git.kernel.org/stable/c/6af3b92b1c0b58ca281d0e1501bad2567f73c1a5\n5. https://git.kernel.org/stable/c/7772621041ee78823ccc5f1fe38f6faa22af7023\n6. https://git.kernel.org/stable/c/5479a6af3c96f73bec2d2819532b6d6814f52dd6\n7. https://git.kernel.org/stable/c/1c22356dfb041e5292835c9ff44d5f91bef8dd18\n8. https://git.kernel.org/stable/c/114d94f095aa405fa9a51484c4be34846d7bb386\n9. https://git.kernel.org/stable/c/d027951dc85cb2e15924c980dc22a6754d100c7c", "creation_timestamp": "2025-05-20T11:40:20.000000Z"}, {"uuid": "7d838c34-f42a-4cc7-9ef3-65180f0449d9", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37943", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/17102", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-37943\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nwifi: ath12k: Fix invalid data access in ath12k_dp_rx_h_undecap_nwifi\n\nIn certain cases, hardware might provide packets with a\nlength greater than the maximum native Wi-Fi header length.\nThis can lead to accessing and modifying fields in the header\nwithin the ath12k_dp_rx_h_undecap_nwifi function for\nDP_RX_DECAP_TYPE_NATIVE_WIFI decap type and\npotentially resulting in invalid data access and memory corruption.\n\nAdd a sanity check before processing the SKB to prevent invalid\ndata access in the undecap native Wi-Fi function for the\nDP_RX_DECAP_TYPE_NATIVE_WIFI decap type.\n\nTested-on: QCN9274 hw2.0 PCI WLAN.WBE.1.3.1-00173-QCAHKSWPL_SILICONZ-1\n\ud83d\udccf Published: 2025-05-20T15:58:19.607Z\n\ud83d\udccf Modified: 2025-05-21T07:58:19.832Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/7f1d986da5c6abb75ffe4d0d325fc9b341c41a1c\n2. https://git.kernel.org/stable/c/3abe15e756481c45f6acba3d476cb3ca4afc3b61\n3. https://git.kernel.org/stable/c/6ee653194ddb83674913fd2727b8ecfae0597ade\n4. https://git.kernel.org/stable/c/50be1fb76556e80af9f5da80f28168b6c71bce58\n5. https://git.kernel.org/stable/c/9a0dddfb30f120db3851627935851d262e4e7acb", "creation_timestamp": "2025-05-21T08:46:05.000000Z"}, {"uuid": "07ff2c76-4dba-4679-9bc9-48d8e3ffa63a", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37934", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/16999", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-37934\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nASoC: simple-card-utils: Fix pointer check in graph_util_parse_link_direction\n\nActually check if the passed pointers are valid, before writing to them.\nThis also fixes a USBAN warning:\nUBSAN: invalid-load in ../sound/soc/fsl/imx-card.c:687:25\nload of value 255 is not a valid value for type '_Bool'\n\nThis is because playback_only is uninitialized and is not written to, as\nthe playback-only property is absent.\n\ud83d\udccf Published: 2025-05-20T15:21:58.770Z\n\ud83d\udccf Modified: 2025-05-20T15:21:58.770Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/b41a49d5435e0f76da320f231b7252800e8f736f\n2. https://git.kernel.org/stable/c/9b5b3088c4d1752253491705919bd7d067964288\n3. https://git.kernel.org/stable/c/3cc393d2232ec770b5f79bf0673d67702a3536c3", "creation_timestamp": "2025-05-20T15:40:38.000000Z"}, {"uuid": "2a2c50de-403b-4c89-85ed-405900db1765", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37935", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/16998", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-37935\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nnet: ethernet: mtk_eth_soc: fix SER panic with 4GB+ RAM\n\nIf the mtk_poll_rx() function detects the MTK_RESETTING flag, it will\njump to release_desc and refill the high word of the SDP on the 4GB RFB.\nSubsequently, mtk_rx_clean will process an incorrect SDP, leading to a\npanic.\n\nAdd patch from MediaTek's SDK to resolve this.\n\ud83d\udccf Published: 2025-05-20T15:21:59.381Z\n\ud83d\udccf Modified: 2025-05-20T15:21:59.381Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/cb625f783f70dc6614f03612b8e64ad99cb0a13c\n2. https://git.kernel.org/stable/c/317013d1ad13524be02d60b9e98f08fbd13f8c14\n3. https://git.kernel.org/stable/c/67619cf69dec5d1d7792808dfa548616742dd51d\n4. https://git.kernel.org/stable/c/6e0490fc36cdac696f96e57b61d93b9ae32e0f4c", "creation_timestamp": "2025-05-20T15:40:37.000000Z"}, {"uuid": "0594aac1-4554-4a2a-ada2-cd6f565596c5", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37936", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/16997", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-37936\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nperf/x86/intel: KVM: Mask PEBS_ENABLE loaded for guest with vCPU's value.\n\nWhen generating the MSR_IA32_PEBS_ENABLE value that will be loaded on\nVM-Entry to a KVM guest, mask the value with the vCPU's desired PEBS_ENABLE\nvalue.  Consulting only the host kernel's host vs. guest masks results in\nrunning the guest with PEBS enabled even when the guest doesn't want to use\nPEBS.  Because KVM uses perf events to proxy the guest virtual PMU, simply\nlooking at exclude_host can't differentiate between events created by host\nuserspace, and events created by KVM on behalf of the guest.\n\nRunning the guest with PEBS unexpectedly enabled typically manifests as\ncrashes due to a near-infinite stream of #PFs.  E.g. if the guest hasn't\nwritten MSR_IA32_DS_AREA, the CPU will hit page faults on address '0' when\ntrying to record PEBS events.\n\nThe issue is most easily reproduced by running `perf kvm top` from before\ncommit 7b100989b4f6 (\"perf evlist: Remove __evlist__add_default\") (after\nwhich, `perf kvm top` effectively stopped using PEBS). The userspace side\nof perf creates a guest-only PEBS event, which intel_guest_get_msrs()\nmisconstrues a guest-*owned* PEBS event.\n\nArguably, this is a userspace bug, as enabling PEBS on guest-only events\nsimply cannot work, and userspace can kill VMs in many other ways (there\nis no danger to the host).  However, even if this is considered to be bad\nuserspace behavior, there's zero downside to perf/KVM restricting PEBS to\nguest-owned events.\n\nNote, commit 854250329c02 (\"KVM: x86/pmu: Disable guest PEBS temporarily\nin two rare situations\") fixed the case where host userspace is profiling\nKVM *and* userspace, but missed the case where userspace is profiling only\nKVM.\n\ud83d\udccf Published: 2025-05-20T15:22:00.557Z\n\ud83d\udccf Modified: 2025-05-20T15:22:00.557Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/160153cf9e4aa875ad086cc094ce34aac8e13d63\n2. https://git.kernel.org/stable/c/34b6fa11431aef71045ae5a00d90a7d630597eda\n3. https://git.kernel.org/stable/c/44ee0afc9d1e7a7c1932698de01362ed80cfc4b5\n4. https://git.kernel.org/stable/c/86aa62895fc2fb7ab09d7ca40fae8ad09841f66b\n5. https://git.kernel.org/stable/c/58f6217e5d0132a9f14e401e62796916aa055c1b", "creation_timestamp": "2025-05-20T15:40:37.000000Z"}, {"uuid": "ef7d6776-a83c-466e-bc28-f8ec1a85908b", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37990", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/17026", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-37990\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nwifi: brcm80211: fmac: Add error handling for brcmf_usb_dl_writeimage()\n\nThe function brcmf_usb_dl_writeimage() calls the function\nbrcmf_usb_dl_cmd() but dose not check its return value. The\n'state.state' and the 'state.bytes' are uninitialized if the\nfunction brcmf_usb_dl_cmd() fails. It is dangerous to use\nuninitialized variables in the conditions.\n\nAdd error handling for brcmf_usb_dl_cmd() to jump to error\nhandling path if the brcmf_usb_dl_cmd() fails and the\n'state.state' and the 'state.bytes' are uninitialized.\n\nImprove the error message to report more detailed error\ninformation.\n\ud83d\udccf Published: 2025-05-20T17:18:45.366Z\n\ud83d\udccf Modified: 2025-05-20T17:18:45.366Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/508be7c001437bacad7b9a43f08a723887bcd1ea\n2. https://git.kernel.org/stable/c/524b70441baba453b193c418e3142bd31059cc1f\n3. https://git.kernel.org/stable/c/08424a0922fb9e32a19b09d852ee87fb6c497538\n4. https://git.kernel.org/stable/c/bdb435ef9815b1ae28eefffa01c6959d0fcf1fa7\n5. https://git.kernel.org/stable/c/fa9b9f02212574ee1867fbefb0a675362a71b31d\n6. https://git.kernel.org/stable/c/8e089e7b585d95122c8122d732d1d5ef8f879396", "creation_timestamp": "2025-05-20T17:44:31.000000Z"}, {"uuid": "de71871f-3e63-4a2a-9266-811901ec1763", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37977", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/17038", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-37977\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nscsi: ufs: exynos: Disable iocc if dma-coherent property isn't set\n\nIf dma-coherent property isn't set then descriptors are non-cacheable\nand the iocc shareability bits should be disabled. Without this UFS can\nend up in an incompatible configuration and suffer from random cache\nrelated stability issues.\n\ud83d\udccf Published: 2025-05-20T16:58:20.693Z\n\ud83d\udccf Modified: 2025-05-20T16:58:20.693Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/869749e48115ef944eeabec8e84138908471fa51\n2. https://git.kernel.org/stable/c/f0c6728a6f2e269ebb234a9b5bb6c2c24aafeb51\n3. https://git.kernel.org/stable/c/f92bb7436802f8eb7ee72dc911a33c8897fde366", "creation_timestamp": "2025-05-20T17:47:08.000000Z"}, {"uuid": "90dfcb75-25dc-4222-a6d4-00fae1b19e7e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37981", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/17035", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-37981\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nscsi: smartpqi: Use is_kdump_kernel() to check for kdump\n\nThe smartpqi driver checks the reset_devices variable to determine\nwhether special adjustments need to be made for kdump. This has the\neffect that after a regular kexec reboot, some driver parameters such as\nmax_transfer_size are much lower than usual. More importantly, kexec\nreboot tests have revealed memory corruption caused by the driver log\nbeing written to system memory after a kexec.\n\nFix this by testing is_kdump_kernel() rather than reset_devices where\nappropriate.\n\ud83d\udccf Published: 2025-05-20T16:58:23.299Z\n\ud83d\udccf Modified: 2025-05-20T16:58:23.299Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/7cc670e8ebaa5241dd99c0ad75eceb8f8f64f607\n2. https://git.kernel.org/stable/c/ebf673c76ce91e612a882dfaa9a3824962994aae\n3. https://git.kernel.org/stable/c/a2d5a0072235a69749ceb04c1a26dc75df66a31a", "creation_timestamp": "2025-05-20T17:45:46.000000Z"}, {"uuid": "700b2223-b405-4545-9cd4-9c85da3ac719", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37973", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/17042", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-37973\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nwifi: cfg80211: fix out-of-bounds access during multi-link element defragmentation\n\nCurrently during the multi-link element defragmentation process, the\nmulti-link element length added to the total IEs length when calculating\nthe length of remaining IEs after the multi-link element in\ncfg80211_defrag_mle(). This could lead to out-of-bounds access if the\nmulti-link element or its corresponding fragment elements are the last\nelements in the IEs buffer.\n\nTo address this issue, correctly calculate the remaining IEs length by\ndeducting the multi-link element end offset from total IEs end offset.\n\ud83d\udccf Published: 2025-05-20T16:47:19.074Z\n\ud83d\udccf Modified: 2025-05-20T16:47:19.074Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/73dde269a1a43e6b1aa92eba13ad2df58bfdd38e\n2. https://git.kernel.org/stable/c/9423f6da825172b8dc60d4688ed3d147291c3be9\n3. https://git.kernel.org/stable/c/e1c6d0c6199bd5f4cfc7a66ae7032b6e805f904d\n4. https://git.kernel.org/stable/c/023c1f2f0609218103cbcb48e0104b144d4a16dc", "creation_timestamp": "2025-05-20T17:47:13.000000Z"}, {"uuid": "3ad81d2b-b065-4143-88c0-1712828308d8", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37974", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/17041", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-37974\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\ns390/pci: Fix missing check for zpci_create_device() error return\n\nThe zpci_create_device() function returns an error pointer that needs to\nbe checked before dereferencing it as a struct zpci_dev pointer. Add the\nmissing check in __clp_add() where it was missed when adding the\nscan_list in the fixed commit. Simply not adding the device to the scan\nlist results in the previous behavior.\n\ud83d\udccf Published: 2025-05-20T16:47:19.676Z\n\ud83d\udccf Modified: 2025-05-20T16:47:19.676Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/be54b750c333a9db7c3b3686846bb06b07b011fe\n2. https://git.kernel.org/stable/c/2769b718e164df983c20c314b263a71a699be6cd\n3. https://git.kernel.org/stable/c/42420c50c68f3e95e90de2479464f420602229fc", "creation_timestamp": "2025-05-20T17:47:11.000000Z"}, {"uuid": "42f8d8ed-3d52-49fd-b162-560c4a4d6375", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37975", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/17040", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-37975\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nriscv: module: Fix out-of-bounds relocation access\n\nThe current code allows rel[j] to access one element past the end of the\nrelocation section. Simplify to num_relocations which is equivalent to\nthe existing size expression.\n\ud83d\udccf Published: 2025-05-20T16:58:19.270Z\n\ud83d\udccf Modified: 2025-05-20T16:58:19.270Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/a068ea00009d373d825c528f9c168501519211b4\n2. https://git.kernel.org/stable/c/95e4e1c1cf614d125f159db9726b7abb32e18385\n3. https://git.kernel.org/stable/c/0b4cce68efb93e31a8e51795d696df6e379cb41c", "creation_timestamp": "2025-05-20T17:47:10.000000Z"}, {"uuid": "f4326c26-4d39-42a0-8661-3ac8bf542d7a", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37899", "type": "seen", "source": "https://t.me/DarkWebInformer_CVEAlerts/17104", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-37899\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nksmbd: fix use-after-free in session logoff\n\nThe sess->user object can currently be in use by another thread, for\nexample if another connection has sent a session setup request to\nbind to the session being free'd. The handler for that connection could\nbe in the smb2_sess_setup function which makes use of sess->user.\n\ud83d\udccf Published: 2025-05-20T15:21:34.782Z\n\ud83d\udccf Modified: 2025-05-21T07:58:14.534Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/d5ec1d79509b3ee01de02c236f096bc050221b7f\n2. https://git.kernel.org/stable/c/02d16046cd11a5c037b28c12ffb818c56dd3ef43\n3. https://git.kernel.org/stable/c/2fc9feff45d92a92cd5f96487655d5be23fb7e2b", "creation_timestamp": "2025-05-21T08:47:52.000000Z"}, {"uuid": "e9fd482c-b39b-447d-843e-f92b57570f38", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37907", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/17103", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-37907\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\naccel/ivpu: Fix locking order in ivpu_job_submit\n\nFix deadlock in job submission and abort handling.\nWhen a thread aborts currently executing jobs due to a fault,\nit first locks the global lock protecting submitted_jobs (#1).\n\nAfter the last job is destroyed, it proceeds to release the related context\nand locks file_priv (#2). Meanwhile, in the job submission thread,\nthe file_priv lock (#2) is taken first, and then the submitted_jobs\nlock (#1) is obtained when a job is added to the submitted jobs list.\n\n       CPU0                            CPU1\n       ----                            ----\n  (for example due to a fault)         (jobs submissions keep coming)\n\n  lock(&vdev->submitted_jobs_lock) #1\n  ivpu_jobs_abort_all()\n  job_destroy()\n                                      lock(&file_priv->lock)           #2\n                                      lock(&vdev->submitted_jobs_lock) #1\n  file_priv_release()\n  lock(&vdev->context_list_lock)\n  lock(&file_priv->lock)           #2\n\nThis order of locking causes a deadlock. To resolve this issue,\nchange the order of locking in ivpu_job_submit().\n\ud83d\udccf Published: 2025-05-20T15:21:40.482Z\n\ud83d\udccf Modified: 2025-05-21T07:58:16.031Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/079d2622f8c9e0c380149645fff21d35c59ce6ff\n2. https://git.kernel.org/stable/c/b9b70924a272c2d72023306bc56f521c056212ee\n3. https://git.kernel.org/stable/c/ab680dc6c78aa035e944ecc8c48a1caab9f39924", "creation_timestamp": "2025-05-21T08:47:21.000000Z"}, {"uuid": "9894d174-bf72-457c-b898-41ae78f90392", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37992", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/17571", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-37992\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nnet_sched: Flush gso_skb list too during ->change()\n\nPreviously, when reducing a qdisc's limit via the ->change() operation, only\nthe main skb queue was trimmed, potentially leaving packets in the gso_skb\nlist. This could result in NULL pointer dereference when we only check\nsch->limit against sch->q.qlen.\n\nThis patch introduces a new helper, qdisc_dequeue_internal(), which ensures\nboth the gso_skb list and the main queue are properly flushed when trimming\nexcess packets. All relevant qdiscs (codel, fq, fq_codel, fq_pie, hhf, pie)\nare updated to use this helper in their ->change() routines.\n\ud83d\udccf Published: 2025-05-26T14:54:15.796Z\n\ud83d\udccf Modified: 2025-05-26T14:54:15.796Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/d3336f746f196c6a53e0480923ae93939f047b6c\n2. https://git.kernel.org/stable/c/d38939ebe0d992d581acb6885c1723fa83c1fb2c\n3. https://git.kernel.org/stable/c/a7d6e0ac0a8861f6b1027488062251a8e28150fd\n4. https://git.kernel.org/stable/c/d1365ca80b012d8a7863e45949e413fb61fa4861\n5. https://git.kernel.org/stable/c/fe88c7e4fc2c1cd75a278a15ffbf1689efad4e76\n6. https://git.kernel.org/stable/c/2d3cbfd6d54a2c39ce3244f33f85c595844bd7b8", "creation_timestamp": "2025-05-26T15:47:09.000000Z"}, {"uuid": "2dcb4be2-a4e8-4c73-b960-793cb45868fc", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37100", "type": "seen", "source": "https://t.me/DarkWebInformer_CVEAlerts/17896", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-37100\n\ud83d\udd25 CVSS Score: 7.7 (cvssV3_1, Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N)\n\ud83d\udd39 Description: A vulnerability in the APIs of HPE Aruba Networking Private 5G Core\u00a0could potentially expose sensitive information to unauthorized users. \nA successful exploitation could allow an attacker to iteratively navigate through the filesystem and ultimately download protected system files containing sensitive information.\n\ud83d\udccf Published: 2025-06-10T15:05:55.025Z\n\ud83d\udccf Modified: 2025-06-10T15:19:27.298Z\n\ud83d\udd17 References:\n1. https://support.hpe.com/hpesc/public/docDisplay?docId=hpesbnw04883en_us&docLocale=en_US", "creation_timestamp": "2025-06-10T15:30:51.000000Z"}, {"uuid": "dd7f3d5e-7054-4b9f-a42a-93de6e8a61da", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37855", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/18861", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-37855\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/amd/display: Guard Possible Null Pointer Dereference\n\n[WHY]\nIn some situations, dc->res_pool may be null.\n\n[HOW]\nCheck if pointer is null before dereference.\n\ud83d\udccf Published: 2025-05-09T06:42:03.545Z\n\ud83d\udccf Modified: 2025-06-19T12:56:48.089Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/dc2de1ac7145f882f3c03d2d6f84583ae7e35d41\n2. https://git.kernel.org/stable/c/c87d202692de34ee71d1fd4679a549a29095658a", "creation_timestamp": "2025-06-19T13:39:54.000000Z"}, {"uuid": "05d04742-53f1-4503-a0c2-200ff61a2d0a", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3722", "type": "seen", "source": "https://t.me/DarkWebInformer_CVEAlerts/19589", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-3722\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: A path traversal vulnerability in System Information Reporter (SIR) 1.0.3 and prior allowed  an authenticated high privileged user to issue malicious  ePO post requests to System Information Reporter, leading to creation of  files anywhere on the filesystem and possibly overwriting existing files and exposing sensitive information disclosure.\n\ud83d\udccf Published: 2025-06-26T11:08:53.374Z\n\ud83d\udccf Modified: 2025-06-26T11:08:53.374Z\n\ud83d\udd17 References:\n1. https://thrive.trellix.com/s/article/000014635", "creation_timestamp": "2025-06-26T11:51:21.000000Z"}, {"uuid": "2407fc35-54e1-4fe4-9e56-3f83b1df035e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3745", "type": "seen", "source": "https://t.me/DarkWebInformer_CVEAlerts/19905", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-3745\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: The WP Lightbox 2 WordPress plugin before 3.0.6.8 does not correctly sanitize the value of the title attribute of links before using them, which may allow malicious users to conduct XSS attacks.\n\ud83d\udccf Published: 2025-06-30T06:00:01.235Z\n\ud83d\udccf Modified: 2025-06-30T06:00:01.235Z\n\ud83d\udd17 References:\n1. https://wpscan.com/vulnerability/1b50f686-c2e0-4963-95c8-b27137dcc059/", "creation_timestamp": "2025-06-30T06:58:20.000000Z"}, {"uuid": "e736f248-cc16-45c6-bc6f-0438b3686abf", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37948", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/19686", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-37948\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\narm64: bpf: Add BHB mitigation to the epilogue for cBPF programs\n\nA malicious BPF program may manipulate the branch history to influence\nwhat the hardware speculates will happen next.\n\nOn exit from a BPF program, emit the BHB mititgation sequence.\n\nThis is only applied for 'classic' cBPF programs that are loaded by\nseccomp.\n\ud83d\udccf Published: 2025-05-20T16:01:44.452Z\n\ud83d\udccf Modified: 2025-06-27T10:21:20.431Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/c6a8735d841bcb7649734bb3a787bb174c67c0d8\n2. https://git.kernel.org/stable/c/993f63239c219696aef8887a4e7d3a16bf5a8ece\n3. https://git.kernel.org/stable/c/8fe5c37b0e08a97cf0210bb75970e945aaaeebab\n4. https://git.kernel.org/stable/c/42a20cf51011788f04cf2adbcd7681f02bdb6c27\n5. https://git.kernel.org/stable/c/38c345fd54afd9d6ed8d3fcddf3f6ea23887bf78\n6. https://git.kernel.org/stable/c/852b8ae934b5cbdc62496fa56ce9969aa2edda7f\n7. https://git.kernel.org/stable/c/0dfefc2ea2f29ced2416017d7e5b1253a54c2735", "creation_timestamp": "2025-06-27T10:49:52.000000Z"}, {"uuid": "a73b8bd8-94aa-4791-9f67-3701bba1a985", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37101", "type": "seen", "source": "https://t.me/DarkWebInformer_CVEAlerts/19577", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-37101\n\ud83d\udd25 CVSS Score: 8.7 (cvssV3_1, Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:N/I:H/A:H)\n\ud83d\udd39 Description: A potential security vulnerability has been identified in HPE OneView for VMware vCenter (OV4VC). This vulnerability could be exploited allowing an attacker with read only privilege to cause Vertical Privilege Escalation (operator can perform admin actions).\n\ud83d\udccf Published: 2025-06-26T05:19:02.298Z\n\ud83d\udccf Modified: 2025-06-26T05:19:02.298Z\n\ud83d\udd17 References:\n1. https://support.hpe.com/hpesc/public/docDisplay?docId=hpesbgn04876en_us&docLocale=en_US", "creation_timestamp": "2025-06-26T05:49:33.000000Z"}, {"uuid": "eb57ba16-629d-49c3-a4c3-673910d8f92e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37099", "type": "seen", "source": "https://t.me/DarkWebInformer_CVEAlerts/20068", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-37099\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: A remote code execution vulnerability exists in HPE Insight Remote Support (IRS) prior to v7.15.0.646.\n\ud83d\udccf Published: 2025-07-01T17:30:25.166Z\n\ud83d\udccf Modified: 2025-07-01T17:52:22.258Z\n\ud83d\udd17 References:\n1. https://support.hpe.com/hpesc/public/docDisplay?docId=hpesbgn04878en_us&docLocale=en_US", "creation_timestamp": "2025-07-01T18:08:59.000000Z"}, {"uuid": "1770de2d-7218-4b9a-8ebc-8346c39c105a", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3788", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/12415", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-3788\n\ud83d\udd25 CVSS Score: 5.1 (cvssV4_0, Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N)\n\ud83d\udd39 Description: A vulnerability was found in baseweb JSite 1.0. It has been declared as problematic. Affected by this vulnerability is an unknown functionality of the file /a/sys/user/save. The manipulation of the argument Name leads to cross site scripting. The attack can be launched remotely. The exploit has been disclosed to the public and may be used.\n\ud83d\udccf Published: 2025-04-18T10:00:12.652Z\n\ud83d\udccf Modified: 2025-04-18T10:00:12.652Z\n\ud83d\udd17 References:\n1. https://vuldb.com/?id.305611\n2. https://vuldb.com/?ctiid.305611\n3. https://vuldb.com/?submit.554565\n4. https://github.com/caigo8/CVE-md/blob/main/JSite/XSS1.md", "creation_timestamp": "2025-04-18T10:59:16.000000Z"}, {"uuid": "81ad4b88-f53f-4a59-96d1-076656aaa7e6", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37976", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/17039", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-37976\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nwifi: ath12k: Fix invalid entry fetch in ath12k_dp_mon_srng_process\n\n[ Upstream commit 63fdc4509bcf483e79548de6bc08bf3c8e504bb3 ]\n\nCurrently, ath12k_dp_mon_srng_process uses ath12k_hal_srng_src_get_next_entry\nto fetch the next entry from the destination ring. This is incorrect because\nath12k_hal_srng_src_get_next_entry is intended for source rings, not destination\nrings. This leads to invalid entry fetches, causing potential data corruption or\ncrashes due to accessing incorrect memory locations. This happens because the\nsource ring and destination ring have different handling mechanisms and using\nthe wrong function results in incorrect pointer arithmetic and ring management.\n\nTo fix this issue, replace the call to ath12k_hal_srng_src_get_next_entry with\nath12k_hal_srng_dst_get_next_entry in ath12k_dp_mon_srng_process. This ensures\nthat the correct function is used for fetching entries from the destination\nring, preventing invalid memory accesses.\n\nTested-on: QCN9274 hw2.0 PCI WLAN.WBE.1.3.1-00173-QCAHKSWPL_SILICONZ-1\nTested-on: WCN7850 hw2.0 WLAN.HMT.1.0.c5-00481-QCAHMTSWPL_V1.0_V2.0_SILICONZ-3\n\ud83d\udccf Published: 2025-05-20T16:58:19.992Z\n\ud83d\udccf Modified: 2025-05-20T16:58:19.992Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/0c1015493f0e3979bcbd3a12ebc0977578c87f21", "creation_timestamp": "2025-05-20T17:47:10.000000Z"}, {"uuid": "fc801231-a467-42c7-9468-4c22cbfe6f49", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3704", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/17643", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-3704\n\ud83d\udd25 CVSS Score: 5.9 (cvssV3_1, Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:L)\n\ud83d\udd39 Description: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in DBAR Productions Volunteer Sign Up Sheets allows Stored XSS.This issue affects Volunteer Sign Up Sheets: from n/a before 5.5.5.\n\nThe patch is available exclusively on GitHub at  https://github.com/dbarproductions/pta-volunteer-sign-up-sheets , as the vendor encounters difficulties using SVN to deploy to the WordPress.org repository.\n\ud83d\udccf Published: 2025-05-27T14:39:32.084Z\n\ud83d\udccf Modified: 2025-05-27T14:40:17.936Z\n\ud83d\udd17 References:\n1. https://patchstack.com/database/wordpress/plugin/pta-volunteer-sign-up-sheets/vulnerability/wordpress-volunteer-sign-up-sheets-plugin-5-5-5-cross-site-scripting-xss-vulnerability?_s_id=cve\n2. https://github.com/dbarproductions/pta-volunteer-sign-up-sheets/archive/refs/tags/5.5.5.zip", "creation_timestamp": "2025-05-27T14:48:33.000000Z"}, {"uuid": "ff5fa7ba-df98-4838-9815-484b86e56630", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37092", "type": "seen", "source": "https://t.me/ics_cert/1191", "content": "\u0628\u062f\u0648\u0646 \u0646\u06cc\u0627\u0632 \u0628\u0647 \u0648\u0631\u0648\u062f - \u062f\u0633\u062a\u0631\u0633\u06cc \u06a9\u0627\u0645\u0644: StoreOnce \u0641\u0631\u0627\u0645\u0648\u0634 \u06a9\u0631\u062f \u06a9\u0647 \u062f\u0631\u0650 \u0627\u0631\u0632\u0634\u0645\u0646\u062f\u062a\u0631\u06cc\u0646\u200c\u0647\u0627 \u0631\u0627 \u0628\u0628\u0646\u062f\u062f\n\n\u062f\u0631 \u062d\u0627\u0644\u06cc \u06a9\u0647 \u0628\u0631\u062e\u06cc \u062f\u0631 \u062d\u0627\u0644 \u062a\u0647\u06cc\u0647 \u0646\u0633\u062e\u0647 \u067e\u0634\u062a\u06cc\u0628\u0627\u0646 \u0628\u0648\u062f\u0646\u062f\u060c \u0628\u0631\u062e\u06cc \u062f\u06cc\u06af\u0631 \u0628\u0647 \u062f\u0646\u0628\u0627\u0644 \u0631\u0627\u0647\u200c\u0647\u0627\u06cc\u06cc \u0628\u0631\u0627\u06cc \u0647\u06a9 \u06a9\u0631\u062f\u0646 \u0645\u062e\u0641\u06cc\u0627\u0646\u0647 \u0633\u06cc\u0633\u062a\u0645 \u0634\u062e\u0635 \u062f\u06cc\u06af\u0631\u06cc \u0628\u0648\u062f\u0646\u062f.\n\n\n\u0634\u0631\u06a9\u062a Hewlett Packard Enterprise \u062f\u0631 \u0631\u0627\u0628\u0637\u0647 \u0628\u0627 \u0647\u0634\u062a \u0622\u0633\u06cc\u0628\u200c\u067e\u0630\u06cc\u0631\u06cc \u062f\u0631 \u067e\u0644\u062a\u0641\u0631\u0645 \u0646\u0631\u0645\u200c\u0627\u0641\u0632\u0627\u0631\u06cc StoreOnce backup \u0648 data deduplication \u062e\u0648\u062f\u060c \u06cc\u06a9 \u0647\u0634\u062f\u0627\u0631 \u0627\u0645\u0646\u06cc\u062a\u06cc \u0641\u0648\u0631\u06cc \u0635\u0627\u062f\u0631 \u06a9\u0631\u062f\u0647 \u0627\u0633\u062a. \u062a\u0645\u0627\u0645 \u0622\u0633\u06cc\u0628\u200c\u067e\u0630\u06cc\u0631\u06cc\u200c\u0647\u0627 \u062f\u0631 \u0646\u0633\u062e\u0647 \u062c\u062f\u06cc\u062f \u0646\u0631\u0645\u200c\u0627\u0641\u0632\u0627\u0631\u060c StoreOnce 4.3.11\u060c \u06a9\u0647 \u0627\u06a9\u0646\u0648\u0646 \u0628\u0631\u0627\u06cc \u0647\u0645\u0647 \u06a9\u0627\u0631\u0628\u0631\u0627\u0646 \u062a\u0648\u0635\u06cc\u0647 \u0645\u06cc\u200c\u0634\u0648\u062f\u060c \u0628\u0631\u0637\u0631\u0641 \u0634\u062f\u0647\u200c\u0627\u0646\u062f.\n\n\u062e\u0637\u0631\u0646\u0627\u06a9\u200c\u062a\u0631\u06cc\u0646 \u0622\u0633\u06cc\u0628\u200c\u067e\u0630\u06cc\u0631\u06cc CVE-2025-37093 \u0627\u0633\u062a \u06a9\u0647 \u062f\u0631 \u0645\u0642\u06cc\u0627\u0633 CVSS \u0646\u0633\u062e\u0647 \u06f3.\u06f1 \u0627\u0645\u062a\u06cc\u0627\u0632 \u0628\u062d\u0631\u0627\u0646\u06cc \u06f9.\u06f8 \u0631\u0627 \u062f\u0631\u06cc\u0627\u0641\u062a \u06a9\u0631\u062f\u0647 \u0627\u0633\u062a. \u0627\u06cc\u0646 \u0622\u0633\u06cc\u0628\u200c\u067e\u0630\u06cc\u0631\u06cc \u0628\u0647 \u0645\u0647\u0627\u062c\u0645 \u0627\u062c\u0627\u0632\u0647 \u0645\u06cc\u200c\u062f\u0647\u062f \u062a\u0627 \u0628\u0647 \u062f\u0644\u06cc\u0644 \u062e\u0637\u0627\u06cc\u06cc \u062f\u0631 \u067e\u06cc\u0627\u062f\u0647\u200c\u0633\u0627\u0632\u06cc \u0631\u0648\u0634 machineAccountCheck\u060c \u0645\u06a9\u0627\u0646\u06cc\u0632\u0645 \u0627\u062d\u0631\u0627\u0632 \u0647\u0648\u06cc\u062a \u0631\u0627 \u062f\u0648\u0631 \u0628\u0632\u0646\u062f. \u0647\u0645\u0627\u0646\u0637\u0648\u0631 \u06a9\u0647 \u062a\u06cc\u0645 ZDI\u060c \u06a9\u0647 \u0627\u06cc\u0646 \u0627\u0634\u06a9\u0627\u0644 \u0631\u0627 \u0634\u0646\u0627\u0633\u0627\u06cc\u06cc \u06a9\u0631\u062f\u0647 \u0627\u0633\u062a\u060c \u062a\u0648\u0636\u06cc\u062d \u0645\u06cc\u200c\u062f\u0647\u062f\u060c \u0627\u0635\u0644 \u0645\u0634\u06a9\u0644 \u062f\u0631 \u0645\u0646\u0637\u0642 \u0627\u062d\u0631\u0627\u0632 \u0647\u0648\u06cc\u062a \u0646\u0627\u062f\u0631\u0633\u062a \u0646\u0647\u0641\u062a\u0647 \u0627\u0633\u062a - \u0645\u06cc\u200c\u062a\u0648\u0627\u0646 \u0622\u0646 \u0631\u0627 \u0628\u0647 \u0637\u0648\u0631 \u06a9\u0627\u0645\u0644 \u062f\u0648\u0631 \u0632\u062f \u0648 \u0631\u0627\u0647 \u0631\u0627 \u0628\u0631\u0627\u06cc \u0633\u0627\u06cc\u0631 \u0622\u0633\u06cc\u0628\u200c\u067e\u0630\u06cc\u0631\u06cc\u200c\u0647\u0627 \u0628\u0627\u0632 \u06a9\u0631\u062f.\n\n\u0641\u0647\u0631\u0633\u062a \u062a\u0645\u0627\u0645 \u0622\u0633\u06cc\u0628\u200c\u067e\u0630\u06cc\u0631\u06cc\u200c\u0647\u0627\u06cc \u0631\u0641\u0639\u200c\u0634\u062f\u0647 \u062f\u0631 \u0646\u0633\u062e\u0647 \u06f4.\u06f3.\u06f1\u06f1 \u0634\u0627\u0645\u0644 \u0645\u0648\u0627\u0631\u062f \u0632\u06cc\u0631 \u0627\u0633\u062a:\n\nCVE-2025-37089 - \u0627\u062c\u0631\u0627\u06cc \u06a9\u062f \u0627\u0632 \u0631\u0627\u0647 \u062f\u0648\u0631\u061b\nCVE-2025-37090 - \u062d\u0645\u0644\u0647 \u062c\u0639\u0644 \u062f\u0631\u062e\u0648\u0627\u0633\u062a \u0633\u0631\u0648\u0631 (SSRF)\u061b\nCVE-2025-37091 - \u0627\u062c\u0631\u0627\u06cc \u06a9\u062f \u0627\u0632 \u0631\u0627\u0647 \u062f\u0648\u0631\u061b\nCVE-2025-37092 - \u0627\u062c\u0631\u0627\u06cc \u06a9\u062f \u0627\u0632 \u0631\u0627\u0647 \u062f\u0648\u0631\u061b\nCVE-2025-37093 - \u062f\u0648\u0631 \u0632\u062f\u0646 \u0627\u062d\u0631\u0627\u0632 \u0647\u0648\u06cc\u062a (\u0628\u062d\u0631\u0627\u0646\u06cc)\u061b\nCVE-2025-37094 - \u062d\u0630\u0641 \u0641\u0627\u06cc\u0644\u200c\u0647\u0627\u06cc \u062f\u0644\u062e\u0648\u0627\u0647 \u0627\u0632 \u0637\u0631\u06cc\u0642 \u067e\u06cc\u0645\u0627\u06cc\u0634 \u062f\u0627\u06cc\u0631\u06a9\u062a\u0648\u0631\u06cc\u061b\nCVE-2025-37095 - \u0627\u0641\u0634\u0627\u06cc \u0627\u0637\u0644\u0627\u0639\u0627\u062a \u0627\u0632 \u0637\u0631\u06cc\u0642 \u067e\u06cc\u0645\u0627\u06cc\u0634 \u062f\u0627\u06cc\u0631\u06a9\u062a\u0648\u0631\u06cc\u061b\nCVE-2025-37096 - \u0627\u062c\u0631\u0627\u06cc \u06a9\u062f \u0627\u0632 \u0631\u0627\u0647 \u062f\u0648\u0631.\n\u0627\u06af\u0631\u0686\u0647 CVE-2025-37093 \u062a\u0646\u0647\u0627 \u0645\u0648\u0631\u062f\u06cc \u0627\u0633\u062a \u06a9\u0647 \u0631\u0633\u0645\u0627\u064b \u0628\u0647 \u0639\u0646\u0648\u0627\u0646 \u0628\u062d\u0631\u0627\u0646\u06cc \u0637\u0628\u0642\u0647\u200c\u0628\u0646\u062f\u06cc \u0634\u062f\u0647 \u0627\u0633\u062a\u060c \u06a9\u0627\u0631\u0634\u0646\u0627\u0633\u0627\u0646 \u062a\u0623\u06a9\u06cc\u062f \u0645\u06cc\u200c\u06a9\u0646\u0646\u062f \u06a9\u0647 \u0633\u0627\u06cc\u0631 \u0622\u0633\u06cc\u0628\u200c\u067e\u0630\u06cc\u0631\u06cc\u200c\u0647\u0627 \u0631\u0627 \u0646\u0628\u0627\u06cc\u062f \u062f\u0633\u062a \u06a9\u0645 \u06af\u0631\u0641\u062a. \u062e\u0637\u0631 \u062a\u0631\u06a9\u06cc\u0628\u06cc \u0622\u0646\u0647\u0627 \u062f\u0631 \u0635\u0648\u0631\u062a \u062f\u0648\u0631 \u0632\u062f\u0646 \u0645\u0648\u0641\u0642\u06cc\u062a\u200c\u0622\u0645\u06cc\u0632 \u0627\u062d\u0631\u0627\u0632 \u0647\u0648\u06cc\u062a \u0628\u0647 \u0637\u0648\u0631 \u0642\u0627\u0628\u0644 \u062a\u0648\u062c\u0647\u06cc \u0627\u0641\u0632\u0627\u06cc\u0634 \u0645\u06cc\u200c\u06cc\u0627\u0628\u062f. \u0627\u06cc\u0646 \u0627\u0645\u0631 \u062d\u062a\u06cc \u0622\u0633\u06cc\u0628\u200c\u067e\u0630\u06cc\u0631\u06cc\u200c\u0647\u0627\u06cc \u0628\u0627 \u062f\u0631\u062c\u0647 \u0645\u062a\u0648\u0633\u0637 \u200b\u200b\u0645\u0627\u0646\u0646\u062f CVE-2025-37094 \u0648 CVE-2025-37095 \u0631\u0627 \u0628\u0633\u06cc\u0627\u0631 \u062e\u0637\u0631\u0646\u0627\u06a9 \u0645\u06cc\u200c\u06a9\u0646\u062f - \u062d\u0630\u0641 \u0641\u0627\u06cc\u0644 \u0648 \u0646\u0634\u062a \u062f\u0627\u062f\u0647\u200c\u0647\u0627 \u0628\u062f\u0648\u0646 \u062a\u0644\u0627\u0634 \u0632\u06cc\u0627\u062f \u0627\u0645\u06a9\u0627\u0646\u200c\u067e\u0630\u06cc\u0631 \u0627\u0633\u062a.\n\n\u0637\u0628\u0642 \u06af\u0632\u0627\u0631\u0634 Zero Day Initiative\u060c StoreOnce \u0628\u06cc\u0634 \u0627\u0632 \u0634\u0634 \u0645\u0627\u0647 \u062f\u0631 \u0628\u0631\u0627\u0628\u0631 \u0627\u06cc\u0646 \u0622\u0633\u06cc\u0628\u200c\u067e\u0630\u06cc\u0631\u06cc\u200c\u0647\u0627 \u0622\u0633\u06cc\u0628\u200c\u067e\u0630\u06cc\u0631 \u0628\u0648\u062f\u0647 \u0627\u0633\u062a. \u06a9\u0627\u0631\u0634\u0646\u0627\u0633\u0627\u0646 \u0627\u06cc\u0646 \u0645\u0634\u06a9\u0644\u0627\u062a \u0631\u0627 \u062f\u0631 \u0627\u06a9\u062a\u0628\u0631 \u06f2\u06f0\u06f2\u06f4 \u06af\u0632\u0627\u0631\u0634 \u06a9\u0631\u062f\u0646\u062f\u060c \u0627\u0645\u0627 \u062d\u062f\u0648\u062f \u0647\u0641\u062a \u0645\u0627\u0647 \u0637\u0648\u0644 \u06a9\u0634\u06cc\u062f \u062a\u0627 \u0648\u0635\u0644\u0647\u200c\u0647\u0627 \u0645\u0646\u062a\u0634\u0631 \u0634\u0648\u0646\u062f. \u0628\u0627 \u0648\u062c\u0648\u062f \u0627\u06cc\u0646\u060c \u0647\u06cc\u0686 \u062a\u0623\u06cc\u06cc\u062f\u06cc \u0648\u062c\u0648\u062f \u0646\u062f\u0627\u0631\u062f \u06a9\u0647 \u0627\u06cc\u0646 \u0622\u0633\u06cc\u0628\u200c\u067e\u0630\u06cc\u0631\u06cc\u200c\u0647\u0627 \u0628\u0647 \u0637\u0648\u0631 \u0641\u0639\u0627\u0644 \u062f\u0631 \u062d\u0645\u0644\u0627\u062a \u0648\u0627\u0642\u0639\u06cc \u0645\u0648\u0631\u062f \u0633\u0648\u0621\u0627\u0633\u062a\u0641\u0627\u062f\u0647 \u0642\u0631\u0627\u0631 \u06af\u0631\u0641\u062a\u0647\u200c\u0627\u0646\u062f.\n\nStoreOnce \u062f\u0631 \u0632\u06cc\u0631\u0633\u0627\u062e\u062a\u200c\u0647\u0627\u06cc \u0628\u0632\u0631\u06af \u0641\u0646\u0627\u0648\u0631\u06cc \u0627\u0637\u0644\u0627\u0639\u0627\u062a\u060c \u0645\u0631\u0627\u06a9\u0632 \u062f\u0627\u062f\u0647 \u0648 \u0633\u0627\u0632\u0645\u0627\u0646\u200c\u0647\u0627\u06cc\u06cc \u0628\u0627 \u062d\u062c\u0645 \u0632\u06cc\u0627\u062f\u06cc \u0627\u0632 \u062f\u0627\u062f\u0647\u200c\u0647\u0627 - \u0627\u0632 \u0627\u0631\u0627\u0626\u0647\u200c\u062f\u0647\u0646\u062f\u06af\u0627\u0646 \u062e\u062f\u0645\u0627\u062a \u0627\u0628\u0631\u06cc \u06af\u0631\u0641\u062a\u0647 \u062a\u0627 \u06a9\u0627\u0631\u0628\u0631\u0627\u0646 \u0634\u0631\u06a9\u062a\u06cc - \u0627\u0633\u062a\u0641\u0627\u062f\u0647 \u0645\u06cc\u200c\u0634\u0648\u062f. \u0627\u0632 \u062c\u0645\u0644\u0647 \u062f\u0631 \u0631\u0648\u0633\u06cc\u0647. \u0627\u06cc\u0646 \u0645\u062d\u0635\u0648\u0644 \u0628\u0627 \u0631\u0627\u0647\u06a9\u0627\u0631\u0647\u0627\u06cc \u067e\u0634\u062a\u06cc\u0628\u0627\u0646\u200c\u06af\u06cc\u0631\u06cc \u0645\u0627\u0646\u0646\u062f HPE Data Protector\u060c Veeam\u060c Commvault \u0648 Veritas NetBackup \u0627\u062f\u063a\u0627\u0645 \u0645\u06cc\u200c\u0634\u0648\u062f \u0648 \u0628\u0647 \u0639\u0646\u0648\u0627\u0646 \u06cc\u06a9 \u062c\u0632\u0621 \u06a9\u0644\u06cc\u062f\u06cc \u062f\u0631 \u0627\u0633\u062a\u0631\u0627\u062a\u0698\u06cc\u200c\u0647\u0627\u06cc \u062a\u062f\u0627\u0648\u0645 \u06a9\u0633\u0628\u200c\u0648\u06a9\u0627\u0631 \u0639\u0645\u0644 \u0645\u06cc\u200c\u06a9\u0646\u062f.\n\nHPE \u0647\u06cc\u0686 \u0631\u0627\u0647 \u062d\u0644 \u0645\u0648\u0642\u062a \u06cc\u0627 \u0627\u0642\u062f\u0627\u0645 \u0645\u0648\u0642\u062a\u06cc \u0628\u0631\u0627\u06cc \u0645\u062d\u0627\u0641\u0638\u062a \u062f\u0631 \u0628\u0631\u0627\u0628\u0631 \u0645\u0634\u06a9\u0644\u0627\u062a \u0634\u0646\u0627\u0633\u0627\u06cc\u06cc \u0634\u062f\u0647 \u0627\u0631\u0627\u0626\u0647 \u0646\u06a9\u0631\u062f\u0647 \u0627\u0633\u062a. \u062a\u0646\u0647\u0627 \u0631\u0627\u0647 \u0628\u0631\u0627\u06cc \u0628\u0633\u062a\u0646 \u0627\u06cc\u0646 \u0622\u0633\u06cc\u0628\u200c\u067e\u0630\u06cc\u0631\u06cc\u200c\u0647\u0627\u060c \u0646\u0633\u062e\u0647 \u0641\u0639\u0644\u06cc StoreOnce 4.3.11 \u0627\u0633\u062a. \u0628\u0631\u0627\u06cc \u0645\u062f\u06cc\u0631\u0627\u0646 \u0633\u06cc\u0633\u062a\u0645 \u06a9\u0647 \u0645\u062d\u06cc\u0637\u200c\u0647\u0627\u06cc \u0622\u0633\u06cc\u0628\u200c\u062f\u06cc\u062f\u0647 \u0631\u0627 \u0646\u06af\u0647\u062f\u0627\u0631\u06cc \u0645\u06cc\u200c\u06a9\u0646\u0646\u062f\u060c \u0627\u06cc\u0646 \u0628\u0647\u200c\u0631\u0648\u0632\u0631\u0633\u0627\u0646\u06cc \u062f\u0631 \u0627\u0648\u0644\u0648\u06cc\u062a \u0642\u0631\u0627\u0631 \u0645\u06cc\u200c\u06af\u06cc\u0631\u062f.\n\ud83c\udfed \u0648\u0628\u0633\u0627\u06cc\u062a \u0648 \u06a9\u0627\u0646\u0627\u0644 \u062a\u062e\u0635\u0635\u06cc \u0627\u0645\u0646\u06cc\u062a \u0632\u06cc\u0631\u0633\u0627\u062e\u062a\u0647\u0627\u06cc \u0627\u062a\u0648\u0645\u0627\u0633\u06cc\u0648\u0646 \u0648 \u06a9\u0646\u062a\u0631\u0644 \u0635\u0646\u0639\u062a\u06cc\n\ud83d\udc6e\ud83c\udffd\u200d\u2640\ufe0f\u0647\u0631\u06af\u0648\u0646\u0647 \u0627\u0646\u062a\u0634\u0627\u0631 \u0648 \u0630\u06a9\u0631 \u0645\u0637\u0627\u0644\u0628 \u0628\u062f\u0648\u0646 \u0630\u06a9\u0631 \u062f\u0642\u06cc\u0642 \u0645\u0646\u0628\u0639 \u0648 \u0622\u062f\u0631\u0633 \u0644\u06cc\u0646\u06a9 \u0622\u0646 \u0645\u0645\u0646\u0648\u0639 \u0627\u0633\u062a. \n\u0627\u062f\u0645\u06cc\u0646:\n\u200fhttps://t.me/pedram_kiani\n\u06a9\u0627\u0646\u0627\u0644 \u062a\u0644\u06af\u0631\u0627\u0645:\nhttps://t.me/ics_cert\n\u06af\u0631\u0648\u0647 \u0648\u0627\u062a\u0633 \u0622\u067e :\nhttps://chat.whatsapp.com/FpB620AWEeSKvd8U6cFh33\n\u06af\u0631\u0648\u0647 \u062a\u0644\u06af\u0631\u0627\u0645:\nhttps://t.me/ICSCERT_IR", "creation_timestamp": "2025-06-12T19:42:43.000000Z"}, {"uuid": "e0c1f8d5-3e0d-43c6-8db1-0348c14b9125", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37095", "type": "seen", "source": "https://t.me/ics_cert/1191", "content": "\u0628\u062f\u0648\u0646 \u0646\u06cc\u0627\u0632 \u0628\u0647 \u0648\u0631\u0648\u062f - \u062f\u0633\u062a\u0631\u0633\u06cc \u06a9\u0627\u0645\u0644: StoreOnce \u0641\u0631\u0627\u0645\u0648\u0634 \u06a9\u0631\u062f \u06a9\u0647 \u062f\u0631\u0650 \u0627\u0631\u0632\u0634\u0645\u0646\u062f\u062a\u0631\u06cc\u0646\u200c\u0647\u0627 \u0631\u0627 \u0628\u0628\u0646\u062f\u062f\n\n\u062f\u0631 \u062d\u0627\u0644\u06cc \u06a9\u0647 \u0628\u0631\u062e\u06cc \u062f\u0631 \u062d\u0627\u0644 \u062a\u0647\u06cc\u0647 \u0646\u0633\u062e\u0647 \u067e\u0634\u062a\u06cc\u0628\u0627\u0646 \u0628\u0648\u062f\u0646\u062f\u060c \u0628\u0631\u062e\u06cc \u062f\u06cc\u06af\u0631 \u0628\u0647 \u062f\u0646\u0628\u0627\u0644 \u0631\u0627\u0647\u200c\u0647\u0627\u06cc\u06cc \u0628\u0631\u0627\u06cc \u0647\u06a9 \u06a9\u0631\u062f\u0646 \u0645\u062e\u0641\u06cc\u0627\u0646\u0647 \u0633\u06cc\u0633\u062a\u0645 \u0634\u062e\u0635 \u062f\u06cc\u06af\u0631\u06cc \u0628\u0648\u062f\u0646\u062f.\n\n\n\u0634\u0631\u06a9\u062a Hewlett Packard Enterprise \u062f\u0631 \u0631\u0627\u0628\u0637\u0647 \u0628\u0627 \u0647\u0634\u062a \u0622\u0633\u06cc\u0628\u200c\u067e\u0630\u06cc\u0631\u06cc \u062f\u0631 \u067e\u0644\u062a\u0641\u0631\u0645 \u0646\u0631\u0645\u200c\u0627\u0641\u0632\u0627\u0631\u06cc StoreOnce backup \u0648 data deduplication \u062e\u0648\u062f\u060c \u06cc\u06a9 \u0647\u0634\u062f\u0627\u0631 \u0627\u0645\u0646\u06cc\u062a\u06cc \u0641\u0648\u0631\u06cc \u0635\u0627\u062f\u0631 \u06a9\u0631\u062f\u0647 \u0627\u0633\u062a. \u062a\u0645\u0627\u0645 \u0622\u0633\u06cc\u0628\u200c\u067e\u0630\u06cc\u0631\u06cc\u200c\u0647\u0627 \u062f\u0631 \u0646\u0633\u062e\u0647 \u062c\u062f\u06cc\u062f \u0646\u0631\u0645\u200c\u0627\u0641\u0632\u0627\u0631\u060c StoreOnce 4.3.11\u060c \u06a9\u0647 \u0627\u06a9\u0646\u0648\u0646 \u0628\u0631\u0627\u06cc \u0647\u0645\u0647 \u06a9\u0627\u0631\u0628\u0631\u0627\u0646 \u062a\u0648\u0635\u06cc\u0647 \u0645\u06cc\u200c\u0634\u0648\u062f\u060c \u0628\u0631\u0637\u0631\u0641 \u0634\u062f\u0647\u200c\u0627\u0646\u062f.\n\n\u062e\u0637\u0631\u0646\u0627\u06a9\u200c\u062a\u0631\u06cc\u0646 \u0622\u0633\u06cc\u0628\u200c\u067e\u0630\u06cc\u0631\u06cc CVE-2025-37093 \u0627\u0633\u062a \u06a9\u0647 \u062f\u0631 \u0645\u0642\u06cc\u0627\u0633 CVSS \u0646\u0633\u062e\u0647 \u06f3.\u06f1 \u0627\u0645\u062a\u06cc\u0627\u0632 \u0628\u062d\u0631\u0627\u0646\u06cc \u06f9.\u06f8 \u0631\u0627 \u062f\u0631\u06cc\u0627\u0641\u062a \u06a9\u0631\u062f\u0647 \u0627\u0633\u062a. \u0627\u06cc\u0646 \u0622\u0633\u06cc\u0628\u200c\u067e\u0630\u06cc\u0631\u06cc \u0628\u0647 \u0645\u0647\u0627\u062c\u0645 \u0627\u062c\u0627\u0632\u0647 \u0645\u06cc\u200c\u062f\u0647\u062f \u062a\u0627 \u0628\u0647 \u062f\u0644\u06cc\u0644 \u062e\u0637\u0627\u06cc\u06cc \u062f\u0631 \u067e\u06cc\u0627\u062f\u0647\u200c\u0633\u0627\u0632\u06cc \u0631\u0648\u0634 machineAccountCheck\u060c \u0645\u06a9\u0627\u0646\u06cc\u0632\u0645 \u0627\u062d\u0631\u0627\u0632 \u0647\u0648\u06cc\u062a \u0631\u0627 \u062f\u0648\u0631 \u0628\u0632\u0646\u062f. \u0647\u0645\u0627\u0646\u0637\u0648\u0631 \u06a9\u0647 \u062a\u06cc\u0645 ZDI\u060c \u06a9\u0647 \u0627\u06cc\u0646 \u0627\u0634\u06a9\u0627\u0644 \u0631\u0627 \u0634\u0646\u0627\u0633\u0627\u06cc\u06cc \u06a9\u0631\u062f\u0647 \u0627\u0633\u062a\u060c \u062a\u0648\u0636\u06cc\u062d \u0645\u06cc\u200c\u062f\u0647\u062f\u060c \u0627\u0635\u0644 \u0645\u0634\u06a9\u0644 \u062f\u0631 \u0645\u0646\u0637\u0642 \u0627\u062d\u0631\u0627\u0632 \u0647\u0648\u06cc\u062a \u0646\u0627\u062f\u0631\u0633\u062a \u0646\u0647\u0641\u062a\u0647 \u0627\u0633\u062a - \u0645\u06cc\u200c\u062a\u0648\u0627\u0646 \u0622\u0646 \u0631\u0627 \u0628\u0647 \u0637\u0648\u0631 \u06a9\u0627\u0645\u0644 \u062f\u0648\u0631 \u0632\u062f \u0648 \u0631\u0627\u0647 \u0631\u0627 \u0628\u0631\u0627\u06cc \u0633\u0627\u06cc\u0631 \u0622\u0633\u06cc\u0628\u200c\u067e\u0630\u06cc\u0631\u06cc\u200c\u0647\u0627 \u0628\u0627\u0632 \u06a9\u0631\u062f.\n\n\u0641\u0647\u0631\u0633\u062a \u062a\u0645\u0627\u0645 \u0622\u0633\u06cc\u0628\u200c\u067e\u0630\u06cc\u0631\u06cc\u200c\u0647\u0627\u06cc \u0631\u0641\u0639\u200c\u0634\u062f\u0647 \u062f\u0631 \u0646\u0633\u062e\u0647 \u06f4.\u06f3.\u06f1\u06f1 \u0634\u0627\u0645\u0644 \u0645\u0648\u0627\u0631\u062f \u0632\u06cc\u0631 \u0627\u0633\u062a:\n\nCVE-2025-37089 - \u0627\u062c\u0631\u0627\u06cc \u06a9\u062f \u0627\u0632 \u0631\u0627\u0647 \u062f\u0648\u0631\u061b\nCVE-2025-37090 - \u062d\u0645\u0644\u0647 \u062c\u0639\u0644 \u062f\u0631\u062e\u0648\u0627\u0633\u062a \u0633\u0631\u0648\u0631 (SSRF)\u061b\nCVE-2025-37091 - \u0627\u062c\u0631\u0627\u06cc \u06a9\u062f \u0627\u0632 \u0631\u0627\u0647 \u062f\u0648\u0631\u061b\nCVE-2025-37092 - \u0627\u062c\u0631\u0627\u06cc \u06a9\u062f \u0627\u0632 \u0631\u0627\u0647 \u062f\u0648\u0631\u061b\nCVE-2025-37093 - \u062f\u0648\u0631 \u0632\u062f\u0646 \u0627\u062d\u0631\u0627\u0632 \u0647\u0648\u06cc\u062a (\u0628\u062d\u0631\u0627\u0646\u06cc)\u061b\nCVE-2025-37094 - \u062d\u0630\u0641 \u0641\u0627\u06cc\u0644\u200c\u0647\u0627\u06cc \u062f\u0644\u062e\u0648\u0627\u0647 \u0627\u0632 \u0637\u0631\u06cc\u0642 \u067e\u06cc\u0645\u0627\u06cc\u0634 \u062f\u0627\u06cc\u0631\u06a9\u062a\u0648\u0631\u06cc\u061b\nCVE-2025-37095 - \u0627\u0641\u0634\u0627\u06cc \u0627\u0637\u0644\u0627\u0639\u0627\u062a \u0627\u0632 \u0637\u0631\u06cc\u0642 \u067e\u06cc\u0645\u0627\u06cc\u0634 \u062f\u0627\u06cc\u0631\u06a9\u062a\u0648\u0631\u06cc\u061b\nCVE-2025-37096 - \u0627\u062c\u0631\u0627\u06cc \u06a9\u062f \u0627\u0632 \u0631\u0627\u0647 \u062f\u0648\u0631.\n\u0627\u06af\u0631\u0686\u0647 CVE-2025-37093 \u062a\u0646\u0647\u0627 \u0645\u0648\u0631\u062f\u06cc \u0627\u0633\u062a \u06a9\u0647 \u0631\u0633\u0645\u0627\u064b \u0628\u0647 \u0639\u0646\u0648\u0627\u0646 \u0628\u062d\u0631\u0627\u0646\u06cc \u0637\u0628\u0642\u0647\u200c\u0628\u0646\u062f\u06cc \u0634\u062f\u0647 \u0627\u0633\u062a\u060c \u06a9\u0627\u0631\u0634\u0646\u0627\u0633\u0627\u0646 \u062a\u0623\u06a9\u06cc\u062f \u0645\u06cc\u200c\u06a9\u0646\u0646\u062f \u06a9\u0647 \u0633\u0627\u06cc\u0631 \u0622\u0633\u06cc\u0628\u200c\u067e\u0630\u06cc\u0631\u06cc\u200c\u0647\u0627 \u0631\u0627 \u0646\u0628\u0627\u06cc\u062f \u062f\u0633\u062a \u06a9\u0645 \u06af\u0631\u0641\u062a. \u062e\u0637\u0631 \u062a\u0631\u06a9\u06cc\u0628\u06cc \u0622\u0646\u0647\u0627 \u062f\u0631 \u0635\u0648\u0631\u062a \u062f\u0648\u0631 \u0632\u062f\u0646 \u0645\u0648\u0641\u0642\u06cc\u062a\u200c\u0622\u0645\u06cc\u0632 \u0627\u062d\u0631\u0627\u0632 \u0647\u0648\u06cc\u062a \u0628\u0647 \u0637\u0648\u0631 \u0642\u0627\u0628\u0644 \u062a\u0648\u062c\u0647\u06cc \u0627\u0641\u0632\u0627\u06cc\u0634 \u0645\u06cc\u200c\u06cc\u0627\u0628\u062f. \u0627\u06cc\u0646 \u0627\u0645\u0631 \u062d\u062a\u06cc \u0622\u0633\u06cc\u0628\u200c\u067e\u0630\u06cc\u0631\u06cc\u200c\u0647\u0627\u06cc \u0628\u0627 \u062f\u0631\u062c\u0647 \u0645\u062a\u0648\u0633\u0637 \u200b\u200b\u0645\u0627\u0646\u0646\u062f CVE-2025-37094 \u0648 CVE-2025-37095 \u0631\u0627 \u0628\u0633\u06cc\u0627\u0631 \u062e\u0637\u0631\u0646\u0627\u06a9 \u0645\u06cc\u200c\u06a9\u0646\u062f - \u062d\u0630\u0641 \u0641\u0627\u06cc\u0644 \u0648 \u0646\u0634\u062a \u062f\u0627\u062f\u0647\u200c\u0647\u0627 \u0628\u062f\u0648\u0646 \u062a\u0644\u0627\u0634 \u0632\u06cc\u0627\u062f \u0627\u0645\u06a9\u0627\u0646\u200c\u067e\u0630\u06cc\u0631 \u0627\u0633\u062a.\n\n\u0637\u0628\u0642 \u06af\u0632\u0627\u0631\u0634 Zero Day Initiative\u060c StoreOnce \u0628\u06cc\u0634 \u0627\u0632 \u0634\u0634 \u0645\u0627\u0647 \u062f\u0631 \u0628\u0631\u0627\u0628\u0631 \u0627\u06cc\u0646 \u0622\u0633\u06cc\u0628\u200c\u067e\u0630\u06cc\u0631\u06cc\u200c\u0647\u0627 \u0622\u0633\u06cc\u0628\u200c\u067e\u0630\u06cc\u0631 \u0628\u0648\u062f\u0647 \u0627\u0633\u062a. \u06a9\u0627\u0631\u0634\u0646\u0627\u0633\u0627\u0646 \u0627\u06cc\u0646 \u0645\u0634\u06a9\u0644\u0627\u062a \u0631\u0627 \u062f\u0631 \u0627\u06a9\u062a\u0628\u0631 \u06f2\u06f0\u06f2\u06f4 \u06af\u0632\u0627\u0631\u0634 \u06a9\u0631\u062f\u0646\u062f\u060c \u0627\u0645\u0627 \u062d\u062f\u0648\u062f \u0647\u0641\u062a \u0645\u0627\u0647 \u0637\u0648\u0644 \u06a9\u0634\u06cc\u062f \u062a\u0627 \u0648\u0635\u0644\u0647\u200c\u0647\u0627 \u0645\u0646\u062a\u0634\u0631 \u0634\u0648\u0646\u062f. \u0628\u0627 \u0648\u062c\u0648\u062f \u0627\u06cc\u0646\u060c \u0647\u06cc\u0686 \u062a\u0623\u06cc\u06cc\u062f\u06cc \u0648\u062c\u0648\u062f \u0646\u062f\u0627\u0631\u062f \u06a9\u0647 \u0627\u06cc\u0646 \u0622\u0633\u06cc\u0628\u200c\u067e\u0630\u06cc\u0631\u06cc\u200c\u0647\u0627 \u0628\u0647 \u0637\u0648\u0631 \u0641\u0639\u0627\u0644 \u062f\u0631 \u062d\u0645\u0644\u0627\u062a \u0648\u0627\u0642\u0639\u06cc \u0645\u0648\u0631\u062f \u0633\u0648\u0621\u0627\u0633\u062a\u0641\u0627\u062f\u0647 \u0642\u0631\u0627\u0631 \u06af\u0631\u0641\u062a\u0647\u200c\u0627\u0646\u062f.\n\nStoreOnce \u062f\u0631 \u0632\u06cc\u0631\u0633\u0627\u062e\u062a\u200c\u0647\u0627\u06cc \u0628\u0632\u0631\u06af \u0641\u0646\u0627\u0648\u0631\u06cc \u0627\u0637\u0644\u0627\u0639\u0627\u062a\u060c \u0645\u0631\u0627\u06a9\u0632 \u062f\u0627\u062f\u0647 \u0648 \u0633\u0627\u0632\u0645\u0627\u0646\u200c\u0647\u0627\u06cc\u06cc \u0628\u0627 \u062d\u062c\u0645 \u0632\u06cc\u0627\u062f\u06cc \u0627\u0632 \u062f\u0627\u062f\u0647\u200c\u0647\u0627 - \u0627\u0632 \u0627\u0631\u0627\u0626\u0647\u200c\u062f\u0647\u0646\u062f\u06af\u0627\u0646 \u062e\u062f\u0645\u0627\u062a \u0627\u0628\u0631\u06cc \u06af\u0631\u0641\u062a\u0647 \u062a\u0627 \u06a9\u0627\u0631\u0628\u0631\u0627\u0646 \u0634\u0631\u06a9\u062a\u06cc - \u0627\u0633\u062a\u0641\u0627\u062f\u0647 \u0645\u06cc\u200c\u0634\u0648\u062f. \u0627\u0632 \u062c\u0645\u0644\u0647 \u062f\u0631 \u0631\u0648\u0633\u06cc\u0647. \u0627\u06cc\u0646 \u0645\u062d\u0635\u0648\u0644 \u0628\u0627 \u0631\u0627\u0647\u06a9\u0627\u0631\u0647\u0627\u06cc \u067e\u0634\u062a\u06cc\u0628\u0627\u0646\u200c\u06af\u06cc\u0631\u06cc \u0645\u0627\u0646\u0646\u062f HPE Data Protector\u060c Veeam\u060c Commvault \u0648 Veritas NetBackup \u0627\u062f\u063a\u0627\u0645 \u0645\u06cc\u200c\u0634\u0648\u062f \u0648 \u0628\u0647 \u0639\u0646\u0648\u0627\u0646 \u06cc\u06a9 \u062c\u0632\u0621 \u06a9\u0644\u06cc\u062f\u06cc \u062f\u0631 \u0627\u0633\u062a\u0631\u0627\u062a\u0698\u06cc\u200c\u0647\u0627\u06cc \u062a\u062f\u0627\u0648\u0645 \u06a9\u0633\u0628\u200c\u0648\u06a9\u0627\u0631 \u0639\u0645\u0644 \u0645\u06cc\u200c\u06a9\u0646\u062f.\n\nHPE \u0647\u06cc\u0686 \u0631\u0627\u0647 \u062d\u0644 \u0645\u0648\u0642\u062a \u06cc\u0627 \u0627\u0642\u062f\u0627\u0645 \u0645\u0648\u0642\u062a\u06cc \u0628\u0631\u0627\u06cc \u0645\u062d\u0627\u0641\u0638\u062a \u062f\u0631 \u0628\u0631\u0627\u0628\u0631 \u0645\u0634\u06a9\u0644\u0627\u062a \u0634\u0646\u0627\u0633\u0627\u06cc\u06cc \u0634\u062f\u0647 \u0627\u0631\u0627\u0626\u0647 \u0646\u06a9\u0631\u062f\u0647 \u0627\u0633\u062a. \u062a\u0646\u0647\u0627 \u0631\u0627\u0647 \u0628\u0631\u0627\u06cc \u0628\u0633\u062a\u0646 \u0627\u06cc\u0646 \u0622\u0633\u06cc\u0628\u200c\u067e\u0630\u06cc\u0631\u06cc\u200c\u0647\u0627\u060c \u0646\u0633\u062e\u0647 \u0641\u0639\u0644\u06cc StoreOnce 4.3.11 \u0627\u0633\u062a. \u0628\u0631\u0627\u06cc \u0645\u062f\u06cc\u0631\u0627\u0646 \u0633\u06cc\u0633\u062a\u0645 \u06a9\u0647 \u0645\u062d\u06cc\u0637\u200c\u0647\u0627\u06cc \u0622\u0633\u06cc\u0628\u200c\u062f\u06cc\u062f\u0647 \u0631\u0627 \u0646\u06af\u0647\u062f\u0627\u0631\u06cc \u0645\u06cc\u200c\u06a9\u0646\u0646\u062f\u060c \u0627\u06cc\u0646 \u0628\u0647\u200c\u0631\u0648\u0632\u0631\u0633\u0627\u0646\u06cc \u062f\u0631 \u0627\u0648\u0644\u0648\u06cc\u062a \u0642\u0631\u0627\u0631 \u0645\u06cc\u200c\u06af\u06cc\u0631\u062f.\n\ud83c\udfed \u0648\u0628\u0633\u0627\u06cc\u062a \u0648 \u06a9\u0627\u0646\u0627\u0644 \u062a\u062e\u0635\u0635\u06cc \u0627\u0645\u0646\u06cc\u062a \u0632\u06cc\u0631\u0633\u0627\u062e\u062a\u0647\u0627\u06cc \u0627\u062a\u0648\u0645\u0627\u0633\u06cc\u0648\u0646 \u0648 \u06a9\u0646\u062a\u0631\u0644 \u0635\u0646\u0639\u062a\u06cc\n\ud83d\udc6e\ud83c\udffd\u200d\u2640\ufe0f\u0647\u0631\u06af\u0648\u0646\u0647 \u0627\u0646\u062a\u0634\u0627\u0631 \u0648 \u0630\u06a9\u0631 \u0645\u0637\u0627\u0644\u0628 \u0628\u062f\u0648\u0646 \u0630\u06a9\u0631 \u062f\u0642\u06cc\u0642 \u0645\u0646\u0628\u0639 \u0648 \u0622\u062f\u0631\u0633 \u0644\u06cc\u0646\u06a9 \u0622\u0646 \u0645\u0645\u0646\u0648\u0639 \u0627\u0633\u062a. \n\u0627\u062f\u0645\u06cc\u0646:\n\u200fhttps://t.me/pedram_kiani\n\u06a9\u0627\u0646\u0627\u0644 \u062a\u0644\u06af\u0631\u0627\u0645:\nhttps://t.me/ics_cert\n\u06af\u0631\u0648\u0647 \u0648\u0627\u062a\u0633 \u0622\u067e :\nhttps://chat.whatsapp.com/FpB620AWEeSKvd8U6cFh33\n\u06af\u0631\u0648\u0647 \u062a\u0644\u06af\u0631\u0627\u0645:\nhttps://t.me/ICSCERT_IR", "creation_timestamp": "2025-06-12T19:42:43.000000Z"}, {"uuid": "1197f790-60ae-4e03-bd0f-dd951d18be21", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37090", "type": "seen", "source": "https://t.me/ics_cert/1191", "content": "\u0628\u062f\u0648\u0646 \u0646\u06cc\u0627\u0632 \u0628\u0647 \u0648\u0631\u0648\u062f - \u062f\u0633\u062a\u0631\u0633\u06cc \u06a9\u0627\u0645\u0644: StoreOnce \u0641\u0631\u0627\u0645\u0648\u0634 \u06a9\u0631\u062f \u06a9\u0647 \u062f\u0631\u0650 \u0627\u0631\u0632\u0634\u0645\u0646\u062f\u062a\u0631\u06cc\u0646\u200c\u0647\u0627 \u0631\u0627 \u0628\u0628\u0646\u062f\u062f\n\n\u062f\u0631 \u062d\u0627\u0644\u06cc \u06a9\u0647 \u0628\u0631\u062e\u06cc \u062f\u0631 \u062d\u0627\u0644 \u062a\u0647\u06cc\u0647 \u0646\u0633\u062e\u0647 \u067e\u0634\u062a\u06cc\u0628\u0627\u0646 \u0628\u0648\u062f\u0646\u062f\u060c \u0628\u0631\u062e\u06cc \u062f\u06cc\u06af\u0631 \u0628\u0647 \u062f\u0646\u0628\u0627\u0644 \u0631\u0627\u0647\u200c\u0647\u0627\u06cc\u06cc \u0628\u0631\u0627\u06cc \u0647\u06a9 \u06a9\u0631\u062f\u0646 \u0645\u062e\u0641\u06cc\u0627\u0646\u0647 \u0633\u06cc\u0633\u062a\u0645 \u0634\u062e\u0635 \u062f\u06cc\u06af\u0631\u06cc \u0628\u0648\u062f\u0646\u062f.\n\n\n\u0634\u0631\u06a9\u062a Hewlett Packard Enterprise \u062f\u0631 \u0631\u0627\u0628\u0637\u0647 \u0628\u0627 \u0647\u0634\u062a \u0622\u0633\u06cc\u0628\u200c\u067e\u0630\u06cc\u0631\u06cc \u062f\u0631 \u067e\u0644\u062a\u0641\u0631\u0645 \u0646\u0631\u0645\u200c\u0627\u0641\u0632\u0627\u0631\u06cc StoreOnce backup \u0648 data deduplication \u062e\u0648\u062f\u060c \u06cc\u06a9 \u0647\u0634\u062f\u0627\u0631 \u0627\u0645\u0646\u06cc\u062a\u06cc \u0641\u0648\u0631\u06cc \u0635\u0627\u062f\u0631 \u06a9\u0631\u062f\u0647 \u0627\u0633\u062a. \u062a\u0645\u0627\u0645 \u0622\u0633\u06cc\u0628\u200c\u067e\u0630\u06cc\u0631\u06cc\u200c\u0647\u0627 \u062f\u0631 \u0646\u0633\u062e\u0647 \u062c\u062f\u06cc\u062f \u0646\u0631\u0645\u200c\u0627\u0641\u0632\u0627\u0631\u060c StoreOnce 4.3.11\u060c \u06a9\u0647 \u0627\u06a9\u0646\u0648\u0646 \u0628\u0631\u0627\u06cc \u0647\u0645\u0647 \u06a9\u0627\u0631\u0628\u0631\u0627\u0646 \u062a\u0648\u0635\u06cc\u0647 \u0645\u06cc\u200c\u0634\u0648\u062f\u060c \u0628\u0631\u0637\u0631\u0641 \u0634\u062f\u0647\u200c\u0627\u0646\u062f.\n\n\u062e\u0637\u0631\u0646\u0627\u06a9\u200c\u062a\u0631\u06cc\u0646 \u0622\u0633\u06cc\u0628\u200c\u067e\u0630\u06cc\u0631\u06cc CVE-2025-37093 \u0627\u0633\u062a \u06a9\u0647 \u062f\u0631 \u0645\u0642\u06cc\u0627\u0633 CVSS \u0646\u0633\u062e\u0647 \u06f3.\u06f1 \u0627\u0645\u062a\u06cc\u0627\u0632 \u0628\u062d\u0631\u0627\u0646\u06cc \u06f9.\u06f8 \u0631\u0627 \u062f\u0631\u06cc\u0627\u0641\u062a \u06a9\u0631\u062f\u0647 \u0627\u0633\u062a. \u0627\u06cc\u0646 \u0622\u0633\u06cc\u0628\u200c\u067e\u0630\u06cc\u0631\u06cc \u0628\u0647 \u0645\u0647\u0627\u062c\u0645 \u0627\u062c\u0627\u0632\u0647 \u0645\u06cc\u200c\u062f\u0647\u062f \u062a\u0627 \u0628\u0647 \u062f\u0644\u06cc\u0644 \u062e\u0637\u0627\u06cc\u06cc \u062f\u0631 \u067e\u06cc\u0627\u062f\u0647\u200c\u0633\u0627\u0632\u06cc \u0631\u0648\u0634 machineAccountCheck\u060c \u0645\u06a9\u0627\u0646\u06cc\u0632\u0645 \u0627\u062d\u0631\u0627\u0632 \u0647\u0648\u06cc\u062a \u0631\u0627 \u062f\u0648\u0631 \u0628\u0632\u0646\u062f. \u0647\u0645\u0627\u0646\u0637\u0648\u0631 \u06a9\u0647 \u062a\u06cc\u0645 ZDI\u060c \u06a9\u0647 \u0627\u06cc\u0646 \u0627\u0634\u06a9\u0627\u0644 \u0631\u0627 \u0634\u0646\u0627\u0633\u0627\u06cc\u06cc \u06a9\u0631\u062f\u0647 \u0627\u0633\u062a\u060c \u062a\u0648\u0636\u06cc\u062d \u0645\u06cc\u200c\u062f\u0647\u062f\u060c \u0627\u0635\u0644 \u0645\u0634\u06a9\u0644 \u062f\u0631 \u0645\u0646\u0637\u0642 \u0627\u062d\u0631\u0627\u0632 \u0647\u0648\u06cc\u062a \u0646\u0627\u062f\u0631\u0633\u062a \u0646\u0647\u0641\u062a\u0647 \u0627\u0633\u062a - \u0645\u06cc\u200c\u062a\u0648\u0627\u0646 \u0622\u0646 \u0631\u0627 \u0628\u0647 \u0637\u0648\u0631 \u06a9\u0627\u0645\u0644 \u062f\u0648\u0631 \u0632\u062f \u0648 \u0631\u0627\u0647 \u0631\u0627 \u0628\u0631\u0627\u06cc \u0633\u0627\u06cc\u0631 \u0622\u0633\u06cc\u0628\u200c\u067e\u0630\u06cc\u0631\u06cc\u200c\u0647\u0627 \u0628\u0627\u0632 \u06a9\u0631\u062f.\n\n\u0641\u0647\u0631\u0633\u062a \u062a\u0645\u0627\u0645 \u0622\u0633\u06cc\u0628\u200c\u067e\u0630\u06cc\u0631\u06cc\u200c\u0647\u0627\u06cc \u0631\u0641\u0639\u200c\u0634\u062f\u0647 \u062f\u0631 \u0646\u0633\u062e\u0647 \u06f4.\u06f3.\u06f1\u06f1 \u0634\u0627\u0645\u0644 \u0645\u0648\u0627\u0631\u062f \u0632\u06cc\u0631 \u0627\u0633\u062a:\n\nCVE-2025-37089 - \u0627\u062c\u0631\u0627\u06cc \u06a9\u062f \u0627\u0632 \u0631\u0627\u0647 \u062f\u0648\u0631\u061b\nCVE-2025-37090 - \u062d\u0645\u0644\u0647 \u062c\u0639\u0644 \u062f\u0631\u062e\u0648\u0627\u0633\u062a \u0633\u0631\u0648\u0631 (SSRF)\u061b\nCVE-2025-37091 - \u0627\u062c\u0631\u0627\u06cc \u06a9\u062f \u0627\u0632 \u0631\u0627\u0647 \u062f\u0648\u0631\u061b\nCVE-2025-37092 - \u0627\u062c\u0631\u0627\u06cc \u06a9\u062f \u0627\u0632 \u0631\u0627\u0647 \u062f\u0648\u0631\u061b\nCVE-2025-37093 - \u062f\u0648\u0631 \u0632\u062f\u0646 \u0627\u062d\u0631\u0627\u0632 \u0647\u0648\u06cc\u062a (\u0628\u062d\u0631\u0627\u0646\u06cc)\u061b\nCVE-2025-37094 - \u062d\u0630\u0641 \u0641\u0627\u06cc\u0644\u200c\u0647\u0627\u06cc \u062f\u0644\u062e\u0648\u0627\u0647 \u0627\u0632 \u0637\u0631\u06cc\u0642 \u067e\u06cc\u0645\u0627\u06cc\u0634 \u062f\u0627\u06cc\u0631\u06a9\u062a\u0648\u0631\u06cc\u061b\nCVE-2025-37095 - \u0627\u0641\u0634\u0627\u06cc \u0627\u0637\u0644\u0627\u0639\u0627\u062a \u0627\u0632 \u0637\u0631\u06cc\u0642 \u067e\u06cc\u0645\u0627\u06cc\u0634 \u062f\u0627\u06cc\u0631\u06a9\u062a\u0648\u0631\u06cc\u061b\nCVE-2025-37096 - \u0627\u062c\u0631\u0627\u06cc \u06a9\u062f \u0627\u0632 \u0631\u0627\u0647 \u062f\u0648\u0631.\n\u0627\u06af\u0631\u0686\u0647 CVE-2025-37093 \u062a\u0646\u0647\u0627 \u0645\u0648\u0631\u062f\u06cc \u0627\u0633\u062a \u06a9\u0647 \u0631\u0633\u0645\u0627\u064b \u0628\u0647 \u0639\u0646\u0648\u0627\u0646 \u0628\u062d\u0631\u0627\u0646\u06cc \u0637\u0628\u0642\u0647\u200c\u0628\u0646\u062f\u06cc \u0634\u062f\u0647 \u0627\u0633\u062a\u060c \u06a9\u0627\u0631\u0634\u0646\u0627\u0633\u0627\u0646 \u062a\u0623\u06a9\u06cc\u062f \u0645\u06cc\u200c\u06a9\u0646\u0646\u062f \u06a9\u0647 \u0633\u0627\u06cc\u0631 \u0622\u0633\u06cc\u0628\u200c\u067e\u0630\u06cc\u0631\u06cc\u200c\u0647\u0627 \u0631\u0627 \u0646\u0628\u0627\u06cc\u062f \u062f\u0633\u062a \u06a9\u0645 \u06af\u0631\u0641\u062a. \u062e\u0637\u0631 \u062a\u0631\u06a9\u06cc\u0628\u06cc \u0622\u0646\u0647\u0627 \u062f\u0631 \u0635\u0648\u0631\u062a \u062f\u0648\u0631 \u0632\u062f\u0646 \u0645\u0648\u0641\u0642\u06cc\u062a\u200c\u0622\u0645\u06cc\u0632 \u0627\u062d\u0631\u0627\u0632 \u0647\u0648\u06cc\u062a \u0628\u0647 \u0637\u0648\u0631 \u0642\u0627\u0628\u0644 \u062a\u0648\u062c\u0647\u06cc \u0627\u0641\u0632\u0627\u06cc\u0634 \u0645\u06cc\u200c\u06cc\u0627\u0628\u062f. \u0627\u06cc\u0646 \u0627\u0645\u0631 \u062d\u062a\u06cc \u0622\u0633\u06cc\u0628\u200c\u067e\u0630\u06cc\u0631\u06cc\u200c\u0647\u0627\u06cc \u0628\u0627 \u062f\u0631\u062c\u0647 \u0645\u062a\u0648\u0633\u0637 \u200b\u200b\u0645\u0627\u0646\u0646\u062f CVE-2025-37094 \u0648 CVE-2025-37095 \u0631\u0627 \u0628\u0633\u06cc\u0627\u0631 \u062e\u0637\u0631\u0646\u0627\u06a9 \u0645\u06cc\u200c\u06a9\u0646\u062f - \u062d\u0630\u0641 \u0641\u0627\u06cc\u0644 \u0648 \u0646\u0634\u062a \u062f\u0627\u062f\u0647\u200c\u0647\u0627 \u0628\u062f\u0648\u0646 \u062a\u0644\u0627\u0634 \u0632\u06cc\u0627\u062f \u0627\u0645\u06a9\u0627\u0646\u200c\u067e\u0630\u06cc\u0631 \u0627\u0633\u062a.\n\n\u0637\u0628\u0642 \u06af\u0632\u0627\u0631\u0634 Zero Day Initiative\u060c StoreOnce \u0628\u06cc\u0634 \u0627\u0632 \u0634\u0634 \u0645\u0627\u0647 \u062f\u0631 \u0628\u0631\u0627\u0628\u0631 \u0627\u06cc\u0646 \u0622\u0633\u06cc\u0628\u200c\u067e\u0630\u06cc\u0631\u06cc\u200c\u0647\u0627 \u0622\u0633\u06cc\u0628\u200c\u067e\u0630\u06cc\u0631 \u0628\u0648\u062f\u0647 \u0627\u0633\u062a. \u06a9\u0627\u0631\u0634\u0646\u0627\u0633\u0627\u0646 \u0627\u06cc\u0646 \u0645\u0634\u06a9\u0644\u0627\u062a \u0631\u0627 \u062f\u0631 \u0627\u06a9\u062a\u0628\u0631 \u06f2\u06f0\u06f2\u06f4 \u06af\u0632\u0627\u0631\u0634 \u06a9\u0631\u062f\u0646\u062f\u060c \u0627\u0645\u0627 \u062d\u062f\u0648\u062f \u0647\u0641\u062a \u0645\u0627\u0647 \u0637\u0648\u0644 \u06a9\u0634\u06cc\u062f \u062a\u0627 \u0648\u0635\u0644\u0647\u200c\u0647\u0627 \u0645\u0646\u062a\u0634\u0631 \u0634\u0648\u0646\u062f. \u0628\u0627 \u0648\u062c\u0648\u062f \u0627\u06cc\u0646\u060c \u0647\u06cc\u0686 \u062a\u0623\u06cc\u06cc\u062f\u06cc \u0648\u062c\u0648\u062f \u0646\u062f\u0627\u0631\u062f \u06a9\u0647 \u0627\u06cc\u0646 \u0622\u0633\u06cc\u0628\u200c\u067e\u0630\u06cc\u0631\u06cc\u200c\u0647\u0627 \u0628\u0647 \u0637\u0648\u0631 \u0641\u0639\u0627\u0644 \u062f\u0631 \u062d\u0645\u0644\u0627\u062a \u0648\u0627\u0642\u0639\u06cc \u0645\u0648\u0631\u062f \u0633\u0648\u0621\u0627\u0633\u062a\u0641\u0627\u062f\u0647 \u0642\u0631\u0627\u0631 \u06af\u0631\u0641\u062a\u0647\u200c\u0627\u0646\u062f.\n\nStoreOnce \u062f\u0631 \u0632\u06cc\u0631\u0633\u0627\u062e\u062a\u200c\u0647\u0627\u06cc \u0628\u0632\u0631\u06af \u0641\u0646\u0627\u0648\u0631\u06cc \u0627\u0637\u0644\u0627\u0639\u0627\u062a\u060c \u0645\u0631\u0627\u06a9\u0632 \u062f\u0627\u062f\u0647 \u0648 \u0633\u0627\u0632\u0645\u0627\u0646\u200c\u0647\u0627\u06cc\u06cc \u0628\u0627 \u062d\u062c\u0645 \u0632\u06cc\u0627\u062f\u06cc \u0627\u0632 \u062f\u0627\u062f\u0647\u200c\u0647\u0627 - \u0627\u0632 \u0627\u0631\u0627\u0626\u0647\u200c\u062f\u0647\u0646\u062f\u06af\u0627\u0646 \u062e\u062f\u0645\u0627\u062a \u0627\u0628\u0631\u06cc \u06af\u0631\u0641\u062a\u0647 \u062a\u0627 \u06a9\u0627\u0631\u0628\u0631\u0627\u0646 \u0634\u0631\u06a9\u062a\u06cc - \u0627\u0633\u062a\u0641\u0627\u062f\u0647 \u0645\u06cc\u200c\u0634\u0648\u062f. \u0627\u0632 \u062c\u0645\u0644\u0647 \u062f\u0631 \u0631\u0648\u0633\u06cc\u0647. \u0627\u06cc\u0646 \u0645\u062d\u0635\u0648\u0644 \u0628\u0627 \u0631\u0627\u0647\u06a9\u0627\u0631\u0647\u0627\u06cc \u067e\u0634\u062a\u06cc\u0628\u0627\u0646\u200c\u06af\u06cc\u0631\u06cc \u0645\u0627\u0646\u0646\u062f HPE Data Protector\u060c Veeam\u060c Commvault \u0648 Veritas NetBackup \u0627\u062f\u063a\u0627\u0645 \u0645\u06cc\u200c\u0634\u0648\u062f \u0648 \u0628\u0647 \u0639\u0646\u0648\u0627\u0646 \u06cc\u06a9 \u062c\u0632\u0621 \u06a9\u0644\u06cc\u062f\u06cc \u062f\u0631 \u0627\u0633\u062a\u0631\u0627\u062a\u0698\u06cc\u200c\u0647\u0627\u06cc \u062a\u062f\u0627\u0648\u0645 \u06a9\u0633\u0628\u200c\u0648\u06a9\u0627\u0631 \u0639\u0645\u0644 \u0645\u06cc\u200c\u06a9\u0646\u062f.\n\nHPE \u0647\u06cc\u0686 \u0631\u0627\u0647 \u062d\u0644 \u0645\u0648\u0642\u062a \u06cc\u0627 \u0627\u0642\u062f\u0627\u0645 \u0645\u0648\u0642\u062a\u06cc \u0628\u0631\u0627\u06cc \u0645\u062d\u0627\u0641\u0638\u062a \u062f\u0631 \u0628\u0631\u0627\u0628\u0631 \u0645\u0634\u06a9\u0644\u0627\u062a \u0634\u0646\u0627\u0633\u0627\u06cc\u06cc \u0634\u062f\u0647 \u0627\u0631\u0627\u0626\u0647 \u0646\u06a9\u0631\u062f\u0647 \u0627\u0633\u062a. \u062a\u0646\u0647\u0627 \u0631\u0627\u0647 \u0628\u0631\u0627\u06cc \u0628\u0633\u062a\u0646 \u0627\u06cc\u0646 \u0622\u0633\u06cc\u0628\u200c\u067e\u0630\u06cc\u0631\u06cc\u200c\u0647\u0627\u060c \u0646\u0633\u062e\u0647 \u0641\u0639\u0644\u06cc StoreOnce 4.3.11 \u0627\u0633\u062a. \u0628\u0631\u0627\u06cc \u0645\u062f\u06cc\u0631\u0627\u0646 \u0633\u06cc\u0633\u062a\u0645 \u06a9\u0647 \u0645\u062d\u06cc\u0637\u200c\u0647\u0627\u06cc \u0622\u0633\u06cc\u0628\u200c\u062f\u06cc\u062f\u0647 \u0631\u0627 \u0646\u06af\u0647\u062f\u0627\u0631\u06cc \u0645\u06cc\u200c\u06a9\u0646\u0646\u062f\u060c \u0627\u06cc\u0646 \u0628\u0647\u200c\u0631\u0648\u0632\u0631\u0633\u0627\u0646\u06cc \u062f\u0631 \u0627\u0648\u0644\u0648\u06cc\u062a \u0642\u0631\u0627\u0631 \u0645\u06cc\u200c\u06af\u06cc\u0631\u062f.\n\ud83c\udfed \u0648\u0628\u0633\u0627\u06cc\u062a \u0648 \u06a9\u0627\u0646\u0627\u0644 \u062a\u062e\u0635\u0635\u06cc \u0627\u0645\u0646\u06cc\u062a \u0632\u06cc\u0631\u0633\u0627\u062e\u062a\u0647\u0627\u06cc \u0627\u062a\u0648\u0645\u0627\u0633\u06cc\u0648\u0646 \u0648 \u06a9\u0646\u062a\u0631\u0644 \u0635\u0646\u0639\u062a\u06cc\n\ud83d\udc6e\ud83c\udffd\u200d\u2640\ufe0f\u0647\u0631\u06af\u0648\u0646\u0647 \u0627\u0646\u062a\u0634\u0627\u0631 \u0648 \u0630\u06a9\u0631 \u0645\u0637\u0627\u0644\u0628 \u0628\u062f\u0648\u0646 \u0630\u06a9\u0631 \u062f\u0642\u06cc\u0642 \u0645\u0646\u0628\u0639 \u0648 \u0622\u062f\u0631\u0633 \u0644\u06cc\u0646\u06a9 \u0622\u0646 \u0645\u0645\u0646\u0648\u0639 \u0627\u0633\u062a. \n\u0627\u062f\u0645\u06cc\u0646:\n\u200fhttps://t.me/pedram_kiani\n\u06a9\u0627\u0646\u0627\u0644 \u062a\u0644\u06af\u0631\u0627\u0645:\nhttps://t.me/ics_cert\n\u06af\u0631\u0648\u0647 \u0648\u0627\u062a\u0633 \u0622\u067e :\nhttps://chat.whatsapp.com/FpB620AWEeSKvd8U6cFh33\n\u06af\u0631\u0648\u0647 \u062a\u0644\u06af\u0631\u0627\u0645:\nhttps://t.me/ICSCERT_IR", "creation_timestamp": "2025-06-12T19:42:43.000000Z"}, {"uuid": "16ce85cf-2f7c-45a0-9d75-708ffb503a2f", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37091", "type": "seen", "source": "https://t.me/ics_cert/1191", "content": "\u0628\u062f\u0648\u0646 \u0646\u06cc\u0627\u0632 \u0628\u0647 \u0648\u0631\u0648\u062f - \u062f\u0633\u062a\u0631\u0633\u06cc \u06a9\u0627\u0645\u0644: StoreOnce \u0641\u0631\u0627\u0645\u0648\u0634 \u06a9\u0631\u062f \u06a9\u0647 \u062f\u0631\u0650 \u0627\u0631\u0632\u0634\u0645\u0646\u062f\u062a\u0631\u06cc\u0646\u200c\u0647\u0627 \u0631\u0627 \u0628\u0628\u0646\u062f\u062f\n\n\u062f\u0631 \u062d\u0627\u0644\u06cc \u06a9\u0647 \u0628\u0631\u062e\u06cc \u062f\u0631 \u062d\u0627\u0644 \u062a\u0647\u06cc\u0647 \u0646\u0633\u062e\u0647 \u067e\u0634\u062a\u06cc\u0628\u0627\u0646 \u0628\u0648\u062f\u0646\u062f\u060c \u0628\u0631\u062e\u06cc \u062f\u06cc\u06af\u0631 \u0628\u0647 \u062f\u0646\u0628\u0627\u0644 \u0631\u0627\u0647\u200c\u0647\u0627\u06cc\u06cc \u0628\u0631\u0627\u06cc \u0647\u06a9 \u06a9\u0631\u062f\u0646 \u0645\u062e\u0641\u06cc\u0627\u0646\u0647 \u0633\u06cc\u0633\u062a\u0645 \u0634\u062e\u0635 \u062f\u06cc\u06af\u0631\u06cc \u0628\u0648\u062f\u0646\u062f.\n\n\n\u0634\u0631\u06a9\u062a Hewlett Packard Enterprise \u062f\u0631 \u0631\u0627\u0628\u0637\u0647 \u0628\u0627 \u0647\u0634\u062a \u0622\u0633\u06cc\u0628\u200c\u067e\u0630\u06cc\u0631\u06cc \u062f\u0631 \u067e\u0644\u062a\u0641\u0631\u0645 \u0646\u0631\u0645\u200c\u0627\u0641\u0632\u0627\u0631\u06cc StoreOnce backup \u0648 data deduplication \u062e\u0648\u062f\u060c \u06cc\u06a9 \u0647\u0634\u062f\u0627\u0631 \u0627\u0645\u0646\u06cc\u062a\u06cc \u0641\u0648\u0631\u06cc \u0635\u0627\u062f\u0631 \u06a9\u0631\u062f\u0647 \u0627\u0633\u062a. \u062a\u0645\u0627\u0645 \u0622\u0633\u06cc\u0628\u200c\u067e\u0630\u06cc\u0631\u06cc\u200c\u0647\u0627 \u062f\u0631 \u0646\u0633\u062e\u0647 \u062c\u062f\u06cc\u062f \u0646\u0631\u0645\u200c\u0627\u0641\u0632\u0627\u0631\u060c StoreOnce 4.3.11\u060c \u06a9\u0647 \u0627\u06a9\u0646\u0648\u0646 \u0628\u0631\u0627\u06cc \u0647\u0645\u0647 \u06a9\u0627\u0631\u0628\u0631\u0627\u0646 \u062a\u0648\u0635\u06cc\u0647 \u0645\u06cc\u200c\u0634\u0648\u062f\u060c \u0628\u0631\u0637\u0631\u0641 \u0634\u062f\u0647\u200c\u0627\u0646\u062f.\n\n\u062e\u0637\u0631\u0646\u0627\u06a9\u200c\u062a\u0631\u06cc\u0646 \u0622\u0633\u06cc\u0628\u200c\u067e\u0630\u06cc\u0631\u06cc CVE-2025-37093 \u0627\u0633\u062a \u06a9\u0647 \u062f\u0631 \u0645\u0642\u06cc\u0627\u0633 CVSS \u0646\u0633\u062e\u0647 \u06f3.\u06f1 \u0627\u0645\u062a\u06cc\u0627\u0632 \u0628\u062d\u0631\u0627\u0646\u06cc \u06f9.\u06f8 \u0631\u0627 \u062f\u0631\u06cc\u0627\u0641\u062a \u06a9\u0631\u062f\u0647 \u0627\u0633\u062a. \u0627\u06cc\u0646 \u0622\u0633\u06cc\u0628\u200c\u067e\u0630\u06cc\u0631\u06cc \u0628\u0647 \u0645\u0647\u0627\u062c\u0645 \u0627\u062c\u0627\u0632\u0647 \u0645\u06cc\u200c\u062f\u0647\u062f \u062a\u0627 \u0628\u0647 \u062f\u0644\u06cc\u0644 \u062e\u0637\u0627\u06cc\u06cc \u062f\u0631 \u067e\u06cc\u0627\u062f\u0647\u200c\u0633\u0627\u0632\u06cc \u0631\u0648\u0634 machineAccountCheck\u060c \u0645\u06a9\u0627\u0646\u06cc\u0632\u0645 \u0627\u062d\u0631\u0627\u0632 \u0647\u0648\u06cc\u062a \u0631\u0627 \u062f\u0648\u0631 \u0628\u0632\u0646\u062f. \u0647\u0645\u0627\u0646\u0637\u0648\u0631 \u06a9\u0647 \u062a\u06cc\u0645 ZDI\u060c \u06a9\u0647 \u0627\u06cc\u0646 \u0627\u0634\u06a9\u0627\u0644 \u0631\u0627 \u0634\u0646\u0627\u0633\u0627\u06cc\u06cc \u06a9\u0631\u062f\u0647 \u0627\u0633\u062a\u060c \u062a\u0648\u0636\u06cc\u062d \u0645\u06cc\u200c\u062f\u0647\u062f\u060c \u0627\u0635\u0644 \u0645\u0634\u06a9\u0644 \u062f\u0631 \u0645\u0646\u0637\u0642 \u0627\u062d\u0631\u0627\u0632 \u0647\u0648\u06cc\u062a \u0646\u0627\u062f\u0631\u0633\u062a \u0646\u0647\u0641\u062a\u0647 \u0627\u0633\u062a - \u0645\u06cc\u200c\u062a\u0648\u0627\u0646 \u0622\u0646 \u0631\u0627 \u0628\u0647 \u0637\u0648\u0631 \u06a9\u0627\u0645\u0644 \u062f\u0648\u0631 \u0632\u062f \u0648 \u0631\u0627\u0647 \u0631\u0627 \u0628\u0631\u0627\u06cc \u0633\u0627\u06cc\u0631 \u0622\u0633\u06cc\u0628\u200c\u067e\u0630\u06cc\u0631\u06cc\u200c\u0647\u0627 \u0628\u0627\u0632 \u06a9\u0631\u062f.\n\n\u0641\u0647\u0631\u0633\u062a \u062a\u0645\u0627\u0645 \u0622\u0633\u06cc\u0628\u200c\u067e\u0630\u06cc\u0631\u06cc\u200c\u0647\u0627\u06cc \u0631\u0641\u0639\u200c\u0634\u062f\u0647 \u062f\u0631 \u0646\u0633\u062e\u0647 \u06f4.\u06f3.\u06f1\u06f1 \u0634\u0627\u0645\u0644 \u0645\u0648\u0627\u0631\u062f \u0632\u06cc\u0631 \u0627\u0633\u062a:\n\nCVE-2025-37089 - \u0627\u062c\u0631\u0627\u06cc \u06a9\u062f \u0627\u0632 \u0631\u0627\u0647 \u062f\u0648\u0631\u061b\nCVE-2025-37090 - \u062d\u0645\u0644\u0647 \u062c\u0639\u0644 \u062f\u0631\u062e\u0648\u0627\u0633\u062a \u0633\u0631\u0648\u0631 (SSRF)\u061b\nCVE-2025-37091 - \u0627\u062c\u0631\u0627\u06cc \u06a9\u062f \u0627\u0632 \u0631\u0627\u0647 \u062f\u0648\u0631\u061b\nCVE-2025-37092 - \u0627\u062c\u0631\u0627\u06cc \u06a9\u062f \u0627\u0632 \u0631\u0627\u0647 \u062f\u0648\u0631\u061b\nCVE-2025-37093 - \u062f\u0648\u0631 \u0632\u062f\u0646 \u0627\u062d\u0631\u0627\u0632 \u0647\u0648\u06cc\u062a (\u0628\u062d\u0631\u0627\u0646\u06cc)\u061b\nCVE-2025-37094 - \u062d\u0630\u0641 \u0641\u0627\u06cc\u0644\u200c\u0647\u0627\u06cc \u062f\u0644\u062e\u0648\u0627\u0647 \u0627\u0632 \u0637\u0631\u06cc\u0642 \u067e\u06cc\u0645\u0627\u06cc\u0634 \u062f\u0627\u06cc\u0631\u06a9\u062a\u0648\u0631\u06cc\u061b\nCVE-2025-37095 - \u0627\u0641\u0634\u0627\u06cc \u0627\u0637\u0644\u0627\u0639\u0627\u062a \u0627\u0632 \u0637\u0631\u06cc\u0642 \u067e\u06cc\u0645\u0627\u06cc\u0634 \u062f\u0627\u06cc\u0631\u06a9\u062a\u0648\u0631\u06cc\u061b\nCVE-2025-37096 - \u0627\u062c\u0631\u0627\u06cc \u06a9\u062f \u0627\u0632 \u0631\u0627\u0647 \u062f\u0648\u0631.\n\u0627\u06af\u0631\u0686\u0647 CVE-2025-37093 \u062a\u0646\u0647\u0627 \u0645\u0648\u0631\u062f\u06cc \u0627\u0633\u062a \u06a9\u0647 \u0631\u0633\u0645\u0627\u064b \u0628\u0647 \u0639\u0646\u0648\u0627\u0646 \u0628\u062d\u0631\u0627\u0646\u06cc \u0637\u0628\u0642\u0647\u200c\u0628\u0646\u062f\u06cc \u0634\u062f\u0647 \u0627\u0633\u062a\u060c \u06a9\u0627\u0631\u0634\u0646\u0627\u0633\u0627\u0646 \u062a\u0623\u06a9\u06cc\u062f \u0645\u06cc\u200c\u06a9\u0646\u0646\u062f \u06a9\u0647 \u0633\u0627\u06cc\u0631 \u0622\u0633\u06cc\u0628\u200c\u067e\u0630\u06cc\u0631\u06cc\u200c\u0647\u0627 \u0631\u0627 \u0646\u0628\u0627\u06cc\u062f \u062f\u0633\u062a \u06a9\u0645 \u06af\u0631\u0641\u062a. \u062e\u0637\u0631 \u062a\u0631\u06a9\u06cc\u0628\u06cc \u0622\u0646\u0647\u0627 \u062f\u0631 \u0635\u0648\u0631\u062a \u062f\u0648\u0631 \u0632\u062f\u0646 \u0645\u0648\u0641\u0642\u06cc\u062a\u200c\u0622\u0645\u06cc\u0632 \u0627\u062d\u0631\u0627\u0632 \u0647\u0648\u06cc\u062a \u0628\u0647 \u0637\u0648\u0631 \u0642\u0627\u0628\u0644 \u062a\u0648\u062c\u0647\u06cc \u0627\u0641\u0632\u0627\u06cc\u0634 \u0645\u06cc\u200c\u06cc\u0627\u0628\u062f. \u0627\u06cc\u0646 \u0627\u0645\u0631 \u062d\u062a\u06cc \u0622\u0633\u06cc\u0628\u200c\u067e\u0630\u06cc\u0631\u06cc\u200c\u0647\u0627\u06cc \u0628\u0627 \u062f\u0631\u062c\u0647 \u0645\u062a\u0648\u0633\u0637 \u200b\u200b\u0645\u0627\u0646\u0646\u062f CVE-2025-37094 \u0648 CVE-2025-37095 \u0631\u0627 \u0628\u0633\u06cc\u0627\u0631 \u062e\u0637\u0631\u0646\u0627\u06a9 \u0645\u06cc\u200c\u06a9\u0646\u062f - \u062d\u0630\u0641 \u0641\u0627\u06cc\u0644 \u0648 \u0646\u0634\u062a \u062f\u0627\u062f\u0647\u200c\u0647\u0627 \u0628\u062f\u0648\u0646 \u062a\u0644\u0627\u0634 \u0632\u06cc\u0627\u062f \u0627\u0645\u06a9\u0627\u0646\u200c\u067e\u0630\u06cc\u0631 \u0627\u0633\u062a.\n\n\u0637\u0628\u0642 \u06af\u0632\u0627\u0631\u0634 Zero Day Initiative\u060c StoreOnce \u0628\u06cc\u0634 \u0627\u0632 \u0634\u0634 \u0645\u0627\u0647 \u062f\u0631 \u0628\u0631\u0627\u0628\u0631 \u0627\u06cc\u0646 \u0622\u0633\u06cc\u0628\u200c\u067e\u0630\u06cc\u0631\u06cc\u200c\u0647\u0627 \u0622\u0633\u06cc\u0628\u200c\u067e\u0630\u06cc\u0631 \u0628\u0648\u062f\u0647 \u0627\u0633\u062a. \u06a9\u0627\u0631\u0634\u0646\u0627\u0633\u0627\u0646 \u0627\u06cc\u0646 \u0645\u0634\u06a9\u0644\u0627\u062a \u0631\u0627 \u062f\u0631 \u0627\u06a9\u062a\u0628\u0631 \u06f2\u06f0\u06f2\u06f4 \u06af\u0632\u0627\u0631\u0634 \u06a9\u0631\u062f\u0646\u062f\u060c \u0627\u0645\u0627 \u062d\u062f\u0648\u062f \u0647\u0641\u062a \u0645\u0627\u0647 \u0637\u0648\u0644 \u06a9\u0634\u06cc\u062f \u062a\u0627 \u0648\u0635\u0644\u0647\u200c\u0647\u0627 \u0645\u0646\u062a\u0634\u0631 \u0634\u0648\u0646\u062f. \u0628\u0627 \u0648\u062c\u0648\u062f \u0627\u06cc\u0646\u060c \u0647\u06cc\u0686 \u062a\u0623\u06cc\u06cc\u062f\u06cc \u0648\u062c\u0648\u062f \u0646\u062f\u0627\u0631\u062f \u06a9\u0647 \u0627\u06cc\u0646 \u0622\u0633\u06cc\u0628\u200c\u067e\u0630\u06cc\u0631\u06cc\u200c\u0647\u0627 \u0628\u0647 \u0637\u0648\u0631 \u0641\u0639\u0627\u0644 \u062f\u0631 \u062d\u0645\u0644\u0627\u062a \u0648\u0627\u0642\u0639\u06cc \u0645\u0648\u0631\u062f \u0633\u0648\u0621\u0627\u0633\u062a\u0641\u0627\u062f\u0647 \u0642\u0631\u0627\u0631 \u06af\u0631\u0641\u062a\u0647\u200c\u0627\u0646\u062f.\n\nStoreOnce \u062f\u0631 \u0632\u06cc\u0631\u0633\u0627\u062e\u062a\u200c\u0647\u0627\u06cc \u0628\u0632\u0631\u06af \u0641\u0646\u0627\u0648\u0631\u06cc \u0627\u0637\u0644\u0627\u0639\u0627\u062a\u060c \u0645\u0631\u0627\u06a9\u0632 \u062f\u0627\u062f\u0647 \u0648 \u0633\u0627\u0632\u0645\u0627\u0646\u200c\u0647\u0627\u06cc\u06cc \u0628\u0627 \u062d\u062c\u0645 \u0632\u06cc\u0627\u062f\u06cc \u0627\u0632 \u062f\u0627\u062f\u0647\u200c\u0647\u0627 - \u0627\u0632 \u0627\u0631\u0627\u0626\u0647\u200c\u062f\u0647\u0646\u062f\u06af\u0627\u0646 \u062e\u062f\u0645\u0627\u062a \u0627\u0628\u0631\u06cc \u06af\u0631\u0641\u062a\u0647 \u062a\u0627 \u06a9\u0627\u0631\u0628\u0631\u0627\u0646 \u0634\u0631\u06a9\u062a\u06cc - \u0627\u0633\u062a\u0641\u0627\u062f\u0647 \u0645\u06cc\u200c\u0634\u0648\u062f. \u0627\u0632 \u062c\u0645\u0644\u0647 \u062f\u0631 \u0631\u0648\u0633\u06cc\u0647. \u0627\u06cc\u0646 \u0645\u062d\u0635\u0648\u0644 \u0628\u0627 \u0631\u0627\u0647\u06a9\u0627\u0631\u0647\u0627\u06cc \u067e\u0634\u062a\u06cc\u0628\u0627\u0646\u200c\u06af\u06cc\u0631\u06cc \u0645\u0627\u0646\u0646\u062f HPE Data Protector\u060c Veeam\u060c Commvault \u0648 Veritas NetBackup \u0627\u062f\u063a\u0627\u0645 \u0645\u06cc\u200c\u0634\u0648\u062f \u0648 \u0628\u0647 \u0639\u0646\u0648\u0627\u0646 \u06cc\u06a9 \u062c\u0632\u0621 \u06a9\u0644\u06cc\u062f\u06cc \u062f\u0631 \u0627\u0633\u062a\u0631\u0627\u062a\u0698\u06cc\u200c\u0647\u0627\u06cc \u062a\u062f\u0627\u0648\u0645 \u06a9\u0633\u0628\u200c\u0648\u06a9\u0627\u0631 \u0639\u0645\u0644 \u0645\u06cc\u200c\u06a9\u0646\u062f.\n\nHPE \u0647\u06cc\u0686 \u0631\u0627\u0647 \u062d\u0644 \u0645\u0648\u0642\u062a \u06cc\u0627 \u0627\u0642\u062f\u0627\u0645 \u0645\u0648\u0642\u062a\u06cc \u0628\u0631\u0627\u06cc \u0645\u062d\u0627\u0641\u0638\u062a \u062f\u0631 \u0628\u0631\u0627\u0628\u0631 \u0645\u0634\u06a9\u0644\u0627\u062a \u0634\u0646\u0627\u0633\u0627\u06cc\u06cc \u0634\u062f\u0647 \u0627\u0631\u0627\u0626\u0647 \u0646\u06a9\u0631\u062f\u0647 \u0627\u0633\u062a. \u062a\u0646\u0647\u0627 \u0631\u0627\u0647 \u0628\u0631\u0627\u06cc \u0628\u0633\u062a\u0646 \u0627\u06cc\u0646 \u0622\u0633\u06cc\u0628\u200c\u067e\u0630\u06cc\u0631\u06cc\u200c\u0647\u0627\u060c \u0646\u0633\u062e\u0647 \u0641\u0639\u0644\u06cc StoreOnce 4.3.11 \u0627\u0633\u062a. \u0628\u0631\u0627\u06cc \u0645\u062f\u06cc\u0631\u0627\u0646 \u0633\u06cc\u0633\u062a\u0645 \u06a9\u0647 \u0645\u062d\u06cc\u0637\u200c\u0647\u0627\u06cc \u0622\u0633\u06cc\u0628\u200c\u062f\u06cc\u062f\u0647 \u0631\u0627 \u0646\u06af\u0647\u062f\u0627\u0631\u06cc \u0645\u06cc\u200c\u06a9\u0646\u0646\u062f\u060c \u0627\u06cc\u0646 \u0628\u0647\u200c\u0631\u0648\u0632\u0631\u0633\u0627\u0646\u06cc \u062f\u0631 \u0627\u0648\u0644\u0648\u06cc\u062a \u0642\u0631\u0627\u0631 \u0645\u06cc\u200c\u06af\u06cc\u0631\u062f.\n\ud83c\udfed \u0648\u0628\u0633\u0627\u06cc\u062a \u0648 \u06a9\u0627\u0646\u0627\u0644 \u062a\u062e\u0635\u0635\u06cc \u0627\u0645\u0646\u06cc\u062a \u0632\u06cc\u0631\u0633\u0627\u062e\u062a\u0647\u0627\u06cc \u0627\u062a\u0648\u0645\u0627\u0633\u06cc\u0648\u0646 \u0648 \u06a9\u0646\u062a\u0631\u0644 \u0635\u0646\u0639\u062a\u06cc\n\ud83d\udc6e\ud83c\udffd\u200d\u2640\ufe0f\u0647\u0631\u06af\u0648\u0646\u0647 \u0627\u0646\u062a\u0634\u0627\u0631 \u0648 \u0630\u06a9\u0631 \u0645\u0637\u0627\u0644\u0628 \u0628\u062f\u0648\u0646 \u0630\u06a9\u0631 \u062f\u0642\u06cc\u0642 \u0645\u0646\u0628\u0639 \u0648 \u0622\u062f\u0631\u0633 \u0644\u06cc\u0646\u06a9 \u0622\u0646 \u0645\u0645\u0646\u0648\u0639 \u0627\u0633\u062a. \n\u0627\u062f\u0645\u06cc\u0646:\n\u200fhttps://t.me/pedram_kiani\n\u06a9\u0627\u0646\u0627\u0644 \u062a\u0644\u06af\u0631\u0627\u0645:\nhttps://t.me/ics_cert\n\u06af\u0631\u0648\u0647 \u0648\u0627\u062a\u0633 \u0622\u067e :\nhttps://chat.whatsapp.com/FpB620AWEeSKvd8U6cFh33\n\u06af\u0631\u0648\u0647 \u062a\u0644\u06af\u0631\u0627\u0645:\nhttps://t.me/ICSCERT_IR", "creation_timestamp": "2025-06-12T19:42:43.000000Z"}, {"uuid": "19dedbb9-69b1-432f-9a55-cbd446b694df", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37089", "type": "seen", "source": "https://t.me/ics_cert/1191", "content": "\u0628\u062f\u0648\u0646 \u0646\u06cc\u0627\u0632 \u0628\u0647 \u0648\u0631\u0648\u062f - \u062f\u0633\u062a\u0631\u0633\u06cc \u06a9\u0627\u0645\u0644: StoreOnce \u0641\u0631\u0627\u0645\u0648\u0634 \u06a9\u0631\u062f \u06a9\u0647 \u062f\u0631\u0650 \u0627\u0631\u0632\u0634\u0645\u0646\u062f\u062a\u0631\u06cc\u0646\u200c\u0647\u0627 \u0631\u0627 \u0628\u0628\u0646\u062f\u062f\n\n\u062f\u0631 \u062d\u0627\u0644\u06cc \u06a9\u0647 \u0628\u0631\u062e\u06cc \u062f\u0631 \u062d\u0627\u0644 \u062a\u0647\u06cc\u0647 \u0646\u0633\u062e\u0647 \u067e\u0634\u062a\u06cc\u0628\u0627\u0646 \u0628\u0648\u062f\u0646\u062f\u060c \u0628\u0631\u062e\u06cc \u062f\u06cc\u06af\u0631 \u0628\u0647 \u062f\u0646\u0628\u0627\u0644 \u0631\u0627\u0647\u200c\u0647\u0627\u06cc\u06cc \u0628\u0631\u0627\u06cc \u0647\u06a9 \u06a9\u0631\u062f\u0646 \u0645\u062e\u0641\u06cc\u0627\u0646\u0647 \u0633\u06cc\u0633\u062a\u0645 \u0634\u062e\u0635 \u062f\u06cc\u06af\u0631\u06cc \u0628\u0648\u062f\u0646\u062f.\n\n\n\u0634\u0631\u06a9\u062a Hewlett Packard Enterprise \u062f\u0631 \u0631\u0627\u0628\u0637\u0647 \u0628\u0627 \u0647\u0634\u062a \u0622\u0633\u06cc\u0628\u200c\u067e\u0630\u06cc\u0631\u06cc \u062f\u0631 \u067e\u0644\u062a\u0641\u0631\u0645 \u0646\u0631\u0645\u200c\u0627\u0641\u0632\u0627\u0631\u06cc StoreOnce backup \u0648 data deduplication \u062e\u0648\u062f\u060c \u06cc\u06a9 \u0647\u0634\u062f\u0627\u0631 \u0627\u0645\u0646\u06cc\u062a\u06cc \u0641\u0648\u0631\u06cc \u0635\u0627\u062f\u0631 \u06a9\u0631\u062f\u0647 \u0627\u0633\u062a. \u062a\u0645\u0627\u0645 \u0622\u0633\u06cc\u0628\u200c\u067e\u0630\u06cc\u0631\u06cc\u200c\u0647\u0627 \u062f\u0631 \u0646\u0633\u062e\u0647 \u062c\u062f\u06cc\u062f \u0646\u0631\u0645\u200c\u0627\u0641\u0632\u0627\u0631\u060c StoreOnce 4.3.11\u060c \u06a9\u0647 \u0627\u06a9\u0646\u0648\u0646 \u0628\u0631\u0627\u06cc \u0647\u0645\u0647 \u06a9\u0627\u0631\u0628\u0631\u0627\u0646 \u062a\u0648\u0635\u06cc\u0647 \u0645\u06cc\u200c\u0634\u0648\u062f\u060c \u0628\u0631\u0637\u0631\u0641 \u0634\u062f\u0647\u200c\u0627\u0646\u062f.\n\n\u062e\u0637\u0631\u0646\u0627\u06a9\u200c\u062a\u0631\u06cc\u0646 \u0622\u0633\u06cc\u0628\u200c\u067e\u0630\u06cc\u0631\u06cc CVE-2025-37093 \u0627\u0633\u062a \u06a9\u0647 \u062f\u0631 \u0645\u0642\u06cc\u0627\u0633 CVSS \u0646\u0633\u062e\u0647 \u06f3.\u06f1 \u0627\u0645\u062a\u06cc\u0627\u0632 \u0628\u062d\u0631\u0627\u0646\u06cc \u06f9.\u06f8 \u0631\u0627 \u062f\u0631\u06cc\u0627\u0641\u062a \u06a9\u0631\u062f\u0647 \u0627\u0633\u062a. \u0627\u06cc\u0646 \u0622\u0633\u06cc\u0628\u200c\u067e\u0630\u06cc\u0631\u06cc \u0628\u0647 \u0645\u0647\u0627\u062c\u0645 \u0627\u062c\u0627\u0632\u0647 \u0645\u06cc\u200c\u062f\u0647\u062f \u062a\u0627 \u0628\u0647 \u062f\u0644\u06cc\u0644 \u062e\u0637\u0627\u06cc\u06cc \u062f\u0631 \u067e\u06cc\u0627\u062f\u0647\u200c\u0633\u0627\u0632\u06cc \u0631\u0648\u0634 machineAccountCheck\u060c \u0645\u06a9\u0627\u0646\u06cc\u0632\u0645 \u0627\u062d\u0631\u0627\u0632 \u0647\u0648\u06cc\u062a \u0631\u0627 \u062f\u0648\u0631 \u0628\u0632\u0646\u062f. \u0647\u0645\u0627\u0646\u0637\u0648\u0631 \u06a9\u0647 \u062a\u06cc\u0645 ZDI\u060c \u06a9\u0647 \u0627\u06cc\u0646 \u0627\u0634\u06a9\u0627\u0644 \u0631\u0627 \u0634\u0646\u0627\u0633\u0627\u06cc\u06cc \u06a9\u0631\u062f\u0647 \u0627\u0633\u062a\u060c \u062a\u0648\u0636\u06cc\u062d \u0645\u06cc\u200c\u062f\u0647\u062f\u060c \u0627\u0635\u0644 \u0645\u0634\u06a9\u0644 \u062f\u0631 \u0645\u0646\u0637\u0642 \u0627\u062d\u0631\u0627\u0632 \u0647\u0648\u06cc\u062a \u0646\u0627\u062f\u0631\u0633\u062a \u0646\u0647\u0641\u062a\u0647 \u0627\u0633\u062a - \u0645\u06cc\u200c\u062a\u0648\u0627\u0646 \u0622\u0646 \u0631\u0627 \u0628\u0647 \u0637\u0648\u0631 \u06a9\u0627\u0645\u0644 \u062f\u0648\u0631 \u0632\u062f \u0648 \u0631\u0627\u0647 \u0631\u0627 \u0628\u0631\u0627\u06cc \u0633\u0627\u06cc\u0631 \u0622\u0633\u06cc\u0628\u200c\u067e\u0630\u06cc\u0631\u06cc\u200c\u0647\u0627 \u0628\u0627\u0632 \u06a9\u0631\u062f.\n\n\u0641\u0647\u0631\u0633\u062a \u062a\u0645\u0627\u0645 \u0622\u0633\u06cc\u0628\u200c\u067e\u0630\u06cc\u0631\u06cc\u200c\u0647\u0627\u06cc \u0631\u0641\u0639\u200c\u0634\u062f\u0647 \u062f\u0631 \u0646\u0633\u062e\u0647 \u06f4.\u06f3.\u06f1\u06f1 \u0634\u0627\u0645\u0644 \u0645\u0648\u0627\u0631\u062f \u0632\u06cc\u0631 \u0627\u0633\u062a:\n\nCVE-2025-37089 - \u0627\u062c\u0631\u0627\u06cc \u06a9\u062f \u0627\u0632 \u0631\u0627\u0647 \u062f\u0648\u0631\u061b\nCVE-2025-37090 - \u062d\u0645\u0644\u0647 \u062c\u0639\u0644 \u062f\u0631\u062e\u0648\u0627\u0633\u062a \u0633\u0631\u0648\u0631 (SSRF)\u061b\nCVE-2025-37091 - \u0627\u062c\u0631\u0627\u06cc \u06a9\u062f \u0627\u0632 \u0631\u0627\u0647 \u062f\u0648\u0631\u061b\nCVE-2025-37092 - \u0627\u062c\u0631\u0627\u06cc \u06a9\u062f \u0627\u0632 \u0631\u0627\u0647 \u062f\u0648\u0631\u061b\nCVE-2025-37093 - \u062f\u0648\u0631 \u0632\u062f\u0646 \u0627\u062d\u0631\u0627\u0632 \u0647\u0648\u06cc\u062a (\u0628\u062d\u0631\u0627\u0646\u06cc)\u061b\nCVE-2025-37094 - \u062d\u0630\u0641 \u0641\u0627\u06cc\u0644\u200c\u0647\u0627\u06cc \u062f\u0644\u062e\u0648\u0627\u0647 \u0627\u0632 \u0637\u0631\u06cc\u0642 \u067e\u06cc\u0645\u0627\u06cc\u0634 \u062f\u0627\u06cc\u0631\u06a9\u062a\u0648\u0631\u06cc\u061b\nCVE-2025-37095 - \u0627\u0641\u0634\u0627\u06cc \u0627\u0637\u0644\u0627\u0639\u0627\u062a \u0627\u0632 \u0637\u0631\u06cc\u0642 \u067e\u06cc\u0645\u0627\u06cc\u0634 \u062f\u0627\u06cc\u0631\u06a9\u062a\u0648\u0631\u06cc\u061b\nCVE-2025-37096 - \u0627\u062c\u0631\u0627\u06cc \u06a9\u062f \u0627\u0632 \u0631\u0627\u0647 \u062f\u0648\u0631.\n\u0627\u06af\u0631\u0686\u0647 CVE-2025-37093 \u062a\u0646\u0647\u0627 \u0645\u0648\u0631\u062f\u06cc \u0627\u0633\u062a \u06a9\u0647 \u0631\u0633\u0645\u0627\u064b \u0628\u0647 \u0639\u0646\u0648\u0627\u0646 \u0628\u062d\u0631\u0627\u0646\u06cc \u0637\u0628\u0642\u0647\u200c\u0628\u0646\u062f\u06cc \u0634\u062f\u0647 \u0627\u0633\u062a\u060c \u06a9\u0627\u0631\u0634\u0646\u0627\u0633\u0627\u0646 \u062a\u0623\u06a9\u06cc\u062f \u0645\u06cc\u200c\u06a9\u0646\u0646\u062f \u06a9\u0647 \u0633\u0627\u06cc\u0631 \u0622\u0633\u06cc\u0628\u200c\u067e\u0630\u06cc\u0631\u06cc\u200c\u0647\u0627 \u0631\u0627 \u0646\u0628\u0627\u06cc\u062f \u062f\u0633\u062a \u06a9\u0645 \u06af\u0631\u0641\u062a. \u062e\u0637\u0631 \u062a\u0631\u06a9\u06cc\u0628\u06cc \u0622\u0646\u0647\u0627 \u062f\u0631 \u0635\u0648\u0631\u062a \u062f\u0648\u0631 \u0632\u062f\u0646 \u0645\u0648\u0641\u0642\u06cc\u062a\u200c\u0622\u0645\u06cc\u0632 \u0627\u062d\u0631\u0627\u0632 \u0647\u0648\u06cc\u062a \u0628\u0647 \u0637\u0648\u0631 \u0642\u0627\u0628\u0644 \u062a\u0648\u062c\u0647\u06cc \u0627\u0641\u0632\u0627\u06cc\u0634 \u0645\u06cc\u200c\u06cc\u0627\u0628\u062f. \u0627\u06cc\u0646 \u0627\u0645\u0631 \u062d\u062a\u06cc \u0622\u0633\u06cc\u0628\u200c\u067e\u0630\u06cc\u0631\u06cc\u200c\u0647\u0627\u06cc \u0628\u0627 \u062f\u0631\u062c\u0647 \u0645\u062a\u0648\u0633\u0637 \u200b\u200b\u0645\u0627\u0646\u0646\u062f CVE-2025-37094 \u0648 CVE-2025-37095 \u0631\u0627 \u0628\u0633\u06cc\u0627\u0631 \u062e\u0637\u0631\u0646\u0627\u06a9 \u0645\u06cc\u200c\u06a9\u0646\u062f - \u062d\u0630\u0641 \u0641\u0627\u06cc\u0644 \u0648 \u0646\u0634\u062a \u062f\u0627\u062f\u0647\u200c\u0647\u0627 \u0628\u062f\u0648\u0646 \u062a\u0644\u0627\u0634 \u0632\u06cc\u0627\u062f \u0627\u0645\u06a9\u0627\u0646\u200c\u067e\u0630\u06cc\u0631 \u0627\u0633\u062a.\n\n\u0637\u0628\u0642 \u06af\u0632\u0627\u0631\u0634 Zero Day Initiative\u060c StoreOnce \u0628\u06cc\u0634 \u0627\u0632 \u0634\u0634 \u0645\u0627\u0647 \u062f\u0631 \u0628\u0631\u0627\u0628\u0631 \u0627\u06cc\u0646 \u0622\u0633\u06cc\u0628\u200c\u067e\u0630\u06cc\u0631\u06cc\u200c\u0647\u0627 \u0622\u0633\u06cc\u0628\u200c\u067e\u0630\u06cc\u0631 \u0628\u0648\u062f\u0647 \u0627\u0633\u062a. \u06a9\u0627\u0631\u0634\u0646\u0627\u0633\u0627\u0646 \u0627\u06cc\u0646 \u0645\u0634\u06a9\u0644\u0627\u062a \u0631\u0627 \u062f\u0631 \u0627\u06a9\u062a\u0628\u0631 \u06f2\u06f0\u06f2\u06f4 \u06af\u0632\u0627\u0631\u0634 \u06a9\u0631\u062f\u0646\u062f\u060c \u0627\u0645\u0627 \u062d\u062f\u0648\u062f \u0647\u0641\u062a \u0645\u0627\u0647 \u0637\u0648\u0644 \u06a9\u0634\u06cc\u062f \u062a\u0627 \u0648\u0635\u0644\u0647\u200c\u0647\u0627 \u0645\u0646\u062a\u0634\u0631 \u0634\u0648\u0646\u062f. \u0628\u0627 \u0648\u062c\u0648\u062f \u0627\u06cc\u0646\u060c \u0647\u06cc\u0686 \u062a\u0623\u06cc\u06cc\u062f\u06cc \u0648\u062c\u0648\u062f \u0646\u062f\u0627\u0631\u062f \u06a9\u0647 \u0627\u06cc\u0646 \u0622\u0633\u06cc\u0628\u200c\u067e\u0630\u06cc\u0631\u06cc\u200c\u0647\u0627 \u0628\u0647 \u0637\u0648\u0631 \u0641\u0639\u0627\u0644 \u062f\u0631 \u062d\u0645\u0644\u0627\u062a \u0648\u0627\u0642\u0639\u06cc \u0645\u0648\u0631\u062f \u0633\u0648\u0621\u0627\u0633\u062a\u0641\u0627\u062f\u0647 \u0642\u0631\u0627\u0631 \u06af\u0631\u0641\u062a\u0647\u200c\u0627\u0646\u062f.\n\nStoreOnce \u062f\u0631 \u0632\u06cc\u0631\u0633\u0627\u062e\u062a\u200c\u0647\u0627\u06cc \u0628\u0632\u0631\u06af \u0641\u0646\u0627\u0648\u0631\u06cc \u0627\u0637\u0644\u0627\u0639\u0627\u062a\u060c \u0645\u0631\u0627\u06a9\u0632 \u062f\u0627\u062f\u0647 \u0648 \u0633\u0627\u0632\u0645\u0627\u0646\u200c\u0647\u0627\u06cc\u06cc \u0628\u0627 \u062d\u062c\u0645 \u0632\u06cc\u0627\u062f\u06cc \u0627\u0632 \u062f\u0627\u062f\u0647\u200c\u0647\u0627 - \u0627\u0632 \u0627\u0631\u0627\u0626\u0647\u200c\u062f\u0647\u0646\u062f\u06af\u0627\u0646 \u062e\u062f\u0645\u0627\u062a \u0627\u0628\u0631\u06cc \u06af\u0631\u0641\u062a\u0647 \u062a\u0627 \u06a9\u0627\u0631\u0628\u0631\u0627\u0646 \u0634\u0631\u06a9\u062a\u06cc - \u0627\u0633\u062a\u0641\u0627\u062f\u0647 \u0645\u06cc\u200c\u0634\u0648\u062f. \u0627\u0632 \u062c\u0645\u0644\u0647 \u062f\u0631 \u0631\u0648\u0633\u06cc\u0647. \u0627\u06cc\u0646 \u0645\u062d\u0635\u0648\u0644 \u0628\u0627 \u0631\u0627\u0647\u06a9\u0627\u0631\u0647\u0627\u06cc \u067e\u0634\u062a\u06cc\u0628\u0627\u0646\u200c\u06af\u06cc\u0631\u06cc \u0645\u0627\u0646\u0646\u062f HPE Data Protector\u060c Veeam\u060c Commvault \u0648 Veritas NetBackup \u0627\u062f\u063a\u0627\u0645 \u0645\u06cc\u200c\u0634\u0648\u062f \u0648 \u0628\u0647 \u0639\u0646\u0648\u0627\u0646 \u06cc\u06a9 \u062c\u0632\u0621 \u06a9\u0644\u06cc\u062f\u06cc \u062f\u0631 \u0627\u0633\u062a\u0631\u0627\u062a\u0698\u06cc\u200c\u0647\u0627\u06cc \u062a\u062f\u0627\u0648\u0645 \u06a9\u0633\u0628\u200c\u0648\u06a9\u0627\u0631 \u0639\u0645\u0644 \u0645\u06cc\u200c\u06a9\u0646\u062f.\n\nHPE \u0647\u06cc\u0686 \u0631\u0627\u0647 \u062d\u0644 \u0645\u0648\u0642\u062a \u06cc\u0627 \u0627\u0642\u062f\u0627\u0645 \u0645\u0648\u0642\u062a\u06cc \u0628\u0631\u0627\u06cc \u0645\u062d\u0627\u0641\u0638\u062a \u062f\u0631 \u0628\u0631\u0627\u0628\u0631 \u0645\u0634\u06a9\u0644\u0627\u062a \u0634\u0646\u0627\u0633\u0627\u06cc\u06cc \u0634\u062f\u0647 \u0627\u0631\u0627\u0626\u0647 \u0646\u06a9\u0631\u062f\u0647 \u0627\u0633\u062a. \u062a\u0646\u0647\u0627 \u0631\u0627\u0647 \u0628\u0631\u0627\u06cc \u0628\u0633\u062a\u0646 \u0627\u06cc\u0646 \u0622\u0633\u06cc\u0628\u200c\u067e\u0630\u06cc\u0631\u06cc\u200c\u0647\u0627\u060c \u0646\u0633\u062e\u0647 \u0641\u0639\u0644\u06cc StoreOnce 4.3.11 \u0627\u0633\u062a. \u0628\u0631\u0627\u06cc \u0645\u062f\u06cc\u0631\u0627\u0646 \u0633\u06cc\u0633\u062a\u0645 \u06a9\u0647 \u0645\u062d\u06cc\u0637\u200c\u0647\u0627\u06cc \u0622\u0633\u06cc\u0628\u200c\u062f\u06cc\u062f\u0647 \u0631\u0627 \u0646\u06af\u0647\u062f\u0627\u0631\u06cc \u0645\u06cc\u200c\u06a9\u0646\u0646\u062f\u060c \u0627\u06cc\u0646 \u0628\u0647\u200c\u0631\u0648\u0632\u0631\u0633\u0627\u0646\u06cc \u062f\u0631 \u0627\u0648\u0644\u0648\u06cc\u062a \u0642\u0631\u0627\u0631 \u0645\u06cc\u200c\u06af\u06cc\u0631\u062f.\n\ud83c\udfed \u0648\u0628\u0633\u0627\u06cc\u062a \u0648 \u06a9\u0627\u0646\u0627\u0644 \u062a\u062e\u0635\u0635\u06cc \u0627\u0645\u0646\u06cc\u062a \u0632\u06cc\u0631\u0633\u0627\u062e\u062a\u0647\u0627\u06cc \u0627\u062a\u0648\u0645\u0627\u0633\u06cc\u0648\u0646 \u0648 \u06a9\u0646\u062a\u0631\u0644 \u0635\u0646\u0639\u062a\u06cc\n\ud83d\udc6e\ud83c\udffd\u200d\u2640\ufe0f\u0647\u0631\u06af\u0648\u0646\u0647 \u0627\u0646\u062a\u0634\u0627\u0631 \u0648 \u0630\u06a9\u0631 \u0645\u0637\u0627\u0644\u0628 \u0628\u062f\u0648\u0646 \u0630\u06a9\u0631 \u062f\u0642\u06cc\u0642 \u0645\u0646\u0628\u0639 \u0648 \u0622\u062f\u0631\u0633 \u0644\u06cc\u0646\u06a9 \u0622\u0646 \u0645\u0645\u0646\u0648\u0639 \u0627\u0633\u062a. \n\u0627\u062f\u0645\u06cc\u0646:\n\u200fhttps://t.me/pedram_kiani\n\u06a9\u0627\u0646\u0627\u0644 \u062a\u0644\u06af\u0631\u0627\u0645:\nhttps://t.me/ics_cert\n\u06af\u0631\u0648\u0647 \u0648\u0627\u062a\u0633 \u0622\u067e :\nhttps://chat.whatsapp.com/FpB620AWEeSKvd8U6cFh33\n\u06af\u0631\u0648\u0647 \u062a\u0644\u06af\u0631\u0627\u0645:\nhttps://t.me/ICSCERT_IR", "creation_timestamp": "2025-06-12T19:42:43.000000Z"}, {"uuid": "3aa56baa-db2d-4b03-84b1-d5f60e6eecbd", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37096", "type": "seen", "source": "https://t.me/ics_cert/1191", "content": "\u0628\u062f\u0648\u0646 \u0646\u06cc\u0627\u0632 \u0628\u0647 \u0648\u0631\u0648\u062f - \u062f\u0633\u062a\u0631\u0633\u06cc \u06a9\u0627\u0645\u0644: StoreOnce \u0641\u0631\u0627\u0645\u0648\u0634 \u06a9\u0631\u062f \u06a9\u0647 \u062f\u0631\u0650 \u0627\u0631\u0632\u0634\u0645\u0646\u062f\u062a\u0631\u06cc\u0646\u200c\u0647\u0627 \u0631\u0627 \u0628\u0628\u0646\u062f\u062f\n\n\u062f\u0631 \u062d\u0627\u0644\u06cc \u06a9\u0647 \u0628\u0631\u062e\u06cc \u062f\u0631 \u062d\u0627\u0644 \u062a\u0647\u06cc\u0647 \u0646\u0633\u062e\u0647 \u067e\u0634\u062a\u06cc\u0628\u0627\u0646 \u0628\u0648\u062f\u0646\u062f\u060c \u0628\u0631\u062e\u06cc \u062f\u06cc\u06af\u0631 \u0628\u0647 \u062f\u0646\u0628\u0627\u0644 \u0631\u0627\u0647\u200c\u0647\u0627\u06cc\u06cc \u0628\u0631\u0627\u06cc \u0647\u06a9 \u06a9\u0631\u062f\u0646 \u0645\u062e\u0641\u06cc\u0627\u0646\u0647 \u0633\u06cc\u0633\u062a\u0645 \u0634\u062e\u0635 \u062f\u06cc\u06af\u0631\u06cc \u0628\u0648\u062f\u0646\u062f.\n\n\n\u0634\u0631\u06a9\u062a Hewlett Packard Enterprise \u062f\u0631 \u0631\u0627\u0628\u0637\u0647 \u0628\u0627 \u0647\u0634\u062a \u0622\u0633\u06cc\u0628\u200c\u067e\u0630\u06cc\u0631\u06cc \u062f\u0631 \u067e\u0644\u062a\u0641\u0631\u0645 \u0646\u0631\u0645\u200c\u0627\u0641\u0632\u0627\u0631\u06cc StoreOnce backup \u0648 data deduplication \u062e\u0648\u062f\u060c \u06cc\u06a9 \u0647\u0634\u062f\u0627\u0631 \u0627\u0645\u0646\u06cc\u062a\u06cc \u0641\u0648\u0631\u06cc \u0635\u0627\u062f\u0631 \u06a9\u0631\u062f\u0647 \u0627\u0633\u062a. \u062a\u0645\u0627\u0645 \u0622\u0633\u06cc\u0628\u200c\u067e\u0630\u06cc\u0631\u06cc\u200c\u0647\u0627 \u062f\u0631 \u0646\u0633\u062e\u0647 \u062c\u062f\u06cc\u062f \u0646\u0631\u0645\u200c\u0627\u0641\u0632\u0627\u0631\u060c StoreOnce 4.3.11\u060c \u06a9\u0647 \u0627\u06a9\u0646\u0648\u0646 \u0628\u0631\u0627\u06cc \u0647\u0645\u0647 \u06a9\u0627\u0631\u0628\u0631\u0627\u0646 \u062a\u0648\u0635\u06cc\u0647 \u0645\u06cc\u200c\u0634\u0648\u062f\u060c \u0628\u0631\u0637\u0631\u0641 \u0634\u062f\u0647\u200c\u0627\u0646\u062f.\n\n\u062e\u0637\u0631\u0646\u0627\u06a9\u200c\u062a\u0631\u06cc\u0646 \u0622\u0633\u06cc\u0628\u200c\u067e\u0630\u06cc\u0631\u06cc CVE-2025-37093 \u0627\u0633\u062a \u06a9\u0647 \u062f\u0631 \u0645\u0642\u06cc\u0627\u0633 CVSS \u0646\u0633\u062e\u0647 \u06f3.\u06f1 \u0627\u0645\u062a\u06cc\u0627\u0632 \u0628\u062d\u0631\u0627\u0646\u06cc \u06f9.\u06f8 \u0631\u0627 \u062f\u0631\u06cc\u0627\u0641\u062a \u06a9\u0631\u062f\u0647 \u0627\u0633\u062a. \u0627\u06cc\u0646 \u0622\u0633\u06cc\u0628\u200c\u067e\u0630\u06cc\u0631\u06cc \u0628\u0647 \u0645\u0647\u0627\u062c\u0645 \u0627\u062c\u0627\u0632\u0647 \u0645\u06cc\u200c\u062f\u0647\u062f \u062a\u0627 \u0628\u0647 \u062f\u0644\u06cc\u0644 \u062e\u0637\u0627\u06cc\u06cc \u062f\u0631 \u067e\u06cc\u0627\u062f\u0647\u200c\u0633\u0627\u0632\u06cc \u0631\u0648\u0634 machineAccountCheck\u060c \u0645\u06a9\u0627\u0646\u06cc\u0632\u0645 \u0627\u062d\u0631\u0627\u0632 \u0647\u0648\u06cc\u062a \u0631\u0627 \u062f\u0648\u0631 \u0628\u0632\u0646\u062f. \u0647\u0645\u0627\u0646\u0637\u0648\u0631 \u06a9\u0647 \u062a\u06cc\u0645 ZDI\u060c \u06a9\u0647 \u0627\u06cc\u0646 \u0627\u0634\u06a9\u0627\u0644 \u0631\u0627 \u0634\u0646\u0627\u0633\u0627\u06cc\u06cc \u06a9\u0631\u062f\u0647 \u0627\u0633\u062a\u060c \u062a\u0648\u0636\u06cc\u062d \u0645\u06cc\u200c\u062f\u0647\u062f\u060c \u0627\u0635\u0644 \u0645\u0634\u06a9\u0644 \u062f\u0631 \u0645\u0646\u0637\u0642 \u0627\u062d\u0631\u0627\u0632 \u0647\u0648\u06cc\u062a \u0646\u0627\u062f\u0631\u0633\u062a \u0646\u0647\u0641\u062a\u0647 \u0627\u0633\u062a - \u0645\u06cc\u200c\u062a\u0648\u0627\u0646 \u0622\u0646 \u0631\u0627 \u0628\u0647 \u0637\u0648\u0631 \u06a9\u0627\u0645\u0644 \u062f\u0648\u0631 \u0632\u062f \u0648 \u0631\u0627\u0647 \u0631\u0627 \u0628\u0631\u0627\u06cc \u0633\u0627\u06cc\u0631 \u0622\u0633\u06cc\u0628\u200c\u067e\u0630\u06cc\u0631\u06cc\u200c\u0647\u0627 \u0628\u0627\u0632 \u06a9\u0631\u062f.\n\n\u0641\u0647\u0631\u0633\u062a \u062a\u0645\u0627\u0645 \u0622\u0633\u06cc\u0628\u200c\u067e\u0630\u06cc\u0631\u06cc\u200c\u0647\u0627\u06cc \u0631\u0641\u0639\u200c\u0634\u062f\u0647 \u062f\u0631 \u0646\u0633\u062e\u0647 \u06f4.\u06f3.\u06f1\u06f1 \u0634\u0627\u0645\u0644 \u0645\u0648\u0627\u0631\u062f \u0632\u06cc\u0631 \u0627\u0633\u062a:\n\nCVE-2025-37089 - \u0627\u062c\u0631\u0627\u06cc \u06a9\u062f \u0627\u0632 \u0631\u0627\u0647 \u062f\u0648\u0631\u061b\nCVE-2025-37090 - \u062d\u0645\u0644\u0647 \u062c\u0639\u0644 \u062f\u0631\u062e\u0648\u0627\u0633\u062a \u0633\u0631\u0648\u0631 (SSRF)\u061b\nCVE-2025-37091 - \u0627\u062c\u0631\u0627\u06cc \u06a9\u062f \u0627\u0632 \u0631\u0627\u0647 \u062f\u0648\u0631\u061b\nCVE-2025-37092 - \u0627\u062c\u0631\u0627\u06cc \u06a9\u062f \u0627\u0632 \u0631\u0627\u0647 \u062f\u0648\u0631\u061b\nCVE-2025-37093 - \u062f\u0648\u0631 \u0632\u062f\u0646 \u0627\u062d\u0631\u0627\u0632 \u0647\u0648\u06cc\u062a (\u0628\u062d\u0631\u0627\u0646\u06cc)\u061b\nCVE-2025-37094 - \u062d\u0630\u0641 \u0641\u0627\u06cc\u0644\u200c\u0647\u0627\u06cc \u062f\u0644\u062e\u0648\u0627\u0647 \u0627\u0632 \u0637\u0631\u06cc\u0642 \u067e\u06cc\u0645\u0627\u06cc\u0634 \u062f\u0627\u06cc\u0631\u06a9\u062a\u0648\u0631\u06cc\u061b\nCVE-2025-37095 - \u0627\u0641\u0634\u0627\u06cc \u0627\u0637\u0644\u0627\u0639\u0627\u062a \u0627\u0632 \u0637\u0631\u06cc\u0642 \u067e\u06cc\u0645\u0627\u06cc\u0634 \u062f\u0627\u06cc\u0631\u06a9\u062a\u0648\u0631\u06cc\u061b\nCVE-2025-37096 - \u0627\u062c\u0631\u0627\u06cc \u06a9\u062f \u0627\u0632 \u0631\u0627\u0647 \u062f\u0648\u0631.\n\u0627\u06af\u0631\u0686\u0647 CVE-2025-37093 \u062a\u0646\u0647\u0627 \u0645\u0648\u0631\u062f\u06cc \u0627\u0633\u062a \u06a9\u0647 \u0631\u0633\u0645\u0627\u064b \u0628\u0647 \u0639\u0646\u0648\u0627\u0646 \u0628\u062d\u0631\u0627\u0646\u06cc \u0637\u0628\u0642\u0647\u200c\u0628\u0646\u062f\u06cc \u0634\u062f\u0647 \u0627\u0633\u062a\u060c \u06a9\u0627\u0631\u0634\u0646\u0627\u0633\u0627\u0646 \u062a\u0623\u06a9\u06cc\u062f \u0645\u06cc\u200c\u06a9\u0646\u0646\u062f \u06a9\u0647 \u0633\u0627\u06cc\u0631 \u0622\u0633\u06cc\u0628\u200c\u067e\u0630\u06cc\u0631\u06cc\u200c\u0647\u0627 \u0631\u0627 \u0646\u0628\u0627\u06cc\u062f \u062f\u0633\u062a \u06a9\u0645 \u06af\u0631\u0641\u062a. \u062e\u0637\u0631 \u062a\u0631\u06a9\u06cc\u0628\u06cc \u0622\u0646\u0647\u0627 \u062f\u0631 \u0635\u0648\u0631\u062a \u062f\u0648\u0631 \u0632\u062f\u0646 \u0645\u0648\u0641\u0642\u06cc\u062a\u200c\u0622\u0645\u06cc\u0632 \u0627\u062d\u0631\u0627\u0632 \u0647\u0648\u06cc\u062a \u0628\u0647 \u0637\u0648\u0631 \u0642\u0627\u0628\u0644 \u062a\u0648\u062c\u0647\u06cc \u0627\u0641\u0632\u0627\u06cc\u0634 \u0645\u06cc\u200c\u06cc\u0627\u0628\u062f. \u0627\u06cc\u0646 \u0627\u0645\u0631 \u062d\u062a\u06cc \u0622\u0633\u06cc\u0628\u200c\u067e\u0630\u06cc\u0631\u06cc\u200c\u0647\u0627\u06cc \u0628\u0627 \u062f\u0631\u062c\u0647 \u0645\u062a\u0648\u0633\u0637 \u200b\u200b\u0645\u0627\u0646\u0646\u062f CVE-2025-37094 \u0648 CVE-2025-37095 \u0631\u0627 \u0628\u0633\u06cc\u0627\u0631 \u062e\u0637\u0631\u0646\u0627\u06a9 \u0645\u06cc\u200c\u06a9\u0646\u062f - \u062d\u0630\u0641 \u0641\u0627\u06cc\u0644 \u0648 \u0646\u0634\u062a \u062f\u0627\u062f\u0647\u200c\u0647\u0627 \u0628\u062f\u0648\u0646 \u062a\u0644\u0627\u0634 \u0632\u06cc\u0627\u062f \u0627\u0645\u06a9\u0627\u0646\u200c\u067e\u0630\u06cc\u0631 \u0627\u0633\u062a.\n\n\u0637\u0628\u0642 \u06af\u0632\u0627\u0631\u0634 Zero Day Initiative\u060c StoreOnce \u0628\u06cc\u0634 \u0627\u0632 \u0634\u0634 \u0645\u0627\u0647 \u062f\u0631 \u0628\u0631\u0627\u0628\u0631 \u0627\u06cc\u0646 \u0622\u0633\u06cc\u0628\u200c\u067e\u0630\u06cc\u0631\u06cc\u200c\u0647\u0627 \u0622\u0633\u06cc\u0628\u200c\u067e\u0630\u06cc\u0631 \u0628\u0648\u062f\u0647 \u0627\u0633\u062a. \u06a9\u0627\u0631\u0634\u0646\u0627\u0633\u0627\u0646 \u0627\u06cc\u0646 \u0645\u0634\u06a9\u0644\u0627\u062a \u0631\u0627 \u062f\u0631 \u0627\u06a9\u062a\u0628\u0631 \u06f2\u06f0\u06f2\u06f4 \u06af\u0632\u0627\u0631\u0634 \u06a9\u0631\u062f\u0646\u062f\u060c \u0627\u0645\u0627 \u062d\u062f\u0648\u062f \u0647\u0641\u062a \u0645\u0627\u0647 \u0637\u0648\u0644 \u06a9\u0634\u06cc\u062f \u062a\u0627 \u0648\u0635\u0644\u0647\u200c\u0647\u0627 \u0645\u0646\u062a\u0634\u0631 \u0634\u0648\u0646\u062f. \u0628\u0627 \u0648\u062c\u0648\u062f \u0627\u06cc\u0646\u060c \u0647\u06cc\u0686 \u062a\u0623\u06cc\u06cc\u062f\u06cc \u0648\u062c\u0648\u062f \u0646\u062f\u0627\u0631\u062f \u06a9\u0647 \u0627\u06cc\u0646 \u0622\u0633\u06cc\u0628\u200c\u067e\u0630\u06cc\u0631\u06cc\u200c\u0647\u0627 \u0628\u0647 \u0637\u0648\u0631 \u0641\u0639\u0627\u0644 \u062f\u0631 \u062d\u0645\u0644\u0627\u062a \u0648\u0627\u0642\u0639\u06cc \u0645\u0648\u0631\u062f \u0633\u0648\u0621\u0627\u0633\u062a\u0641\u0627\u062f\u0647 \u0642\u0631\u0627\u0631 \u06af\u0631\u0641\u062a\u0647\u200c\u0627\u0646\u062f.\n\nStoreOnce \u062f\u0631 \u0632\u06cc\u0631\u0633\u0627\u062e\u062a\u200c\u0647\u0627\u06cc \u0628\u0632\u0631\u06af \u0641\u0646\u0627\u0648\u0631\u06cc \u0627\u0637\u0644\u0627\u0639\u0627\u062a\u060c \u0645\u0631\u0627\u06a9\u0632 \u062f\u0627\u062f\u0647 \u0648 \u0633\u0627\u0632\u0645\u0627\u0646\u200c\u0647\u0627\u06cc\u06cc \u0628\u0627 \u062d\u062c\u0645 \u0632\u06cc\u0627\u062f\u06cc \u0627\u0632 \u062f\u0627\u062f\u0647\u200c\u0647\u0627 - \u0627\u0632 \u0627\u0631\u0627\u0626\u0647\u200c\u062f\u0647\u0646\u062f\u06af\u0627\u0646 \u062e\u062f\u0645\u0627\u062a \u0627\u0628\u0631\u06cc \u06af\u0631\u0641\u062a\u0647 \u062a\u0627 \u06a9\u0627\u0631\u0628\u0631\u0627\u0646 \u0634\u0631\u06a9\u062a\u06cc - \u0627\u0633\u062a\u0641\u0627\u062f\u0647 \u0645\u06cc\u200c\u0634\u0648\u062f. \u0627\u0632 \u062c\u0645\u0644\u0647 \u062f\u0631 \u0631\u0648\u0633\u06cc\u0647. \u0627\u06cc\u0646 \u0645\u062d\u0635\u0648\u0644 \u0628\u0627 \u0631\u0627\u0647\u06a9\u0627\u0631\u0647\u0627\u06cc \u067e\u0634\u062a\u06cc\u0628\u0627\u0646\u200c\u06af\u06cc\u0631\u06cc \u0645\u0627\u0646\u0646\u062f HPE Data Protector\u060c Veeam\u060c Commvault \u0648 Veritas NetBackup \u0627\u062f\u063a\u0627\u0645 \u0645\u06cc\u200c\u0634\u0648\u062f \u0648 \u0628\u0647 \u0639\u0646\u0648\u0627\u0646 \u06cc\u06a9 \u062c\u0632\u0621 \u06a9\u0644\u06cc\u062f\u06cc \u062f\u0631 \u0627\u0633\u062a\u0631\u0627\u062a\u0698\u06cc\u200c\u0647\u0627\u06cc \u062a\u062f\u0627\u0648\u0645 \u06a9\u0633\u0628\u200c\u0648\u06a9\u0627\u0631 \u0639\u0645\u0644 \u0645\u06cc\u200c\u06a9\u0646\u062f.\n\nHPE \u0647\u06cc\u0686 \u0631\u0627\u0647 \u062d\u0644 \u0645\u0648\u0642\u062a \u06cc\u0627 \u0627\u0642\u062f\u0627\u0645 \u0645\u0648\u0642\u062a\u06cc \u0628\u0631\u0627\u06cc \u0645\u062d\u0627\u0641\u0638\u062a \u062f\u0631 \u0628\u0631\u0627\u0628\u0631 \u0645\u0634\u06a9\u0644\u0627\u062a \u0634\u0646\u0627\u0633\u0627\u06cc\u06cc \u0634\u062f\u0647 \u0627\u0631\u0627\u0626\u0647 \u0646\u06a9\u0631\u062f\u0647 \u0627\u0633\u062a. \u062a\u0646\u0647\u0627 \u0631\u0627\u0647 \u0628\u0631\u0627\u06cc \u0628\u0633\u062a\u0646 \u0627\u06cc\u0646 \u0622\u0633\u06cc\u0628\u200c\u067e\u0630\u06cc\u0631\u06cc\u200c\u0647\u0627\u060c \u0646\u0633\u062e\u0647 \u0641\u0639\u0644\u06cc StoreOnce 4.3.11 \u0627\u0633\u062a. \u0628\u0631\u0627\u06cc \u0645\u062f\u06cc\u0631\u0627\u0646 \u0633\u06cc\u0633\u062a\u0645 \u06a9\u0647 \u0645\u062d\u06cc\u0637\u200c\u0647\u0627\u06cc \u0622\u0633\u06cc\u0628\u200c\u062f\u06cc\u062f\u0647 \u0631\u0627 \u0646\u06af\u0647\u062f\u0627\u0631\u06cc \u0645\u06cc\u200c\u06a9\u0646\u0646\u062f\u060c \u0627\u06cc\u0646 \u0628\u0647\u200c\u0631\u0648\u0632\u0631\u0633\u0627\u0646\u06cc \u062f\u0631 \u0627\u0648\u0644\u0648\u06cc\u062a \u0642\u0631\u0627\u0631 \u0645\u06cc\u200c\u06af\u06cc\u0631\u062f.\n\ud83c\udfed \u0648\u0628\u0633\u0627\u06cc\u062a \u0648 \u06a9\u0627\u0646\u0627\u0644 \u062a\u062e\u0635\u0635\u06cc \u0627\u0645\u0646\u06cc\u062a \u0632\u06cc\u0631\u0633\u0627\u062e\u062a\u0647\u0627\u06cc \u0627\u062a\u0648\u0645\u0627\u0633\u06cc\u0648\u0646 \u0648 \u06a9\u0646\u062a\u0631\u0644 \u0635\u0646\u0639\u062a\u06cc\n\ud83d\udc6e\ud83c\udffd\u200d\u2640\ufe0f\u0647\u0631\u06af\u0648\u0646\u0647 \u0627\u0646\u062a\u0634\u0627\u0631 \u0648 \u0630\u06a9\u0631 \u0645\u0637\u0627\u0644\u0628 \u0628\u062f\u0648\u0646 \u0630\u06a9\u0631 \u062f\u0642\u06cc\u0642 \u0645\u0646\u0628\u0639 \u0648 \u0622\u062f\u0631\u0633 \u0644\u06cc\u0646\u06a9 \u0622\u0646 \u0645\u0645\u0646\u0648\u0639 \u0627\u0633\u062a. \n\u0627\u062f\u0645\u06cc\u0646:\n\u200fhttps://t.me/pedram_kiani\n\u06a9\u0627\u0646\u0627\u0644 \u062a\u0644\u06af\u0631\u0627\u0645:\nhttps://t.me/ics_cert\n\u06af\u0631\u0648\u0647 \u0648\u0627\u062a\u0633 \u0622\u067e :\nhttps://chat.whatsapp.com/FpB620AWEeSKvd8U6cFh33\n\u06af\u0631\u0648\u0647 \u062a\u0644\u06af\u0631\u0627\u0645:\nhttps://t.me/ICSCERT_IR", "creation_timestamp": "2025-06-12T19:42:43.000000Z"}, {"uuid": "595af721-9797-41f9-9e78-8ff15de6938d", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37093", "type": "seen", "source": "https://t.me/ics_cert/1191", "content": "\u0628\u062f\u0648\u0646 \u0646\u06cc\u0627\u0632 \u0628\u0647 \u0648\u0631\u0648\u062f - \u062f\u0633\u062a\u0631\u0633\u06cc \u06a9\u0627\u0645\u0644: StoreOnce \u0641\u0631\u0627\u0645\u0648\u0634 \u06a9\u0631\u062f \u06a9\u0647 \u062f\u0631\u0650 \u0627\u0631\u0632\u0634\u0645\u0646\u062f\u062a\u0631\u06cc\u0646\u200c\u0647\u0627 \u0631\u0627 \u0628\u0628\u0646\u062f\u062f\n\n\u062f\u0631 \u062d\u0627\u0644\u06cc \u06a9\u0647 \u0628\u0631\u062e\u06cc \u062f\u0631 \u062d\u0627\u0644 \u062a\u0647\u06cc\u0647 \u0646\u0633\u062e\u0647 \u067e\u0634\u062a\u06cc\u0628\u0627\u0646 \u0628\u0648\u062f\u0646\u062f\u060c \u0628\u0631\u062e\u06cc \u062f\u06cc\u06af\u0631 \u0628\u0647 \u062f\u0646\u0628\u0627\u0644 \u0631\u0627\u0647\u200c\u0647\u0627\u06cc\u06cc \u0628\u0631\u0627\u06cc \u0647\u06a9 \u06a9\u0631\u062f\u0646 \u0645\u062e\u0641\u06cc\u0627\u0646\u0647 \u0633\u06cc\u0633\u062a\u0645 \u0634\u062e\u0635 \u062f\u06cc\u06af\u0631\u06cc \u0628\u0648\u062f\u0646\u062f.\n\n\n\u0634\u0631\u06a9\u062a Hewlett Packard Enterprise \u062f\u0631 \u0631\u0627\u0628\u0637\u0647 \u0628\u0627 \u0647\u0634\u062a \u0622\u0633\u06cc\u0628\u200c\u067e\u0630\u06cc\u0631\u06cc \u062f\u0631 \u067e\u0644\u062a\u0641\u0631\u0645 \u0646\u0631\u0645\u200c\u0627\u0641\u0632\u0627\u0631\u06cc StoreOnce backup \u0648 data deduplication \u062e\u0648\u062f\u060c \u06cc\u06a9 \u0647\u0634\u062f\u0627\u0631 \u0627\u0645\u0646\u06cc\u062a\u06cc \u0641\u0648\u0631\u06cc \u0635\u0627\u062f\u0631 \u06a9\u0631\u062f\u0647 \u0627\u0633\u062a. \u062a\u0645\u0627\u0645 \u0622\u0633\u06cc\u0628\u200c\u067e\u0630\u06cc\u0631\u06cc\u200c\u0647\u0627 \u062f\u0631 \u0646\u0633\u062e\u0647 \u062c\u062f\u06cc\u062f \u0646\u0631\u0645\u200c\u0627\u0641\u0632\u0627\u0631\u060c StoreOnce 4.3.11\u060c \u06a9\u0647 \u0627\u06a9\u0646\u0648\u0646 \u0628\u0631\u0627\u06cc \u0647\u0645\u0647 \u06a9\u0627\u0631\u0628\u0631\u0627\u0646 \u062a\u0648\u0635\u06cc\u0647 \u0645\u06cc\u200c\u0634\u0648\u062f\u060c \u0628\u0631\u0637\u0631\u0641 \u0634\u062f\u0647\u200c\u0627\u0646\u062f.\n\n\u062e\u0637\u0631\u0646\u0627\u06a9\u200c\u062a\u0631\u06cc\u0646 \u0622\u0633\u06cc\u0628\u200c\u067e\u0630\u06cc\u0631\u06cc CVE-2025-37093 \u0627\u0633\u062a \u06a9\u0647 \u062f\u0631 \u0645\u0642\u06cc\u0627\u0633 CVSS \u0646\u0633\u062e\u0647 \u06f3.\u06f1 \u0627\u0645\u062a\u06cc\u0627\u0632 \u0628\u062d\u0631\u0627\u0646\u06cc \u06f9.\u06f8 \u0631\u0627 \u062f\u0631\u06cc\u0627\u0641\u062a \u06a9\u0631\u062f\u0647 \u0627\u0633\u062a. \u0627\u06cc\u0646 \u0622\u0633\u06cc\u0628\u200c\u067e\u0630\u06cc\u0631\u06cc \u0628\u0647 \u0645\u0647\u0627\u062c\u0645 \u0627\u062c\u0627\u0632\u0647 \u0645\u06cc\u200c\u062f\u0647\u062f \u062a\u0627 \u0628\u0647 \u062f\u0644\u06cc\u0644 \u062e\u0637\u0627\u06cc\u06cc \u062f\u0631 \u067e\u06cc\u0627\u062f\u0647\u200c\u0633\u0627\u0632\u06cc \u0631\u0648\u0634 machineAccountCheck\u060c \u0645\u06a9\u0627\u0646\u06cc\u0632\u0645 \u0627\u062d\u0631\u0627\u0632 \u0647\u0648\u06cc\u062a \u0631\u0627 \u062f\u0648\u0631 \u0628\u0632\u0646\u062f. \u0647\u0645\u0627\u0646\u0637\u0648\u0631 \u06a9\u0647 \u062a\u06cc\u0645 ZDI\u060c \u06a9\u0647 \u0627\u06cc\u0646 \u0627\u0634\u06a9\u0627\u0644 \u0631\u0627 \u0634\u0646\u0627\u0633\u0627\u06cc\u06cc \u06a9\u0631\u062f\u0647 \u0627\u0633\u062a\u060c \u062a\u0648\u0636\u06cc\u062d \u0645\u06cc\u200c\u062f\u0647\u062f\u060c \u0627\u0635\u0644 \u0645\u0634\u06a9\u0644 \u062f\u0631 \u0645\u0646\u0637\u0642 \u0627\u062d\u0631\u0627\u0632 \u0647\u0648\u06cc\u062a \u0646\u0627\u062f\u0631\u0633\u062a \u0646\u0647\u0641\u062a\u0647 \u0627\u0633\u062a - \u0645\u06cc\u200c\u062a\u0648\u0627\u0646 \u0622\u0646 \u0631\u0627 \u0628\u0647 \u0637\u0648\u0631 \u06a9\u0627\u0645\u0644 \u062f\u0648\u0631 \u0632\u062f \u0648 \u0631\u0627\u0647 \u0631\u0627 \u0628\u0631\u0627\u06cc \u0633\u0627\u06cc\u0631 \u0622\u0633\u06cc\u0628\u200c\u067e\u0630\u06cc\u0631\u06cc\u200c\u0647\u0627 \u0628\u0627\u0632 \u06a9\u0631\u062f.\n\n\u0641\u0647\u0631\u0633\u062a \u062a\u0645\u0627\u0645 \u0622\u0633\u06cc\u0628\u200c\u067e\u0630\u06cc\u0631\u06cc\u200c\u0647\u0627\u06cc \u0631\u0641\u0639\u200c\u0634\u062f\u0647 \u062f\u0631 \u0646\u0633\u062e\u0647 \u06f4.\u06f3.\u06f1\u06f1 \u0634\u0627\u0645\u0644 \u0645\u0648\u0627\u0631\u062f \u0632\u06cc\u0631 \u0627\u0633\u062a:\n\nCVE-2025-37089 - \u0627\u062c\u0631\u0627\u06cc \u06a9\u062f \u0627\u0632 \u0631\u0627\u0647 \u062f\u0648\u0631\u061b\nCVE-2025-37090 - \u062d\u0645\u0644\u0647 \u062c\u0639\u0644 \u062f\u0631\u062e\u0648\u0627\u0633\u062a \u0633\u0631\u0648\u0631 (SSRF)\u061b\nCVE-2025-37091 - \u0627\u062c\u0631\u0627\u06cc \u06a9\u062f \u0627\u0632 \u0631\u0627\u0647 \u062f\u0648\u0631\u061b\nCVE-2025-37092 - \u0627\u062c\u0631\u0627\u06cc \u06a9\u062f \u0627\u0632 \u0631\u0627\u0647 \u062f\u0648\u0631\u061b\nCVE-2025-37093 - \u062f\u0648\u0631 \u0632\u062f\u0646 \u0627\u062d\u0631\u0627\u0632 \u0647\u0648\u06cc\u062a (\u0628\u062d\u0631\u0627\u0646\u06cc)\u061b\nCVE-2025-37094 - \u062d\u0630\u0641 \u0641\u0627\u06cc\u0644\u200c\u0647\u0627\u06cc \u062f\u0644\u062e\u0648\u0627\u0647 \u0627\u0632 \u0637\u0631\u06cc\u0642 \u067e\u06cc\u0645\u0627\u06cc\u0634 \u062f\u0627\u06cc\u0631\u06a9\u062a\u0648\u0631\u06cc\u061b\nCVE-2025-37095 - \u0627\u0641\u0634\u0627\u06cc \u0627\u0637\u0644\u0627\u0639\u0627\u062a \u0627\u0632 \u0637\u0631\u06cc\u0642 \u067e\u06cc\u0645\u0627\u06cc\u0634 \u062f\u0627\u06cc\u0631\u06a9\u062a\u0648\u0631\u06cc\u061b\nCVE-2025-37096 - \u0627\u062c\u0631\u0627\u06cc \u06a9\u062f \u0627\u0632 \u0631\u0627\u0647 \u062f\u0648\u0631.\n\u0627\u06af\u0631\u0686\u0647 CVE-2025-37093 \u062a\u0646\u0647\u0627 \u0645\u0648\u0631\u062f\u06cc \u0627\u0633\u062a \u06a9\u0647 \u0631\u0633\u0645\u0627\u064b \u0628\u0647 \u0639\u0646\u0648\u0627\u0646 \u0628\u062d\u0631\u0627\u0646\u06cc \u0637\u0628\u0642\u0647\u200c\u0628\u0646\u062f\u06cc \u0634\u062f\u0647 \u0627\u0633\u062a\u060c \u06a9\u0627\u0631\u0634\u0646\u0627\u0633\u0627\u0646 \u062a\u0623\u06a9\u06cc\u062f \u0645\u06cc\u200c\u06a9\u0646\u0646\u062f \u06a9\u0647 \u0633\u0627\u06cc\u0631 \u0622\u0633\u06cc\u0628\u200c\u067e\u0630\u06cc\u0631\u06cc\u200c\u0647\u0627 \u0631\u0627 \u0646\u0628\u0627\u06cc\u062f \u062f\u0633\u062a \u06a9\u0645 \u06af\u0631\u0641\u062a. \u062e\u0637\u0631 \u062a\u0631\u06a9\u06cc\u0628\u06cc \u0622\u0646\u0647\u0627 \u062f\u0631 \u0635\u0648\u0631\u062a \u062f\u0648\u0631 \u0632\u062f\u0646 \u0645\u0648\u0641\u0642\u06cc\u062a\u200c\u0622\u0645\u06cc\u0632 \u0627\u062d\u0631\u0627\u0632 \u0647\u0648\u06cc\u062a \u0628\u0647 \u0637\u0648\u0631 \u0642\u0627\u0628\u0644 \u062a\u0648\u062c\u0647\u06cc \u0627\u0641\u0632\u0627\u06cc\u0634 \u0645\u06cc\u200c\u06cc\u0627\u0628\u062f. \u0627\u06cc\u0646 \u0627\u0645\u0631 \u062d\u062a\u06cc \u0622\u0633\u06cc\u0628\u200c\u067e\u0630\u06cc\u0631\u06cc\u200c\u0647\u0627\u06cc \u0628\u0627 \u062f\u0631\u062c\u0647 \u0645\u062a\u0648\u0633\u0637 \u200b\u200b\u0645\u0627\u0646\u0646\u062f CVE-2025-37094 \u0648 CVE-2025-37095 \u0631\u0627 \u0628\u0633\u06cc\u0627\u0631 \u062e\u0637\u0631\u0646\u0627\u06a9 \u0645\u06cc\u200c\u06a9\u0646\u062f - \u062d\u0630\u0641 \u0641\u0627\u06cc\u0644 \u0648 \u0646\u0634\u062a \u062f\u0627\u062f\u0647\u200c\u0647\u0627 \u0628\u062f\u0648\u0646 \u062a\u0644\u0627\u0634 \u0632\u06cc\u0627\u062f \u0627\u0645\u06a9\u0627\u0646\u200c\u067e\u0630\u06cc\u0631 \u0627\u0633\u062a.\n\n\u0637\u0628\u0642 \u06af\u0632\u0627\u0631\u0634 Zero Day Initiative\u060c StoreOnce \u0628\u06cc\u0634 \u0627\u0632 \u0634\u0634 \u0645\u0627\u0647 \u062f\u0631 \u0628\u0631\u0627\u0628\u0631 \u0627\u06cc\u0646 \u0622\u0633\u06cc\u0628\u200c\u067e\u0630\u06cc\u0631\u06cc\u200c\u0647\u0627 \u0622\u0633\u06cc\u0628\u200c\u067e\u0630\u06cc\u0631 \u0628\u0648\u062f\u0647 \u0627\u0633\u062a. \u06a9\u0627\u0631\u0634\u0646\u0627\u0633\u0627\u0646 \u0627\u06cc\u0646 \u0645\u0634\u06a9\u0644\u0627\u062a \u0631\u0627 \u062f\u0631 \u0627\u06a9\u062a\u0628\u0631 \u06f2\u06f0\u06f2\u06f4 \u06af\u0632\u0627\u0631\u0634 \u06a9\u0631\u062f\u0646\u062f\u060c \u0627\u0645\u0627 \u062d\u062f\u0648\u062f \u0647\u0641\u062a \u0645\u0627\u0647 \u0637\u0648\u0644 \u06a9\u0634\u06cc\u062f \u062a\u0627 \u0648\u0635\u0644\u0647\u200c\u0647\u0627 \u0645\u0646\u062a\u0634\u0631 \u0634\u0648\u0646\u062f. \u0628\u0627 \u0648\u062c\u0648\u062f \u0627\u06cc\u0646\u060c \u0647\u06cc\u0686 \u062a\u0623\u06cc\u06cc\u062f\u06cc \u0648\u062c\u0648\u062f \u0646\u062f\u0627\u0631\u062f \u06a9\u0647 \u0627\u06cc\u0646 \u0622\u0633\u06cc\u0628\u200c\u067e\u0630\u06cc\u0631\u06cc\u200c\u0647\u0627 \u0628\u0647 \u0637\u0648\u0631 \u0641\u0639\u0627\u0644 \u062f\u0631 \u062d\u0645\u0644\u0627\u062a \u0648\u0627\u0642\u0639\u06cc \u0645\u0648\u0631\u062f \u0633\u0648\u0621\u0627\u0633\u062a\u0641\u0627\u062f\u0647 \u0642\u0631\u0627\u0631 \u06af\u0631\u0641\u062a\u0647\u200c\u0627\u0646\u062f.\n\nStoreOnce \u062f\u0631 \u0632\u06cc\u0631\u0633\u0627\u062e\u062a\u200c\u0647\u0627\u06cc \u0628\u0632\u0631\u06af \u0641\u0646\u0627\u0648\u0631\u06cc \u0627\u0637\u0644\u0627\u0639\u0627\u062a\u060c \u0645\u0631\u0627\u06a9\u0632 \u062f\u0627\u062f\u0647 \u0648 \u0633\u0627\u0632\u0645\u0627\u0646\u200c\u0647\u0627\u06cc\u06cc \u0628\u0627 \u062d\u062c\u0645 \u0632\u06cc\u0627\u062f\u06cc \u0627\u0632 \u062f\u0627\u062f\u0647\u200c\u0647\u0627 - \u0627\u0632 \u0627\u0631\u0627\u0626\u0647\u200c\u062f\u0647\u0646\u062f\u06af\u0627\u0646 \u062e\u062f\u0645\u0627\u062a \u0627\u0628\u0631\u06cc \u06af\u0631\u0641\u062a\u0647 \u062a\u0627 \u06a9\u0627\u0631\u0628\u0631\u0627\u0646 \u0634\u0631\u06a9\u062a\u06cc - \u0627\u0633\u062a\u0641\u0627\u062f\u0647 \u0645\u06cc\u200c\u0634\u0648\u062f. \u0627\u0632 \u062c\u0645\u0644\u0647 \u062f\u0631 \u0631\u0648\u0633\u06cc\u0647. \u0627\u06cc\u0646 \u0645\u062d\u0635\u0648\u0644 \u0628\u0627 \u0631\u0627\u0647\u06a9\u0627\u0631\u0647\u0627\u06cc \u067e\u0634\u062a\u06cc\u0628\u0627\u0646\u200c\u06af\u06cc\u0631\u06cc \u0645\u0627\u0646\u0646\u062f HPE Data Protector\u060c Veeam\u060c Commvault \u0648 Veritas NetBackup \u0627\u062f\u063a\u0627\u0645 \u0645\u06cc\u200c\u0634\u0648\u062f \u0648 \u0628\u0647 \u0639\u0646\u0648\u0627\u0646 \u06cc\u06a9 \u062c\u0632\u0621 \u06a9\u0644\u06cc\u062f\u06cc \u062f\u0631 \u0627\u0633\u062a\u0631\u0627\u062a\u0698\u06cc\u200c\u0647\u0627\u06cc \u062a\u062f\u0627\u0648\u0645 \u06a9\u0633\u0628\u200c\u0648\u06a9\u0627\u0631 \u0639\u0645\u0644 \u0645\u06cc\u200c\u06a9\u0646\u062f.\n\nHPE \u0647\u06cc\u0686 \u0631\u0627\u0647 \u062d\u0644 \u0645\u0648\u0642\u062a \u06cc\u0627 \u0627\u0642\u062f\u0627\u0645 \u0645\u0648\u0642\u062a\u06cc \u0628\u0631\u0627\u06cc \u0645\u062d\u0627\u0641\u0638\u062a \u062f\u0631 \u0628\u0631\u0627\u0628\u0631 \u0645\u0634\u06a9\u0644\u0627\u062a \u0634\u0646\u0627\u0633\u0627\u06cc\u06cc \u0634\u062f\u0647 \u0627\u0631\u0627\u0626\u0647 \u0646\u06a9\u0631\u062f\u0647 \u0627\u0633\u062a. \u062a\u0646\u0647\u0627 \u0631\u0627\u0647 \u0628\u0631\u0627\u06cc \u0628\u0633\u062a\u0646 \u0627\u06cc\u0646 \u0622\u0633\u06cc\u0628\u200c\u067e\u0630\u06cc\u0631\u06cc\u200c\u0647\u0627\u060c \u0646\u0633\u062e\u0647 \u0641\u0639\u0644\u06cc StoreOnce 4.3.11 \u0627\u0633\u062a. \u0628\u0631\u0627\u06cc \u0645\u062f\u06cc\u0631\u0627\u0646 \u0633\u06cc\u0633\u062a\u0645 \u06a9\u0647 \u0645\u062d\u06cc\u0637\u200c\u0647\u0627\u06cc \u0622\u0633\u06cc\u0628\u200c\u062f\u06cc\u062f\u0647 \u0631\u0627 \u0646\u06af\u0647\u062f\u0627\u0631\u06cc \u0645\u06cc\u200c\u06a9\u0646\u0646\u062f\u060c \u0627\u06cc\u0646 \u0628\u0647\u200c\u0631\u0648\u0632\u0631\u0633\u0627\u0646\u06cc \u062f\u0631 \u0627\u0648\u0644\u0648\u06cc\u062a \u0642\u0631\u0627\u0631 \u0645\u06cc\u200c\u06af\u06cc\u0631\u062f.\n\ud83c\udfed \u0648\u0628\u0633\u0627\u06cc\u062a \u0648 \u06a9\u0627\u0646\u0627\u0644 \u062a\u062e\u0635\u0635\u06cc \u0627\u0645\u0646\u06cc\u062a \u0632\u06cc\u0631\u0633\u0627\u062e\u062a\u0647\u0627\u06cc \u0627\u062a\u0648\u0645\u0627\u0633\u06cc\u0648\u0646 \u0648 \u06a9\u0646\u062a\u0631\u0644 \u0635\u0646\u0639\u062a\u06cc\n\ud83d\udc6e\ud83c\udffd\u200d\u2640\ufe0f\u0647\u0631\u06af\u0648\u0646\u0647 \u0627\u0646\u062a\u0634\u0627\u0631 \u0648 \u0630\u06a9\u0631 \u0645\u0637\u0627\u0644\u0628 \u0628\u062f\u0648\u0646 \u0630\u06a9\u0631 \u062f\u0642\u06cc\u0642 \u0645\u0646\u0628\u0639 \u0648 \u0622\u062f\u0631\u0633 \u0644\u06cc\u0646\u06a9 \u0622\u0646 \u0645\u0645\u0646\u0648\u0639 \u0627\u0633\u062a. \n\u0627\u062f\u0645\u06cc\u0646:\n\u200fhttps://t.me/pedram_kiani\n\u06a9\u0627\u0646\u0627\u0644 \u062a\u0644\u06af\u0631\u0627\u0645:\nhttps://t.me/ics_cert\n\u06af\u0631\u0648\u0647 \u0648\u0627\u062a\u0633 \u0622\u067e :\nhttps://chat.whatsapp.com/FpB620AWEeSKvd8U6cFh33\n\u06af\u0631\u0648\u0647 \u062a\u0644\u06af\u0631\u0627\u0645:\nhttps://t.me/ICSCERT_IR", "creation_timestamp": "2025-06-12T19:42:43.000000Z"}, {"uuid": "379d638f-775c-4f9a-9fd8-9410f044695a", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37093", "type": "seen", "source": "https://t.me/ics_cert/1190", "content": "\u0648\u0642\u062a\u06cc \u0628\u0647\u200c\u0631\u0648\u0632\u0631\u0633\u0627\u0646\u06cc \u0627\u0632 \u067e\u0634\u062a\u06cc\u0628\u0627\u0646\u200c\u06af\u06cc\u0631\u06cc \u0645\u0647\u0645\u200c\u062a\u0631 \u0627\u0633\u062a\n\n\ud83d\udccd \u0622\u0633\u06cc\u0628\u200c\u067e\u0630\u06cc\u0631\u06cc StoreOnce \u06cc\u06a9 \u06cc\u0627\u062f\u0622\u0648\u0631\u06cc \u0627\u0633\u062a: \u0627\u0645\u0646\u06cc\u062a \u06cc\u06a9 \u0633\u06cc\u0633\u062a\u0645 \u0630\u062e\u06cc\u0631\u0647\u200c\u0633\u0627\u0632\u06cc \u062f\u0627\u062f\u0647 \u0628\u0647 \u0627\u0646\u062f\u0627\u0632\u0647 \u0642\u0627\u0628\u0644\u06cc\u062a \u0627\u0637\u0645\u06cc\u0646\u0627\u0646 \u0622\u0646 \u0645\u0647\u0645 \u0627\u0633\u062a. CVE-2025-37093 \u0646\u0634\u0627\u0646 \u0645\u06cc\u200c\u062f\u0647\u062f \u06a9\u0647 \u0686\u06af\u0648\u0646\u0647 \u06cc\u06a9 \u0622\u0633\u06cc\u0628\u200c\u067e\u0630\u06cc\u0631\u06cc \u062f\u0631 \u0633\u0637\u062d \u0627\u062d\u0631\u0627\u0632 \u0647\u0648\u06cc\u062a\u060c \u06cc\u06a9 \u0627\u0628\u0632\u0627\u0631 \u067e\u0634\u062a\u06cc\u0628\u0627\u0646\u200c\u06af\u06cc\u0631\u06cc \u0631\u0627 \u0628\u0647 \u062c\u0627\u06cc \u0645\u062d\u0627\u0641\u0638\u062a\u060c \u0628\u0647 \u06cc\u06a9 \u0646\u0642\u0637\u0647 \u062e\u0637\u0631 \u062a\u0628\u062f\u06cc\u0644 \u0645\u06cc\u200c\u06a9\u0646\u062f. \u0628\u0647 \u062e\u0635\u0648\u0635 \u0648\u0642\u062a\u06cc \u0635\u062d\u0628\u062a \u0627\u0632 \u067e\u0644\u062a\u0641\u0631\u0645\u200c\u0647\u0627\u06cc\u06cc \u062f\u0631 \u0645\u0631\u06a9\u0632 \u0686\u0634\u0645\u200c\u0627\u0646\u062f\u0627\u0632 \u0641\u0646\u0627\u0648\u0631\u06cc \u0627\u0637\u0644\u0627\u0639\u0627\u062a \u0628\u0627\u0634\u062f.\n\n\ud83d\udd0d \u06cc\u06a9 \u0633\u0648\u0627\u0644 \u0645\u0647\u0645 \u0627\u0633\u062a\u0631\u0627\u062a\u0698\u06cc\u06a9 \u062f\u06cc\u06af\u0631: \u0686\u06af\u0648\u0646\u0647 StoreOnce \u0628\u0647 \u0645\u062f\u062a \u0634\u0634 \u0645\u0627\u0647 \u0628\u062f\u0648\u0646 \u0647\u06cc\u0686 \u0646\u0634\u0627\u0646\u0647 \u0639\u0645\u0648\u0645\u06cc \u0627\u0632 \u0641\u0639\u0627\u0644\u06cc\u062a\u060c \u0622\u0633\u06cc\u0628\u200c\u067e\u0630\u06cc\u0631 \u0634\u062f\u061f \u0627\u06cc\u0646 \u0646\u0645\u0648\u0646\u0647\u200c\u0627\u06cc \u0627\u0632 \u06cc\u06a9 \u0646\u0642\u0637\u0647 \u06a9\u0648\u0631 \u0627\u0633\u062a\u060c \u0632\u0645\u0627\u0646\u06cc \u06a9\u0647 \u0645\u062d\u0635\u0648\u0644\u0627\u062a \u0632\u06cc\u0631\u0633\u0627\u062e\u062a\u06cc \"\u0633\u0627\u06a9\u062a\" \u0648 \u0638\u0627\u0647\u0631\u0627\u064b \u0627\u06cc\u0645\u0646 \u0628\u0647 \u0646\u0638\u0631 \u0645\u06cc\u200c\u0631\u0633\u0646\u062f. \u0627\u0645\u0627 \u0686\u0646\u06cc\u0646 \u06af\u0631\u0647\u200c\u0647\u0627\u06cc \u0633\u0627\u06a9\u062a\u06cc \u0627\u0647\u062f\u0627\u0641 \u0645\u0646\u0627\u0633\u0628\u06cc \u0647\u0633\u062a\u0646\u062f: \u0647\u06cc\u0686 \u06a9\u0633 \u0627\u0646\u062a\u0638\u0627\u0631 \u062d\u0645\u0644\u0647 \u0628\u0647 \u0631\u0627\u0647\u06a9\u0627\u0631\u06cc \u0631\u0627 \u0646\u062f\u0627\u0631\u062f \u06a9\u0647 \u0627\u0632 \u062f\u0627\u062f\u0647\u200c\u0647\u0627 \u0645\u062d\u0627\u0641\u0638\u062a \u0645\u06cc\u200c\u06a9\u0646\u062f.\n\n\ud83d\udccc \u062f\u0631 \u062d\u0627\u0644 \u062d\u0627\u0636\u0631\u060c StoreOnce \u0627\u0642\u062f\u0627\u0645\u0627\u062a \u062d\u0641\u0627\u0638\u062a\u06cc \u0645\u0648\u0642\u062a \u0627\u0631\u0627\u0626\u0647 \u0646\u0645\u06cc\u200c\u062f\u0647\u062f - \u0641\u0642\u0637 \u06cc\u06a9 \u0627\u0631\u062a\u0642\u0627\u0621 \u0627\u0631\u0627\u0626\u0647 \u0645\u06cc\u200c\u062f\u0647\u062f. \u0627\u06af\u0631 \u0627\u06cc\u0646 \u067e\u0644\u062a\u0641\u0631\u0645 \u062f\u0631 \u0645\u062d\u06cc\u0637\u200c\u0647\u0627\u06cc \u0628\u062d\u0631\u0627\u0646\u06cc \u0627\u0633\u062a\u0641\u0627\u062f\u0647 \u0634\u0648\u062f\u060c \u0627\u0631\u062a\u0642\u0627\u0621 \u0628\u0627 \u062a\u0623\u062e\u06cc\u0631 \u0646\u0647 \u062a\u0646\u0647\u0627 \u06cc\u06a9 \u0631\u06cc\u0633\u06a9 \u0627\u0633\u062a\u060c \u0628\u0644\u06a9\u0647 \u06cc\u06a9 \u0646\u0642\u0637\u0647 \u0634\u06a9\u0633\u062a \u0627\u062d\u062a\u0645\u0627\u0644\u06cc \u0628\u0631\u0627\u06cc \u06a9\u0644 \u062a\u062f\u0627\u0648\u0645 \u06a9\u0633\u0628\u200c\u0648\u06a9\u0627\u0631 \u0627\u0633\u062a.\n\n#hpe #storeonce\n\ud83c\udfed \u0648\u0628\u0633\u0627\u06cc\u062a \u0648 \u06a9\u0627\u0646\u0627\u0644 \u062a\u062e\u0635\u0635\u06cc \u0627\u0645\u0646\u06cc\u062a \u0632\u06cc\u0631\u0633\u0627\u062e\u062a\u0647\u0627\u06cc \u0627\u062a\u0648\u0645\u0627\u0633\u06cc\u0648\u0646 \u0648 \u06a9\u0646\u062a\u0631\u0644 \u0635\u0646\u0639\u062a\u06cc\n\ud83d\udc6e\ud83c\udffd\u200d\u2640\ufe0f\u0647\u0631\u06af\u0648\u0646\u0647 \u0627\u0646\u062a\u0634\u0627\u0631 \u0648 \u0630\u06a9\u0631 \u0645\u0637\u0627\u0644\u0628 \u0628\u062f\u0648\u0646 \u0630\u06a9\u0631 \u062f\u0642\u06cc\u0642 \u0645\u0646\u0628\u0639 \u0648 \u0622\u062f\u0631\u0633 \u0644\u06cc\u0646\u06a9 \u0622\u0646 \u0645\u0645\u0646\u0648\u0639 \u0627\u0633\u062a. \n\u0627\u062f\u0645\u06cc\u0646:\n\u200fhttps://t.me/pedram_kiani\n\u06a9\u0627\u0646\u0627\u0644 \u062a\u0644\u06af\u0631\u0627\u0645:\nhttps://t.me/ics_cert\n\u06af\u0631\u0648\u0647 \u0648\u0627\u062a\u0633 \u0622\u067e :\nhttps://chat.whatsapp.com/FpB620AWEeSKvd8U6cFh33\n\u06af\u0631\u0648\u0647 \u062a\u0644\u06af\u0631\u0627\u0645:\nhttps://t.me/ICSCERT_IR", "creation_timestamp": "2025-06-12T19:39:30.000000Z"}, {"uuid": "ade4dcd5-0c67-4fa0-93b3-96ed71787f70", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37094", "type": "seen", "source": "https://t.me/ics_cert/1191", "content": "\u0628\u062f\u0648\u0646 \u0646\u06cc\u0627\u0632 \u0628\u0647 \u0648\u0631\u0648\u062f - \u062f\u0633\u062a\u0631\u0633\u06cc \u06a9\u0627\u0645\u0644: StoreOnce \u0641\u0631\u0627\u0645\u0648\u0634 \u06a9\u0631\u062f \u06a9\u0647 \u062f\u0631\u0650 \u0627\u0631\u0632\u0634\u0645\u0646\u062f\u062a\u0631\u06cc\u0646\u200c\u0647\u0627 \u0631\u0627 \u0628\u0628\u0646\u062f\u062f\n\n\u062f\u0631 \u062d\u0627\u0644\u06cc \u06a9\u0647 \u0628\u0631\u062e\u06cc \u062f\u0631 \u062d\u0627\u0644 \u062a\u0647\u06cc\u0647 \u0646\u0633\u062e\u0647 \u067e\u0634\u062a\u06cc\u0628\u0627\u0646 \u0628\u0648\u062f\u0646\u062f\u060c \u0628\u0631\u062e\u06cc \u062f\u06cc\u06af\u0631 \u0628\u0647 \u062f\u0646\u0628\u0627\u0644 \u0631\u0627\u0647\u200c\u0647\u0627\u06cc\u06cc \u0628\u0631\u0627\u06cc \u0647\u06a9 \u06a9\u0631\u062f\u0646 \u0645\u062e\u0641\u06cc\u0627\u0646\u0647 \u0633\u06cc\u0633\u062a\u0645 \u0634\u062e\u0635 \u062f\u06cc\u06af\u0631\u06cc \u0628\u0648\u062f\u0646\u062f.\n\n\n\u0634\u0631\u06a9\u062a Hewlett Packard Enterprise \u062f\u0631 \u0631\u0627\u0628\u0637\u0647 \u0628\u0627 \u0647\u0634\u062a \u0622\u0633\u06cc\u0628\u200c\u067e\u0630\u06cc\u0631\u06cc \u062f\u0631 \u067e\u0644\u062a\u0641\u0631\u0645 \u0646\u0631\u0645\u200c\u0627\u0641\u0632\u0627\u0631\u06cc StoreOnce backup \u0648 data deduplication \u062e\u0648\u062f\u060c \u06cc\u06a9 \u0647\u0634\u062f\u0627\u0631 \u0627\u0645\u0646\u06cc\u062a\u06cc \u0641\u0648\u0631\u06cc \u0635\u0627\u062f\u0631 \u06a9\u0631\u062f\u0647 \u0627\u0633\u062a. \u062a\u0645\u0627\u0645 \u0622\u0633\u06cc\u0628\u200c\u067e\u0630\u06cc\u0631\u06cc\u200c\u0647\u0627 \u062f\u0631 \u0646\u0633\u062e\u0647 \u062c\u062f\u06cc\u062f \u0646\u0631\u0645\u200c\u0627\u0641\u0632\u0627\u0631\u060c StoreOnce 4.3.11\u060c \u06a9\u0647 \u0627\u06a9\u0646\u0648\u0646 \u0628\u0631\u0627\u06cc \u0647\u0645\u0647 \u06a9\u0627\u0631\u0628\u0631\u0627\u0646 \u062a\u0648\u0635\u06cc\u0647 \u0645\u06cc\u200c\u0634\u0648\u062f\u060c \u0628\u0631\u0637\u0631\u0641 \u0634\u062f\u0647\u200c\u0627\u0646\u062f.\n\n\u062e\u0637\u0631\u0646\u0627\u06a9\u200c\u062a\u0631\u06cc\u0646 \u0622\u0633\u06cc\u0628\u200c\u067e\u0630\u06cc\u0631\u06cc CVE-2025-37093 \u0627\u0633\u062a \u06a9\u0647 \u062f\u0631 \u0645\u0642\u06cc\u0627\u0633 CVSS \u0646\u0633\u062e\u0647 \u06f3.\u06f1 \u0627\u0645\u062a\u06cc\u0627\u0632 \u0628\u062d\u0631\u0627\u0646\u06cc \u06f9.\u06f8 \u0631\u0627 \u062f\u0631\u06cc\u0627\u0641\u062a \u06a9\u0631\u062f\u0647 \u0627\u0633\u062a. \u0627\u06cc\u0646 \u0622\u0633\u06cc\u0628\u200c\u067e\u0630\u06cc\u0631\u06cc \u0628\u0647 \u0645\u0647\u0627\u062c\u0645 \u0627\u062c\u0627\u0632\u0647 \u0645\u06cc\u200c\u062f\u0647\u062f \u062a\u0627 \u0628\u0647 \u062f\u0644\u06cc\u0644 \u062e\u0637\u0627\u06cc\u06cc \u062f\u0631 \u067e\u06cc\u0627\u062f\u0647\u200c\u0633\u0627\u0632\u06cc \u0631\u0648\u0634 machineAccountCheck\u060c \u0645\u06a9\u0627\u0646\u06cc\u0632\u0645 \u0627\u062d\u0631\u0627\u0632 \u0647\u0648\u06cc\u062a \u0631\u0627 \u062f\u0648\u0631 \u0628\u0632\u0646\u062f. \u0647\u0645\u0627\u0646\u0637\u0648\u0631 \u06a9\u0647 \u062a\u06cc\u0645 ZDI\u060c \u06a9\u0647 \u0627\u06cc\u0646 \u0627\u0634\u06a9\u0627\u0644 \u0631\u0627 \u0634\u0646\u0627\u0633\u0627\u06cc\u06cc \u06a9\u0631\u062f\u0647 \u0627\u0633\u062a\u060c \u062a\u0648\u0636\u06cc\u062d \u0645\u06cc\u200c\u062f\u0647\u062f\u060c \u0627\u0635\u0644 \u0645\u0634\u06a9\u0644 \u062f\u0631 \u0645\u0646\u0637\u0642 \u0627\u062d\u0631\u0627\u0632 \u0647\u0648\u06cc\u062a \u0646\u0627\u062f\u0631\u0633\u062a \u0646\u0647\u0641\u062a\u0647 \u0627\u0633\u062a - \u0645\u06cc\u200c\u062a\u0648\u0627\u0646 \u0622\u0646 \u0631\u0627 \u0628\u0647 \u0637\u0648\u0631 \u06a9\u0627\u0645\u0644 \u062f\u0648\u0631 \u0632\u062f \u0648 \u0631\u0627\u0647 \u0631\u0627 \u0628\u0631\u0627\u06cc \u0633\u0627\u06cc\u0631 \u0622\u0633\u06cc\u0628\u200c\u067e\u0630\u06cc\u0631\u06cc\u200c\u0647\u0627 \u0628\u0627\u0632 \u06a9\u0631\u062f.\n\n\u0641\u0647\u0631\u0633\u062a \u062a\u0645\u0627\u0645 \u0622\u0633\u06cc\u0628\u200c\u067e\u0630\u06cc\u0631\u06cc\u200c\u0647\u0627\u06cc \u0631\u0641\u0639\u200c\u0634\u062f\u0647 \u062f\u0631 \u0646\u0633\u062e\u0647 \u06f4.\u06f3.\u06f1\u06f1 \u0634\u0627\u0645\u0644 \u0645\u0648\u0627\u0631\u062f \u0632\u06cc\u0631 \u0627\u0633\u062a:\n\nCVE-2025-37089 - \u0627\u062c\u0631\u0627\u06cc \u06a9\u062f \u0627\u0632 \u0631\u0627\u0647 \u062f\u0648\u0631\u061b\nCVE-2025-37090 - \u062d\u0645\u0644\u0647 \u062c\u0639\u0644 \u062f\u0631\u062e\u0648\u0627\u0633\u062a \u0633\u0631\u0648\u0631 (SSRF)\u061b\nCVE-2025-37091 - \u0627\u062c\u0631\u0627\u06cc \u06a9\u062f \u0627\u0632 \u0631\u0627\u0647 \u062f\u0648\u0631\u061b\nCVE-2025-37092 - \u0627\u062c\u0631\u0627\u06cc \u06a9\u062f \u0627\u0632 \u0631\u0627\u0647 \u062f\u0648\u0631\u061b\nCVE-2025-37093 - \u062f\u0648\u0631 \u0632\u062f\u0646 \u0627\u062d\u0631\u0627\u0632 \u0647\u0648\u06cc\u062a (\u0628\u062d\u0631\u0627\u0646\u06cc)\u061b\nCVE-2025-37094 - \u062d\u0630\u0641 \u0641\u0627\u06cc\u0644\u200c\u0647\u0627\u06cc \u062f\u0644\u062e\u0648\u0627\u0647 \u0627\u0632 \u0637\u0631\u06cc\u0642 \u067e\u06cc\u0645\u0627\u06cc\u0634 \u062f\u0627\u06cc\u0631\u06a9\u062a\u0648\u0631\u06cc\u061b\nCVE-2025-37095 - \u0627\u0641\u0634\u0627\u06cc \u0627\u0637\u0644\u0627\u0639\u0627\u062a \u0627\u0632 \u0637\u0631\u06cc\u0642 \u067e\u06cc\u0645\u0627\u06cc\u0634 \u062f\u0627\u06cc\u0631\u06a9\u062a\u0648\u0631\u06cc\u061b\nCVE-2025-37096 - \u0627\u062c\u0631\u0627\u06cc \u06a9\u062f \u0627\u0632 \u0631\u0627\u0647 \u062f\u0648\u0631.\n\u0627\u06af\u0631\u0686\u0647 CVE-2025-37093 \u062a\u0646\u0647\u0627 \u0645\u0648\u0631\u062f\u06cc \u0627\u0633\u062a \u06a9\u0647 \u0631\u0633\u0645\u0627\u064b \u0628\u0647 \u0639\u0646\u0648\u0627\u0646 \u0628\u062d\u0631\u0627\u0646\u06cc \u0637\u0628\u0642\u0647\u200c\u0628\u0646\u062f\u06cc \u0634\u062f\u0647 \u0627\u0633\u062a\u060c \u06a9\u0627\u0631\u0634\u0646\u0627\u0633\u0627\u0646 \u062a\u0623\u06a9\u06cc\u062f \u0645\u06cc\u200c\u06a9\u0646\u0646\u062f \u06a9\u0647 \u0633\u0627\u06cc\u0631 \u0622\u0633\u06cc\u0628\u200c\u067e\u0630\u06cc\u0631\u06cc\u200c\u0647\u0627 \u0631\u0627 \u0646\u0628\u0627\u06cc\u062f \u062f\u0633\u062a \u06a9\u0645 \u06af\u0631\u0641\u062a. \u062e\u0637\u0631 \u062a\u0631\u06a9\u06cc\u0628\u06cc \u0622\u0646\u0647\u0627 \u062f\u0631 \u0635\u0648\u0631\u062a \u062f\u0648\u0631 \u0632\u062f\u0646 \u0645\u0648\u0641\u0642\u06cc\u062a\u200c\u0622\u0645\u06cc\u0632 \u0627\u062d\u0631\u0627\u0632 \u0647\u0648\u06cc\u062a \u0628\u0647 \u0637\u0648\u0631 \u0642\u0627\u0628\u0644 \u062a\u0648\u062c\u0647\u06cc \u0627\u0641\u0632\u0627\u06cc\u0634 \u0645\u06cc\u200c\u06cc\u0627\u0628\u062f. \u0627\u06cc\u0646 \u0627\u0645\u0631 \u062d\u062a\u06cc \u0622\u0633\u06cc\u0628\u200c\u067e\u0630\u06cc\u0631\u06cc\u200c\u0647\u0627\u06cc \u0628\u0627 \u062f\u0631\u062c\u0647 \u0645\u062a\u0648\u0633\u0637 \u200b\u200b\u0645\u0627\u0646\u0646\u062f CVE-2025-37094 \u0648 CVE-2025-37095 \u0631\u0627 \u0628\u0633\u06cc\u0627\u0631 \u062e\u0637\u0631\u0646\u0627\u06a9 \u0645\u06cc\u200c\u06a9\u0646\u062f - \u062d\u0630\u0641 \u0641\u0627\u06cc\u0644 \u0648 \u0646\u0634\u062a \u062f\u0627\u062f\u0647\u200c\u0647\u0627 \u0628\u062f\u0648\u0646 \u062a\u0644\u0627\u0634 \u0632\u06cc\u0627\u062f \u0627\u0645\u06a9\u0627\u0646\u200c\u067e\u0630\u06cc\u0631 \u0627\u0633\u062a.\n\n\u0637\u0628\u0642 \u06af\u0632\u0627\u0631\u0634 Zero Day Initiative\u060c StoreOnce \u0628\u06cc\u0634 \u0627\u0632 \u0634\u0634 \u0645\u0627\u0647 \u062f\u0631 \u0628\u0631\u0627\u0628\u0631 \u0627\u06cc\u0646 \u0622\u0633\u06cc\u0628\u200c\u067e\u0630\u06cc\u0631\u06cc\u200c\u0647\u0627 \u0622\u0633\u06cc\u0628\u200c\u067e\u0630\u06cc\u0631 \u0628\u0648\u062f\u0647 \u0627\u0633\u062a. \u06a9\u0627\u0631\u0634\u0646\u0627\u0633\u0627\u0646 \u0627\u06cc\u0646 \u0645\u0634\u06a9\u0644\u0627\u062a \u0631\u0627 \u062f\u0631 \u0627\u06a9\u062a\u0628\u0631 \u06f2\u06f0\u06f2\u06f4 \u06af\u0632\u0627\u0631\u0634 \u06a9\u0631\u062f\u0646\u062f\u060c \u0627\u0645\u0627 \u062d\u062f\u0648\u062f \u0647\u0641\u062a \u0645\u0627\u0647 \u0637\u0648\u0644 \u06a9\u0634\u06cc\u062f \u062a\u0627 \u0648\u0635\u0644\u0647\u200c\u0647\u0627 \u0645\u0646\u062a\u0634\u0631 \u0634\u0648\u0646\u062f. \u0628\u0627 \u0648\u062c\u0648\u062f \u0627\u06cc\u0646\u060c \u0647\u06cc\u0686 \u062a\u0623\u06cc\u06cc\u062f\u06cc \u0648\u062c\u0648\u062f \u0646\u062f\u0627\u0631\u062f \u06a9\u0647 \u0627\u06cc\u0646 \u0622\u0633\u06cc\u0628\u200c\u067e\u0630\u06cc\u0631\u06cc\u200c\u0647\u0627 \u0628\u0647 \u0637\u0648\u0631 \u0641\u0639\u0627\u0644 \u062f\u0631 \u062d\u0645\u0644\u0627\u062a \u0648\u0627\u0642\u0639\u06cc \u0645\u0648\u0631\u062f \u0633\u0648\u0621\u0627\u0633\u062a\u0641\u0627\u062f\u0647 \u0642\u0631\u0627\u0631 \u06af\u0631\u0641\u062a\u0647\u200c\u0627\u0646\u062f.\n\nStoreOnce \u062f\u0631 \u0632\u06cc\u0631\u0633\u0627\u062e\u062a\u200c\u0647\u0627\u06cc \u0628\u0632\u0631\u06af \u0641\u0646\u0627\u0648\u0631\u06cc \u0627\u0637\u0644\u0627\u0639\u0627\u062a\u060c \u0645\u0631\u0627\u06a9\u0632 \u062f\u0627\u062f\u0647 \u0648 \u0633\u0627\u0632\u0645\u0627\u0646\u200c\u0647\u0627\u06cc\u06cc \u0628\u0627 \u062d\u062c\u0645 \u0632\u06cc\u0627\u062f\u06cc \u0627\u0632 \u062f\u0627\u062f\u0647\u200c\u0647\u0627 - \u0627\u0632 \u0627\u0631\u0627\u0626\u0647\u200c\u062f\u0647\u0646\u062f\u06af\u0627\u0646 \u062e\u062f\u0645\u0627\u062a \u0627\u0628\u0631\u06cc \u06af\u0631\u0641\u062a\u0647 \u062a\u0627 \u06a9\u0627\u0631\u0628\u0631\u0627\u0646 \u0634\u0631\u06a9\u062a\u06cc - \u0627\u0633\u062a\u0641\u0627\u062f\u0647 \u0645\u06cc\u200c\u0634\u0648\u062f. \u0627\u0632 \u062c\u0645\u0644\u0647 \u062f\u0631 \u0631\u0648\u0633\u06cc\u0647. \u0627\u06cc\u0646 \u0645\u062d\u0635\u0648\u0644 \u0628\u0627 \u0631\u0627\u0647\u06a9\u0627\u0631\u0647\u0627\u06cc \u067e\u0634\u062a\u06cc\u0628\u0627\u0646\u200c\u06af\u06cc\u0631\u06cc \u0645\u0627\u0646\u0646\u062f HPE Data Protector\u060c Veeam\u060c Commvault \u0648 Veritas NetBackup \u0627\u062f\u063a\u0627\u0645 \u0645\u06cc\u200c\u0634\u0648\u062f \u0648 \u0628\u0647 \u0639\u0646\u0648\u0627\u0646 \u06cc\u06a9 \u062c\u0632\u0621 \u06a9\u0644\u06cc\u062f\u06cc \u062f\u0631 \u0627\u0633\u062a\u0631\u0627\u062a\u0698\u06cc\u200c\u0647\u0627\u06cc \u062a\u062f\u0627\u0648\u0645 \u06a9\u0633\u0628\u200c\u0648\u06a9\u0627\u0631 \u0639\u0645\u0644 \u0645\u06cc\u200c\u06a9\u0646\u062f.\n\nHPE \u0647\u06cc\u0686 \u0631\u0627\u0647 \u062d\u0644 \u0645\u0648\u0642\u062a \u06cc\u0627 \u0627\u0642\u062f\u0627\u0645 \u0645\u0648\u0642\u062a\u06cc \u0628\u0631\u0627\u06cc \u0645\u062d\u0627\u0641\u0638\u062a \u062f\u0631 \u0628\u0631\u0627\u0628\u0631 \u0645\u0634\u06a9\u0644\u0627\u062a \u0634\u0646\u0627\u0633\u0627\u06cc\u06cc \u0634\u062f\u0647 \u0627\u0631\u0627\u0626\u0647 \u0646\u06a9\u0631\u062f\u0647 \u0627\u0633\u062a. \u062a\u0646\u0647\u0627 \u0631\u0627\u0647 \u0628\u0631\u0627\u06cc \u0628\u0633\u062a\u0646 \u0627\u06cc\u0646 \u0622\u0633\u06cc\u0628\u200c\u067e\u0630\u06cc\u0631\u06cc\u200c\u0647\u0627\u060c \u0646\u0633\u062e\u0647 \u0641\u0639\u0644\u06cc StoreOnce 4.3.11 \u0627\u0633\u062a. \u0628\u0631\u0627\u06cc \u0645\u062f\u06cc\u0631\u0627\u0646 \u0633\u06cc\u0633\u062a\u0645 \u06a9\u0647 \u0645\u062d\u06cc\u0637\u200c\u0647\u0627\u06cc \u0622\u0633\u06cc\u0628\u200c\u062f\u06cc\u062f\u0647 \u0631\u0627 \u0646\u06af\u0647\u062f\u0627\u0631\u06cc \u0645\u06cc\u200c\u06a9\u0646\u0646\u062f\u060c \u0627\u06cc\u0646 \u0628\u0647\u200c\u0631\u0648\u0632\u0631\u0633\u0627\u0646\u06cc \u062f\u0631 \u0627\u0648\u0644\u0648\u06cc\u062a \u0642\u0631\u0627\u0631 \u0645\u06cc\u200c\u06af\u06cc\u0631\u062f.\n\ud83c\udfed \u0648\u0628\u0633\u0627\u06cc\u062a \u0648 \u06a9\u0627\u0646\u0627\u0644 \u062a\u062e\u0635\u0635\u06cc \u0627\u0645\u0646\u06cc\u062a \u0632\u06cc\u0631\u0633\u0627\u062e\u062a\u0647\u0627\u06cc \u0627\u062a\u0648\u0645\u0627\u0633\u06cc\u0648\u0646 \u0648 \u06a9\u0646\u062a\u0631\u0644 \u0635\u0646\u0639\u062a\u06cc\n\ud83d\udc6e\ud83c\udffd\u200d\u2640\ufe0f\u0647\u0631\u06af\u0648\u0646\u0647 \u0627\u0646\u062a\u0634\u0627\u0631 \u0648 \u0630\u06a9\u0631 \u0645\u0637\u0627\u0644\u0628 \u0628\u062f\u0648\u0646 \u0630\u06a9\u0631 \u062f\u0642\u06cc\u0642 \u0645\u0646\u0628\u0639 \u0648 \u0622\u062f\u0631\u0633 \u0644\u06cc\u0646\u06a9 \u0622\u0646 \u0645\u0645\u0646\u0648\u0639 \u0627\u0633\u062a. \n\u0627\u062f\u0645\u06cc\u0646:\n\u200fhttps://t.me/pedram_kiani\n\u06a9\u0627\u0646\u0627\u0644 \u062a\u0644\u06af\u0631\u0627\u0645:\nhttps://t.me/ics_cert\n\u06af\u0631\u0648\u0647 \u0648\u0627\u062a\u0633 \u0622\u067e :\nhttps://chat.whatsapp.com/FpB620AWEeSKvd8U6cFh33\n\u06af\u0631\u0648\u0647 \u062a\u0644\u06af\u0631\u0627\u0645:\nhttps://t.me/ICSCERT_IR", "creation_timestamp": "2025-06-12T19:42:43.000000Z"}, {"uuid": "da5a5b7b-a281-4855-a993-572008b82ae9", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3740", "type": "published-proof-of-concept", "source": "https://t.me/captainsmok3r_official/68", "content": "CVE-2025-3740 \u2013 School Management System for WordPress\nexploit: https://target.com/wp-content/plugins/school-management/includes/plugin.php?page=../../../../wp-config.php", "creation_timestamp": "2025-08-11T22:05:38.000000Z"}, {"uuid": "a1819470-6a75-4b4c-a1e5-2a83744f45e5", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37899", "type": "published-proof-of-concept", "source": "Telegram/YOs3MGfPipiC-oFVpHZn4Kc6j2xeVsEEDgpo2CWOrctHtw", "content": "", "creation_timestamp": "2025-05-22T13:35:55.000000Z"}, {"uuid": "bfe7db5b-d123-40ca-bae3-9e3d61d5c5ef", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37093", "type": "seen", "source": "https://t.me/hackyourmom/11647", "content": "\ud83d\uddfd HPE \u0432\u0438\u043f\u0443\u0441\u0442\u0438\u043b\u0430 \u0442\u0435\u0440\u043c\u0456\u043d\u043e\u0432\u0435 \u043e\u043d\u043e\u0432\u043b\u0435\u043d\u043d\u044f \u0431\u0435\u0437\u043f\u0435\u043a\u0438 \u0434\u043b\u044f StoreOnce, \u0443\u0441\u0443\u043d\u0443\u0432\u0448\u0438 8 \u043a\u0440\u0438\u0442\u0438\u0447\u043d\u0438\u0445 \u0432\u0440\u0430\u0437\u043b\u0438\u0432\u043e\u0441\u0442\u0435\u0439, \u0441\u0435\u0440\u0435\u0434 \u044f\u043a\u0438\u0445 CVE-2025-37093 (CVSS 9.8), \u0449\u043e \u0434\u043e\u0437\u0432\u043e\u043b\u044f\u0454 \u043e\u0431\u0445\u0456\u0434 \u0430\u0432\u0442\u0435\u043d\u0442\u0438\u0444\u0456\u043a\u0430\u0446\u0456\u0457 \u0442\u0430 \u0432\u0456\u0434\u0434\u0430\u043b\u0435\u043d\u0435 \u0432\u0438\u043a\u043e\u043d\u0430\u043d\u043d\u044f \u043a\u043e\u0434\u0443 \ud83d\udc7e #cybernews", "creation_timestamp": "2025-06-04T16:35:21.000000Z"}, {"uuid": "490a2df1-1a87-48f4-97b5-ebcc03566d0b", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37103", "type": "seen", "source": "Telegram/7WkyeVrt5XilYx12HR2ozHDgP_8g75ujA8R-FCDUzqugag", "content": "", "creation_timestamp": "2025-07-21T08:02:51.000000Z"}, {"uuid": "686d9b74-7fc1-4c8f-b966-357211c588d5", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37103", "type": "seen", "source": "https://t.me/true_secator/7257", "content": "Hewlett-Packard Enterprise (HPE) \u043f\u0440\u0435\u0434\u0443\u043f\u0440\u0435\u0436\u0434\u0430\u0435\u0442 \u043e \u0436\u0435\u0441\u0442\u043a\u043e \u0437\u0430\u043f\u0440\u043e\u0433\u0440\u0430\u043c\u043c\u0438\u0440\u043e\u0432\u0430\u043d\u043d\u044b\u0445 \u0443\u0447\u0435\u0442\u043d\u044b\u0445 \u0434\u0430\u043d\u043d\u044b\u0445 \u0432 \u0442\u043e\u0447\u043a\u0430\u0445 \u0434\u043e\u0441\u0442\u0443\u043f\u0430 Aruba Instant On, \u043a\u043e\u0442\u043e\u0440\u044b\u0435 \u043f\u043e\u0437\u0432\u043e\u043b\u044f\u044e\u0442 \u0437\u043b\u043e\u0443\u043c\u044b\u0448\u043b\u0435\u043d\u043d\u0438\u043a\u0430\u043c \u043e\u0431\u0445\u043e\u0434\u0438\u0442\u044c \u043e\u0431\u044b\u0447\u043d\u0443\u044e \u0430\u0443\u0442\u0435\u043d\u0442\u0438\u0444\u0438\u043a\u0430\u0446\u0438\u044e \u0443\u0441\u0442\u0440\u043e\u0439\u0441\u0442\u0432\u0430 \u0438 \u043f\u043e\u043b\u0443\u0447\u0430\u0442\u044c \u0434\u043e\u0441\u0442\u0443\u043f \u043a \u0432\u0435\u0431-\u0438\u043d\u0442\u0435\u0440\u0444\u0435\u0439\u0441\u0443.\n\nAruba Instant On - \u044d\u0442\u043e \u043a\u043e\u043c\u043f\u0430\u043a\u0442\u043d\u044b\u0435 \u0431\u0435\u0441\u043f\u0440\u043e\u0432\u043e\u0434\u043d\u044b\u0435 (Wi-Fi) \u0443\u0441\u0442\u0440\u043e\u0439\u0441\u0442\u0432\u0430 \u0441 \u0444\u0443\u043d\u043a\u0446\u0438\u0435\u0439 plug-and-play, \u0440\u0430\u0437\u0440\u0430\u0431\u043e\u0442\u0430\u043d\u043d\u044b\u0435 \u0434\u043b\u044f \u043c\u0430\u043b\u043e\u0433\u043e \u0438 \u0441\u0440\u0435\u0434\u043d\u0435\u0433\u043e \u0431\u0438\u0437\u043d\u0435\u0441\u0430 \u0441 \u0444\u0443\u043d\u043a\u0446\u0438\u043e\u043d\u0430\u043b\u043e\u043c \u043a\u043e\u0440\u043f\u043e\u0440\u0430\u0442\u0438\u0432\u043d\u043e\u0433\u043e \u0443\u0440\u043e\u0432\u043d\u044f (\u0433\u043e\u0441\u0442\u0435\u0432\u044b\u0435 \u0441\u0435\u0442\u0438, \u0441\u0435\u0433\u043c\u0435\u043d\u0442\u0430\u0446\u0438\u044f \u0442\u0440\u0430\u0444\u0438\u043a\u0430) \u0438 \u0443\u043f\u0440\u0430\u0432\u043b\u0435\u043d\u0438\u0435\u043c \u0447\u0435\u0440\u0435\u0437 \u043e\u0431\u043b\u0430\u043a\u043e/\u043c\u043e\u0431\u0438\u043b\u044c\u043d\u044b\u0435 \u043f\u0440\u0438\u043b\u043e\u0436\u0435\u043d\u0438\u044f.\n\nCVE-2025-37103 \u0438\u043c\u0435\u0435\u0442 \u043e\u0446\u0435\u043d\u043a\u0443 CVSS v3.1: 9,8 \u0438 \u0437\u0430\u0442\u0440\u0430\u0433\u0438\u0432\u0430\u0435\u0442 \u0442\u043e\u0447\u043a\u0438 \u0434\u043e\u0441\u0442\u0443\u043f\u0430 Instant On \u0441 \u0432\u0435\u0440\u0441\u0438\u0435\u0439 \u043f\u0440\u043e\u0448\u0438\u0432\u043a\u0438 3.2.0.1 \u0438 \u043d\u0438\u0436\u0435.\n\n\u0423\u0441\u043f\u0435\u0448\u043d\u0430\u044f \u044d\u043a\u0441\u043f\u043b\u0443\u0430\u0442\u0430\u0446\u0438\u044f \u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u0438 \u043f\u043e\u0437\u0432\u043e\u043b\u044f\u0435\u0442 \u0443\u0434\u0430\u043b\u0435\u043d\u043d\u043e\u043c\u0443 \u0437\u043b\u043e\u0443\u043c\u044b\u0448\u043b\u0435\u043d\u043d\u0438\u043a\u0443 \u043f\u043e\u043b\u0443\u0447\u0438\u0442\u044c \u0430\u0434\u043c\u0438\u043d\u0438\u0441\u0442\u0440\u0430\u0442\u0438\u0432\u043d\u044b\u0439 \u0434\u043e\u0441\u0442\u0443\u043f \u043a \u0441\u0438\u0441\u0442\u0435\u043c\u0435.\n\n\u041f\u043e\u0441\u043a\u043e\u043b\u044c\u043a\u0443 \u0430\u0434\u043c\u0438\u043d\u0438\u0441\u0442\u0440\u0430\u0442\u0438\u0432\u043d\u044b\u0435 \u0443\u0447\u0435\u0442\u043d\u044b\u0435 \u0434\u0430\u043d\u043d\u044b\u0435 \u0436\u0435\u0441\u0442\u043a\u043e \u0437\u0430\u043f\u0440\u043e\u0433\u0440\u0430\u043c\u043c\u0438\u0440\u043e\u0432\u0430\u043d\u044b \u0432 \u043f\u0440\u043e\u0448\u0438\u0432\u043a\u0435, \u0434\u043b\u044f \u043e\u043f\u044b\u0442\u043d\u044b\u0445 \u043f\u043e\u043b\u044c\u0437\u043e\u0432\u0430\u0442\u0435\u043b\u0435\u0439 \u0438\u0445 \u043e\u0431\u043d\u0430\u0440\u0443\u0436\u0435\u043d\u0438\u0435 \u043d\u0435 \u043f\u0440\u0435\u0434\u0441\u0442\u0430\u0432\u043b\u044f\u0435\u0442 \u043e\u0441\u043e\u0431\u043e\u0439 \u0441\u043b\u043e\u0436\u043d\u043e\u0441\u0442\u0438.\n\n\u041f\u043e\u043b\u0443\u0447\u0438\u0432 \u0434\u043e\u0441\u0442\u0443\u043f \u043a \u0432\u0435\u0431-\u0438\u043d\u0442\u0435\u0440\u0444\u0435\u0439\u0441\u0443 \u0432 \u043a\u0430\u0447\u0435\u0441\u0442\u0432\u0435 \u0430\u0434\u043c\u0438\u043d\u0438\u0441\u0442\u0440\u0430\u0442\u043e\u0440\u043e\u0432, \u0437\u043b\u043e\u0443\u043c\u044b\u0448\u043b\u0435\u043d\u043d\u0438\u043a\u0438 \u043c\u043e\u0433\u0443\u0442 \u0438\u0437\u043c\u0435\u043d\u0438\u0442\u044c \u043d\u0430\u0441\u0442\u0440\u043e\u0439\u043a\u0438 \u0442\u043e\u0447\u043a\u0438 \u0434\u043e\u0441\u0442\u0443\u043f\u0430, \u043f\u0435\u0440\u0435\u043d\u0430\u0441\u0442\u0440\u043e\u0438\u0442\u044c \u0441\u0438\u0441\u0442\u0435\u043c\u0443 \u0431\u0435\u0437\u043e\u043f\u0430\u0441\u043d\u043e\u0441\u0442\u0438, \u0443\u0441\u0442\u0430\u043d\u043e\u0432\u0438\u0442\u044c \u0431\u044d\u043a\u0434\u043e\u0440\u044b, \u043e\u0441\u0443\u0449\u0435\u0441\u0442\u0432\u043b\u044f\u0442\u044c \u043f\u0435\u0440\u0435\u0445\u0432\u0430\u0442 \u0442\u0440\u0430\u0444\u0438\u043a\u0430 \u0438 \u0434\u0430\u0436\u0435 \u043e\u0441\u0443\u0449\u0435\u0441\u0442\u0432\u0438\u0442\u044c \u0433\u043e\u0440\u0438\u0437\u043e\u043d\u0442\u0430\u043b\u044c\u043d\u043e\u0435 \u043f\u0435\u0440\u0435\u043c\u0435\u0449\u0435\u043d\u0438\u0435.\n\n\u0423\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u044c \u0431\u044b\u043b\u0430 \u043e\u0431\u043d\u0430\u0440\u0443\u0436\u0435\u043d\u0430 \u0438\u0441\u0441\u043b\u0435\u0434\u043e\u0432\u0430\u0442\u0435\u043b\u0435\u043c ZZ \u0438\u0437 Ubisectech Sirius, \u043a\u043e\u0442\u043e\u0440\u044b\u0439 \u0441\u043e\u043e\u0431\u0449\u0438\u043b \u043e \u043d\u0435\u0439 \u043d\u0435\u043f\u043e\u0441\u0440\u0435\u0434\u0441\u0442\u0432\u0435\u043d\u043d\u043e \u043f\u043e\u0441\u0442\u0430\u0432\u0449\u0438\u043a\u0443.\n\n\u0412 \u0442\u043e\u043c \u0436\u0435 \u0431\u044e\u043b\u043b\u0435\u0442\u0435\u043d\u0435 HPE \u0443\u043a\u0430\u0437\u044b\u0432\u0430\u0435\u0442 \u043d\u0430 \u0432\u0442\u043e\u0440\u0443\u044e \u0441\u0435\u0440\u044c\u0451\u0437\u043d\u0443\u044e CVE-2025-37102, \u0441\u0432\u044f\u0437\u0430\u043d\u043d\u0443\u044e \u0441 \u0430\u0443\u0442\u0435\u043d\u0442\u0438\u0444\u0438\u0446\u0438\u0440\u043e\u0432\u0430\u043d\u043d\u044b\u043c \u0432\u043d\u0435\u0434\u0440\u0435\u043d\u0438\u0435\u043c \u043a\u043e\u043c\u0430\u043d\u0434 \u0432 \u0438\u043d\u0442\u0435\u0440\u0444\u0435\u0439\u0441 \u043a\u043e\u043c\u0430\u043d\u0434\u043d\u043e\u0439 \u0441\u0442\u0440\u043e\u043a\u0438 (CLI) \u0442\u043e\u0447\u0435\u043a \u0434\u043e\u0441\u0442\u0443\u043f\u0430 Aruba Instant On.\n\n\u0415\u0435 \u043c\u043e\u0436\u043d\u043e \u0441\u0432\u044f\u0437\u0430\u0442\u044c \u0441 CVE-2025-37103, \u043f\u043e\u0441\u043a\u043e\u043b\u044c\u043a\u0443 \u0434\u043b\u044f \u0435\u0435 \u044d\u043a\u0441\u043f\u043b\u0443\u0430\u0442\u0430\u0446\u0438\u0438 \u0442\u0440\u0435\u0431\u0443\u044e\u0442\u0441\u044f \u043f\u0440\u0430\u0432\u0430 \u0430\u0434\u043c\u0438\u043d\u0438\u0441\u0442\u0440\u0430\u0442\u043e\u0440\u0430, \u0447\u0442\u043e \u043f\u043e\u0437\u0432\u043e\u043b\u044f\u0435\u0442 \u0437\u043b\u043e\u0443\u043c\u044b\u0448\u043b\u0435\u043d\u043d\u0438\u043a\u0430\u043c \u0432\u0432\u043e\u0434\u0438\u0442\u044c \u043f\u0440\u043e\u0438\u0437\u0432\u043e\u043b\u044c\u043d\u044b\u0435 \u043a\u043e\u043c\u0430\u043d\u0434\u044b \u0432 CLI \u0434\u043b\u044f \u0438\u0437\u0432\u043b\u0435\u0447\u0435\u043d\u0438\u044f \u0434\u0430\u043d\u043d\u044b\u0445, \u043e\u0442\u043a\u043b\u044e\u0447\u0435\u043d\u0438\u044f \u0431\u0435\u0437\u043e\u043f\u0430\u0441\u043d\u043e\u0441\u0442\u0438 \u0438 \u043e\u0431\u0435\u0441\u043f\u0435\u0447\u0435\u043d\u0438\u044f \u0443\u0441\u0442\u043e\u0439\u0447\u0438\u0432\u043e\u0441\u0442\u0438.\n\n\u041e\u0431\u0435 \u043f\u0440\u043e\u0431\u043b\u0435\u043c\u044b \u0440\u0435\u0448\u0430\u044e\u0442\u0441\u044f \u043e\u0431\u043d\u043e\u0432\u043b\u0435\u043d\u0438\u0435\u043c \u043f\u0440\u043e\u0448\u0438\u0432\u043a\u0438 \u0434\u043e \u0432\u0435\u0440\u0441\u0438\u0438 3.2.1.0 (\u0438\u043b\u0438 \u0431\u043e\u043b\u0435\u0435 \u043f\u043e\u0437\u0434\u043d\u0435\u0439), \u043e\u0431\u0445\u043e\u0434\u043d\u044b\u0435 \u043f\u0443\u0442\u0438 \u043e\u0442\u0441\u0443\u0442\u0441\u0442\u0432\u0443\u044e\u0442.\n\nHPE Aruba Networking \u043d\u0435 \u0440\u0430\u0441\u043f\u043e\u043b\u0430\u0433\u0430\u0435\u0442 \u0438\u043d\u0444\u043e\u0440\u043c\u0430\u0446\u0438\u0435\u0439 \u043e\u0431 \u044d\u043a\u0441\u043f\u043b\u0443\u0430\u0442\u0430\u0446\u0438\u0438 \u044d\u0442\u0438\u0445 \u0434\u0432\u0443\u0445 \u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u0435\u0439, \u043e\u0434\u043d\u0430\u043a\u043e, \u043a\u0430\u043a \u043f\u043e\u043b\u0430\u0433\u0430\u0435\u0442 \u043f\u043e\u0441\u0442\u0430\u0432\u0449\u0438\u043a, \u0441\u0438\u0442\u0443\u0430\u0446\u0438\u044f \u043c\u043e\u0436\u0435\u0442 \u0431\u044b\u0441\u0442\u0440\u043e \u0438\u0437\u043c\u0435\u043d\u0438\u0442\u044c\u0441\u044f.", "creation_timestamp": "2025-07-22T16:53:21.000000Z"}, {"uuid": "51573023-5ae7-42f9-9efc-3dc1ce03db3a", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37102", "type": "seen", "source": "https://t.me/true_secator/7257", "content": "Hewlett-Packard Enterprise (HPE) \u043f\u0440\u0435\u0434\u0443\u043f\u0440\u0435\u0436\u0434\u0430\u0435\u0442 \u043e \u0436\u0435\u0441\u0442\u043a\u043e \u0437\u0430\u043f\u0440\u043e\u0433\u0440\u0430\u043c\u043c\u0438\u0440\u043e\u0432\u0430\u043d\u043d\u044b\u0445 \u0443\u0447\u0435\u0442\u043d\u044b\u0445 \u0434\u0430\u043d\u043d\u044b\u0445 \u0432 \u0442\u043e\u0447\u043a\u0430\u0445 \u0434\u043e\u0441\u0442\u0443\u043f\u0430 Aruba Instant On, \u043a\u043e\u0442\u043e\u0440\u044b\u0435 \u043f\u043e\u0437\u0432\u043e\u043b\u044f\u044e\u0442 \u0437\u043b\u043e\u0443\u043c\u044b\u0448\u043b\u0435\u043d\u043d\u0438\u043a\u0430\u043c \u043e\u0431\u0445\u043e\u0434\u0438\u0442\u044c \u043e\u0431\u044b\u0447\u043d\u0443\u044e \u0430\u0443\u0442\u0435\u043d\u0442\u0438\u0444\u0438\u043a\u0430\u0446\u0438\u044e \u0443\u0441\u0442\u0440\u043e\u0439\u0441\u0442\u0432\u0430 \u0438 \u043f\u043e\u043b\u0443\u0447\u0430\u0442\u044c \u0434\u043e\u0441\u0442\u0443\u043f \u043a \u0432\u0435\u0431-\u0438\u043d\u0442\u0435\u0440\u0444\u0435\u0439\u0441\u0443.\n\nAruba Instant On - \u044d\u0442\u043e \u043a\u043e\u043c\u043f\u0430\u043a\u0442\u043d\u044b\u0435 \u0431\u0435\u0441\u043f\u0440\u043e\u0432\u043e\u0434\u043d\u044b\u0435 (Wi-Fi) \u0443\u0441\u0442\u0440\u043e\u0439\u0441\u0442\u0432\u0430 \u0441 \u0444\u0443\u043d\u043a\u0446\u0438\u0435\u0439 plug-and-play, \u0440\u0430\u0437\u0440\u0430\u0431\u043e\u0442\u0430\u043d\u043d\u044b\u0435 \u0434\u043b\u044f \u043c\u0430\u043b\u043e\u0433\u043e \u0438 \u0441\u0440\u0435\u0434\u043d\u0435\u0433\u043e \u0431\u0438\u0437\u043d\u0435\u0441\u0430 \u0441 \u0444\u0443\u043d\u043a\u0446\u0438\u043e\u043d\u0430\u043b\u043e\u043c \u043a\u043e\u0440\u043f\u043e\u0440\u0430\u0442\u0438\u0432\u043d\u043e\u0433\u043e \u0443\u0440\u043e\u0432\u043d\u044f (\u0433\u043e\u0441\u0442\u0435\u0432\u044b\u0435 \u0441\u0435\u0442\u0438, \u0441\u0435\u0433\u043c\u0435\u043d\u0442\u0430\u0446\u0438\u044f \u0442\u0440\u0430\u0444\u0438\u043a\u0430) \u0438 \u0443\u043f\u0440\u0430\u0432\u043b\u0435\u043d\u0438\u0435\u043c \u0447\u0435\u0440\u0435\u0437 \u043e\u0431\u043b\u0430\u043a\u043e/\u043c\u043e\u0431\u0438\u043b\u044c\u043d\u044b\u0435 \u043f\u0440\u0438\u043b\u043e\u0436\u0435\u043d\u0438\u044f.\n\nCVE-2025-37103 \u0438\u043c\u0435\u0435\u0442 \u043e\u0446\u0435\u043d\u043a\u0443 CVSS v3.1: 9,8 \u0438 \u0437\u0430\u0442\u0440\u0430\u0433\u0438\u0432\u0430\u0435\u0442 \u0442\u043e\u0447\u043a\u0438 \u0434\u043e\u0441\u0442\u0443\u043f\u0430 Instant On \u0441 \u0432\u0435\u0440\u0441\u0438\u0435\u0439 \u043f\u0440\u043e\u0448\u0438\u0432\u043a\u0438 3.2.0.1 \u0438 \u043d\u0438\u0436\u0435.\n\n\u0423\u0441\u043f\u0435\u0448\u043d\u0430\u044f \u044d\u043a\u0441\u043f\u043b\u0443\u0430\u0442\u0430\u0446\u0438\u044f \u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u0438 \u043f\u043e\u0437\u0432\u043e\u043b\u044f\u0435\u0442 \u0443\u0434\u0430\u043b\u0435\u043d\u043d\u043e\u043c\u0443 \u0437\u043b\u043e\u0443\u043c\u044b\u0448\u043b\u0435\u043d\u043d\u0438\u043a\u0443 \u043f\u043e\u043b\u0443\u0447\u0438\u0442\u044c \u0430\u0434\u043c\u0438\u043d\u0438\u0441\u0442\u0440\u0430\u0442\u0438\u0432\u043d\u044b\u0439 \u0434\u043e\u0441\u0442\u0443\u043f \u043a \u0441\u0438\u0441\u0442\u0435\u043c\u0435.\n\n\u041f\u043e\u0441\u043a\u043e\u043b\u044c\u043a\u0443 \u0430\u0434\u043c\u0438\u043d\u0438\u0441\u0442\u0440\u0430\u0442\u0438\u0432\u043d\u044b\u0435 \u0443\u0447\u0435\u0442\u043d\u044b\u0435 \u0434\u0430\u043d\u043d\u044b\u0435 \u0436\u0435\u0441\u0442\u043a\u043e \u0437\u0430\u043f\u0440\u043e\u0433\u0440\u0430\u043c\u043c\u0438\u0440\u043e\u0432\u0430\u043d\u044b \u0432 \u043f\u0440\u043e\u0448\u0438\u0432\u043a\u0435, \u0434\u043b\u044f \u043e\u043f\u044b\u0442\u043d\u044b\u0445 \u043f\u043e\u043b\u044c\u0437\u043e\u0432\u0430\u0442\u0435\u043b\u0435\u0439 \u0438\u0445 \u043e\u0431\u043d\u0430\u0440\u0443\u0436\u0435\u043d\u0438\u0435 \u043d\u0435 \u043f\u0440\u0435\u0434\u0441\u0442\u0430\u0432\u043b\u044f\u0435\u0442 \u043e\u0441\u043e\u0431\u043e\u0439 \u0441\u043b\u043e\u0436\u043d\u043e\u0441\u0442\u0438.\n\n\u041f\u043e\u043b\u0443\u0447\u0438\u0432 \u0434\u043e\u0441\u0442\u0443\u043f \u043a \u0432\u0435\u0431-\u0438\u043d\u0442\u0435\u0440\u0444\u0435\u0439\u0441\u0443 \u0432 \u043a\u0430\u0447\u0435\u0441\u0442\u0432\u0435 \u0430\u0434\u043c\u0438\u043d\u0438\u0441\u0442\u0440\u0430\u0442\u043e\u0440\u043e\u0432, \u0437\u043b\u043e\u0443\u043c\u044b\u0448\u043b\u0435\u043d\u043d\u0438\u043a\u0438 \u043c\u043e\u0433\u0443\u0442 \u0438\u0437\u043c\u0435\u043d\u0438\u0442\u044c \u043d\u0430\u0441\u0442\u0440\u043e\u0439\u043a\u0438 \u0442\u043e\u0447\u043a\u0438 \u0434\u043e\u0441\u0442\u0443\u043f\u0430, \u043f\u0435\u0440\u0435\u043d\u0430\u0441\u0442\u0440\u043e\u0438\u0442\u044c \u0441\u0438\u0441\u0442\u0435\u043c\u0443 \u0431\u0435\u0437\u043e\u043f\u0430\u0441\u043d\u043e\u0441\u0442\u0438, \u0443\u0441\u0442\u0430\u043d\u043e\u0432\u0438\u0442\u044c \u0431\u044d\u043a\u0434\u043e\u0440\u044b, \u043e\u0441\u0443\u0449\u0435\u0441\u0442\u0432\u043b\u044f\u0442\u044c \u043f\u0435\u0440\u0435\u0445\u0432\u0430\u0442 \u0442\u0440\u0430\u0444\u0438\u043a\u0430 \u0438 \u0434\u0430\u0436\u0435 \u043e\u0441\u0443\u0449\u0435\u0441\u0442\u0432\u0438\u0442\u044c \u0433\u043e\u0440\u0438\u0437\u043e\u043d\u0442\u0430\u043b\u044c\u043d\u043e\u0435 \u043f\u0435\u0440\u0435\u043c\u0435\u0449\u0435\u043d\u0438\u0435.\n\n\u0423\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u044c \u0431\u044b\u043b\u0430 \u043e\u0431\u043d\u0430\u0440\u0443\u0436\u0435\u043d\u0430 \u0438\u0441\u0441\u043b\u0435\u0434\u043e\u0432\u0430\u0442\u0435\u043b\u0435\u043c ZZ \u0438\u0437 Ubisectech Sirius, \u043a\u043e\u0442\u043e\u0440\u044b\u0439 \u0441\u043e\u043e\u0431\u0449\u0438\u043b \u043e \u043d\u0435\u0439 \u043d\u0435\u043f\u043e\u0441\u0440\u0435\u0434\u0441\u0442\u0432\u0435\u043d\u043d\u043e \u043f\u043e\u0441\u0442\u0430\u0432\u0449\u0438\u043a\u0443.\n\n\u0412 \u0442\u043e\u043c \u0436\u0435 \u0431\u044e\u043b\u043b\u0435\u0442\u0435\u043d\u0435 HPE \u0443\u043a\u0430\u0437\u044b\u0432\u0430\u0435\u0442 \u043d\u0430 \u0432\u0442\u043e\u0440\u0443\u044e \u0441\u0435\u0440\u044c\u0451\u0437\u043d\u0443\u044e CVE-2025-37102, \u0441\u0432\u044f\u0437\u0430\u043d\u043d\u0443\u044e \u0441 \u0430\u0443\u0442\u0435\u043d\u0442\u0438\u0444\u0438\u0446\u0438\u0440\u043e\u0432\u0430\u043d\u043d\u044b\u043c \u0432\u043d\u0435\u0434\u0440\u0435\u043d\u0438\u0435\u043c \u043a\u043e\u043c\u0430\u043d\u0434 \u0432 \u0438\u043d\u0442\u0435\u0440\u0444\u0435\u0439\u0441 \u043a\u043e\u043c\u0430\u043d\u0434\u043d\u043e\u0439 \u0441\u0442\u0440\u043e\u043a\u0438 (CLI) \u0442\u043e\u0447\u0435\u043a \u0434\u043e\u0441\u0442\u0443\u043f\u0430 Aruba Instant On.\n\n\u0415\u0435 \u043c\u043e\u0436\u043d\u043e \u0441\u0432\u044f\u0437\u0430\u0442\u044c \u0441 CVE-2025-37103, \u043f\u043e\u0441\u043a\u043e\u043b\u044c\u043a\u0443 \u0434\u043b\u044f \u0435\u0435 \u044d\u043a\u0441\u043f\u043b\u0443\u0430\u0442\u0430\u0446\u0438\u0438 \u0442\u0440\u0435\u0431\u0443\u044e\u0442\u0441\u044f \u043f\u0440\u0430\u0432\u0430 \u0430\u0434\u043c\u0438\u043d\u0438\u0441\u0442\u0440\u0430\u0442\u043e\u0440\u0430, \u0447\u0442\u043e \u043f\u043e\u0437\u0432\u043e\u043b\u044f\u0435\u0442 \u0437\u043b\u043e\u0443\u043c\u044b\u0448\u043b\u0435\u043d\u043d\u0438\u043a\u0430\u043c \u0432\u0432\u043e\u0434\u0438\u0442\u044c \u043f\u0440\u043e\u0438\u0437\u0432\u043e\u043b\u044c\u043d\u044b\u0435 \u043a\u043e\u043c\u0430\u043d\u0434\u044b \u0432 CLI \u0434\u043b\u044f \u0438\u0437\u0432\u043b\u0435\u0447\u0435\u043d\u0438\u044f \u0434\u0430\u043d\u043d\u044b\u0445, \u043e\u0442\u043a\u043b\u044e\u0447\u0435\u043d\u0438\u044f \u0431\u0435\u0437\u043e\u043f\u0430\u0441\u043d\u043e\u0441\u0442\u0438 \u0438 \u043e\u0431\u0435\u0441\u043f\u0435\u0447\u0435\u043d\u0438\u044f \u0443\u0441\u0442\u043e\u0439\u0447\u0438\u0432\u043e\u0441\u0442\u0438.\n\n\u041e\u0431\u0435 \u043f\u0440\u043e\u0431\u043b\u0435\u043c\u044b \u0440\u0435\u0448\u0430\u044e\u0442\u0441\u044f \u043e\u0431\u043d\u043e\u0432\u043b\u0435\u043d\u0438\u0435\u043c \u043f\u0440\u043e\u0448\u0438\u0432\u043a\u0438 \u0434\u043e \u0432\u0435\u0440\u0441\u0438\u0438 3.2.1.0 (\u0438\u043b\u0438 \u0431\u043e\u043b\u0435\u0435 \u043f\u043e\u0437\u0434\u043d\u0435\u0439), \u043e\u0431\u0445\u043e\u0434\u043d\u044b\u0435 \u043f\u0443\u0442\u0438 \u043e\u0442\u0441\u0443\u0442\u0441\u0442\u0432\u0443\u044e\u0442.\n\nHPE Aruba Networking \u043d\u0435 \u0440\u0430\u0441\u043f\u043e\u043b\u0430\u0433\u0430\u0435\u0442 \u0438\u043d\u0444\u043e\u0440\u043c\u0430\u0446\u0438\u0435\u0439 \u043e\u0431 \u044d\u043a\u0441\u043f\u043b\u0443\u0430\u0442\u0430\u0446\u0438\u0438 \u044d\u0442\u0438\u0445 \u0434\u0432\u0443\u0445 \u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u0435\u0439, \u043e\u0434\u043d\u0430\u043a\u043e, \u043a\u0430\u043a \u043f\u043e\u043b\u0430\u0433\u0430\u0435\u0442 \u043f\u043e\u0441\u0442\u0430\u0432\u0449\u0438\u043a, \u0441\u0438\u0442\u0443\u0430\u0446\u0438\u044f \u043c\u043e\u0436\u0435\u0442 \u0431\u044b\u0441\u0442\u0440\u043e \u0438\u0437\u043c\u0435\u043d\u0438\u0442\u044c\u0441\u044f.", "creation_timestamp": "2025-07-22T16:53:21.000000Z"}, {"uuid": "0813070b-0f95-4628-9392-3a9bd6829f28", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37103", "type": "published-proof-of-concept", "source": "https://t.me/thehackernews/7190", "content": "\ud83d\udea8 HPE Wi-Fi gear shipped with hardcoded admin logins.\n\nCVE-2025-37103 scores 9.8/10\u2014no password needed to hijack your network.\n\nIt can be chained with a second bug for full system takeover.\n\nFull details \u2192 https://thehackernews.com/2025/07/hard-coded-credentials-found-in-hpe.html", "creation_timestamp": "2025-07-21T04:03:28.000000Z"}, {"uuid": "7a3925cd-1b95-4583-9342-6d75a4b96517", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37899", "type": "seen", "source": "https://t.me/linkersec/318", "content": "How I used o3 to find CVE-2025-37899, a remote zeroday vulnerability in the Linux kernel's SMB implementation\n\nArticle by Sean Heelan about rediscovering a bug in the ksmbd module via the OpenAI's o3 model and then finding a 0-day vulnerability as well.\n\nThe researcher had to rerun the prompt multiple times before getting a true-positive result. The o3 model managed to find the 0-day vulnerability in only ~1 out of 50 runs.", "creation_timestamp": "2025-06-06T14:29:17.000000Z"}, {"uuid": "b67ebc38-0328-41a0-8ef5-3278cdeaca12", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37752", "type": "published-proof-of-concept", "source": "https://t.me/linkersec/314", "content": "[CVE-2025-37752] Two Bytes Of Madness: Pwning The Linux Kernel With A 0x0000 Written 262636 Bytes Out-Of-Bounds\n\nGreat article by D3vil about exploiting a type confusion in the network scheduler subsystem and pwning all kernelCTF instances.\n\nAuthor exploited a severely-limited OOB side-effect of the bug to corrupt pipe_inode_info->tmp_page and gain a page UAF read/write primitive. Researcher then swapped the private_data and f_cred fields of a signalfd file structure and overwrote the credentials via signalfd_ctx.", "creation_timestamp": "2025-05-13T20:33:47.000000Z"}, {"uuid": "29194baf-7e96-4522-941e-74f825cbc989", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37778", "type": "seen", "source": "https://t.me/kasperskylab_ru/6229", "content": "\u0412 \u043d\u043e\u0432\u043e\u043c #kaspersky_securityweek:\n\n\ud83d\udd18 \u0412 \u0445\u043e\u0434\u0435 \u044d\u043a\u0441\u043f\u0435\u0440\u0438\u043c\u0435\u043d\u0442\u0430 \u043f\u043e \u043f\u043e\u0438\u0441\u043a\u0443 \u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u0435\u0439 \u0441 \u043f\u043e\u043c\u043e\u0449\u044c\u044e LLM \u043e\u0431\u043d\u0430\u0440\u0443\u0436\u0435\u043d\u0430 \u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u044c \u0442\u0438\u043f\u0430 Use-After-Free \u0432 \u044f\u0434\u0440\u0435 Linux. \u0418\u0441\u0441\u043b\u0435\u0434\u043e\u0432\u0430\u0442\u0435\u043b\u044c \u0437\u0430\u0441\u0442\u0430\u0432\u043b\u044f\u043b \u043d\u0435\u0439\u0440\u043e\u0441\u0435\u0442\u044c \u0430\u043d\u0430\u043b\u0438\u0437\u0438\u0440\u043e\u0432\u0430\u0442\u044c \u043a\u043e\u0434, \u0432 \u043a\u043e\u0442\u043e\u0440\u043e\u043c \u0443\u0436\u0435 \u0431\u044b\u043b\u0430 \u0432\u0440\u0443\u0447\u043d\u0443\u044e \u043e\u0431\u043d\u0430\u0440\u0443\u0436\u0435\u043d\u0430 CVE-2025-37778. \u041f\u0440\u043e\u0433\u043d\u0430\u0432 \u0437\u0430\u043f\u0440\u043e\u0441 \u0441\u0442\u043e \u0440\u0430\u0437 \u0438 \u0438\u0437\u0443\u0447\u0438\u0432 \u043f\u043e\u043b\u0443\u0447\u0435\u043d\u043d\u044b\u0435 \u043e\u0442 \u044f\u0437\u044b\u043a\u043e\u0432\u043e\u0439 \u043c\u043e\u0434\u0435\u043b\u0438 \u043e\u0442\u0447\u0451\u0442\u044b, \u0441\u043f\u0435\u0446\u0438\u0430\u043b\u0438\u0441\u0442 \u043e\u0431\u043d\u0430\u0440\u0443\u0436\u0438\u043b, \u0447\u0442\u043e CVE-2025-37778 \u043d\u0435\u0439\u0440\u043e\u0441\u0435\u0442\u044c \u043d\u0430\u0448\u043b\u0430 \u0432\u0441\u0435\u0433\u043e \u043e\u0434\u0438\u043d \u0440\u0430\u0437, \u043d\u043e \u0441\u0440\u0435\u0434\u0438 \u043c\u0430\u0441\u0441\u044b \u0433\u0430\u043b\u043b\u044e\u0446\u0438\u043d\u0430\u0446\u0438\u0439 \u0438 \u0440\u0435\u043f\u043e\u0440\u0442\u043e\u0432 \u043e\u0431 \u043e\u0442\u0441\u0443\u0442\u0441\u0442\u0432\u0438\u0438 \u043f\u0440\u043e\u0431\u043b\u0435\u043c \u043e\u0431\u043d\u0430\u0440\u0443\u0436\u0438\u043b\u0441\u044f \u043e\u0442\u0447\u0451\u0442 \u0438 \u043e\u0431 \u0435\u0449\u0435 \u043e\u0434\u043d\u043e\u0439 \u0440\u0435\u0430\u043b\u044c\u043d\u043e\u0439, \u043d\u043e \u0440\u0430\u043d\u0435\u0435 \u043d\u0435\u0438\u0437\u0432\u0435\u0441\u0442\u043d\u043e\u0439 \u043f\u0440\u043e\u0431\u043b\u0435\u043c\u0435. \u041e\u043d\u0430 \u043f\u043e\u043b\u0443\u0447\u0438\u043b\u0430 \u0438\u0434\u0435\u043d\u0442\u0438\u0444\u0438\u043a\u0430\u0442\u043e\u0440 CVE-2025-37899.\n\n\ud83d\udd18 \u042d\u043a\u0441\u043f\u0435\u0440\u0442\u044b \u00ab\u041b\u0430\u0431\u043e\u0440\u0430\u0442\u043e\u0440\u0438\u0438 \u041a\u0430\u0441\u043f\u0435\u0440\u0441\u043a\u043e\u0433\u043e\u00bb \u043f\u0440\u043e\u0430\u043d\u0430\u043b\u0438\u0437\u0438\u0440\u043e\u0432\u0430\u043b\u0438 \u043c\u0430\u0441\u0441\u043e\u0432\u043e\u0435 \u0437\u0430\u0440\u0430\u0436\u0435\u043d\u0438\u0435 \u043a\u043e\u043d\u0442\u0435\u0439\u043d\u0435\u0440\u0438\u0437\u043e\u0432\u0430\u043d\u043d\u044b\u0445 \u0441\u0440\u0435\u0434 \u0447\u0435\u0440\u0435\u0437 \u043e\u0442\u043a\u0440\u044b\u0442\u044b\u0439 API Docker \u0438 \u0440\u0430\u0437\u043e\u0431\u0440\u0430\u043b\u0438 \u0430\u0442\u0430\u043a\u0438 \u043d\u0430 \u0440\u043e\u0441\u0441\u0438\u0439\u0441\u043a\u0438\u0435 \u043e\u0440\u0433\u0430\u043d\u0438\u0437\u0430\u0446\u0438\u0438 \u0441 \u0438\u0441\u043f\u043e\u043b\u044c\u0437\u043e\u0432\u0430\u043d\u0438\u0435\u043c \u0431\u044d\u043a\u0434\u043e\u0440\u0430 PureRAT.\n\n\ud83d\udd18 \u0412 \u043e\u0442\u0432\u0435\u0442 \u043d\u0430 \u0432\u043d\u0435\u0434\u0440\u0435\u043d\u0438\u0435 \u0441\u043f\u043e\u0440\u043d\u043e\u0439 \u0444\u0438\u0447\u0438 Microsoft Recall \u0440\u0430\u0437\u0440\u0430\u0431\u043e\u0442\u0447\u0438\u043a\u0438 \u043c\u0435\u0441\u0441\u0435\u043d\u0434\u0436\u0435\u0440\u0430 Signal \u0434\u043e\u0431\u0430\u0432\u0438\u043b\u0438 \u0432 \u043d\u0430\u0441\u0442\u0440\u043e\u0439\u043a\u0438 Windows-\u0432\u0435\u0440\u0441\u0438\u0438 \u0432\u043e\u0437\u043c\u043e\u0436\u043d\u043e\u0441\u0442\u044c \u0437\u0430\u043f\u0440\u0435\u0442\u0438\u0442\u044c \u0441\u043d\u0438\u043c\u0430\u0442\u044c \u0441\u043a\u0440\u0438\u043d\u0448\u043e\u0442\u044b \u043f\u0440\u0438\u043b\u043e\u0436\u0435\u043d\u0438\u044f. \u0412 Windows 11 \u044d\u0442\u0430 \u043d\u0430\u0441\u0442\u0440\u043e\u0439\u043a\u0430 \u0432\u043a\u043b\u044e\u0447\u0430\u0435\u0442\u0441\u044f \u043f\u043e \u0443\u043c\u043e\u043b\u0447\u0430\u043d\u0438\u044e.", "creation_timestamp": "2025-05-27T11:54:25.000000Z"}, {"uuid": "8c99d664-056c-4837-b1dd-b135ee8046e2", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37899", "type": "seen", "source": "https://t.me/kasperskylab_ru/6229", "content": "\u0412 \u043d\u043e\u0432\u043e\u043c #kaspersky_securityweek:\n\n\ud83d\udd18 \u0412 \u0445\u043e\u0434\u0435 \u044d\u043a\u0441\u043f\u0435\u0440\u0438\u043c\u0435\u043d\u0442\u0430 \u043f\u043e \u043f\u043e\u0438\u0441\u043a\u0443 \u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u0435\u0439 \u0441 \u043f\u043e\u043c\u043e\u0449\u044c\u044e LLM \u043e\u0431\u043d\u0430\u0440\u0443\u0436\u0435\u043d\u0430 \u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u044c \u0442\u0438\u043f\u0430 Use-After-Free \u0432 \u044f\u0434\u0440\u0435 Linux. \u0418\u0441\u0441\u043b\u0435\u0434\u043e\u0432\u0430\u0442\u0435\u043b\u044c \u0437\u0430\u0441\u0442\u0430\u0432\u043b\u044f\u043b \u043d\u0435\u0439\u0440\u043e\u0441\u0435\u0442\u044c \u0430\u043d\u0430\u043b\u0438\u0437\u0438\u0440\u043e\u0432\u0430\u0442\u044c \u043a\u043e\u0434, \u0432 \u043a\u043e\u0442\u043e\u0440\u043e\u043c \u0443\u0436\u0435 \u0431\u044b\u043b\u0430 \u0432\u0440\u0443\u0447\u043d\u0443\u044e \u043e\u0431\u043d\u0430\u0440\u0443\u0436\u0435\u043d\u0430 CVE-2025-37778. \u041f\u0440\u043e\u0433\u043d\u0430\u0432 \u0437\u0430\u043f\u0440\u043e\u0441 \u0441\u0442\u043e \u0440\u0430\u0437 \u0438 \u0438\u0437\u0443\u0447\u0438\u0432 \u043f\u043e\u043b\u0443\u0447\u0435\u043d\u043d\u044b\u0435 \u043e\u0442 \u044f\u0437\u044b\u043a\u043e\u0432\u043e\u0439 \u043c\u043e\u0434\u0435\u043b\u0438 \u043e\u0442\u0447\u0451\u0442\u044b, \u0441\u043f\u0435\u0446\u0438\u0430\u043b\u0438\u0441\u0442 \u043e\u0431\u043d\u0430\u0440\u0443\u0436\u0438\u043b, \u0447\u0442\u043e CVE-2025-37778 \u043d\u0435\u0439\u0440\u043e\u0441\u0435\u0442\u044c \u043d\u0430\u0448\u043b\u0430 \u0432\u0441\u0435\u0433\u043e \u043e\u0434\u0438\u043d \u0440\u0430\u0437, \u043d\u043e \u0441\u0440\u0435\u0434\u0438 \u043c\u0430\u0441\u0441\u044b \u0433\u0430\u043b\u043b\u044e\u0446\u0438\u043d\u0430\u0446\u0438\u0439 \u0438 \u0440\u0435\u043f\u043e\u0440\u0442\u043e\u0432 \u043e\u0431 \u043e\u0442\u0441\u0443\u0442\u0441\u0442\u0432\u0438\u0438 \u043f\u0440\u043e\u0431\u043b\u0435\u043c \u043e\u0431\u043d\u0430\u0440\u0443\u0436\u0438\u043b\u0441\u044f \u043e\u0442\u0447\u0451\u0442 \u0438 \u043e\u0431 \u0435\u0449\u0435 \u043e\u0434\u043d\u043e\u0439 \u0440\u0435\u0430\u043b\u044c\u043d\u043e\u0439, \u043d\u043e \u0440\u0430\u043d\u0435\u0435 \u043d\u0435\u0438\u0437\u0432\u0435\u0441\u0442\u043d\u043e\u0439 \u043f\u0440\u043e\u0431\u043b\u0435\u043c\u0435. \u041e\u043d\u0430 \u043f\u043e\u043b\u0443\u0447\u0438\u043b\u0430 \u0438\u0434\u0435\u043d\u0442\u0438\u0444\u0438\u043a\u0430\u0442\u043e\u0440 CVE-2025-37899.\n\n\ud83d\udd18 \u042d\u043a\u0441\u043f\u0435\u0440\u0442\u044b \u00ab\u041b\u0430\u0431\u043e\u0440\u0430\u0442\u043e\u0440\u0438\u0438 \u041a\u0430\u0441\u043f\u0435\u0440\u0441\u043a\u043e\u0433\u043e\u00bb \u043f\u0440\u043e\u0430\u043d\u0430\u043b\u0438\u0437\u0438\u0440\u043e\u0432\u0430\u043b\u0438 \u043c\u0430\u0441\u0441\u043e\u0432\u043e\u0435 \u0437\u0430\u0440\u0430\u0436\u0435\u043d\u0438\u0435 \u043a\u043e\u043d\u0442\u0435\u0439\u043d\u0435\u0440\u0438\u0437\u043e\u0432\u0430\u043d\u043d\u044b\u0445 \u0441\u0440\u0435\u0434 \u0447\u0435\u0440\u0435\u0437 \u043e\u0442\u043a\u0440\u044b\u0442\u044b\u0439 API Docker \u0438 \u0440\u0430\u0437\u043e\u0431\u0440\u0430\u043b\u0438 \u0430\u0442\u0430\u043a\u0438 \u043d\u0430 \u0440\u043e\u0441\u0441\u0438\u0439\u0441\u043a\u0438\u0435 \u043e\u0440\u0433\u0430\u043d\u0438\u0437\u0430\u0446\u0438\u0438 \u0441 \u0438\u0441\u043f\u043e\u043b\u044c\u0437\u043e\u0432\u0430\u043d\u0438\u0435\u043c \u0431\u044d\u043a\u0434\u043e\u0440\u0430 PureRAT.\n\n\ud83d\udd18 \u0412 \u043e\u0442\u0432\u0435\u0442 \u043d\u0430 \u0432\u043d\u0435\u0434\u0440\u0435\u043d\u0438\u0435 \u0441\u043f\u043e\u0440\u043d\u043e\u0439 \u0444\u0438\u0447\u0438 Microsoft Recall \u0440\u0430\u0437\u0440\u0430\u0431\u043e\u0442\u0447\u0438\u043a\u0438 \u043c\u0435\u0441\u0441\u0435\u043d\u0434\u0436\u0435\u0440\u0430 Signal \u0434\u043e\u0431\u0430\u0432\u0438\u043b\u0438 \u0432 \u043d\u0430\u0441\u0442\u0440\u043e\u0439\u043a\u0438 Windows-\u0432\u0435\u0440\u0441\u0438\u0438 \u0432\u043e\u0437\u043c\u043e\u0436\u043d\u043e\u0441\u0442\u044c \u0437\u0430\u043f\u0440\u0435\u0442\u0438\u0442\u044c \u0441\u043d\u0438\u043c\u0430\u0442\u044c \u0441\u043a\u0440\u0438\u043d\u0448\u043e\u0442\u044b \u043f\u0440\u0438\u043b\u043e\u0436\u0435\u043d\u0438\u044f. \u0412 Windows 11 \u044d\u0442\u0430 \u043d\u0430\u0441\u0442\u0440\u043e\u0439\u043a\u0430 \u0432\u043a\u043b\u044e\u0447\u0430\u0435\u0442\u0441\u044f \u043f\u043e \u0443\u043c\u043e\u043b\u0447\u0430\u043d\u0438\u044e.", "creation_timestamp": "2025-05-27T11:54:25.000000Z"}, {"uuid": "65276dd1-4072-4c93-92c7-1dee67c609e3", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37089", "type": "seen", "source": "Telegram/gkh687utgOctgjszmsMxTUPnrLH3iSmfkgQMbemL6f96aIw", "content": "", "creation_timestamp": "2025-06-02T14:00:51.000000Z"}, {"uuid": "51af1e55-7af4-4270-9925-3a57b0b6728f", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37093", "type": "seen", "source": "Telegram/7xIhyJO7Z_WQeZYOmdLINMZ_9FIiDPF6RfLVlvHuHgi-enE", "content": "", "creation_timestamp": "2025-06-02T15:01:46.000000Z"}, {"uuid": "08ee5fa9-c2b0-4eff-8a23-6b5fcb447fdb", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37096", "type": "seen", "source": "Telegram/7xIhyJO7Z_WQeZYOmdLINMZ_9FIiDPF6RfLVlvHuHgi-enE", "content": "", "creation_timestamp": "2025-06-02T15:01:46.000000Z"}, {"uuid": "02ebb358-6b1c-4d93-87df-d2ce124395a5", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37091", "type": "seen", "source": "Telegram/7xIhyJO7Z_WQeZYOmdLINMZ_9FIiDPF6RfLVlvHuHgi-enE", "content": "", "creation_timestamp": "2025-06-02T15:01:46.000000Z"}, {"uuid": "f06cb1b3-9e8e-4ffb-bc9b-0f4903306587", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37092", "type": "seen", "source": "Telegram/7xIhyJO7Z_WQeZYOmdLINMZ_9FIiDPF6RfLVlvHuHgi-enE", "content": "", "creation_timestamp": "2025-06-02T15:01:46.000000Z"}, {"uuid": "ef76e8ff-547b-40f6-915a-8a4186683cb7", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37899", "type": "published-proof-of-concept", "source": "https://t.me/CyberSecurityIL/69950", "content": "\u05d4\u05de\u05db\u05d5\u05e0\u05d5\u05ea \u05dc\u05d0 \u05e2\u05d5\u05de\u05d3\u05d5\u05ea \u05dc\u05d4\u05d7\u05dc\u05d9\u05e3 \u05d0\u05d5\u05ea\u05da. \u05dc\u05de\u05e2\u05e9\u05d4, \u05d6\u05d4 \u05d1\u05d3\u05d9\u05d5\u05e7 \u05d4\u05d4\u05e4\u05da, \u05d4\u05df \u05e0\u05de\u05e6\u05d0\u05d5\u05ea \u05db\u05e2\u05ea \u05d1\u05e9\u05dc\u05d1 \u05e9\u05d1\u05d5 \u05d4\u05df \u05d9\u05db\u05d5\u05dc\u05d5\u05ea \u05dc\u05d4\u05e4\u05d5\u05da \u05d0\u05d5\u05ea\u05da \u05dc\u05d9\u05e2\u05d9\u05dc \u05d5\u05d0\u05e4\u05e7\u05d8\u05d9\u05d1\u05d9 \u05de\u05e9\u05de\u05e2\u05d5\u05ea\u05d9\u05ea \u05d9\u05d5\u05ea\u05e8.\n\n\u05d0\u05ea \u05d4\u05de\u05e9\u05e4\u05d8 \u05d4\u05d1\u05d0 \u05db\u05ea\u05d1 \u05d7\u05d5\u05e7\u05e8 \u05d0\u05d1\u05d8\u05f4\u05de \u05d4\u05de\u05ea\u05d0\u05e8 \u05db\u05d9\u05e6\u05d3 \u05de\u05d5\u05d3\u05dc o3 \u05e9\u05dc OpenAI \u05d6\u05d9\u05d4\u05d4 \u05d7\u05d5\u05dc\u05e9\u05ea 0-day \u05d1-Linux kernel.\n\n\u05d4\u05d7\u05d5\u05e7\u05e8 \u05d8\u05d5\u05e2\u05df \u05db\u05d9 \u05d4\u05d7\u05d5\u05dc\u05e9\u05d4 (CVE-2025-37899) \u05d4\u05d9\u05e0\u05d4 \u05d4\u05e8\u05d0\u05e9\u05d5\u05e0\u05d4 \u05e9\u05d6\u05d5\u05d4\u05ea\u05d4 \u05d1\u05d0\u05d5\u05e4\u05df \u05d8\u05d1\u05e2\u05d9 \u05e2\u05dc \u05d9\u05d3\u05d9 \u05de\u05d5\u05d3\u05dc \u05d1\u05d9\u05e0\u05d4 \u05de\u05dc\u05d0\u05db\u05d5\u05ea\u05d9\u05ea.\n\n\u05d0\u05d6 \u05e0\u05db\u05d5\u05df, \u05db\u05e8\u05d2\u05e2 \u05dc\u05d0 \u05de\u05d3\u05d5\u05d1\u05e8 \u05d1\u05d7\u05d5\u05dc\u05e9\u05d4 \u05e2\u05dd CVSS \u05d2\u05d1\u05d5\u05d4, \u05d0\u05d1\u05dc \u05d0\u05dd \u05d0\u05ea\u05dd \u05d7\u05d5\u05e7\u05e8\u05d9 \u05d0\u05d1\u05d8\u05f4\u05de \u05d0\u05ea\u05dd \u05d7\u05d9\u05d9\u05d1\u05d9\u05dd \u05dc\u05e9\u05d0\u05d5\u05dc \u05d0\u05ea \u05e2\u05e6\u05de\u05db\u05dd \u05db\u05d9\u05e6\u05d3 \u05d1\u05d9\u05e0\u05d4 \u05de\u05dc\u05d0\u05db\u05d5\u05ea\u05d9\u05ea \u05d4\u05d5\u05dc\u05db\u05ea \u05dc\u05e9\u05de\u05e9 \u05d0\u05ea\u05db\u05dd \u05d1\u05e2\u05d1\u05d5\u05d3\u05d4 \u05d4\u05e9\u05d5\u05d8\u05e4\u05ea \u05e9\u05dc\u05db\u05dd, \u05d5\u05de\u05d4 \u05d4\u05e1\u05d9\u05d1\u05d4 \u05e9\u05dc\u05d0 \u05ea\u05d5\u05d7\u05dc\u05e4\u05d5 \u05d1\u05de\u05d5\u05d3\u05dc \u05db\u05d6\u05d4 \u05d1\u05e9\u05dc\u05d1 \u05e9\u05d1\u05d5 \u05d4\u05de\u05d5\u05d3\u05dc\u05d9\u05dd \u05d9\u05d4\u05d9\u05d5 \u05de\u05e1\u05e4\u05d9\u05e7 \u05d7\u05db\u05de\u05d9\u05dd...\n\n\u05d0\u05dd \u05d1\u05d0 \u05dc\u05db\u05dd \u05dc\u05d4\u05ea\u05e2\u05de\u05e7 \u05d1\u05e4\u05e8\u05d8\u05d9\u05dd \u05d4\u05d8\u05db\u05e0\u05d9\u05d9\u05dd \u05e9\u05dc \u05d4\u05d7\u05d5\u05dc\u05e9\u05d4 \u05d5\u05d4\u05ea\u05d4\u05dc\u05d9\u05da \u05dc\u05de\u05e6\u05d9\u05d0\u05ea\u05d4 \u05de\u05d5\u05d6\u05de\u05e0\u05d9\u05dd \u05dc\u05e7\u05e8\u05d5\u05d0 \u05d0\u05ea \u05d6\u05d4 \u05d1\u05e4\u05d5\u05e1\u05d8 \u05d4\u05de\u05e7\u05d5\u05e8\u05d9 \u05e9\u05dc \u05d4\u05d7\u05d5\u05e7\u05e8.", "creation_timestamp": "2025-05-26T11:12:30.000000Z"}, {"uuid": "a47094ac-752e-4d9d-bc67-ff81ac4646bb", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3794", "type": "seen", "source": "https://t.me/true_secator/7102", "content": "Hewlett Packard Enterprise (HPE) \u0432 \u0441\u0432\u043e\u0435\u043c \u043d\u043e\u0432\u043e\u043c \u0431\u044e\u043b\u043b\u0435\u0442\u0435\u043d\u0435 \u043f\u043e \u0431\u0435\u0437\u043e\u043f\u0430\u0441\u043d\u043e\u0441\u0442\u0438 \u043f\u0440\u0435\u0434\u0443\u043f\u0440\u0435\u0436\u0434\u0430\u0435\u0442 \u043e \u0432\u043e\u0441\u044c\u043c\u0438 \u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u044f\u0445, \u0432\u043b\u0438\u044f\u044e\u0449\u0438\u0445 \u043d\u0430 \u0440\u0430\u0431\u043e\u0442\u0443 StoreOnce, \u0440\u0435\u0448\u0435\u043d\u0438\u044f \u0434\u043b\u044f \u0440\u0435\u0437\u0435\u0440\u0432\u043d\u043e\u0433\u043e \u043a\u043e\u043f\u0438\u0440\u043e\u0432\u0430\u043d\u0438\u044f \u0438 \u0434\u0435\u0434\u0443\u043f\u043b\u0438\u043a\u0430\u0446\u0438\u0438 \u043d\u0430 \u043e\u0441\u043d\u043e\u0432\u0435 \u0434\u0438\u0441\u043a\u043e\u0432.\n\nHPE StoreOnce \u043e\u0431\u044b\u0447\u043d\u043e \u0438\u0441\u043f\u043e\u043b\u044c\u0437\u0443\u0435\u0442\u0441\u044f \u0434\u043b\u044f \u0440\u0435\u0437\u0435\u0440\u0432\u043d\u043e\u0433\u043e \u043a\u043e\u043f\u0438\u0440\u043e\u0432\u0430\u043d\u0438\u044f \u0438 \u0432\u043e\u0441\u0441\u0442\u0430\u043d\u043e\u0432\u043b\u0435\u043d\u0438\u044f \u043d\u0430 \u043a\u0440\u0443\u043f\u043d\u044b\u0445 \u043f\u0440\u0435\u0434\u043f\u0440\u0438\u044f\u0442\u0438\u044f\u0445, \u0432 \u0426\u041e\u0414\u0430\u0445, \u0443 \u043f\u043e\u0441\u0442\u0430\u0432\u0449\u0438\u043a\u043e\u0432 \u043e\u0431\u043b\u0430\u0447\u043d\u044b\u0445 \u0443\u0441\u043b\u0443\u0433 \u0438 \u0432 \u0446\u0435\u043b\u043e\u043c \u0432 \u043e\u0440\u0433\u0430\u043d\u0438\u0437\u0430\u0446\u0438\u044f\u0445, \u043e\u0431\u0440\u0430\u0431\u0430\u0442\u044b\u0432\u0430\u044e\u0449\u0438\u0445 \u0431\u043e\u043b\u044c\u0448\u0438\u0435 \u0434\u0430\u043d\u043d\u044b\u0435 \u0438\u043b\u0438 \u043a\u0440\u0443\u043f\u043d\u044b\u0435 \u0432\u0438\u0440\u0442\u0443\u0430\u043b\u0438\u0437\u0438\u0440\u043e\u0432\u0430\u043d\u043d\u044b\u0435 \u0441\u0440\u0435\u0434\u044b.\n\nStoreOnce \u0438\u043d\u0442\u0435\u0433\u0440\u0438\u0440\u0443\u0435\u0442\u0441\u044f \u0441 \u041f\u041e \u0434\u043b\u044f \u0440\u0435\u0437\u0435\u0440\u0432\u043d\u043e\u0433\u043e \u043a\u043e\u043f\u0438\u0440\u043e\u0432\u0430\u043d\u0438\u044f, \u0432\u043a\u043b\u044e\u0447\u0430\u044f HPE Data Protector, Veeam, Commvault \u0438 Veritas NetBackup, \u043e\u0431\u0435\u0441\u043f\u0435\u0447\u0438\u0432\u0430\u044f \u043d\u0435\u043f\u0440\u0435\u0440\u044b\u0432\u043d\u043e\u0441\u0442\u044c \u0431\u0438\u0437\u043d\u0435\u0441\u0430 \u0438 \u044d\u0444\u0444\u0435\u043a\u0442\u0438\u0432\u043d\u043e\u0435 \u0443\u043f\u0440\u0430\u0432\u043b\u0435\u043d\u0438\u0435 \u0440\u0435\u0437\u0435\u0440\u0432\u043d\u044b\u043c \u043a\u043e\u043f\u0438\u0440\u043e\u0432\u0430\u043d\u0438\u0435\u043c.\n\n\u041e\u0441\u043e\u0431\u043e\u0435 \u0432\u043d\u0438\u043c\u0430\u043d\u0438\u0435 \u0441\u043b\u0435\u0434\u0443\u0435\u0442 \u043e\u0431\u0440\u0430\u0442\u0438\u0442\u044c \u043d\u0430 \u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u044c \u043e\u0431\u0445\u043e\u0434\u0430 \u0430\u0443\u0442\u0435\u043d\u0442\u0438\u0444\u0438\u043a\u0430\u0446\u0438\u0438 \u043a\u0440\u0438\u0442\u0438\u0447\u0435\u0441\u043a\u043e\u0439 \u0441\u0442\u0435\u043f\u0435\u043d\u0438 \u0441\u0435\u0440\u044c\u0435\u0437\u043d\u043e\u0441\u0442\u0438 (CVSS v3.1: 9,8), \u043a\u043e\u0442\u043e\u0440\u0430\u044f \u043e\u0442\u0441\u043b\u0435\u0436\u0438\u0432\u0430\u0435\u0442\u0441\u044f \u043a\u0430\u043a CVE-2025-37093.\n\n\u041a\u0440\u043e\u043c\u0435 \u0442\u043e\u0433\u043e, \u0438\u0441\u043f\u0440\u0430\u0432\u043b\u0435\u043d\u044b \u0447\u0435\u0442\u044b\u0440\u0435 RCE (CVE-2025-37089, 37091, 37092, 37096), \u0434\u0432\u0435 \u043f\u0440\u043e\u0431\u043b\u0435\u043c\u044b \u043e\u0431\u0445\u043e\u0434\u0430 \u043a\u0430\u0442\u0430\u043b\u043e\u0433\u043e\u0432 (CVE-2025-37094 \u0438 CVE-2025-37095) \u0438 \u043f\u0440\u043e\u0431\u043b\u0435\u043c\u0430 \u043f\u043e\u0434\u0434\u0435\u043b\u043a\u0438 \u0437\u0430\u043f\u0440\u043e\u0441\u043e\u0432 \u043d\u0430 \u0441\u0442\u043e\u0440\u043e\u043d\u0435 \u0441\u0435\u0440\u0432\u0435\u0440\u0430 (CVE-2025-37090).\n\n\u0417\u0430\u0442\u0440\u043e\u043d\u0443\u0442\u044b \u0432\u0441\u0435 \u0432\u0435\u0440\u0441\u0438\u0438 HPE StoreOnce \u0434\u043e 4.3.11, \u043a\u043e\u0442\u043e\u0440\u0430\u044f \u0442\u0435\u043f\u0435\u0440\u044c \u044f\u0432\u043b\u044f\u0435\u0442\u0441\u044f \u0440\u0435\u043a\u043e\u043c\u0435\u043d\u0434\u0443\u0435\u043c\u043e\u0439 \u0432\u0435\u0440\u0441\u0438\u0435\u0439 \u043e\u0431\u043d\u043e\u0432\u043b\u0435\u043d\u0438\u044f. \u041d\u0430 \u044d\u0442\u043e\u0442 \u0440\u0430\u0437 \u043f\u043e\u0434\u0440\u043e\u0431\u043d\u043e\u0441\u0442\u0435\u0439 \u043e \u043d\u0435\u0434\u043e\u0441\u0442\u0430\u0442\u043a\u0430\u0445 \u0440\u0430\u0441\u043a\u0440\u044b\u0442\u043e \u043d\u0435 \u0442\u0430\u043a \u043c\u043d\u043e\u0433\u043e.\n\n\u041e\u0434\u043d\u0430\u043a\u043e Zero Day Initiative (ZDI) \u0443\u043f\u043e\u043c\u0438\u043d\u0430\u0435\u0442, \u0447\u0442\u043e \u043a\u0440\u0438\u0442\u0438\u0447\u0435\u0441\u043a\u0430\u044f CVE-2025-37093 \u0441\u0432\u044f\u0437\u0430\u043d\u0430 \u0441 machineAccountCheck \u0438 \u044f\u0432\u043b\u044f\u0435\u0442\u0441\u044f \u0440\u0435\u0437\u0443\u043b\u044c\u0442\u0430\u0442\u043e\u043c \u043d\u0435\u043f\u0440\u0430\u0432\u0438\u043b\u044c\u043d\u043e\u0439 \u0440\u0435\u0430\u043b\u0438\u0437\u0430\u0446\u0438\u0438 \u0430\u043b\u0433\u043e\u0440\u0438\u0442\u043c\u0430 \u0430\u0443\u0442\u0435\u043d\u0442\u0438\u0444\u0438\u043a\u0430\u0446\u0438\u0438.\n\nCVE-2025-37093 - \u0435\u0434\u0438\u043d\u0441\u0442\u0432\u0435\u043d\u043d\u0430\u044f \u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u044c, \u043e\u0446\u0435\u043d\u0435\u043d\u043d\u0430\u044f \u043a\u0430\u043a \u043a\u0440\u0438\u0442\u0438\u0447\u0435\u0441\u043a\u0430\u044f, \u043f\u0440\u0438 \u044d\u0442\u043e\u043c \u0434\u0440\u0443\u0433\u0438\u0435 \u0442\u0430\u043a\u0436\u0435 \u043d\u0435\u0441\u0443\u0442 \u0432 \u0441\u0435\u0431\u0435 \u0437\u043d\u0430\u0447\u0438\u0442\u0435\u043b\u044c\u043d\u044b\u0435 \u0440\u0438\u0441\u043a\u0438, \u0434\u0430\u0436\u0435 \u0435\u0441\u043b\u0438 \u043e\u043d\u0438 \u043e\u0442\u043d\u043e\u0441\u044f\u0442\u0441\u044f \u043a \u0431\u043e\u043b\u0435\u0435 \u043d\u0438\u0437\u043a\u0438\u043c \u043a\u0430\u0442\u0435\u0433\u043e\u0440\u0438\u044f\u043c \u043f\u043e \u0443\u0440\u043e\u0432\u043d\u044e \u0441\u0435\u0440\u044c\u0435\u0437\u043d\u043e\u0441\u0442\u0438.\n\nZDI \u043f\u043e\u044f\u0441\u043d\u044f\u0435\u0442, \u0447\u0442\u043e \u043f\u0440\u043e\u0431\u043b\u0435\u043c\u0430 \u043e\u0431\u0445\u043e\u0434\u0430 \u0430\u0443\u0442\u0435\u043d\u0442\u0438\u0444\u0438\u043a\u0430\u0446\u0438\u0438 \u044f\u0432\u043b\u044f\u0435\u0442\u0441\u044f \u043a\u043b\u044e\u0447\u043e\u043c \u043a \u0440\u0430\u0441\u043a\u0440\u044b\u0442\u0438\u044e \u043f\u043e\u0442\u0435\u043d\u0446\u0438\u0430\u043b\u0430 \u0432\u0441\u0435\u0445 \u043e\u0441\u0442\u0430\u043b\u044c\u043d\u044b\u0445 \u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u0435\u0439, \u043f\u043e\u044d\u0442\u043e\u043c\u0443 \u0438\u0445 \u0440\u0438\u0441\u043a \u043d\u0435 \u0441\u0442\u043e\u0438\u0442 \u0440\u0430\u0441\u0446\u0435\u043d\u0438\u0432\u0430\u0442\u044c \u0438\u0437\u043e\u043b\u0438\u0440\u043e\u0432\u0430\u043d\u043d\u044b\u043c.\n\n\u041f\u0440\u0438\u043c\u0435\u0440\u044b CVE-2025-3794 \u0438 CVE-2025-37095, \u0434\u0432\u0443\u0445 \u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u0435\u0439 \u0441\u0440\u0435\u0434\u043d\u0435\u0439 \u0441\u0442\u0435\u043f\u0435\u043d\u0438 \u0441\u0435\u0440\u044c\u0435\u0437\u043d\u043e\u0441\u0442\u0438, \u0441\u0432\u044f\u0437\u0430\u043d\u043d\u044b\u0445 \u0441 \u0443\u0434\u0430\u043b\u0435\u043d\u0438\u0435\u043c \u0444\u0430\u0439\u043b\u043e\u0432 \u0438 \u0440\u0430\u0441\u043a\u0440\u044b\u0442\u0438\u0435\u043c \u0438\u043d\u0444\u043e\u0440\u043c\u0430\u0446\u0438\u0438, \u043f\u043e\u043a\u0430\u0437\u044b\u0432\u0430\u044e\u0442, \u0447\u0442\u043e \u044d\u043a\u0441\u043f\u043b\u0443\u0430\u0442\u0430\u0446\u0438\u044f \u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u0438 \u043d\u0430 \u043f\u0440\u0430\u043a\u0442\u0438\u043a\u0435 \u043f\u0440\u043e\u0449\u0435, \u0447\u0435\u043c \u044d\u0442\u043e \u043e\u0442\u0440\u0430\u0436\u0435\u043d\u043e \u0432 \u043e\u0446\u0435\u043d\u043a\u0435.\n\n\u042d\u0442\u0430 \u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u044c \u043f\u043e\u0437\u0432\u043e\u043b\u044f\u0435\u0442 \u0443\u0434\u0430\u043b\u0435\u043d\u043d\u044b\u043c \u0437\u043b\u043e\u0443\u043c\u044b\u0448\u043b\u0435\u043d\u043d\u0438\u043a\u0430\u043c \u0440\u0430\u0441\u043a\u0440\u044b\u0432\u0430\u0442\u044c \u043a\u043e\u043d\u0444\u0438\u0434\u0435\u043d\u0446\u0438\u0430\u043b\u044c\u043d\u0443\u044e \u0438\u043d\u0444\u043e\u0440\u043c\u0430\u0446\u0438\u044e \u043e \u0437\u0430\u0442\u0440\u043e\u043d\u0443\u0442\u044b\u0445 \u0443\u0441\u0442\u0430\u043d\u043e\u0432\u043a\u0430\u0445 Hewlett Packard Enterprise StoreOnce VSA. \u0425\u043e\u0442\u044f \u0434\u043b\u044f \u044d\u043a\u0441\u043f\u043b\u0443\u0430\u0442\u0430\u0446\u0438\u0438 \u0442\u0440\u0435\u0431\u0443\u0435\u0442\u0441\u044f \u0430\u0443\u0442\u0435\u043d\u0442\u0438\u0444\u0438\u043a\u0430\u0446\u0438\u044f, \u0441\u0443\u0449\u0435\u0441\u0442\u0432\u0443\u044e\u0449\u0438\u0439 \u043c\u0435\u0445\u0430\u043d\u0438\u0437\u043c \u0430\u0443\u0442\u0435\u043d\u0442\u0438\u0444\u0438\u043a\u0430\u0446\u0438\u0438 \u043c\u043e\u0436\u043d\u043e \u043e\u0431\u043e\u0439\u0442\u0438.\n\n\u041f\u0440\u0438\u043c\u0435\u0447\u0430\u0442\u0435\u043b\u044c\u043d\u043e, \u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u0438 \u0431\u044b\u043b\u0438 \u043e\u0431\u043d\u0430\u0440\u0443\u0436\u0435\u043d\u044b \u0435\u0449\u0435 \u0432 \u043e\u043a\u0442\u044f\u0431\u0440\u0435 2024 \u0433\u043e\u0434\u0430 \u0438 \u043f\u043e\u0442\u0440\u0435\u0431\u043e\u0432\u0430\u043b\u043e\u0441\u044c \u0446\u0435\u043b\u044b\u0445 \u0441\u0435\u043c\u044c \u043c\u0435\u0441\u044f\u0446\u0435\u0432, \u043f\u0440\u0435\u0436\u0434\u0435 \u0447\u0435\u043c \u0438\u0441\u043f\u0440\u0430\u0432\u043b\u0435\u043d\u0438\u044f \u043d\u0430\u043a\u043e\u043d\u0435\u0446-\u0442\u043e \u0441\u0442\u0430\u043b\u0438 \u0434\u043e\u0441\u0442\u0443\u043f\u043d\u044b. \u0422\u0435\u043c \u043d\u0435 \u043c\u0435\u043d\u0435\u0435, \u043d\u0435\u0442 \u043d\u0438\u043a\u0430\u043a\u0438\u0445 \u0441\u043e\u043e\u0431\u0449\u0435\u043d\u0438\u0439 \u043e\u0431 \u0430\u043a\u0442\u0438\u0432\u043d\u043e\u0439 \u044d\u043a\u0441\u043f\u043b\u0443\u0430\u0442\u0430\u0446\u0438\u0438.\n\nHPE \u043d\u0435 \u043e\u0442\u043c\u0435\u0442\u0438\u043b\u0430 \u0432 \u0431\u044e\u043b\u043b\u0435\u0442\u0435\u043d\u0435 \u043d\u0438\u043a\u0430\u043a\u0438\u0445 \u043e\u0431\u0445\u043e\u0434\u043d\u044b\u0445 \u043f\u0443\u0442\u0435\u0439 \u0434\u043b\u044f \u0432\u043e\u0441\u044c\u043c\u0438 \u043d\u0435\u0434\u043e\u0441\u0442\u0430\u0442\u043a\u043e\u0432, \u043f\u043e\u044d\u0442\u043e\u043c\u0443 \u0440\u0435\u043a\u043e\u043c\u0435\u043d\u0434\u0443\u0435\u043c\u044b\u043c \u0440\u0435\u0448\u0435\u043d\u0438\u0435\u043c \u044f\u0432\u043b\u044f\u0435\u0442\u0441\u044f \u043e\u0431\u043d\u043e\u0432\u043b\u0435\u043d\u0438\u0435.", "creation_timestamp": "2025-06-04T16:30:06.000000Z"}, {"uuid": "45aef652-f5e6-4863-afac-94274e3d140c", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37094", "type": "seen", "source": "https://t.me/true_secator/7102", "content": "Hewlett Packard Enterprise (HPE) \u0432 \u0441\u0432\u043e\u0435\u043c \u043d\u043e\u0432\u043e\u043c \u0431\u044e\u043b\u043b\u0435\u0442\u0435\u043d\u0435 \u043f\u043e \u0431\u0435\u0437\u043e\u043f\u0430\u0441\u043d\u043e\u0441\u0442\u0438 \u043f\u0440\u0435\u0434\u0443\u043f\u0440\u0435\u0436\u0434\u0430\u0435\u0442 \u043e \u0432\u043e\u0441\u044c\u043c\u0438 \u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u044f\u0445, \u0432\u043b\u0438\u044f\u044e\u0449\u0438\u0445 \u043d\u0430 \u0440\u0430\u0431\u043e\u0442\u0443 StoreOnce, \u0440\u0435\u0448\u0435\u043d\u0438\u044f \u0434\u043b\u044f \u0440\u0435\u0437\u0435\u0440\u0432\u043d\u043e\u0433\u043e \u043a\u043e\u043f\u0438\u0440\u043e\u0432\u0430\u043d\u0438\u044f \u0438 \u0434\u0435\u0434\u0443\u043f\u043b\u0438\u043a\u0430\u0446\u0438\u0438 \u043d\u0430 \u043e\u0441\u043d\u043e\u0432\u0435 \u0434\u0438\u0441\u043a\u043e\u0432.\n\nHPE StoreOnce \u043e\u0431\u044b\u0447\u043d\u043e \u0438\u0441\u043f\u043e\u043b\u044c\u0437\u0443\u0435\u0442\u0441\u044f \u0434\u043b\u044f \u0440\u0435\u0437\u0435\u0440\u0432\u043d\u043e\u0433\u043e \u043a\u043e\u043f\u0438\u0440\u043e\u0432\u0430\u043d\u0438\u044f \u0438 \u0432\u043e\u0441\u0441\u0442\u0430\u043d\u043e\u0432\u043b\u0435\u043d\u0438\u044f \u043d\u0430 \u043a\u0440\u0443\u043f\u043d\u044b\u0445 \u043f\u0440\u0435\u0434\u043f\u0440\u0438\u044f\u0442\u0438\u044f\u0445, \u0432 \u0426\u041e\u0414\u0430\u0445, \u0443 \u043f\u043e\u0441\u0442\u0430\u0432\u0449\u0438\u043a\u043e\u0432 \u043e\u0431\u043b\u0430\u0447\u043d\u044b\u0445 \u0443\u0441\u043b\u0443\u0433 \u0438 \u0432 \u0446\u0435\u043b\u043e\u043c \u0432 \u043e\u0440\u0433\u0430\u043d\u0438\u0437\u0430\u0446\u0438\u044f\u0445, \u043e\u0431\u0440\u0430\u0431\u0430\u0442\u044b\u0432\u0430\u044e\u0449\u0438\u0445 \u0431\u043e\u043b\u044c\u0448\u0438\u0435 \u0434\u0430\u043d\u043d\u044b\u0435 \u0438\u043b\u0438 \u043a\u0440\u0443\u043f\u043d\u044b\u0435 \u0432\u0438\u0440\u0442\u0443\u0430\u043b\u0438\u0437\u0438\u0440\u043e\u0432\u0430\u043d\u043d\u044b\u0435 \u0441\u0440\u0435\u0434\u044b.\n\nStoreOnce \u0438\u043d\u0442\u0435\u0433\u0440\u0438\u0440\u0443\u0435\u0442\u0441\u044f \u0441 \u041f\u041e \u0434\u043b\u044f \u0440\u0435\u0437\u0435\u0440\u0432\u043d\u043e\u0433\u043e \u043a\u043e\u043f\u0438\u0440\u043e\u0432\u0430\u043d\u0438\u044f, \u0432\u043a\u043b\u044e\u0447\u0430\u044f HPE Data Protector, Veeam, Commvault \u0438 Veritas NetBackup, \u043e\u0431\u0435\u0441\u043f\u0435\u0447\u0438\u0432\u0430\u044f \u043d\u0435\u043f\u0440\u0435\u0440\u044b\u0432\u043d\u043e\u0441\u0442\u044c \u0431\u0438\u0437\u043d\u0435\u0441\u0430 \u0438 \u044d\u0444\u0444\u0435\u043a\u0442\u0438\u0432\u043d\u043e\u0435 \u0443\u043f\u0440\u0430\u0432\u043b\u0435\u043d\u0438\u0435 \u0440\u0435\u0437\u0435\u0440\u0432\u043d\u044b\u043c \u043a\u043e\u043f\u0438\u0440\u043e\u0432\u0430\u043d\u0438\u0435\u043c.\n\n\u041e\u0441\u043e\u0431\u043e\u0435 \u0432\u043d\u0438\u043c\u0430\u043d\u0438\u0435 \u0441\u043b\u0435\u0434\u0443\u0435\u0442 \u043e\u0431\u0440\u0430\u0442\u0438\u0442\u044c \u043d\u0430 \u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u044c \u043e\u0431\u0445\u043e\u0434\u0430 \u0430\u0443\u0442\u0435\u043d\u0442\u0438\u0444\u0438\u043a\u0430\u0446\u0438\u0438 \u043a\u0440\u0438\u0442\u0438\u0447\u0435\u0441\u043a\u043e\u0439 \u0441\u0442\u0435\u043f\u0435\u043d\u0438 \u0441\u0435\u0440\u044c\u0435\u0437\u043d\u043e\u0441\u0442\u0438 (CVSS v3.1: 9,8), \u043a\u043e\u0442\u043e\u0440\u0430\u044f \u043e\u0442\u0441\u043b\u0435\u0436\u0438\u0432\u0430\u0435\u0442\u0441\u044f \u043a\u0430\u043a CVE-2025-37093.\n\n\u041a\u0440\u043e\u043c\u0435 \u0442\u043e\u0433\u043e, \u0438\u0441\u043f\u0440\u0430\u0432\u043b\u0435\u043d\u044b \u0447\u0435\u0442\u044b\u0440\u0435 RCE (CVE-2025-37089, 37091, 37092, 37096), \u0434\u0432\u0435 \u043f\u0440\u043e\u0431\u043b\u0435\u043c\u044b \u043e\u0431\u0445\u043e\u0434\u0430 \u043a\u0430\u0442\u0430\u043b\u043e\u0433\u043e\u0432 (CVE-2025-37094 \u0438 CVE-2025-37095) \u0438 \u043f\u0440\u043e\u0431\u043b\u0435\u043c\u0430 \u043f\u043e\u0434\u0434\u0435\u043b\u043a\u0438 \u0437\u0430\u043f\u0440\u043e\u0441\u043e\u0432 \u043d\u0430 \u0441\u0442\u043e\u0440\u043e\u043d\u0435 \u0441\u0435\u0440\u0432\u0435\u0440\u0430 (CVE-2025-37090).\n\n\u0417\u0430\u0442\u0440\u043e\u043d\u0443\u0442\u044b \u0432\u0441\u0435 \u0432\u0435\u0440\u0441\u0438\u0438 HPE StoreOnce \u0434\u043e 4.3.11, \u043a\u043e\u0442\u043e\u0440\u0430\u044f \u0442\u0435\u043f\u0435\u0440\u044c \u044f\u0432\u043b\u044f\u0435\u0442\u0441\u044f \u0440\u0435\u043a\u043e\u043c\u0435\u043d\u0434\u0443\u0435\u043c\u043e\u0439 \u0432\u0435\u0440\u0441\u0438\u0435\u0439 \u043e\u0431\u043d\u043e\u0432\u043b\u0435\u043d\u0438\u044f. \u041d\u0430 \u044d\u0442\u043e\u0442 \u0440\u0430\u0437 \u043f\u043e\u0434\u0440\u043e\u0431\u043d\u043e\u0441\u0442\u0435\u0439 \u043e \u043d\u0435\u0434\u043e\u0441\u0442\u0430\u0442\u043a\u0430\u0445 \u0440\u0430\u0441\u043a\u0440\u044b\u0442\u043e \u043d\u0435 \u0442\u0430\u043a \u043c\u043d\u043e\u0433\u043e.\n\n\u041e\u0434\u043d\u0430\u043a\u043e Zero Day Initiative (ZDI) \u0443\u043f\u043e\u043c\u0438\u043d\u0430\u0435\u0442, \u0447\u0442\u043e \u043a\u0440\u0438\u0442\u0438\u0447\u0435\u0441\u043a\u0430\u044f CVE-2025-37093 \u0441\u0432\u044f\u0437\u0430\u043d\u0430 \u0441 machineAccountCheck \u0438 \u044f\u0432\u043b\u044f\u0435\u0442\u0441\u044f \u0440\u0435\u0437\u0443\u043b\u044c\u0442\u0430\u0442\u043e\u043c \u043d\u0435\u043f\u0440\u0430\u0432\u0438\u043b\u044c\u043d\u043e\u0439 \u0440\u0435\u0430\u043b\u0438\u0437\u0430\u0446\u0438\u0438 \u0430\u043b\u0433\u043e\u0440\u0438\u0442\u043c\u0430 \u0430\u0443\u0442\u0435\u043d\u0442\u0438\u0444\u0438\u043a\u0430\u0446\u0438\u0438.\n\nCVE-2025-37093 - \u0435\u0434\u0438\u043d\u0441\u0442\u0432\u0435\u043d\u043d\u0430\u044f \u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u044c, \u043e\u0446\u0435\u043d\u0435\u043d\u043d\u0430\u044f \u043a\u0430\u043a \u043a\u0440\u0438\u0442\u0438\u0447\u0435\u0441\u043a\u0430\u044f, \u043f\u0440\u0438 \u044d\u0442\u043e\u043c \u0434\u0440\u0443\u0433\u0438\u0435 \u0442\u0430\u043a\u0436\u0435 \u043d\u0435\u0441\u0443\u0442 \u0432 \u0441\u0435\u0431\u0435 \u0437\u043d\u0430\u0447\u0438\u0442\u0435\u043b\u044c\u043d\u044b\u0435 \u0440\u0438\u0441\u043a\u0438, \u0434\u0430\u0436\u0435 \u0435\u0441\u043b\u0438 \u043e\u043d\u0438 \u043e\u0442\u043d\u043e\u0441\u044f\u0442\u0441\u044f \u043a \u0431\u043e\u043b\u0435\u0435 \u043d\u0438\u0437\u043a\u0438\u043c \u043a\u0430\u0442\u0435\u0433\u043e\u0440\u0438\u044f\u043c \u043f\u043e \u0443\u0440\u043e\u0432\u043d\u044e \u0441\u0435\u0440\u044c\u0435\u0437\u043d\u043e\u0441\u0442\u0438.\n\nZDI \u043f\u043e\u044f\u0441\u043d\u044f\u0435\u0442, \u0447\u0442\u043e \u043f\u0440\u043e\u0431\u043b\u0435\u043c\u0430 \u043e\u0431\u0445\u043e\u0434\u0430 \u0430\u0443\u0442\u0435\u043d\u0442\u0438\u0444\u0438\u043a\u0430\u0446\u0438\u0438 \u044f\u0432\u043b\u044f\u0435\u0442\u0441\u044f \u043a\u043b\u044e\u0447\u043e\u043c \u043a \u0440\u0430\u0441\u043a\u0440\u044b\u0442\u0438\u044e \u043f\u043e\u0442\u0435\u043d\u0446\u0438\u0430\u043b\u0430 \u0432\u0441\u0435\u0445 \u043e\u0441\u0442\u0430\u043b\u044c\u043d\u044b\u0445 \u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u0435\u0439, \u043f\u043e\u044d\u0442\u043e\u043c\u0443 \u0438\u0445 \u0440\u0438\u0441\u043a \u043d\u0435 \u0441\u0442\u043e\u0438\u0442 \u0440\u0430\u0441\u0446\u0435\u043d\u0438\u0432\u0430\u0442\u044c \u0438\u0437\u043e\u043b\u0438\u0440\u043e\u0432\u0430\u043d\u043d\u044b\u043c.\n\n\u041f\u0440\u0438\u043c\u0435\u0440\u044b CVE-2025-3794 \u0438 CVE-2025-37095, \u0434\u0432\u0443\u0445 \u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u0435\u0439 \u0441\u0440\u0435\u0434\u043d\u0435\u0439 \u0441\u0442\u0435\u043f\u0435\u043d\u0438 \u0441\u0435\u0440\u044c\u0435\u0437\u043d\u043e\u0441\u0442\u0438, \u0441\u0432\u044f\u0437\u0430\u043d\u043d\u044b\u0445 \u0441 \u0443\u0434\u0430\u043b\u0435\u043d\u0438\u0435\u043c \u0444\u0430\u0439\u043b\u043e\u0432 \u0438 \u0440\u0430\u0441\u043a\u0440\u044b\u0442\u0438\u0435\u043c \u0438\u043d\u0444\u043e\u0440\u043c\u0430\u0446\u0438\u0438, \u043f\u043e\u043a\u0430\u0437\u044b\u0432\u0430\u044e\u0442, \u0447\u0442\u043e \u044d\u043a\u0441\u043f\u043b\u0443\u0430\u0442\u0430\u0446\u0438\u044f \u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u0438 \u043d\u0430 \u043f\u0440\u0430\u043a\u0442\u0438\u043a\u0435 \u043f\u0440\u043e\u0449\u0435, \u0447\u0435\u043c \u044d\u0442\u043e \u043e\u0442\u0440\u0430\u0436\u0435\u043d\u043e \u0432 \u043e\u0446\u0435\u043d\u043a\u0435.\n\n\u042d\u0442\u0430 \u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u044c \u043f\u043e\u0437\u0432\u043e\u043b\u044f\u0435\u0442 \u0443\u0434\u0430\u043b\u0435\u043d\u043d\u044b\u043c \u0437\u043b\u043e\u0443\u043c\u044b\u0448\u043b\u0435\u043d\u043d\u0438\u043a\u0430\u043c \u0440\u0430\u0441\u043a\u0440\u044b\u0432\u0430\u0442\u044c \u043a\u043e\u043d\u0444\u0438\u0434\u0435\u043d\u0446\u0438\u0430\u043b\u044c\u043d\u0443\u044e \u0438\u043d\u0444\u043e\u0440\u043c\u0430\u0446\u0438\u044e \u043e \u0437\u0430\u0442\u0440\u043e\u043d\u0443\u0442\u044b\u0445 \u0443\u0441\u0442\u0430\u043d\u043e\u0432\u043a\u0430\u0445 Hewlett Packard Enterprise StoreOnce VSA. \u0425\u043e\u0442\u044f \u0434\u043b\u044f \u044d\u043a\u0441\u043f\u043b\u0443\u0430\u0442\u0430\u0446\u0438\u0438 \u0442\u0440\u0435\u0431\u0443\u0435\u0442\u0441\u044f \u0430\u0443\u0442\u0435\u043d\u0442\u0438\u0444\u0438\u043a\u0430\u0446\u0438\u044f, \u0441\u0443\u0449\u0435\u0441\u0442\u0432\u0443\u044e\u0449\u0438\u0439 \u043c\u0435\u0445\u0430\u043d\u0438\u0437\u043c \u0430\u0443\u0442\u0435\u043d\u0442\u0438\u0444\u0438\u043a\u0430\u0446\u0438\u0438 \u043c\u043e\u0436\u043d\u043e \u043e\u0431\u043e\u0439\u0442\u0438.\n\n\u041f\u0440\u0438\u043c\u0435\u0447\u0430\u0442\u0435\u043b\u044c\u043d\u043e, \u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u0438 \u0431\u044b\u043b\u0438 \u043e\u0431\u043d\u0430\u0440\u0443\u0436\u0435\u043d\u044b \u0435\u0449\u0435 \u0432 \u043e\u043a\u0442\u044f\u0431\u0440\u0435 2024 \u0433\u043e\u0434\u0430 \u0438 \u043f\u043e\u0442\u0440\u0435\u0431\u043e\u0432\u0430\u043b\u043e\u0441\u044c \u0446\u0435\u043b\u044b\u0445 \u0441\u0435\u043c\u044c \u043c\u0435\u0441\u044f\u0446\u0435\u0432, \u043f\u0440\u0435\u0436\u0434\u0435 \u0447\u0435\u043c \u0438\u0441\u043f\u0440\u0430\u0432\u043b\u0435\u043d\u0438\u044f \u043d\u0430\u043a\u043e\u043d\u0435\u0446-\u0442\u043e \u0441\u0442\u0430\u043b\u0438 \u0434\u043e\u0441\u0442\u0443\u043f\u043d\u044b. \u0422\u0435\u043c \u043d\u0435 \u043c\u0435\u043d\u0435\u0435, \u043d\u0435\u0442 \u043d\u0438\u043a\u0430\u043a\u0438\u0445 \u0441\u043e\u043e\u0431\u0449\u0435\u043d\u0438\u0439 \u043e\u0431 \u0430\u043a\u0442\u0438\u0432\u043d\u043e\u0439 \u044d\u043a\u0441\u043f\u043b\u0443\u0430\u0442\u0430\u0446\u0438\u0438.\n\nHPE \u043d\u0435 \u043e\u0442\u043c\u0435\u0442\u0438\u043b\u0430 \u0432 \u0431\u044e\u043b\u043b\u0435\u0442\u0435\u043d\u0435 \u043d\u0438\u043a\u0430\u043a\u0438\u0445 \u043e\u0431\u0445\u043e\u0434\u043d\u044b\u0445 \u043f\u0443\u0442\u0435\u0439 \u0434\u043b\u044f \u0432\u043e\u0441\u044c\u043c\u0438 \u043d\u0435\u0434\u043e\u0441\u0442\u0430\u0442\u043a\u043e\u0432, \u043f\u043e\u044d\u0442\u043e\u043c\u0443 \u0440\u0435\u043a\u043e\u043c\u0435\u043d\u0434\u0443\u0435\u043c\u044b\u043c \u0440\u0435\u0448\u0435\u043d\u0438\u0435\u043c \u044f\u0432\u043b\u044f\u0435\u0442\u0441\u044f \u043e\u0431\u043d\u043e\u0432\u043b\u0435\u043d\u0438\u0435.", "creation_timestamp": "2025-06-04T16:30:06.000000Z"}, {"uuid": "f2f89123-c8ca-489a-87cc-6214f9044feb", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37095", "type": "seen", "source": "https://t.me/true_secator/7102", "content": "Hewlett Packard Enterprise (HPE) \u0432 \u0441\u0432\u043e\u0435\u043c \u043d\u043e\u0432\u043e\u043c \u0431\u044e\u043b\u043b\u0435\u0442\u0435\u043d\u0435 \u043f\u043e \u0431\u0435\u0437\u043e\u043f\u0430\u0441\u043d\u043e\u0441\u0442\u0438 \u043f\u0440\u0435\u0434\u0443\u043f\u0440\u0435\u0436\u0434\u0430\u0435\u0442 \u043e \u0432\u043e\u0441\u044c\u043c\u0438 \u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u044f\u0445, \u0432\u043b\u0438\u044f\u044e\u0449\u0438\u0445 \u043d\u0430 \u0440\u0430\u0431\u043e\u0442\u0443 StoreOnce, \u0440\u0435\u0448\u0435\u043d\u0438\u044f \u0434\u043b\u044f \u0440\u0435\u0437\u0435\u0440\u0432\u043d\u043e\u0433\u043e \u043a\u043e\u043f\u0438\u0440\u043e\u0432\u0430\u043d\u0438\u044f \u0438 \u0434\u0435\u0434\u0443\u043f\u043b\u0438\u043a\u0430\u0446\u0438\u0438 \u043d\u0430 \u043e\u0441\u043d\u043e\u0432\u0435 \u0434\u0438\u0441\u043a\u043e\u0432.\n\nHPE StoreOnce \u043e\u0431\u044b\u0447\u043d\u043e \u0438\u0441\u043f\u043e\u043b\u044c\u0437\u0443\u0435\u0442\u0441\u044f \u0434\u043b\u044f \u0440\u0435\u0437\u0435\u0440\u0432\u043d\u043e\u0433\u043e \u043a\u043e\u043f\u0438\u0440\u043e\u0432\u0430\u043d\u0438\u044f \u0438 \u0432\u043e\u0441\u0441\u0442\u0430\u043d\u043e\u0432\u043b\u0435\u043d\u0438\u044f \u043d\u0430 \u043a\u0440\u0443\u043f\u043d\u044b\u0445 \u043f\u0440\u0435\u0434\u043f\u0440\u0438\u044f\u0442\u0438\u044f\u0445, \u0432 \u0426\u041e\u0414\u0430\u0445, \u0443 \u043f\u043e\u0441\u0442\u0430\u0432\u0449\u0438\u043a\u043e\u0432 \u043e\u0431\u043b\u0430\u0447\u043d\u044b\u0445 \u0443\u0441\u043b\u0443\u0433 \u0438 \u0432 \u0446\u0435\u043b\u043e\u043c \u0432 \u043e\u0440\u0433\u0430\u043d\u0438\u0437\u0430\u0446\u0438\u044f\u0445, \u043e\u0431\u0440\u0430\u0431\u0430\u0442\u044b\u0432\u0430\u044e\u0449\u0438\u0445 \u0431\u043e\u043b\u044c\u0448\u0438\u0435 \u0434\u0430\u043d\u043d\u044b\u0435 \u0438\u043b\u0438 \u043a\u0440\u0443\u043f\u043d\u044b\u0435 \u0432\u0438\u0440\u0442\u0443\u0430\u043b\u0438\u0437\u0438\u0440\u043e\u0432\u0430\u043d\u043d\u044b\u0435 \u0441\u0440\u0435\u0434\u044b.\n\nStoreOnce \u0438\u043d\u0442\u0435\u0433\u0440\u0438\u0440\u0443\u0435\u0442\u0441\u044f \u0441 \u041f\u041e \u0434\u043b\u044f \u0440\u0435\u0437\u0435\u0440\u0432\u043d\u043e\u0433\u043e \u043a\u043e\u043f\u0438\u0440\u043e\u0432\u0430\u043d\u0438\u044f, \u0432\u043a\u043b\u044e\u0447\u0430\u044f HPE Data Protector, Veeam, Commvault \u0438 Veritas NetBackup, \u043e\u0431\u0435\u0441\u043f\u0435\u0447\u0438\u0432\u0430\u044f \u043d\u0435\u043f\u0440\u0435\u0440\u044b\u0432\u043d\u043e\u0441\u0442\u044c \u0431\u0438\u0437\u043d\u0435\u0441\u0430 \u0438 \u044d\u0444\u0444\u0435\u043a\u0442\u0438\u0432\u043d\u043e\u0435 \u0443\u043f\u0440\u0430\u0432\u043b\u0435\u043d\u0438\u0435 \u0440\u0435\u0437\u0435\u0440\u0432\u043d\u044b\u043c \u043a\u043e\u043f\u0438\u0440\u043e\u0432\u0430\u043d\u0438\u0435\u043c.\n\n\u041e\u0441\u043e\u0431\u043e\u0435 \u0432\u043d\u0438\u043c\u0430\u043d\u0438\u0435 \u0441\u043b\u0435\u0434\u0443\u0435\u0442 \u043e\u0431\u0440\u0430\u0442\u0438\u0442\u044c \u043d\u0430 \u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u044c \u043e\u0431\u0445\u043e\u0434\u0430 \u0430\u0443\u0442\u0435\u043d\u0442\u0438\u0444\u0438\u043a\u0430\u0446\u0438\u0438 \u043a\u0440\u0438\u0442\u0438\u0447\u0435\u0441\u043a\u043e\u0439 \u0441\u0442\u0435\u043f\u0435\u043d\u0438 \u0441\u0435\u0440\u044c\u0435\u0437\u043d\u043e\u0441\u0442\u0438 (CVSS v3.1: 9,8), \u043a\u043e\u0442\u043e\u0440\u0430\u044f \u043e\u0442\u0441\u043b\u0435\u0436\u0438\u0432\u0430\u0435\u0442\u0441\u044f \u043a\u0430\u043a CVE-2025-37093.\n\n\u041a\u0440\u043e\u043c\u0435 \u0442\u043e\u0433\u043e, \u0438\u0441\u043f\u0440\u0430\u0432\u043b\u0435\u043d\u044b \u0447\u0435\u0442\u044b\u0440\u0435 RCE (CVE-2025-37089, 37091, 37092, 37096), \u0434\u0432\u0435 \u043f\u0440\u043e\u0431\u043b\u0435\u043c\u044b \u043e\u0431\u0445\u043e\u0434\u0430 \u043a\u0430\u0442\u0430\u043b\u043e\u0433\u043e\u0432 (CVE-2025-37094 \u0438 CVE-2025-37095) \u0438 \u043f\u0440\u043e\u0431\u043b\u0435\u043c\u0430 \u043f\u043e\u0434\u0434\u0435\u043b\u043a\u0438 \u0437\u0430\u043f\u0440\u043e\u0441\u043e\u0432 \u043d\u0430 \u0441\u0442\u043e\u0440\u043e\u043d\u0435 \u0441\u0435\u0440\u0432\u0435\u0440\u0430 (CVE-2025-37090).\n\n\u0417\u0430\u0442\u0440\u043e\u043d\u0443\u0442\u044b \u0432\u0441\u0435 \u0432\u0435\u0440\u0441\u0438\u0438 HPE StoreOnce \u0434\u043e 4.3.11, \u043a\u043e\u0442\u043e\u0440\u0430\u044f \u0442\u0435\u043f\u0435\u0440\u044c \u044f\u0432\u043b\u044f\u0435\u0442\u0441\u044f \u0440\u0435\u043a\u043e\u043c\u0435\u043d\u0434\u0443\u0435\u043c\u043e\u0439 \u0432\u0435\u0440\u0441\u0438\u0435\u0439 \u043e\u0431\u043d\u043e\u0432\u043b\u0435\u043d\u0438\u044f. \u041d\u0430 \u044d\u0442\u043e\u0442 \u0440\u0430\u0437 \u043f\u043e\u0434\u0440\u043e\u0431\u043d\u043e\u0441\u0442\u0435\u0439 \u043e \u043d\u0435\u0434\u043e\u0441\u0442\u0430\u0442\u043a\u0430\u0445 \u0440\u0430\u0441\u043a\u0440\u044b\u0442\u043e \u043d\u0435 \u0442\u0430\u043a \u043c\u043d\u043e\u0433\u043e.\n\n\u041e\u0434\u043d\u0430\u043a\u043e Zero Day Initiative (ZDI) \u0443\u043f\u043e\u043c\u0438\u043d\u0430\u0435\u0442, \u0447\u0442\u043e \u043a\u0440\u0438\u0442\u0438\u0447\u0435\u0441\u043a\u0430\u044f CVE-2025-37093 \u0441\u0432\u044f\u0437\u0430\u043d\u0430 \u0441 machineAccountCheck \u0438 \u044f\u0432\u043b\u044f\u0435\u0442\u0441\u044f \u0440\u0435\u0437\u0443\u043b\u044c\u0442\u0430\u0442\u043e\u043c \u043d\u0435\u043f\u0440\u0430\u0432\u0438\u043b\u044c\u043d\u043e\u0439 \u0440\u0435\u0430\u043b\u0438\u0437\u0430\u0446\u0438\u0438 \u0430\u043b\u0433\u043e\u0440\u0438\u0442\u043c\u0430 \u0430\u0443\u0442\u0435\u043d\u0442\u0438\u0444\u0438\u043a\u0430\u0446\u0438\u0438.\n\nCVE-2025-37093 - \u0435\u0434\u0438\u043d\u0441\u0442\u0432\u0435\u043d\u043d\u0430\u044f \u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u044c, \u043e\u0446\u0435\u043d\u0435\u043d\u043d\u0430\u044f \u043a\u0430\u043a \u043a\u0440\u0438\u0442\u0438\u0447\u0435\u0441\u043a\u0430\u044f, \u043f\u0440\u0438 \u044d\u0442\u043e\u043c \u0434\u0440\u0443\u0433\u0438\u0435 \u0442\u0430\u043a\u0436\u0435 \u043d\u0435\u0441\u0443\u0442 \u0432 \u0441\u0435\u0431\u0435 \u0437\u043d\u0430\u0447\u0438\u0442\u0435\u043b\u044c\u043d\u044b\u0435 \u0440\u0438\u0441\u043a\u0438, \u0434\u0430\u0436\u0435 \u0435\u0441\u043b\u0438 \u043e\u043d\u0438 \u043e\u0442\u043d\u043e\u0441\u044f\u0442\u0441\u044f \u043a \u0431\u043e\u043b\u0435\u0435 \u043d\u0438\u0437\u043a\u0438\u043c \u043a\u0430\u0442\u0435\u0433\u043e\u0440\u0438\u044f\u043c \u043f\u043e \u0443\u0440\u043e\u0432\u043d\u044e \u0441\u0435\u0440\u044c\u0435\u0437\u043d\u043e\u0441\u0442\u0438.\n\nZDI \u043f\u043e\u044f\u0441\u043d\u044f\u0435\u0442, \u0447\u0442\u043e \u043f\u0440\u043e\u0431\u043b\u0435\u043c\u0430 \u043e\u0431\u0445\u043e\u0434\u0430 \u0430\u0443\u0442\u0435\u043d\u0442\u0438\u0444\u0438\u043a\u0430\u0446\u0438\u0438 \u044f\u0432\u043b\u044f\u0435\u0442\u0441\u044f \u043a\u043b\u044e\u0447\u043e\u043c \u043a \u0440\u0430\u0441\u043a\u0440\u044b\u0442\u0438\u044e \u043f\u043e\u0442\u0435\u043d\u0446\u0438\u0430\u043b\u0430 \u0432\u0441\u0435\u0445 \u043e\u0441\u0442\u0430\u043b\u044c\u043d\u044b\u0445 \u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u0435\u0439, \u043f\u043e\u044d\u0442\u043e\u043c\u0443 \u0438\u0445 \u0440\u0438\u0441\u043a \u043d\u0435 \u0441\u0442\u043e\u0438\u0442 \u0440\u0430\u0441\u0446\u0435\u043d\u0438\u0432\u0430\u0442\u044c \u0438\u0437\u043e\u043b\u0438\u0440\u043e\u0432\u0430\u043d\u043d\u044b\u043c.\n\n\u041f\u0440\u0438\u043c\u0435\u0440\u044b CVE-2025-3794 \u0438 CVE-2025-37095, \u0434\u0432\u0443\u0445 \u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u0435\u0439 \u0441\u0440\u0435\u0434\u043d\u0435\u0439 \u0441\u0442\u0435\u043f\u0435\u043d\u0438 \u0441\u0435\u0440\u044c\u0435\u0437\u043d\u043e\u0441\u0442\u0438, \u0441\u0432\u044f\u0437\u0430\u043d\u043d\u044b\u0445 \u0441 \u0443\u0434\u0430\u043b\u0435\u043d\u0438\u0435\u043c \u0444\u0430\u0439\u043b\u043e\u0432 \u0438 \u0440\u0430\u0441\u043a\u0440\u044b\u0442\u0438\u0435\u043c \u0438\u043d\u0444\u043e\u0440\u043c\u0430\u0446\u0438\u0438, \u043f\u043e\u043a\u0430\u0437\u044b\u0432\u0430\u044e\u0442, \u0447\u0442\u043e \u044d\u043a\u0441\u043f\u043b\u0443\u0430\u0442\u0430\u0446\u0438\u044f \u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u0438 \u043d\u0430 \u043f\u0440\u0430\u043a\u0442\u0438\u043a\u0435 \u043f\u0440\u043e\u0449\u0435, \u0447\u0435\u043c \u044d\u0442\u043e \u043e\u0442\u0440\u0430\u0436\u0435\u043d\u043e \u0432 \u043e\u0446\u0435\u043d\u043a\u0435.\n\n\u042d\u0442\u0430 \u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u044c \u043f\u043e\u0437\u0432\u043e\u043b\u044f\u0435\u0442 \u0443\u0434\u0430\u043b\u0435\u043d\u043d\u044b\u043c \u0437\u043b\u043e\u0443\u043c\u044b\u0448\u043b\u0435\u043d\u043d\u0438\u043a\u0430\u043c \u0440\u0430\u0441\u043a\u0440\u044b\u0432\u0430\u0442\u044c \u043a\u043e\u043d\u0444\u0438\u0434\u0435\u043d\u0446\u0438\u0430\u043b\u044c\u043d\u0443\u044e \u0438\u043d\u0444\u043e\u0440\u043c\u0430\u0446\u0438\u044e \u043e \u0437\u0430\u0442\u0440\u043e\u043d\u0443\u0442\u044b\u0445 \u0443\u0441\u0442\u0430\u043d\u043e\u0432\u043a\u0430\u0445 Hewlett Packard Enterprise StoreOnce VSA. \u0425\u043e\u0442\u044f \u0434\u043b\u044f \u044d\u043a\u0441\u043f\u043b\u0443\u0430\u0442\u0430\u0446\u0438\u0438 \u0442\u0440\u0435\u0431\u0443\u0435\u0442\u0441\u044f \u0430\u0443\u0442\u0435\u043d\u0442\u0438\u0444\u0438\u043a\u0430\u0446\u0438\u044f, \u0441\u0443\u0449\u0435\u0441\u0442\u0432\u0443\u044e\u0449\u0438\u0439 \u043c\u0435\u0445\u0430\u043d\u0438\u0437\u043c \u0430\u0443\u0442\u0435\u043d\u0442\u0438\u0444\u0438\u043a\u0430\u0446\u0438\u0438 \u043c\u043e\u0436\u043d\u043e \u043e\u0431\u043e\u0439\u0442\u0438.\n\n\u041f\u0440\u0438\u043c\u0435\u0447\u0430\u0442\u0435\u043b\u044c\u043d\u043e, \u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u0438 \u0431\u044b\u043b\u0438 \u043e\u0431\u043d\u0430\u0440\u0443\u0436\u0435\u043d\u044b \u0435\u0449\u0435 \u0432 \u043e\u043a\u0442\u044f\u0431\u0440\u0435 2024 \u0433\u043e\u0434\u0430 \u0438 \u043f\u043e\u0442\u0440\u0435\u0431\u043e\u0432\u0430\u043b\u043e\u0441\u044c \u0446\u0435\u043b\u044b\u0445 \u0441\u0435\u043c\u044c \u043c\u0435\u0441\u044f\u0446\u0435\u0432, \u043f\u0440\u0435\u0436\u0434\u0435 \u0447\u0435\u043c \u0438\u0441\u043f\u0440\u0430\u0432\u043b\u0435\u043d\u0438\u044f \u043d\u0430\u043a\u043e\u043d\u0435\u0446-\u0442\u043e \u0441\u0442\u0430\u043b\u0438 \u0434\u043e\u0441\u0442\u0443\u043f\u043d\u044b. \u0422\u0435\u043c \u043d\u0435 \u043c\u0435\u043d\u0435\u0435, \u043d\u0435\u0442 \u043d\u0438\u043a\u0430\u043a\u0438\u0445 \u0441\u043e\u043e\u0431\u0449\u0435\u043d\u0438\u0439 \u043e\u0431 \u0430\u043a\u0442\u0438\u0432\u043d\u043e\u0439 \u044d\u043a\u0441\u043f\u043b\u0443\u0430\u0442\u0430\u0446\u0438\u0438.\n\nHPE \u043d\u0435 \u043e\u0442\u043c\u0435\u0442\u0438\u043b\u0430 \u0432 \u0431\u044e\u043b\u043b\u0435\u0442\u0435\u043d\u0435 \u043d\u0438\u043a\u0430\u043a\u0438\u0445 \u043e\u0431\u0445\u043e\u0434\u043d\u044b\u0445 \u043f\u0443\u0442\u0435\u0439 \u0434\u043b\u044f \u0432\u043e\u0441\u044c\u043c\u0438 \u043d\u0435\u0434\u043e\u0441\u0442\u0430\u0442\u043a\u043e\u0432, \u043f\u043e\u044d\u0442\u043e\u043c\u0443 \u0440\u0435\u043a\u043e\u043c\u0435\u043d\u0434\u0443\u0435\u043c\u044b\u043c \u0440\u0435\u0448\u0435\u043d\u0438\u0435\u043c \u044f\u0432\u043b\u044f\u0435\u0442\u0441\u044f \u043e\u0431\u043d\u043e\u0432\u043b\u0435\u043d\u0438\u0435.", "creation_timestamp": "2025-06-04T16:30:06.000000Z"}, {"uuid": "01860c4f-2bca-4a79-809a-797b8c6bff7b", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37093", "type": "seen", "source": "https://t.me/CyberBulletin/3404", "content": "\u26a1\ufe0fCVE-2025-37093: HPE Fixes Critical RCE Vulnerability in StoreOnce.\n\n#CyberBulletin", "creation_timestamp": "2025-06-05T06:20:09.000000Z"}, {"uuid": "25548950-1735-42e9-b19b-49fed6293b2d", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37093", "type": "seen", "source": "Telegram/92w8qirUpRLTSGCUJYKAuYim4A7KYC8E14r3wDK65Pi_WLA", "content": "", "creation_timestamp": "2025-06-04T17:32:36.000000Z"}, {"uuid": "d65701fa-b0c2-4c58-a035-e249642a90fe", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37093", "type": "published-proof-of-concept", "source": "https://t.me/thehackernews/6942", "content": "\ud83d\udea8 Critical bugs in HPE StoreOnce | 9.8 CVSS flaw allows auth bypass + RCE as root.\n\n\ud83d\udc40 One bug (CVE-2025-37093) lets attackers skip login\u2014then chain others for full takeover.\n\nPatch now if you're running pre-4.3.11 versions.\n\n\ud83d\udd17 Full details: https://thehackernews.com/2025/06/hpe-issues-security-patch-for-storeonce.html", "creation_timestamp": "2025-06-04T07:38:51.000000Z"}, {"uuid": "11ec2cb4-e814-43a5-b2e3-9e99da525130", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37093", "type": "seen", "source": "https://t.me/true_secator/7102", "content": "Hewlett Packard Enterprise (HPE) \u0432 \u0441\u0432\u043e\u0435\u043c \u043d\u043e\u0432\u043e\u043c \u0431\u044e\u043b\u043b\u0435\u0442\u0435\u043d\u0435 \u043f\u043e \u0431\u0435\u0437\u043e\u043f\u0430\u0441\u043d\u043e\u0441\u0442\u0438 \u043f\u0440\u0435\u0434\u0443\u043f\u0440\u0435\u0436\u0434\u0430\u0435\u0442 \u043e \u0432\u043e\u0441\u044c\u043c\u0438 \u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u044f\u0445, \u0432\u043b\u0438\u044f\u044e\u0449\u0438\u0445 \u043d\u0430 \u0440\u0430\u0431\u043e\u0442\u0443 StoreOnce, \u0440\u0435\u0448\u0435\u043d\u0438\u044f \u0434\u043b\u044f \u0440\u0435\u0437\u0435\u0440\u0432\u043d\u043e\u0433\u043e \u043a\u043e\u043f\u0438\u0440\u043e\u0432\u0430\u043d\u0438\u044f \u0438 \u0434\u0435\u0434\u0443\u043f\u043b\u0438\u043a\u0430\u0446\u0438\u0438 \u043d\u0430 \u043e\u0441\u043d\u043e\u0432\u0435 \u0434\u0438\u0441\u043a\u043e\u0432.\n\nHPE StoreOnce \u043e\u0431\u044b\u0447\u043d\u043e \u0438\u0441\u043f\u043e\u043b\u044c\u0437\u0443\u0435\u0442\u0441\u044f \u0434\u043b\u044f \u0440\u0435\u0437\u0435\u0440\u0432\u043d\u043e\u0433\u043e \u043a\u043e\u043f\u0438\u0440\u043e\u0432\u0430\u043d\u0438\u044f \u0438 \u0432\u043e\u0441\u0441\u0442\u0430\u043d\u043e\u0432\u043b\u0435\u043d\u0438\u044f \u043d\u0430 \u043a\u0440\u0443\u043f\u043d\u044b\u0445 \u043f\u0440\u0435\u0434\u043f\u0440\u0438\u044f\u0442\u0438\u044f\u0445, \u0432 \u0426\u041e\u0414\u0430\u0445, \u0443 \u043f\u043e\u0441\u0442\u0430\u0432\u0449\u0438\u043a\u043e\u0432 \u043e\u0431\u043b\u0430\u0447\u043d\u044b\u0445 \u0443\u0441\u043b\u0443\u0433 \u0438 \u0432 \u0446\u0435\u043b\u043e\u043c \u0432 \u043e\u0440\u0433\u0430\u043d\u0438\u0437\u0430\u0446\u0438\u044f\u0445, \u043e\u0431\u0440\u0430\u0431\u0430\u0442\u044b\u0432\u0430\u044e\u0449\u0438\u0445 \u0431\u043e\u043b\u044c\u0448\u0438\u0435 \u0434\u0430\u043d\u043d\u044b\u0435 \u0438\u043b\u0438 \u043a\u0440\u0443\u043f\u043d\u044b\u0435 \u0432\u0438\u0440\u0442\u0443\u0430\u043b\u0438\u0437\u0438\u0440\u043e\u0432\u0430\u043d\u043d\u044b\u0435 \u0441\u0440\u0435\u0434\u044b.\n\nStoreOnce \u0438\u043d\u0442\u0435\u0433\u0440\u0438\u0440\u0443\u0435\u0442\u0441\u044f \u0441 \u041f\u041e \u0434\u043b\u044f \u0440\u0435\u0437\u0435\u0440\u0432\u043d\u043e\u0433\u043e \u043a\u043e\u043f\u0438\u0440\u043e\u0432\u0430\u043d\u0438\u044f, \u0432\u043a\u043b\u044e\u0447\u0430\u044f HPE Data Protector, Veeam, Commvault \u0438 Veritas NetBackup, \u043e\u0431\u0435\u0441\u043f\u0435\u0447\u0438\u0432\u0430\u044f \u043d\u0435\u043f\u0440\u0435\u0440\u044b\u0432\u043d\u043e\u0441\u0442\u044c \u0431\u0438\u0437\u043d\u0435\u0441\u0430 \u0438 \u044d\u0444\u0444\u0435\u043a\u0442\u0438\u0432\u043d\u043e\u0435 \u0443\u043f\u0440\u0430\u0432\u043b\u0435\u043d\u0438\u0435 \u0440\u0435\u0437\u0435\u0440\u0432\u043d\u044b\u043c \u043a\u043e\u043f\u0438\u0440\u043e\u0432\u0430\u043d\u0438\u0435\u043c.\n\n\u041e\u0441\u043e\u0431\u043e\u0435 \u0432\u043d\u0438\u043c\u0430\u043d\u0438\u0435 \u0441\u043b\u0435\u0434\u0443\u0435\u0442 \u043e\u0431\u0440\u0430\u0442\u0438\u0442\u044c \u043d\u0430 \u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u044c \u043e\u0431\u0445\u043e\u0434\u0430 \u0430\u0443\u0442\u0435\u043d\u0442\u0438\u0444\u0438\u043a\u0430\u0446\u0438\u0438 \u043a\u0440\u0438\u0442\u0438\u0447\u0435\u0441\u043a\u043e\u0439 \u0441\u0442\u0435\u043f\u0435\u043d\u0438 \u0441\u0435\u0440\u044c\u0435\u0437\u043d\u043e\u0441\u0442\u0438 (CVSS v3.1: 9,8), \u043a\u043e\u0442\u043e\u0440\u0430\u044f \u043e\u0442\u0441\u043b\u0435\u0436\u0438\u0432\u0430\u0435\u0442\u0441\u044f \u043a\u0430\u043a CVE-2025-37093.\n\n\u041a\u0440\u043e\u043c\u0435 \u0442\u043e\u0433\u043e, \u0438\u0441\u043f\u0440\u0430\u0432\u043b\u0435\u043d\u044b \u0447\u0435\u0442\u044b\u0440\u0435 RCE (CVE-2025-37089, 37091, 37092, 37096), \u0434\u0432\u0435 \u043f\u0440\u043e\u0431\u043b\u0435\u043c\u044b \u043e\u0431\u0445\u043e\u0434\u0430 \u043a\u0430\u0442\u0430\u043b\u043e\u0433\u043e\u0432 (CVE-2025-37094 \u0438 CVE-2025-37095) \u0438 \u043f\u0440\u043e\u0431\u043b\u0435\u043c\u0430 \u043f\u043e\u0434\u0434\u0435\u043b\u043a\u0438 \u0437\u0430\u043f\u0440\u043e\u0441\u043e\u0432 \u043d\u0430 \u0441\u0442\u043e\u0440\u043e\u043d\u0435 \u0441\u0435\u0440\u0432\u0435\u0440\u0430 (CVE-2025-37090).\n\n\u0417\u0430\u0442\u0440\u043e\u043d\u0443\u0442\u044b \u0432\u0441\u0435 \u0432\u0435\u0440\u0441\u0438\u0438 HPE StoreOnce \u0434\u043e 4.3.11, \u043a\u043e\u0442\u043e\u0440\u0430\u044f \u0442\u0435\u043f\u0435\u0440\u044c \u044f\u0432\u043b\u044f\u0435\u0442\u0441\u044f \u0440\u0435\u043a\u043e\u043c\u0435\u043d\u0434\u0443\u0435\u043c\u043e\u0439 \u0432\u0435\u0440\u0441\u0438\u0435\u0439 \u043e\u0431\u043d\u043e\u0432\u043b\u0435\u043d\u0438\u044f. \u041d\u0430 \u044d\u0442\u043e\u0442 \u0440\u0430\u0437 \u043f\u043e\u0434\u0440\u043e\u0431\u043d\u043e\u0441\u0442\u0435\u0439 \u043e \u043d\u0435\u0434\u043e\u0441\u0442\u0430\u0442\u043a\u0430\u0445 \u0440\u0430\u0441\u043a\u0440\u044b\u0442\u043e \u043d\u0435 \u0442\u0430\u043a \u043c\u043d\u043e\u0433\u043e.\n\n\u041e\u0434\u043d\u0430\u043a\u043e Zero Day Initiative (ZDI) \u0443\u043f\u043e\u043c\u0438\u043d\u0430\u0435\u0442, \u0447\u0442\u043e \u043a\u0440\u0438\u0442\u0438\u0447\u0435\u0441\u043a\u0430\u044f CVE-2025-37093 \u0441\u0432\u044f\u0437\u0430\u043d\u0430 \u0441 machineAccountCheck \u0438 \u044f\u0432\u043b\u044f\u0435\u0442\u0441\u044f \u0440\u0435\u0437\u0443\u043b\u044c\u0442\u0430\u0442\u043e\u043c \u043d\u0435\u043f\u0440\u0430\u0432\u0438\u043b\u044c\u043d\u043e\u0439 \u0440\u0435\u0430\u043b\u0438\u0437\u0430\u0446\u0438\u0438 \u0430\u043b\u0433\u043e\u0440\u0438\u0442\u043c\u0430 \u0430\u0443\u0442\u0435\u043d\u0442\u0438\u0444\u0438\u043a\u0430\u0446\u0438\u0438.\n\nCVE-2025-37093 - \u0435\u0434\u0438\u043d\u0441\u0442\u0432\u0435\u043d\u043d\u0430\u044f \u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u044c, \u043e\u0446\u0435\u043d\u0435\u043d\u043d\u0430\u044f \u043a\u0430\u043a \u043a\u0440\u0438\u0442\u0438\u0447\u0435\u0441\u043a\u0430\u044f, \u043f\u0440\u0438 \u044d\u0442\u043e\u043c \u0434\u0440\u0443\u0433\u0438\u0435 \u0442\u0430\u043a\u0436\u0435 \u043d\u0435\u0441\u0443\u0442 \u0432 \u0441\u0435\u0431\u0435 \u0437\u043d\u0430\u0447\u0438\u0442\u0435\u043b\u044c\u043d\u044b\u0435 \u0440\u0438\u0441\u043a\u0438, \u0434\u0430\u0436\u0435 \u0435\u0441\u043b\u0438 \u043e\u043d\u0438 \u043e\u0442\u043d\u043e\u0441\u044f\u0442\u0441\u044f \u043a \u0431\u043e\u043b\u0435\u0435 \u043d\u0438\u0437\u043a\u0438\u043c \u043a\u0430\u0442\u0435\u0433\u043e\u0440\u0438\u044f\u043c \u043f\u043e \u0443\u0440\u043e\u0432\u043d\u044e \u0441\u0435\u0440\u044c\u0435\u0437\u043d\u043e\u0441\u0442\u0438.\n\nZDI \u043f\u043e\u044f\u0441\u043d\u044f\u0435\u0442, \u0447\u0442\u043e \u043f\u0440\u043e\u0431\u043b\u0435\u043c\u0430 \u043e\u0431\u0445\u043e\u0434\u0430 \u0430\u0443\u0442\u0435\u043d\u0442\u0438\u0444\u0438\u043a\u0430\u0446\u0438\u0438 \u044f\u0432\u043b\u044f\u0435\u0442\u0441\u044f \u043a\u043b\u044e\u0447\u043e\u043c \u043a \u0440\u0430\u0441\u043a\u0440\u044b\u0442\u0438\u044e \u043f\u043e\u0442\u0435\u043d\u0446\u0438\u0430\u043b\u0430 \u0432\u0441\u0435\u0445 \u043e\u0441\u0442\u0430\u043b\u044c\u043d\u044b\u0445 \u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u0435\u0439, \u043f\u043e\u044d\u0442\u043e\u043c\u0443 \u0438\u0445 \u0440\u0438\u0441\u043a \u043d\u0435 \u0441\u0442\u043e\u0438\u0442 \u0440\u0430\u0441\u0446\u0435\u043d\u0438\u0432\u0430\u0442\u044c \u0438\u0437\u043e\u043b\u0438\u0440\u043e\u0432\u0430\u043d\u043d\u044b\u043c.\n\n\u041f\u0440\u0438\u043c\u0435\u0440\u044b CVE-2025-3794 \u0438 CVE-2025-37095, \u0434\u0432\u0443\u0445 \u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u0435\u0439 \u0441\u0440\u0435\u0434\u043d\u0435\u0439 \u0441\u0442\u0435\u043f\u0435\u043d\u0438 \u0441\u0435\u0440\u044c\u0435\u0437\u043d\u043e\u0441\u0442\u0438, \u0441\u0432\u044f\u0437\u0430\u043d\u043d\u044b\u0445 \u0441 \u0443\u0434\u0430\u043b\u0435\u043d\u0438\u0435\u043c \u0444\u0430\u0439\u043b\u043e\u0432 \u0438 \u0440\u0430\u0441\u043a\u0440\u044b\u0442\u0438\u0435\u043c \u0438\u043d\u0444\u043e\u0440\u043c\u0430\u0446\u0438\u0438, \u043f\u043e\u043a\u0430\u0437\u044b\u0432\u0430\u044e\u0442, \u0447\u0442\u043e \u044d\u043a\u0441\u043f\u043b\u0443\u0430\u0442\u0430\u0446\u0438\u044f \u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u0438 \u043d\u0430 \u043f\u0440\u0430\u043a\u0442\u0438\u043a\u0435 \u043f\u0440\u043e\u0449\u0435, \u0447\u0435\u043c \u044d\u0442\u043e \u043e\u0442\u0440\u0430\u0436\u0435\u043d\u043e \u0432 \u043e\u0446\u0435\u043d\u043a\u0435.\n\n\u042d\u0442\u0430 \u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u044c \u043f\u043e\u0437\u0432\u043e\u043b\u044f\u0435\u0442 \u0443\u0434\u0430\u043b\u0435\u043d\u043d\u044b\u043c \u0437\u043b\u043e\u0443\u043c\u044b\u0448\u043b\u0435\u043d\u043d\u0438\u043a\u0430\u043c \u0440\u0430\u0441\u043a\u0440\u044b\u0432\u0430\u0442\u044c \u043a\u043e\u043d\u0444\u0438\u0434\u0435\u043d\u0446\u0438\u0430\u043b\u044c\u043d\u0443\u044e \u0438\u043d\u0444\u043e\u0440\u043c\u0430\u0446\u0438\u044e \u043e \u0437\u0430\u0442\u0440\u043e\u043d\u0443\u0442\u044b\u0445 \u0443\u0441\u0442\u0430\u043d\u043e\u0432\u043a\u0430\u0445 Hewlett Packard Enterprise StoreOnce VSA. \u0425\u043e\u0442\u044f \u0434\u043b\u044f \u044d\u043a\u0441\u043f\u043b\u0443\u0430\u0442\u0430\u0446\u0438\u0438 \u0442\u0440\u0435\u0431\u0443\u0435\u0442\u0441\u044f \u0430\u0443\u0442\u0435\u043d\u0442\u0438\u0444\u0438\u043a\u0430\u0446\u0438\u044f, \u0441\u0443\u0449\u0435\u0441\u0442\u0432\u0443\u044e\u0449\u0438\u0439 \u043c\u0435\u0445\u0430\u043d\u0438\u0437\u043c \u0430\u0443\u0442\u0435\u043d\u0442\u0438\u0444\u0438\u043a\u0430\u0446\u0438\u0438 \u043c\u043e\u0436\u043d\u043e \u043e\u0431\u043e\u0439\u0442\u0438.\n\n\u041f\u0440\u0438\u043c\u0435\u0447\u0430\u0442\u0435\u043b\u044c\u043d\u043e, \u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u0438 \u0431\u044b\u043b\u0438 \u043e\u0431\u043d\u0430\u0440\u0443\u0436\u0435\u043d\u044b \u0435\u0449\u0435 \u0432 \u043e\u043a\u0442\u044f\u0431\u0440\u0435 2024 \u0433\u043e\u0434\u0430 \u0438 \u043f\u043e\u0442\u0440\u0435\u0431\u043e\u0432\u0430\u043b\u043e\u0441\u044c \u0446\u0435\u043b\u044b\u0445 \u0441\u0435\u043c\u044c \u043c\u0435\u0441\u044f\u0446\u0435\u0432, \u043f\u0440\u0435\u0436\u0434\u0435 \u0447\u0435\u043c \u0438\u0441\u043f\u0440\u0430\u0432\u043b\u0435\u043d\u0438\u044f \u043d\u0430\u043a\u043e\u043d\u0435\u0446-\u0442\u043e \u0441\u0442\u0430\u043b\u0438 \u0434\u043e\u0441\u0442\u0443\u043f\u043d\u044b. \u0422\u0435\u043c \u043d\u0435 \u043c\u0435\u043d\u0435\u0435, \u043d\u0435\u0442 \u043d\u0438\u043a\u0430\u043a\u0438\u0445 \u0441\u043e\u043e\u0431\u0449\u0435\u043d\u0438\u0439 \u043e\u0431 \u0430\u043a\u0442\u0438\u0432\u043d\u043e\u0439 \u044d\u043a\u0441\u043f\u043b\u0443\u0430\u0442\u0430\u0446\u0438\u0438.\n\nHPE \u043d\u0435 \u043e\u0442\u043c\u0435\u0442\u0438\u043b\u0430 \u0432 \u0431\u044e\u043b\u043b\u0435\u0442\u0435\u043d\u0435 \u043d\u0438\u043a\u0430\u043a\u0438\u0445 \u043e\u0431\u0445\u043e\u0434\u043d\u044b\u0445 \u043f\u0443\u0442\u0435\u0439 \u0434\u043b\u044f \u0432\u043e\u0441\u044c\u043c\u0438 \u043d\u0435\u0434\u043e\u0441\u0442\u0430\u0442\u043a\u043e\u0432, \u043f\u043e\u044d\u0442\u043e\u043c\u0443 \u0440\u0435\u043a\u043e\u043c\u0435\u043d\u0434\u0443\u0435\u043c\u044b\u043c \u0440\u0435\u0448\u0435\u043d\u0438\u0435\u043c \u044f\u0432\u043b\u044f\u0435\u0442\u0441\u044f \u043e\u0431\u043d\u043e\u0432\u043b\u0435\u043d\u0438\u0435.", "creation_timestamp": "2025-06-04T16:30:06.000000Z"}, {"uuid": "aa37d5d7-1e83-4dcc-b34c-168311143138", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37089", "type": "seen", "source": "https://t.me/true_secator/7102", "content": "Hewlett Packard Enterprise (HPE) \u0432 \u0441\u0432\u043e\u0435\u043c \u043d\u043e\u0432\u043e\u043c \u0431\u044e\u043b\u043b\u0435\u0442\u0435\u043d\u0435 \u043f\u043e \u0431\u0435\u0437\u043e\u043f\u0430\u0441\u043d\u043e\u0441\u0442\u0438 \u043f\u0440\u0435\u0434\u0443\u043f\u0440\u0435\u0436\u0434\u0430\u0435\u0442 \u043e \u0432\u043e\u0441\u044c\u043c\u0438 \u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u044f\u0445, \u0432\u043b\u0438\u044f\u044e\u0449\u0438\u0445 \u043d\u0430 \u0440\u0430\u0431\u043e\u0442\u0443 StoreOnce, \u0440\u0435\u0448\u0435\u043d\u0438\u044f \u0434\u043b\u044f \u0440\u0435\u0437\u0435\u0440\u0432\u043d\u043e\u0433\u043e \u043a\u043e\u043f\u0438\u0440\u043e\u0432\u0430\u043d\u0438\u044f \u0438 \u0434\u0435\u0434\u0443\u043f\u043b\u0438\u043a\u0430\u0446\u0438\u0438 \u043d\u0430 \u043e\u0441\u043d\u043e\u0432\u0435 \u0434\u0438\u0441\u043a\u043e\u0432.\n\nHPE StoreOnce \u043e\u0431\u044b\u0447\u043d\u043e \u0438\u0441\u043f\u043e\u043b\u044c\u0437\u0443\u0435\u0442\u0441\u044f \u0434\u043b\u044f \u0440\u0435\u0437\u0435\u0440\u0432\u043d\u043e\u0433\u043e \u043a\u043e\u043f\u0438\u0440\u043e\u0432\u0430\u043d\u0438\u044f \u0438 \u0432\u043e\u0441\u0441\u0442\u0430\u043d\u043e\u0432\u043b\u0435\u043d\u0438\u044f \u043d\u0430 \u043a\u0440\u0443\u043f\u043d\u044b\u0445 \u043f\u0440\u0435\u0434\u043f\u0440\u0438\u044f\u0442\u0438\u044f\u0445, \u0432 \u0426\u041e\u0414\u0430\u0445, \u0443 \u043f\u043e\u0441\u0442\u0430\u0432\u0449\u0438\u043a\u043e\u0432 \u043e\u0431\u043b\u0430\u0447\u043d\u044b\u0445 \u0443\u0441\u043b\u0443\u0433 \u0438 \u0432 \u0446\u0435\u043b\u043e\u043c \u0432 \u043e\u0440\u0433\u0430\u043d\u0438\u0437\u0430\u0446\u0438\u044f\u0445, \u043e\u0431\u0440\u0430\u0431\u0430\u0442\u044b\u0432\u0430\u044e\u0449\u0438\u0445 \u0431\u043e\u043b\u044c\u0448\u0438\u0435 \u0434\u0430\u043d\u043d\u044b\u0435 \u0438\u043b\u0438 \u043a\u0440\u0443\u043f\u043d\u044b\u0435 \u0432\u0438\u0440\u0442\u0443\u0430\u043b\u0438\u0437\u0438\u0440\u043e\u0432\u0430\u043d\u043d\u044b\u0435 \u0441\u0440\u0435\u0434\u044b.\n\nStoreOnce \u0438\u043d\u0442\u0435\u0433\u0440\u0438\u0440\u0443\u0435\u0442\u0441\u044f \u0441 \u041f\u041e \u0434\u043b\u044f \u0440\u0435\u0437\u0435\u0440\u0432\u043d\u043e\u0433\u043e \u043a\u043e\u043f\u0438\u0440\u043e\u0432\u0430\u043d\u0438\u044f, \u0432\u043a\u043b\u044e\u0447\u0430\u044f HPE Data Protector, Veeam, Commvault \u0438 Veritas NetBackup, \u043e\u0431\u0435\u0441\u043f\u0435\u0447\u0438\u0432\u0430\u044f \u043d\u0435\u043f\u0440\u0435\u0440\u044b\u0432\u043d\u043e\u0441\u0442\u044c \u0431\u0438\u0437\u043d\u0435\u0441\u0430 \u0438 \u044d\u0444\u0444\u0435\u043a\u0442\u0438\u0432\u043d\u043e\u0435 \u0443\u043f\u0440\u0430\u0432\u043b\u0435\u043d\u0438\u0435 \u0440\u0435\u0437\u0435\u0440\u0432\u043d\u044b\u043c \u043a\u043e\u043f\u0438\u0440\u043e\u0432\u0430\u043d\u0438\u0435\u043c.\n\n\u041e\u0441\u043e\u0431\u043e\u0435 \u0432\u043d\u0438\u043c\u0430\u043d\u0438\u0435 \u0441\u043b\u0435\u0434\u0443\u0435\u0442 \u043e\u0431\u0440\u0430\u0442\u0438\u0442\u044c \u043d\u0430 \u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u044c \u043e\u0431\u0445\u043e\u0434\u0430 \u0430\u0443\u0442\u0435\u043d\u0442\u0438\u0444\u0438\u043a\u0430\u0446\u0438\u0438 \u043a\u0440\u0438\u0442\u0438\u0447\u0435\u0441\u043a\u043e\u0439 \u0441\u0442\u0435\u043f\u0435\u043d\u0438 \u0441\u0435\u0440\u044c\u0435\u0437\u043d\u043e\u0441\u0442\u0438 (CVSS v3.1: 9,8), \u043a\u043e\u0442\u043e\u0440\u0430\u044f \u043e\u0442\u0441\u043b\u0435\u0436\u0438\u0432\u0430\u0435\u0442\u0441\u044f \u043a\u0430\u043a CVE-2025-37093.\n\n\u041a\u0440\u043e\u043c\u0435 \u0442\u043e\u0433\u043e, \u0438\u0441\u043f\u0440\u0430\u0432\u043b\u0435\u043d\u044b \u0447\u0435\u0442\u044b\u0440\u0435 RCE (CVE-2025-37089, 37091, 37092, 37096), \u0434\u0432\u0435 \u043f\u0440\u043e\u0431\u043b\u0435\u043c\u044b \u043e\u0431\u0445\u043e\u0434\u0430 \u043a\u0430\u0442\u0430\u043b\u043e\u0433\u043e\u0432 (CVE-2025-37094 \u0438 CVE-2025-37095) \u0438 \u043f\u0440\u043e\u0431\u043b\u0435\u043c\u0430 \u043f\u043e\u0434\u0434\u0435\u043b\u043a\u0438 \u0437\u0430\u043f\u0440\u043e\u0441\u043e\u0432 \u043d\u0430 \u0441\u0442\u043e\u0440\u043e\u043d\u0435 \u0441\u0435\u0440\u0432\u0435\u0440\u0430 (CVE-2025-37090).\n\n\u0417\u0430\u0442\u0440\u043e\u043d\u0443\u0442\u044b \u0432\u0441\u0435 \u0432\u0435\u0440\u0441\u0438\u0438 HPE StoreOnce \u0434\u043e 4.3.11, \u043a\u043e\u0442\u043e\u0440\u0430\u044f \u0442\u0435\u043f\u0435\u0440\u044c \u044f\u0432\u043b\u044f\u0435\u0442\u0441\u044f \u0440\u0435\u043a\u043e\u043c\u0435\u043d\u0434\u0443\u0435\u043c\u043e\u0439 \u0432\u0435\u0440\u0441\u0438\u0435\u0439 \u043e\u0431\u043d\u043e\u0432\u043b\u0435\u043d\u0438\u044f. \u041d\u0430 \u044d\u0442\u043e\u0442 \u0440\u0430\u0437 \u043f\u043e\u0434\u0440\u043e\u0431\u043d\u043e\u0441\u0442\u0435\u0439 \u043e \u043d\u0435\u0434\u043e\u0441\u0442\u0430\u0442\u043a\u0430\u0445 \u0440\u0430\u0441\u043a\u0440\u044b\u0442\u043e \u043d\u0435 \u0442\u0430\u043a \u043c\u043d\u043e\u0433\u043e.\n\n\u041e\u0434\u043d\u0430\u043a\u043e Zero Day Initiative (ZDI) \u0443\u043f\u043e\u043c\u0438\u043d\u0430\u0435\u0442, \u0447\u0442\u043e \u043a\u0440\u0438\u0442\u0438\u0447\u0435\u0441\u043a\u0430\u044f CVE-2025-37093 \u0441\u0432\u044f\u0437\u0430\u043d\u0430 \u0441 machineAccountCheck \u0438 \u044f\u0432\u043b\u044f\u0435\u0442\u0441\u044f \u0440\u0435\u0437\u0443\u043b\u044c\u0442\u0430\u0442\u043e\u043c \u043d\u0435\u043f\u0440\u0430\u0432\u0438\u043b\u044c\u043d\u043e\u0439 \u0440\u0435\u0430\u043b\u0438\u0437\u0430\u0446\u0438\u0438 \u0430\u043b\u0433\u043e\u0440\u0438\u0442\u043c\u0430 \u0430\u0443\u0442\u0435\u043d\u0442\u0438\u0444\u0438\u043a\u0430\u0446\u0438\u0438.\n\nCVE-2025-37093 - \u0435\u0434\u0438\u043d\u0441\u0442\u0432\u0435\u043d\u043d\u0430\u044f \u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u044c, \u043e\u0446\u0435\u043d\u0435\u043d\u043d\u0430\u044f \u043a\u0430\u043a \u043a\u0440\u0438\u0442\u0438\u0447\u0435\u0441\u043a\u0430\u044f, \u043f\u0440\u0438 \u044d\u0442\u043e\u043c \u0434\u0440\u0443\u0433\u0438\u0435 \u0442\u0430\u043a\u0436\u0435 \u043d\u0435\u0441\u0443\u0442 \u0432 \u0441\u0435\u0431\u0435 \u0437\u043d\u0430\u0447\u0438\u0442\u0435\u043b\u044c\u043d\u044b\u0435 \u0440\u0438\u0441\u043a\u0438, \u0434\u0430\u0436\u0435 \u0435\u0441\u043b\u0438 \u043e\u043d\u0438 \u043e\u0442\u043d\u043e\u0441\u044f\u0442\u0441\u044f \u043a \u0431\u043e\u043b\u0435\u0435 \u043d\u0438\u0437\u043a\u0438\u043c \u043a\u0430\u0442\u0435\u0433\u043e\u0440\u0438\u044f\u043c \u043f\u043e \u0443\u0440\u043e\u0432\u043d\u044e \u0441\u0435\u0440\u044c\u0435\u0437\u043d\u043e\u0441\u0442\u0438.\n\nZDI \u043f\u043e\u044f\u0441\u043d\u044f\u0435\u0442, \u0447\u0442\u043e \u043f\u0440\u043e\u0431\u043b\u0435\u043c\u0430 \u043e\u0431\u0445\u043e\u0434\u0430 \u0430\u0443\u0442\u0435\u043d\u0442\u0438\u0444\u0438\u043a\u0430\u0446\u0438\u0438 \u044f\u0432\u043b\u044f\u0435\u0442\u0441\u044f \u043a\u043b\u044e\u0447\u043e\u043c \u043a \u0440\u0430\u0441\u043a\u0440\u044b\u0442\u0438\u044e \u043f\u043e\u0442\u0435\u043d\u0446\u0438\u0430\u043b\u0430 \u0432\u0441\u0435\u0445 \u043e\u0441\u0442\u0430\u043b\u044c\u043d\u044b\u0445 \u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u0435\u0439, \u043f\u043e\u044d\u0442\u043e\u043c\u0443 \u0438\u0445 \u0440\u0438\u0441\u043a \u043d\u0435 \u0441\u0442\u043e\u0438\u0442 \u0440\u0430\u0441\u0446\u0435\u043d\u0438\u0432\u0430\u0442\u044c \u0438\u0437\u043e\u043b\u0438\u0440\u043e\u0432\u0430\u043d\u043d\u044b\u043c.\n\n\u041f\u0440\u0438\u043c\u0435\u0440\u044b CVE-2025-3794 \u0438 CVE-2025-37095, \u0434\u0432\u0443\u0445 \u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u0435\u0439 \u0441\u0440\u0435\u0434\u043d\u0435\u0439 \u0441\u0442\u0435\u043f\u0435\u043d\u0438 \u0441\u0435\u0440\u044c\u0435\u0437\u043d\u043e\u0441\u0442\u0438, \u0441\u0432\u044f\u0437\u0430\u043d\u043d\u044b\u0445 \u0441 \u0443\u0434\u0430\u043b\u0435\u043d\u0438\u0435\u043c \u0444\u0430\u0439\u043b\u043e\u0432 \u0438 \u0440\u0430\u0441\u043a\u0440\u044b\u0442\u0438\u0435\u043c \u0438\u043d\u0444\u043e\u0440\u043c\u0430\u0446\u0438\u0438, \u043f\u043e\u043a\u0430\u0437\u044b\u0432\u0430\u044e\u0442, \u0447\u0442\u043e \u044d\u043a\u0441\u043f\u043b\u0443\u0430\u0442\u0430\u0446\u0438\u044f \u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u0438 \u043d\u0430 \u043f\u0440\u0430\u043a\u0442\u0438\u043a\u0435 \u043f\u0440\u043e\u0449\u0435, \u0447\u0435\u043c \u044d\u0442\u043e \u043e\u0442\u0440\u0430\u0436\u0435\u043d\u043e \u0432 \u043e\u0446\u0435\u043d\u043a\u0435.\n\n\u042d\u0442\u0430 \u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u044c \u043f\u043e\u0437\u0432\u043e\u043b\u044f\u0435\u0442 \u0443\u0434\u0430\u043b\u0435\u043d\u043d\u044b\u043c \u0437\u043b\u043e\u0443\u043c\u044b\u0448\u043b\u0435\u043d\u043d\u0438\u043a\u0430\u043c \u0440\u0430\u0441\u043a\u0440\u044b\u0432\u0430\u0442\u044c \u043a\u043e\u043d\u0444\u0438\u0434\u0435\u043d\u0446\u0438\u0430\u043b\u044c\u043d\u0443\u044e \u0438\u043d\u0444\u043e\u0440\u043c\u0430\u0446\u0438\u044e \u043e \u0437\u0430\u0442\u0440\u043e\u043d\u0443\u0442\u044b\u0445 \u0443\u0441\u0442\u0430\u043d\u043e\u0432\u043a\u0430\u0445 Hewlett Packard Enterprise StoreOnce VSA. \u0425\u043e\u0442\u044f \u0434\u043b\u044f \u044d\u043a\u0441\u043f\u043b\u0443\u0430\u0442\u0430\u0446\u0438\u0438 \u0442\u0440\u0435\u0431\u0443\u0435\u0442\u0441\u044f \u0430\u0443\u0442\u0435\u043d\u0442\u0438\u0444\u0438\u043a\u0430\u0446\u0438\u044f, \u0441\u0443\u0449\u0435\u0441\u0442\u0432\u0443\u044e\u0449\u0438\u0439 \u043c\u0435\u0445\u0430\u043d\u0438\u0437\u043c \u0430\u0443\u0442\u0435\u043d\u0442\u0438\u0444\u0438\u043a\u0430\u0446\u0438\u0438 \u043c\u043e\u0436\u043d\u043e \u043e\u0431\u043e\u0439\u0442\u0438.\n\n\u041f\u0440\u0438\u043c\u0435\u0447\u0430\u0442\u0435\u043b\u044c\u043d\u043e, \u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u0438 \u0431\u044b\u043b\u0438 \u043e\u0431\u043d\u0430\u0440\u0443\u0436\u0435\u043d\u044b \u0435\u0449\u0435 \u0432 \u043e\u043a\u0442\u044f\u0431\u0440\u0435 2024 \u0433\u043e\u0434\u0430 \u0438 \u043f\u043e\u0442\u0440\u0435\u0431\u043e\u0432\u0430\u043b\u043e\u0441\u044c \u0446\u0435\u043b\u044b\u0445 \u0441\u0435\u043c\u044c \u043c\u0435\u0441\u044f\u0446\u0435\u0432, \u043f\u0440\u0435\u0436\u0434\u0435 \u0447\u0435\u043c \u0438\u0441\u043f\u0440\u0430\u0432\u043b\u0435\u043d\u0438\u044f \u043d\u0430\u043a\u043e\u043d\u0435\u0446-\u0442\u043e \u0441\u0442\u0430\u043b\u0438 \u0434\u043e\u0441\u0442\u0443\u043f\u043d\u044b. \u0422\u0435\u043c \u043d\u0435 \u043c\u0435\u043d\u0435\u0435, \u043d\u0435\u0442 \u043d\u0438\u043a\u0430\u043a\u0438\u0445 \u0441\u043e\u043e\u0431\u0449\u0435\u043d\u0438\u0439 \u043e\u0431 \u0430\u043a\u0442\u0438\u0432\u043d\u043e\u0439 \u044d\u043a\u0441\u043f\u043b\u0443\u0430\u0442\u0430\u0446\u0438\u0438.\n\nHPE \u043d\u0435 \u043e\u0442\u043c\u0435\u0442\u0438\u043b\u0430 \u0432 \u0431\u044e\u043b\u043b\u0435\u0442\u0435\u043d\u0435 \u043d\u0438\u043a\u0430\u043a\u0438\u0445 \u043e\u0431\u0445\u043e\u0434\u043d\u044b\u0445 \u043f\u0443\u0442\u0435\u0439 \u0434\u043b\u044f \u0432\u043e\u0441\u044c\u043c\u0438 \u043d\u0435\u0434\u043e\u0441\u0442\u0430\u0442\u043a\u043e\u0432, \u043f\u043e\u044d\u0442\u043e\u043c\u0443 \u0440\u0435\u043a\u043e\u043c\u0435\u043d\u0434\u0443\u0435\u043c\u044b\u043c \u0440\u0435\u0448\u0435\u043d\u0438\u0435\u043c \u044f\u0432\u043b\u044f\u0435\u0442\u0441\u044f \u043e\u0431\u043d\u043e\u0432\u043b\u0435\u043d\u0438\u0435.", "creation_timestamp": "2025-06-04T16:30:06.000000Z"}, {"uuid": "4b82a685-617b-4ad3-b1dd-14c097160c0f", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37090", "type": "seen", "source": "https://t.me/true_secator/7102", "content": "Hewlett Packard Enterprise (HPE) \u0432 \u0441\u0432\u043e\u0435\u043c \u043d\u043e\u0432\u043e\u043c \u0431\u044e\u043b\u043b\u0435\u0442\u0435\u043d\u0435 \u043f\u043e \u0431\u0435\u0437\u043e\u043f\u0430\u0441\u043d\u043e\u0441\u0442\u0438 \u043f\u0440\u0435\u0434\u0443\u043f\u0440\u0435\u0436\u0434\u0430\u0435\u0442 \u043e \u0432\u043e\u0441\u044c\u043c\u0438 \u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u044f\u0445, \u0432\u043b\u0438\u044f\u044e\u0449\u0438\u0445 \u043d\u0430 \u0440\u0430\u0431\u043e\u0442\u0443 StoreOnce, \u0440\u0435\u0448\u0435\u043d\u0438\u044f \u0434\u043b\u044f \u0440\u0435\u0437\u0435\u0440\u0432\u043d\u043e\u0433\u043e \u043a\u043e\u043f\u0438\u0440\u043e\u0432\u0430\u043d\u0438\u044f \u0438 \u0434\u0435\u0434\u0443\u043f\u043b\u0438\u043a\u0430\u0446\u0438\u0438 \u043d\u0430 \u043e\u0441\u043d\u043e\u0432\u0435 \u0434\u0438\u0441\u043a\u043e\u0432.\n\nHPE StoreOnce \u043e\u0431\u044b\u0447\u043d\u043e \u0438\u0441\u043f\u043e\u043b\u044c\u0437\u0443\u0435\u0442\u0441\u044f \u0434\u043b\u044f \u0440\u0435\u0437\u0435\u0440\u0432\u043d\u043e\u0433\u043e \u043a\u043e\u043f\u0438\u0440\u043e\u0432\u0430\u043d\u0438\u044f \u0438 \u0432\u043e\u0441\u0441\u0442\u0430\u043d\u043e\u0432\u043b\u0435\u043d\u0438\u044f \u043d\u0430 \u043a\u0440\u0443\u043f\u043d\u044b\u0445 \u043f\u0440\u0435\u0434\u043f\u0440\u0438\u044f\u0442\u0438\u044f\u0445, \u0432 \u0426\u041e\u0414\u0430\u0445, \u0443 \u043f\u043e\u0441\u0442\u0430\u0432\u0449\u0438\u043a\u043e\u0432 \u043e\u0431\u043b\u0430\u0447\u043d\u044b\u0445 \u0443\u0441\u043b\u0443\u0433 \u0438 \u0432 \u0446\u0435\u043b\u043e\u043c \u0432 \u043e\u0440\u0433\u0430\u043d\u0438\u0437\u0430\u0446\u0438\u044f\u0445, \u043e\u0431\u0440\u0430\u0431\u0430\u0442\u044b\u0432\u0430\u044e\u0449\u0438\u0445 \u0431\u043e\u043b\u044c\u0448\u0438\u0435 \u0434\u0430\u043d\u043d\u044b\u0435 \u0438\u043b\u0438 \u043a\u0440\u0443\u043f\u043d\u044b\u0435 \u0432\u0438\u0440\u0442\u0443\u0430\u043b\u0438\u0437\u0438\u0440\u043e\u0432\u0430\u043d\u043d\u044b\u0435 \u0441\u0440\u0435\u0434\u044b.\n\nStoreOnce \u0438\u043d\u0442\u0435\u0433\u0440\u0438\u0440\u0443\u0435\u0442\u0441\u044f \u0441 \u041f\u041e \u0434\u043b\u044f \u0440\u0435\u0437\u0435\u0440\u0432\u043d\u043e\u0433\u043e \u043a\u043e\u043f\u0438\u0440\u043e\u0432\u0430\u043d\u0438\u044f, \u0432\u043a\u043b\u044e\u0447\u0430\u044f HPE Data Protector, Veeam, Commvault \u0438 Veritas NetBackup, \u043e\u0431\u0435\u0441\u043f\u0435\u0447\u0438\u0432\u0430\u044f \u043d\u0435\u043f\u0440\u0435\u0440\u044b\u0432\u043d\u043e\u0441\u0442\u044c \u0431\u0438\u0437\u043d\u0435\u0441\u0430 \u0438 \u044d\u0444\u0444\u0435\u043a\u0442\u0438\u0432\u043d\u043e\u0435 \u0443\u043f\u0440\u0430\u0432\u043b\u0435\u043d\u0438\u0435 \u0440\u0435\u0437\u0435\u0440\u0432\u043d\u044b\u043c \u043a\u043e\u043f\u0438\u0440\u043e\u0432\u0430\u043d\u0438\u0435\u043c.\n\n\u041e\u0441\u043e\u0431\u043e\u0435 \u0432\u043d\u0438\u043c\u0430\u043d\u0438\u0435 \u0441\u043b\u0435\u0434\u0443\u0435\u0442 \u043e\u0431\u0440\u0430\u0442\u0438\u0442\u044c \u043d\u0430 \u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u044c \u043e\u0431\u0445\u043e\u0434\u0430 \u0430\u0443\u0442\u0435\u043d\u0442\u0438\u0444\u0438\u043a\u0430\u0446\u0438\u0438 \u043a\u0440\u0438\u0442\u0438\u0447\u0435\u0441\u043a\u043e\u0439 \u0441\u0442\u0435\u043f\u0435\u043d\u0438 \u0441\u0435\u0440\u044c\u0435\u0437\u043d\u043e\u0441\u0442\u0438 (CVSS v3.1: 9,8), \u043a\u043e\u0442\u043e\u0440\u0430\u044f \u043e\u0442\u0441\u043b\u0435\u0436\u0438\u0432\u0430\u0435\u0442\u0441\u044f \u043a\u0430\u043a CVE-2025-37093.\n\n\u041a\u0440\u043e\u043c\u0435 \u0442\u043e\u0433\u043e, \u0438\u0441\u043f\u0440\u0430\u0432\u043b\u0435\u043d\u044b \u0447\u0435\u0442\u044b\u0440\u0435 RCE (CVE-2025-37089, 37091, 37092, 37096), \u0434\u0432\u0435 \u043f\u0440\u043e\u0431\u043b\u0435\u043c\u044b \u043e\u0431\u0445\u043e\u0434\u0430 \u043a\u0430\u0442\u0430\u043b\u043e\u0433\u043e\u0432 (CVE-2025-37094 \u0438 CVE-2025-37095) \u0438 \u043f\u0440\u043e\u0431\u043b\u0435\u043c\u0430 \u043f\u043e\u0434\u0434\u0435\u043b\u043a\u0438 \u0437\u0430\u043f\u0440\u043e\u0441\u043e\u0432 \u043d\u0430 \u0441\u0442\u043e\u0440\u043e\u043d\u0435 \u0441\u0435\u0440\u0432\u0435\u0440\u0430 (CVE-2025-37090).\n\n\u0417\u0430\u0442\u0440\u043e\u043d\u0443\u0442\u044b \u0432\u0441\u0435 \u0432\u0435\u0440\u0441\u0438\u0438 HPE StoreOnce \u0434\u043e 4.3.11, \u043a\u043e\u0442\u043e\u0440\u0430\u044f \u0442\u0435\u043f\u0435\u0440\u044c \u044f\u0432\u043b\u044f\u0435\u0442\u0441\u044f \u0440\u0435\u043a\u043e\u043c\u0435\u043d\u0434\u0443\u0435\u043c\u043e\u0439 \u0432\u0435\u0440\u0441\u0438\u0435\u0439 \u043e\u0431\u043d\u043e\u0432\u043b\u0435\u043d\u0438\u044f. \u041d\u0430 \u044d\u0442\u043e\u0442 \u0440\u0430\u0437 \u043f\u043e\u0434\u0440\u043e\u0431\u043d\u043e\u0441\u0442\u0435\u0439 \u043e \u043d\u0435\u0434\u043e\u0441\u0442\u0430\u0442\u043a\u0430\u0445 \u0440\u0430\u0441\u043a\u0440\u044b\u0442\u043e \u043d\u0435 \u0442\u0430\u043a \u043c\u043d\u043e\u0433\u043e.\n\n\u041e\u0434\u043d\u0430\u043a\u043e Zero Day Initiative (ZDI) \u0443\u043f\u043e\u043c\u0438\u043d\u0430\u0435\u0442, \u0447\u0442\u043e \u043a\u0440\u0438\u0442\u0438\u0447\u0435\u0441\u043a\u0430\u044f CVE-2025-37093 \u0441\u0432\u044f\u0437\u0430\u043d\u0430 \u0441 machineAccountCheck \u0438 \u044f\u0432\u043b\u044f\u0435\u0442\u0441\u044f \u0440\u0435\u0437\u0443\u043b\u044c\u0442\u0430\u0442\u043e\u043c \u043d\u0435\u043f\u0440\u0430\u0432\u0438\u043b\u044c\u043d\u043e\u0439 \u0440\u0435\u0430\u043b\u0438\u0437\u0430\u0446\u0438\u0438 \u0430\u043b\u0433\u043e\u0440\u0438\u0442\u043c\u0430 \u0430\u0443\u0442\u0435\u043d\u0442\u0438\u0444\u0438\u043a\u0430\u0446\u0438\u0438.\n\nCVE-2025-37093 - \u0435\u0434\u0438\u043d\u0441\u0442\u0432\u0435\u043d\u043d\u0430\u044f \u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u044c, \u043e\u0446\u0435\u043d\u0435\u043d\u043d\u0430\u044f \u043a\u0430\u043a \u043a\u0440\u0438\u0442\u0438\u0447\u0435\u0441\u043a\u0430\u044f, \u043f\u0440\u0438 \u044d\u0442\u043e\u043c \u0434\u0440\u0443\u0433\u0438\u0435 \u0442\u0430\u043a\u0436\u0435 \u043d\u0435\u0441\u0443\u0442 \u0432 \u0441\u0435\u0431\u0435 \u0437\u043d\u0430\u0447\u0438\u0442\u0435\u043b\u044c\u043d\u044b\u0435 \u0440\u0438\u0441\u043a\u0438, \u0434\u0430\u0436\u0435 \u0435\u0441\u043b\u0438 \u043e\u043d\u0438 \u043e\u0442\u043d\u043e\u0441\u044f\u0442\u0441\u044f \u043a \u0431\u043e\u043b\u0435\u0435 \u043d\u0438\u0437\u043a\u0438\u043c \u043a\u0430\u0442\u0435\u0433\u043e\u0440\u0438\u044f\u043c \u043f\u043e \u0443\u0440\u043e\u0432\u043d\u044e \u0441\u0435\u0440\u044c\u0435\u0437\u043d\u043e\u0441\u0442\u0438.\n\nZDI \u043f\u043e\u044f\u0441\u043d\u044f\u0435\u0442, \u0447\u0442\u043e \u043f\u0440\u043e\u0431\u043b\u0435\u043c\u0430 \u043e\u0431\u0445\u043e\u0434\u0430 \u0430\u0443\u0442\u0435\u043d\u0442\u0438\u0444\u0438\u043a\u0430\u0446\u0438\u0438 \u044f\u0432\u043b\u044f\u0435\u0442\u0441\u044f \u043a\u043b\u044e\u0447\u043e\u043c \u043a \u0440\u0430\u0441\u043a\u0440\u044b\u0442\u0438\u044e \u043f\u043e\u0442\u0435\u043d\u0446\u0438\u0430\u043b\u0430 \u0432\u0441\u0435\u0445 \u043e\u0441\u0442\u0430\u043b\u044c\u043d\u044b\u0445 \u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u0435\u0439, \u043f\u043e\u044d\u0442\u043e\u043c\u0443 \u0438\u0445 \u0440\u0438\u0441\u043a \u043d\u0435 \u0441\u0442\u043e\u0438\u0442 \u0440\u0430\u0441\u0446\u0435\u043d\u0438\u0432\u0430\u0442\u044c \u0438\u0437\u043e\u043b\u0438\u0440\u043e\u0432\u0430\u043d\u043d\u044b\u043c.\n\n\u041f\u0440\u0438\u043c\u0435\u0440\u044b CVE-2025-3794 \u0438 CVE-2025-37095, \u0434\u0432\u0443\u0445 \u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u0435\u0439 \u0441\u0440\u0435\u0434\u043d\u0435\u0439 \u0441\u0442\u0435\u043f\u0435\u043d\u0438 \u0441\u0435\u0440\u044c\u0435\u0437\u043d\u043e\u0441\u0442\u0438, \u0441\u0432\u044f\u0437\u0430\u043d\u043d\u044b\u0445 \u0441 \u0443\u0434\u0430\u043b\u0435\u043d\u0438\u0435\u043c \u0444\u0430\u0439\u043b\u043e\u0432 \u0438 \u0440\u0430\u0441\u043a\u0440\u044b\u0442\u0438\u0435\u043c \u0438\u043d\u0444\u043e\u0440\u043c\u0430\u0446\u0438\u0438, \u043f\u043e\u043a\u0430\u0437\u044b\u0432\u0430\u044e\u0442, \u0447\u0442\u043e \u044d\u043a\u0441\u043f\u043b\u0443\u0430\u0442\u0430\u0446\u0438\u044f \u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u0438 \u043d\u0430 \u043f\u0440\u0430\u043a\u0442\u0438\u043a\u0435 \u043f\u0440\u043e\u0449\u0435, \u0447\u0435\u043c \u044d\u0442\u043e \u043e\u0442\u0440\u0430\u0436\u0435\u043d\u043e \u0432 \u043e\u0446\u0435\u043d\u043a\u0435.\n\n\u042d\u0442\u0430 \u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u044c \u043f\u043e\u0437\u0432\u043e\u043b\u044f\u0435\u0442 \u0443\u0434\u0430\u043b\u0435\u043d\u043d\u044b\u043c \u0437\u043b\u043e\u0443\u043c\u044b\u0448\u043b\u0435\u043d\u043d\u0438\u043a\u0430\u043c \u0440\u0430\u0441\u043a\u0440\u044b\u0432\u0430\u0442\u044c \u043a\u043e\u043d\u0444\u0438\u0434\u0435\u043d\u0446\u0438\u0430\u043b\u044c\u043d\u0443\u044e \u0438\u043d\u0444\u043e\u0440\u043c\u0430\u0446\u0438\u044e \u043e \u0437\u0430\u0442\u0440\u043e\u043d\u0443\u0442\u044b\u0445 \u0443\u0441\u0442\u0430\u043d\u043e\u0432\u043a\u0430\u0445 Hewlett Packard Enterprise StoreOnce VSA. \u0425\u043e\u0442\u044f \u0434\u043b\u044f \u044d\u043a\u0441\u043f\u043b\u0443\u0430\u0442\u0430\u0446\u0438\u0438 \u0442\u0440\u0435\u0431\u0443\u0435\u0442\u0441\u044f \u0430\u0443\u0442\u0435\u043d\u0442\u0438\u0444\u0438\u043a\u0430\u0446\u0438\u044f, \u0441\u0443\u0449\u0435\u0441\u0442\u0432\u0443\u044e\u0449\u0438\u0439 \u043c\u0435\u0445\u0430\u043d\u0438\u0437\u043c \u0430\u0443\u0442\u0435\u043d\u0442\u0438\u0444\u0438\u043a\u0430\u0446\u0438\u0438 \u043c\u043e\u0436\u043d\u043e \u043e\u0431\u043e\u0439\u0442\u0438.\n\n\u041f\u0440\u0438\u043c\u0435\u0447\u0430\u0442\u0435\u043b\u044c\u043d\u043e, \u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u0438 \u0431\u044b\u043b\u0438 \u043e\u0431\u043d\u0430\u0440\u0443\u0436\u0435\u043d\u044b \u0435\u0449\u0435 \u0432 \u043e\u043a\u0442\u044f\u0431\u0440\u0435 2024 \u0433\u043e\u0434\u0430 \u0438 \u043f\u043e\u0442\u0440\u0435\u0431\u043e\u0432\u0430\u043b\u043e\u0441\u044c \u0446\u0435\u043b\u044b\u0445 \u0441\u0435\u043c\u044c \u043c\u0435\u0441\u044f\u0446\u0435\u0432, \u043f\u0440\u0435\u0436\u0434\u0435 \u0447\u0435\u043c \u0438\u0441\u043f\u0440\u0430\u0432\u043b\u0435\u043d\u0438\u044f \u043d\u0430\u043a\u043e\u043d\u0435\u0446-\u0442\u043e \u0441\u0442\u0430\u043b\u0438 \u0434\u043e\u0441\u0442\u0443\u043f\u043d\u044b. \u0422\u0435\u043c \u043d\u0435 \u043c\u0435\u043d\u0435\u0435, \u043d\u0435\u0442 \u043d\u0438\u043a\u0430\u043a\u0438\u0445 \u0441\u043e\u043e\u0431\u0449\u0435\u043d\u0438\u0439 \u043e\u0431 \u0430\u043a\u0442\u0438\u0432\u043d\u043e\u0439 \u044d\u043a\u0441\u043f\u043b\u0443\u0430\u0442\u0430\u0446\u0438\u0438.\n\nHPE \u043d\u0435 \u043e\u0442\u043c\u0435\u0442\u0438\u043b\u0430 \u0432 \u0431\u044e\u043b\u043b\u0435\u0442\u0435\u043d\u0435 \u043d\u0438\u043a\u0430\u043a\u0438\u0445 \u043e\u0431\u0445\u043e\u0434\u043d\u044b\u0445 \u043f\u0443\u0442\u0435\u0439 \u0434\u043b\u044f \u0432\u043e\u0441\u044c\u043c\u0438 \u043d\u0435\u0434\u043e\u0441\u0442\u0430\u0442\u043a\u043e\u0432, \u043f\u043e\u044d\u0442\u043e\u043c\u0443 \u0440\u0435\u043a\u043e\u043c\u0435\u043d\u0434\u0443\u0435\u043c\u044b\u043c \u0440\u0435\u0448\u0435\u043d\u0438\u0435\u043c \u044f\u0432\u043b\u044f\u0435\u0442\u0441\u044f \u043e\u0431\u043d\u043e\u0432\u043b\u0435\u043d\u0438\u0435.", "creation_timestamp": "2025-06-04T16:30:06.000000Z"}, {"uuid": "c2af9a8c-60a0-49e0-9189-ab7ff23df327", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37884", "type": "seen", "source": "https://t.me/cvedetector/24933", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-37884 - Linux Kernel BPF Event Mutex Deadlock\", \n  \"Content\": \"CVE ID : CVE-2025-37884 \nPublished : May 9, 2025, 7:16 a.m. | 44\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nbpf: Fix deadlock between rcu_tasks_trace and event_mutex.  \n  \nFix the following deadlock:  \nCPU A  \n_free_event()  \n  perf_kprobe_destroy()  \n    mutex_lock(&event_mutex)  \n      perf_trace_event_unreg()  \n        synchronize_rcu_tasks_trace()  \n  \nThere are several paths where _free_event() grabs event_mutex  \nand calls sync_rcu_tasks_trace. Above is one such case.  \n  \nCPU B  \nbpf_prog_test_run_syscall()  \n  rcu_read_lock_trace()  \n    bpf_prog_run_pin_on_cpu()  \n      bpf_prog_load()  \n        bpf_tracing_func_proto()  \n          trace_set_clr_event()  \n            mutex_lock(&event_mutex)  \n  \nDelegate trace_set_clr_event() to workqueue to avoid  \nsuch lock dependency. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"09 May 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-05-09T10:22:00.000000Z"}, {"uuid": "a128727b-3c60-4f99-bd77-b27ba3a832a1", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37878", "type": "seen", "source": "https://t.me/cvedetector/24932", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-37878 - Linux Kernel Perf Core Context Assignment Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2025-37878 \nPublished : May 9, 2025, 7:16 a.m. | 44\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nperf/core: Fix WARN_ON(!ctx) in __free_event() for partial init  \n  \nMove the get_ctx(child_ctx) call and the child_event->ctx assignment to  \noccur immediately after the child event is allocated. Ensure that  \nchild_event->ctx is non-NULL before any subsequent error path within  \ninherit_event calls free_event(), satisfying the assumptions of the  \ncleanup code.  \n  \nDetails:  \n  \nThere's no clear Fixes tag, because this bug is a side-effect of  \nmultiple interacting commits over time (up to 15 years old), not  \na single regression.  \n  \nThe code initially incremented refcount then assigned context  \nimmediately after the child_event was created. Later, an early  \nvalidity check for child_event was added before the  \nrefcount/assignment. Even later, a WARN_ON_ONCE() cleanup check was  \nadded, assuming event->ctx is valid if the pmu_ctx is valid.  \nThe problem is that the WARN_ON_ONCE() could trigger after the initial  \ncheck passed but before child_event->ctx was assigned, violating its  \nprecondition. The solution is to assign child_event->ctx right after  \nits initial validation. This ensures the context exists for any  \nsubsequent checks or cleanup routines, resolving the WARN_ON_ONCE().  \n  \nTo resolve it, defer the refcount update and child_event->ctx assignment  \ndirectly after child_event->pmu_ctx is set but before checking if the  \nparent event is orphaned. The cleanup routine depends on  \nevent->pmu_ctx being non-NULL before it verifies event->ctx is  \nnon-NULL. This also maintains the author's original intent of passing  \nin child_ctx to find_get_pmu_context before its refcount/assignment.  \n  \n[ mingo: Expanded the changelog from another email by Gabriel Shahrouzi. ] \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"09 May 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-05-09T10:22:00.000000Z"}, {"uuid": "539dedd4-481f-45f2-8f9a-36ba821150f3", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37882", "type": "seen", "source": "https://t.me/cvedetector/24931", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-37882 - Linux Kernel USB xHCI Isochronous Ring Handling Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2025-37882 \nPublished : May 9, 2025, 7:16 a.m. | 44\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nusb: xhci: Fix isochronous Ring Underrun/Overrun event handling  \n  \nThe TRB pointer of these events points at enqueue at the time of error  \noccurrence on xHCI 1.1+ HCs or it's NULL on older ones. By the time we  \nare handling the event, a new TD may be queued at this ring position.  \n  \nI can trigger this race by rising interrupt moderation to increase IRQ  \nhandling delay. Similar delay may occur naturally due to system load.  \n  \nIf this ever happens after a Missed Service Error, missed TDs will be  \nskipped and the new TD processed as if it matched the event. It could  \nbe given back prematurely, risking data loss or buffer UAF by the xHC.  \n  \nDon't complete TDs on xrun events and don't warn if queued TDs don't  \nmatch the event's TRB pointer, which can be NULL or a link/no-op TRB.  \nDon't warn if there are no queued TDs at all.  \n  \nNow that it's safe, also handle xrun events if the skip flag is clear.  \nThis ensures completion of any TD stuck in 'error mid TD' state right  \nbefore the xrun event, which could happen if a driver submits a finite  \nnumber of URBs to a buggy HC and then an error occurs on the last TD. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"09 May 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-05-09T10:21:59.000000Z"}, {"uuid": "fa2f893c-75aa-4f5e-8c40-5b4fd460759e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37880", "type": "seen", "source": "https://t.me/cvedetector/24930", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-37880 - Linux um Time-Travel Scheduling Vulnerability (Deadlock)\", \n  \"Content\": \"CVE ID : CVE-2025-37880 \nPublished : May 9, 2025, 7:16 a.m. | 44\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \num: work around sched_yield not yielding in time-travel mode  \n  \nsched_yield by a userspace may not actually cause scheduling in  \ntime-travel mode as no time has passed. In the case seen it appears to  \nbe a badly implemented userspace spinlock in ASAN. Unfortunately, with  \ntime-travel it causes an extreme slowdown or even deadlock depending on  \nthe kernel configuration (CONFIG_UML_MAX_USERSPACE_ITERATIONS).  \n  \nWork around it by accounting time to the process whenever it executes a  \nsched_yield syscall. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"09 May 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-05-09T10:21:58.000000Z"}, {"uuid": "f64382f4-cb86-4ff8-a1d9-a27bb1345165", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3790", "type": "seen", "source": "https://t.me/cvedetector/23327", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-3790 - Apache Druid Monitoring Console Remote Improper Access Controls Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2025-3790 \nPublished : April 18, 2025, 1:15 p.m. | 3\u00a0hours, 25\u00a0minutes ago \nDescription : A vulnerability classified as critical has been found in baseweb JSite 1.0. This affects an unknown part of the file /druid/index.html of the component Apache Druid Monitoring Console. The manipulation leads to improper access controls. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used. \nSeverity: 5.3 | MEDIUM \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"18 Apr 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-04-18T19:05:13.000000Z"}, {"uuid": "e12f513a-9402-4d1b-b3db-9d36f766fc6e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3789", "type": "seen", "source": "https://t.me/cvedetector/23326", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-3789 - Baseweb JSite Cross-Site Scripting Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2025-3789 \nPublished : April 18, 2025, 1:15 p.m. | 3\u00a0hours, 25\u00a0minutes ago \nDescription : A vulnerability was found in baseweb JSite 1.0. It has been rated as problematic. Affected by this issue is some unknown functionality of the file /a/sys/area/save. The manipulation of the argument Name leads to cross site scripting. The attack may be launched remotely. The exploit has been disclosed to the public and may be used. \nSeverity: 3.5 | LOW \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"18 Apr 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-04-18T19:05:12.000000Z"}, {"uuid": "bc7d4de7-e38d-438d-be8d-24c18238995d", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37881", "type": "seen", "source": "https://t.me/cvedetector/24929", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-37881 - Aspeed USB Gadget NULL Pointer Dereference\", \n  \"Content\": \"CVE ID : CVE-2025-37881 \nPublished : May 9, 2025, 7:16 a.m. | 44\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nusb: gadget: aspeed: Add NULL pointer check in ast_vhub_init_dev()  \n  \nThe variable d->name, returned by devm_kasprintf(), could be NULL.  \nA pointer check is added to prevent potential NULL pointer dereference.  \nThis is similar to the fix in commit 3027e7b15b02  \n(\"ice: Fix some null pointer dereference issues in ice_ptp.c\").  \n  \nThis issue is found by our static analysis tool \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"09 May 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-05-09T10:21:57.000000Z"}, {"uuid": "a5c9847a-eff3-4d84-878f-6fa473237205", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3765", "type": "seen", "source": "https://t.me/cvedetector/23288", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-3765 - SourceCodester Web-based Pharmacy Product Management System Unrestricted File Upload Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2025-3765 \nPublished : April 17, 2025, 8:15 p.m. | 2\u00a0hours, 10\u00a0minutes ago \nDescription : A vulnerability, which was classified as critical, has been found in SourceCodester Web-based Pharmacy Product Management System 1.0. This issue affects some unknown processing of the file /edit-photo.php. The manipulation of the argument Avatar leads to unrestricted upload. The attack may be initiated remotely. The exploit has been disclosed to the public and may be used. \nSeverity: 6.3 | MEDIUM \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"18 Apr 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-04-18T00:41:46.000000Z"}, {"uuid": "cf0ac917-4262-4a11-9ea2-f7c20cbe781a", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3764", "type": "seen", "source": "https://t.me/cvedetector/23287", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-3764 - SourceCodester Web-based Pharmacy Product Management System Unrestricted File Upload Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2025-3764 \nPublished : April 17, 2025, 8:15 p.m. | 2\u00a0hours, 10\u00a0minutes ago \nDescription : A vulnerability classified as critical was found in SourceCodester Web-based Pharmacy Product Management System 1.0. This vulnerability affects unknown code of the file /edit-product.php. The manipulation of the argument Avatar leads to unrestricted upload. The attack can be initiated remotely. The exploit has been disclosed to the public and may be used. \nSeverity: 6.3 | MEDIUM \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"18 Apr 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-04-18T00:41:45.000000Z"}, {"uuid": "033eb12f-fdcd-4c8d-b818-2387782669bf", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3762", "type": "seen", "source": "https://t.me/cvedetector/23265", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-3762 - PCMan FTP Server MPUT Command Handler Buffer Overflow\", \n  \"Content\": \"CVE ID : CVE-2025-3762 \nPublished : April 17, 2025, 7:16 p.m. | 1\u00a0hour, 7\u00a0minutes ago \nDescription : A vulnerability was found in PCMan FTP Server 2.0.7. It has been rated as critical. Affected by this issue is some unknown functionality of the component MPUT Command Handler. The manipulation leads to buffer overflow. The attack may be launched remotely. The exploit has been disclosed to the public and may be used. \nSeverity: 7.3 | HIGH \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"17 Apr 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-04-17T23:01:02.000000Z"}, {"uuid": "bbf97864-6e54-4b8b-bf55-f97a593eeb25", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3763", "type": "seen", "source": "https://t.me/cvedetector/23264", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-3763 - SourceCodester Phone Management System Buffer Overflow Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2025-3763 \nPublished : April 17, 2025, 7:16 p.m. | 1\u00a0hour, 7\u00a0minutes ago \nDescription : A vulnerability classified as critical has been found in SourceCodester Phone Management System 1.0. This affects the function main of the component Password Handler. The manipulation of the argument s leads to buffer overflow. Local access is required to approach this attack. The exploit has been disclosed to the public and may be used. \nSeverity: 5.3 | MEDIUM \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"17 Apr 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-04-17T23:01:01.000000Z"}, {"uuid": "d4966974-8382-4ca6-9abd-d3a74003b1b2", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3757", "type": "seen", "source": "https://t.me/cvedetector/25237", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-3757 - OpenPubkey Invalid JWS Signature Verification\", \n  \"Content\": \"CVE ID : CVE-2025-3757 \nPublished : May 13, 2025, 5:16 p.m. | 1\u00a0hour, 59\u00a0minutes ago \nDescription : Versions of OpenPubkey library prior to 0.10.0  contained a vulnerability that would allow a specially crafted JWS to bypass signature verification. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"13 May 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-05-13T21:24:47.000000Z"}, {"uuid": "cfca01e7-e2ee-4dd7-8bd6-58e8e5e6cddf", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3744", "type": "seen", "source": "https://t.me/cvedetector/25243", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-3744 - Nomad Sentinel Policy Bypass\", \n  \"Content\": \"CVE ID : CVE-2025-3744 \nPublished : May 13, 2025, 7:15 p.m. | 1\u00a0hour, 59\u00a0minutes ago \nDescription : Nomad Enterprise (\u201cNomad\u201d) jobs using the policy override option are bypassing the mandatory sentinel policies. This vulnerability, identified as CVE-2025-3744, is fixed in Nomad Enterprise 1.10.1, 1.9.9, and 1.8.13. \nSeverity: 7.6 | HIGH \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"13 May 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-05-13T23:56:45.000000Z"}, {"uuid": "4988c9d4-e83f-4c1a-95fc-356128f67aff", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3710", "type": "seen", "source": "https://t.me/cvedetector/24918", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-3710 - \"KVM Over IP Switch CL5708IM Stack-based Buffer Overflow Vulnerability\"\", \n  \"Content\": \"CVE ID : CVE-2025-3710 \nPublished : May 9, 2025, 4:16 a.m. | 1\u00a0hour, 39\u00a0minutes ago \nDescription : The LCD KVM over IP Switch CL5708IM has a Stack-based Buffer Overflow vulnerability, allowing unauthenticated remote attackers to exploit this vulnerability to execute arbitrary code on the device. \nSeverity: 9.8 | CRITICAL \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"09 May 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-05-09T08:41:23.000000Z"}, {"uuid": "e477312a-0d1f-4b7c-a3a8-88011ee8a76d", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3711", "type": "seen", "source": "https://t.me/cvedetector/24917", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-3711 - \"LCD KVM over IP Switch CL5708IM Stack-based Buffer Overflow Vulnerability\"\", \n  \"Content\": \"CVE ID : CVE-2025-3711 \nPublished : May 9, 2025, 4:16 a.m. | 1\u00a0hour, 39\u00a0minutes ago \nDescription : The LCD KVM over IP Switch CL5708IM has a Stack-based Buffer Overflow vulnerability, allowing unauthenticated remote attackers to exploit this vulnerability to execute arbitrary code on the device. \nSeverity: 9.8 | CRITICAL \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"09 May 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-05-09T08:41:19.000000Z"}, {"uuid": "99360d43-26ec-44c1-9bf0-424d390af92d", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3713", "type": "seen", "source": "https://t.me/cvedetector/24916", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-3713 - \"LCD KVM over IP Switch CL5708IM Heap-based Buffer Overflow Denial-of-Service Vulnerability\"\", \n  \"Content\": \"CVE ID : CVE-2025-3713 \nPublished : May 9, 2025, 4:16 a.m. | 1\u00a0hour, 39\u00a0minutes ago \nDescription : The LCD KVM over IP Switch CL5708IM has a Heap-based Buffer Overflow vulnerability, allowing unauthenticated remote attackers to exploit this vulnerability to perform a denial-of-service attack. \nSeverity: 7.5 | HIGH \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"09 May 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-05-09T08:41:18.000000Z"}, {"uuid": "581ee1d4-1958-486f-8480-52f21e830358", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3712", "type": "seen", "source": "https://t.me/cvedetector/24915", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-3712 - \"LCD KVM over IP Switch CL5708IM Heap-based Buffer Overflow Denial-of-Service Vulnerability\"\", \n  \"Content\": \"CVE ID : CVE-2025-3712 \nPublished : May 9, 2025, 4:16 a.m. | 1\u00a0hour, 39\u00a0minutes ago \nDescription : The LCD KVM over IP Switch CL5708IM has a Heap-based Buffer Overflow vulnerability, allowing unauthenticated remote attackers to exploit this vulnerability to perform a denial-of-service attack. \nSeverity: 7.5 | HIGH \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"09 May 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-05-09T08:41:18.000000Z"}, {"uuid": "a37ed625-7a9f-4632-83ab-c7d4dc3f28ab", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3714", "type": "seen", "source": "https://t.me/cvedetector/24914", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-3714 - \"LCD KVM over IP Switch CL5708IM Stack-based Buffer Overflow Vulnerability\"\", \n  \"Content\": \"CVE ID : CVE-2025-3714 \nPublished : May 9, 2025, 4:16 a.m. | 1\u00a0hour, 39\u00a0minutes ago \nDescription : The LCD KVM over IP Switch CL5708IM has a Stack-based Buffer Overflow vulnerability, allowing unauthenticated remote attackers to exploit this vulnerability to execute arbitrary code on the device. \nSeverity: 9.8 | CRITICAL \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"09 May 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-05-09T08:41:17.000000Z"}, {"uuid": "1dc85bad-a888-4e91-9f82-8c1c95acfed3", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3794", "type": "seen", "source": "https://t.me/cvedetector/24987", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-3794 - WordPress WPForms Stored Cross-Site Scripting Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2025-3794 \nPublished : May 9, 2025, 11:15 p.m. | 1\u00a0hour, 6\u00a0minutes ago \nDescription : The WPForms \u2013 Easy Form Builder for WordPress \u2013 Contact Forms, Payment Forms, Surveys, & More plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the start_timestamp parameter in all versions up to, and including, 1.9.5 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with Contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. \nSeverity: 5.4 | MEDIUM \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"10 May 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-05-10T03:04:58.000000Z"}, {"uuid": "4f091a1f-9d56-4f67-bb62-996f984d8990", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37886", "type": "seen", "source": "https://t.me/cvedetector/24935", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-37886 - Linux Kernel PDS Core Use-After-Free Buffer Overflow\", \n  \"Content\": \"CVE ID : CVE-2025-37886 \nPublished : May 9, 2025, 7:16 a.m. | 44\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \npds_core: make wait_context part of q_info  \n  \nMake the wait_context a full part of the q_info struct rather  \nthan a stack variable that goes away after pdsc_adminq_post()  \nis done so that the context is still available after the wait  \nloop has given up.  \n  \nThere was a case where a slow development firmware caused  \nthe adminq request to time out, but then later the FW finally  \nfinished the request and sent the interrupt.  The handler tried  \nto complete_all() the completion context that had been created  \non the stack in pdsc_adminq_post() but no longer existed.  \nThis caused bad pointer usage, kernel crashes, and much wailing  \nand gnashing of teeth. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"09 May 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-05-09T10:22:05.000000Z"}, {"uuid": "fc038030-f4c5-4681-9390-e63ab2ab880f", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37871", "type": "seen", "source": "https://t.me/cvedetector/24938", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-37871 - Linux Kernel NFSd Deadlock Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2025-37871 \nPublished : May 9, 2025, 7:16 a.m. | 44\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nnfsd: decrease sc_count directly if fail to queue dl_recall  \n  \nA deadlock warning occurred when invoking nfs4_put_stid following a failed  \ndl_recall queue operation:  \n            T1                            T2  \n                                nfs4_laundromat  \n                                 nfs4_get_client_reaplist  \n                                  nfs4_anylock_blockers  \n__break_lease  \n spin_lock // ctx->flc_lock  \n                                   spin_lock // clp->cl_lock  \n                                   nfs4_lockowner_has_blockers  \n                                    locks_owner_has_blockers  \n                                     spin_lock // flctx->flc_lock  \n nfsd_break_deleg_cb  \n  nfsd_break_one_deleg  \n   nfs4_put_stid  \n    refcount_dec_and_lock  \n     spin_lock // clp->cl_lock  \n  \nWhen a file is opened, an nfs4_delegation is allocated with sc_count  \ninitialized to 1, and the file_lease holds a reference to the delegation.  \nThe file_lease is then associated with the file through kernel_setlease.  \n  \nThe disassociation is performed in nfsd4_delegreturn via the following  \ncall chain:  \nnfsd4_delegreturn --> destroy_delegation --> destroy_unhashed_deleg -->  \nnfs4_unlock_deleg_lease --> kernel_setlease --> generic_delete_lease  \nThe corresponding sc_count reference will be released after this  \ndisassociation.  \n  \nSince nfsd_break_one_deleg executes while holding the flc_lock, the  \ndisassociation process becomes blocked when attempting to acquire flc_lock  \nin generic_delete_lease. This means:  \n1) sc_count in nfsd_break_one_deleg will not be decremented to 0;  \n2) The nfs4_put_stid called by nfsd_break_one_deleg will not attempt to  \nacquire cl_lock;  \n3) Consequently, no deadlock condition is created.  \n  \nGiven that sc_count in nfsd_break_one_deleg remains non-zero, we can  \nsafely perform refcount_dec on sc_count directly. This approach  \neffectively avoids triggering deadlock warnings. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"09 May 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-05-09T10:22:07.000000Z"}, {"uuid": "c8d9a5c7-5679-4063-b3e5-fac3d13ff95e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37872", "type": "seen", "source": "https://t.me/cvedetector/24937", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-37872 - NetXtreme Gigabit Ethernet (TXGBE) Memory Leak Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2025-37872 \nPublished : May 9, 2025, 7:16 a.m. | 44\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nnet: txgbe: fix memory leak in txgbe_probe() error path  \n  \nWhen txgbe_sw_init() is called, memory is allocated for wx->rss_key  \nin wx_init_rss_key(). However, in txgbe_probe() function, the subsequent  \nerror paths after txgbe_sw_init() don't free the rss_key. Fix that by  \nfreeing it in error path along with wx->mac_table.  \n  \nAlso change the label to which execution jumps when txgbe_sw_init()  \nfails, because otherwise, it could lead to a double free for rss_key,  \nwhen the mac_table allocation fails in wx_sw_init(). \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"09 May 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-05-09T10:22:06.000000Z"}, {"uuid": "d217279a-8006-4035-b529-8d9878d776d5", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37883", "type": "seen", "source": "https://t.me/cvedetector/24936", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-37883 - IBM s390 Linux Kernel Null Pointer Dereference Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2025-37883 \nPublished : May 9, 2025, 7:16 a.m. | 44\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \ns390/sclp: Add check for get_zeroed_page()  \n  \nAdd check for the return value of get_zeroed_page() in  \nsclp_console_init() to prevent null pointer dereference.  \nFurthermore, to solve the memory leak caused by the loop  \nallocation, add a free helper to do the free job. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"09 May 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-05-09T10:22:06.000000Z"}, {"uuid": "bd7274aa-f67a-4218-b09a-a29839b6428a", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37885", "type": "seen", "source": "https://t.me/cvedetector/24934", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-37885 - KVM Linux Kernel MSI Route Handling Use-After-Free Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2025-37885 \nPublished : May 9, 2025, 7:16 a.m. | 44\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nKVM: x86: Reset IRTE to host control if *new* route isn't postable  \n  \nRestore an IRTE back to host control (remapped or posted MSI mode) if the  \n*new* GSI route prevents posting the IRQ directly to a vCPU, regardless of  \nthe GSI routing type.  Updating the IRTE if and only if the new GSI is an  \nMSI results in KVM leaving an IRTE posting to a vCPU.  \n  \nThe dangling IRTE can result in interrupts being incorrectly delivered to  \nthe guest, and in the worst case scenario can result in use-after-free,  \ne.g. if the VM is torn down, but the underlying host IRQ isn't freed. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"09 May 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-05-09T10:22:04.000000Z"}, {"uuid": "1843c637-fb61-47fd-b733-c0a955c47b6a", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37879", "type": "seen", "source": "https://t.me/cvedetector/24928", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-37879 - \"Linux 9p Client Signed Integer Vulnerability\"\", \n  \"Content\": \"CVE ID : CVE-2025-37879 \nPublished : May 9, 2025, 7:16 a.m. | 44\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \n9p/net: fix improper handling of bogus negative read/write replies  \n  \nIn p9_client_write() and p9_client_read_once(), if the server  \nincorrectly replies with success but a negative write/read count then we  \nwould consider written (negative) <=3) \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"09 May 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-05-09T10:21:54.000000Z"}, {"uuid": "3756b69f-291b-44bb-8ffb-c90716a7730b", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37887", "type": "seen", "source": "https://t.me/cvedetector/24927", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-37887 - Linux Kernel PDS_CORE Devlink Command Buffer Overflow\", \n  \"Content\": \"CVE ID : CVE-2025-37887 \nPublished : May 9, 2025, 7:16 a.m. | 44\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \npds_core: handle unsupported PDS_CORE_CMD_FW_CONTROL result  \n  \nIf the FW doesn't support the PDS_CORE_CMD_FW_CONTROL command  \nthe driver might at the least print garbage and at the worst  \ncrash when the user runs the \"devlink dev info\" devlink command.  \n  \nThis happens because the stack variable fw_list is not 0  \ninitialized which results in fw_list.num_fw_slots being a  \ngarbage value from the stack.  Then the driver tries to access  \nfw_list.fw_names[i] with i >= ARRAY_SIZE and runs off the end  \nof the array.  \n  \nFix this by initializing the fw_list and by not failing  \ncompletely if the devcmd fails because other useful information  \nis printed via devlink dev info even if the devcmd fails. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"09 May 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-05-09T10:21:53.000000Z"}, {"uuid": "01f2ea70-7f5e-4091-8262-6f3d64018370", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37889", "type": "seen", "source": "https://t.me/cvedetector/24923", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-37889 - XEN PCI MSI NULL Pointer Dereference Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2025-37889 \nPublished : May 9, 2025, 7:16 a.m. | 44\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nPCI/MSI: Handle the NOMASK flag correctly for all PCI/MSI backends  \n  \nThe conversion of the XEN specific global variable pci_msi_ignore_mask to a  \nMSI domain flag, missed the facts that:  \n  \n    1) Legacy architectures do not provide a interrupt domain  \n    2) Parent MSI domains do not necessarily have a domain info attached  \n     \nBoth cases result in an unconditional NULL pointer dereference. This was  \nunfortunatly missed in review and testing revealed it late.  \n  \nCure this by using the existing pci_msi_domain_supports() helper, which  \nhandles all possible cases correctly. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"09 May 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-05-09T10:21:47.000000Z"}, {"uuid": "072ea304-8c69-4558-939e-3b52cf78ab5f", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37888", "type": "seen", "source": "https://t.me/cvedetector/24922", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-37888 - Intel Mellanox Linux Null Pointer Dereference Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2025-37888 \nPublished : May 9, 2025, 7:16 a.m. | 44\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nnet/mlx5: Fix null-ptr-deref in mlx5_create_{inner_,}ttc_table()  \n  \nAdd NULL check for mlx5_get_flow_namespace() returns in  \nmlx5_create_inner_ttc_table() and mlx5_create_ttc_table() to prevent  \nNULL pointer dereference. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"09 May 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-05-09T10:21:46.000000Z"}, {"uuid": "d06dec75-0fdc-4b5e-a256-d65029490571", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3706", "type": "seen", "source": "https://t.me/cvedetector/23880", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-3706 - 104 Corporation eHRMS Reflected Cross-site Scripting Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2025-3706 \nPublished : April 28, 2025, 3:15 a.m. | 1\u00a0hour, 50\u00a0minutes ago \nDescription : The eHRMS from 104 Corporation has a Reflected Cross-site Scripting vulnerability, allowing unauthenticated remote attackers to execute arbitrary JavaScript codes in user's browser through phishing attacks. \nSeverity: 6.1 | MEDIUM \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"28 Apr 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-04-28T07:22:20.000000Z"}, {"uuid": "a23dde5f-2e98-4b35-afe5-11bf1f9b40af", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37087", "type": "seen", "source": "https://t.me/cvedetector/23559", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-37087 - HPE Performance Cluster Manager (HPCM) Arbitrary File Access Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2025-37087 \nPublished : April 22, 2025, 9:15 p.m. | 47\u00a0minutes ago \nDescription : A vulnerability in the cmdb service of the HPE Performance Cluster Manager (HPCM) could allow an attacker to gain access to an arbitrary file on the server host. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"23 Apr 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-04-23T00:15:51.000000Z"}, {"uuid": "8d2ef587-feed-46a3-83aa-daf6dbb19ecd", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3775", "type": "seen", "source": "https://t.me/cvedetector/23734", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-3775 - ShopLentor WooCommerce Builder SSRF Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2025-3775 \nPublished : April 25, 2025, 5:15 a.m. | 1\u00a0hour, 32\u00a0minutes ago \nDescription : The ShopLentor \u2013 WooCommerce Builder for Elementor & Gutenberg +20 Modules \u2013 All in One Solution (formerly WooLentor) plugin for WordPress is vulnerable to Server-Side Request Forgery in all versions up to, and including, 3.1.2 via the woolentor_template_proxy function. This makes it possible for unauthenticated attackers to make web requests to arbitrary locations originating from the web application, and can be used to query and modify information from internal services. \nSeverity: 6.5 | MEDIUM \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"25 Apr 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-04-25T09:09:17.000000Z"}, {"uuid": "b31c6c34-4019-4120-96d5-2173c002a5bd", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3743", "type": "seen", "source": "https://t.me/cvedetector/23745", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-3743 - WooCommerce Upsell Funnel Builder Order Manipulation Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2025-3743 \nPublished : April 25, 2025, 7:15 a.m. | 1\u00a0hour, 32\u00a0minutes ago \nDescription : The Upsell Funnel Builder for WooCommerce plugin for WordPress is vulnerable to order manipulation in all versions up to, and including, 3.0.0. This is due to the plugin allowing the additional product ID and discount field to be manipulated prior to processing via the 'add_offer_in_cart' function. This makes it possible for unauthenticated attackers to arbitrarily update the product associated with any order bump, and arbitrarily update the discount applied to any order bump item, when adding it to the cart. \nSeverity: 5.3 | MEDIUM \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"25 Apr 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-04-25T10:49:39.000000Z"}, {"uuid": "83e64d97-12dc-42dd-b95e-3f8dae994a8f", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3752", "type": "seen", "source": "https://t.me/cvedetector/23736", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-3752 - Able Player WordPress Stored Cross-Site Scripting Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2025-3752 \nPublished : April 25, 2025, 5:15 a.m. | 1\u00a0hour, 32\u00a0minutes ago \nDescription : The Able Player, accessible HTML5 media player plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the \u2018preload\u2019 parameter in all versions up to, and including, 1.2.1 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with Contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. \nSeverity: 6.4 | MEDIUM \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"25 Apr 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-04-25T09:09:18.000000Z"}, {"uuid": "19a8b860-41ed-4bab-b188-0a122eaa4e32", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3749", "type": "seen", "source": "https://t.me/cvedetector/23714", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-3749 - Breeze Display for WordPress Stored Cross-Site Scripting Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2025-3749 \nPublished : April 24, 2025, 11:15 p.m. | 1\u00a0hour, 21\u00a0minutes ago \nDescription : The Breeze Display plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the \u2018cal_size\u2019 parameter in all versions up to, and including, 1.2.3 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with Contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. \nSeverity: 6.4 | MEDIUM \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"25 Apr 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-04-25T03:18:14.000000Z"}, {"uuid": "196fee0a-d29e-499f-935c-480bb3a36934", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3776", "type": "seen", "source": "https://t.me/cvedetector/23662", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-3776 - WordPress TargetSMS Plugin Remote Code Execution Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2025-3776 \nPublished : April 24, 2025, 9:15 a.m. | 1\u00a0hour, 16\u00a0minutes ago \nDescription : The Verification SMS with TargetSMS plugin for WordPress is vulnerable to limited Remote Code Execution in all versions up to, and including, 1.5 via the 'targetvr_ajax_handler' function. This is due to a lack of validation on the type of function that can be called. This makes it possible for unauthenticated attackers to execute any callable function on the site, such as phpinfo(). \nSeverity: 8.3 | HIGH \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"24 Apr 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-04-24T13:03:49.000000Z"}, {"uuid": "89e15bbd-4570-4197-90cd-87a48c753e5f", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3793", "type": "seen", "source": "https://t.me/cvedetector/23655", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-3793 - Buddypress WordPress Force Password Change Plugin Authentication Bypass\", \n  \"Content\": \"CVE ID : CVE-2025-3793 \nPublished : April 24, 2025, 9:15 a.m. | 1\u00a0hour, 16\u00a0minutes ago \nDescription : The Buddypress Force Password Change plugin for WordPress is vulnerable to authenticated account takeover due to the plugin not properly validating a user's identity prior to updating their password through the 'bp_force_password_ajax' function in all versions up to, and including, 0.1. This makes it possible for authenticated attackers, with subscriber-level access and above and under certain prerequisites, to change arbitrary user's passwords, including administrators, and leverage that to gain access to their accounts. \nSeverity: 4.2 | MEDIUM \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"24 Apr 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-04-24T13:03:37.000000Z"}, {"uuid": "a22313e6-6c4a-489a-afb5-204ceb47d6cc", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3761", "type": "seen", "source": "https://t.me/cvedetector/23648", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-3761 - My Tickets - WordPress Privilege Escalation Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2025-3761 \nPublished : April 24, 2025, 7:15 a.m. | 1\u00a0hour, 15\u00a0minutes ago \nDescription : The My Tickets \u2013 Accessible Event Ticketing plugin for WordPress is vulnerable to Privilege Escalation in all versions up to, and including, 2.0.16. This is due to the mt_save_profile() function not appropriately restricting access to unauthorized users to update roles. This makes it possible for authenticated attackers, with Subscriber-level access and above, to update their role to that of an administrator. \nSeverity: 8.8 | HIGH \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"24 Apr 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-04-24T11:23:19.000000Z"}, {"uuid": "d286f939-d4ee-49f0-b2da-e08922836924", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37088", "type": "seen", "source": "https://t.me/cvedetector/23565", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-37088 - HPE Cray Data Virtualization Service (DVS) Authentication Bypass Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2025-37088 \nPublished : April 22, 2025, 10:15 p.m. | 1\u00a0hour, 51\u00a0minutes ago \nDescription : A security vulnerability has been identified in HPE Cray Data Virtualization Service (DVS). Depending on race conditions and configuration, this vulnerability may lead to local/cluster unauthorized access. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"23 Apr 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-04-23T02:46:26.000000Z"}, {"uuid": "046f5205-85f5-40f6-8176-995f9edb5cca", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3767", "type": "seen", "source": "https://t.me/cvedetector/23533", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-3767 - Centreon BAM SQL Injection Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2025-3767 \nPublished : April 22, 2025, 4:15 p.m. | 1\u00a0hour, 47\u00a0minutes ago \nDescription : Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in Centreon BAM (Boolean KPi Listing modules) allows SQL Injection.  \n  \n  \nThis page is only accessible to authenticated users with high privileges.  \n  \nThis issue affects Centreon BAM: from 24.10 before 24.10.1, from 24.04 before 24.04.5, from 23.10 before 23.10.10, from 23.04 before 23.04.10. \nSeverity: 7.2 | HIGH \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"22 Apr 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-04-22T20:54:50.000000Z"}, {"uuid": "3b693308-b80d-40bd-921b-40dd4e7c5d7f", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3799", "type": "seen", "source": "https://t.me/cvedetector/23382", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-3799 - WordPress CMS SQL Injection Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2025-3799 \nPublished : April 19, 2025, 11:15 a.m. | 1\u00a0hour, 35\u00a0minutes ago \nDescription : A vulnerability, which was classified as critical, was found in WCMS 11. Affected is an unknown function of the file app/controllers/AnonymousController.php. The manipulation of the argument email/username leads to sql injection. It is possible to launch the attack remotely. The exploit has been disclosed to the public and may be used. Other parameters might be affected as well. \nSeverity: 7.3 | HIGH \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"19 Apr 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-04-19T15:09:00.000000Z"}, {"uuid": "e987179b-fa00-419a-a19f-5de73ff0f27b", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3798", "type": "seen", "source": "https://t.me/cvedetector/23379", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-3798 - Apache WCMS Unrestricted File Upload Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2025-3798 \nPublished : April 19, 2025, 10:15 a.m. | 35\u00a0minutes ago \nDescription : A vulnerability, which was classified as critical, has been found in WCMS 11. This issue affects the function sub of the file app/admin/AdvadminController.php of the component Advertisement Image Handler. The manipulation leads to unrestricted upload. The attack may be initiated remotely. The exploit has been disclosed to the public and may be used. \nSeverity: 4.7 | MEDIUM \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"19 Apr 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-04-19T13:28:48.000000Z"}, {"uuid": "f1e53868-8e1f-4726-896b-b408849041f6", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3797", "type": "seen", "source": "https://t.me/cvedetector/23378", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-3797 - SeaCMS SQL Injection Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2025-3797 \nPublished : April 19, 2025, 7:15 a.m. | 1\u00a0hour, 35\u00a0minutes ago \nDescription : A vulnerability classified as critical was found in SeaCMS up to 13.3. This vulnerability affects unknown code of the file /admin_topic.php?action=delall. The manipulation of the argument e_id leads to sql injection. The attack can be initiated remotely. The exploit has been disclosed to the public and may be used. \nSeverity: 4.7 | MEDIUM \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"19 Apr 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-04-19T10:58:27.000000Z"}, {"uuid": "d2af43f2-ec11-4030-ada8-9fd7e0547bf1", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3796", "type": "seen", "source": "https://t.me/cvedetector/23353", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-3796 - PHPGurukul Men Salon Management System SQL Injection Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2025-3796 \nPublished : April 18, 2025, 9:15 p.m. | 1\u00a0hour, 30\u00a0minutes ago \nDescription : A vulnerability classified as critical has been found in PHPGurukul Men Salon Management System 1.0. This affects an unknown part of the file /admin/contact-us.php. The manipulation of the argument pagetitle/pagedes/email/mobnumber/timing leads to sql injection. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used. \nSeverity: 6.3 | MEDIUM \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"19 Apr 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-04-19T00:56:36.000000Z"}, {"uuid": "07140b9a-4cb2-4cf0-b04a-67cc5f04a10a", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3795", "type": "seen", "source": "https://t.me/cvedetector/23348", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-3795 - \"DaiCuo SEO Optimization Settings Section Cross-Site Scripting Vulnerability\"\", \n  \"Content\": \"CVE ID : CVE-2025-3795 \nPublished : April 18, 2025, 8:15 p.m. | 29\u00a0minutes ago \nDescription : A vulnerability was found in DaiCuo 1.3.13. It has been rated as problematic. Affected by this issue is some unknown functionality of the component SEO Optimization Settings Section. The manipulation leads to cross site scripting. The attack may be launched remotely. The exploit has been disclosed to the public and may be used. \nSeverity: 2.4 | LOW \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"18 Apr 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-04-18T23:16:13.000000Z"}, {"uuid": "b69ba166-dccc-4a83-90a1-d4ce508cb788", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37751", "type": "seen", "source": "https://t.me/cvedetector/24224", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-37751 - AMD x86 CPU Array Indexing Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2025-37751 \nPublished : May 1, 2025, 1:15 p.m. | 1\u00a0hour, 5\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nx86/cpu: Avoid running off the end of an AMD erratum table  \n  \nThe NULL array terminator at the end of erratum_1386_microcode was  \nremoved during the switch from x86_cpu_desc to x86_cpu_id. This  \ncauses readers to run off the end of the array.  \n  \nReplace the NULL. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"01 May 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-05-01T16:30:20.000000Z"}, {"uuid": "28963558-0474-4a5c-8547-001aa4060b69", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37747", "type": "seen", "source": "https://t.me/cvedetector/24227", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-37747 - \"Linux Perf Remote Event Reference Leak\"\", \n  \"Content\": \"CVE ID : CVE-2025-37747 \nPublished : May 1, 2025, 1:15 p.m. | 1\u00a0hour, 5\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nperf: Fix hang while freeing sigtrap event  \n  \nPerf can hang while freeing a sigtrap event if a related deferred  \nsignal hadn't managed to be sent before the file got closed:  \n  \nperf_event_overflow()  \n   task_work_add(perf_pending_task)  \n  \nfput()  \n   task_work_add(____fput())  \n  \ntask_work_run()  \n    ____fput()  \n        perf_release()  \n            perf_event_release_kernel()  \n                _free_event()  \n                    perf_pending_task_sync()  \n                        task_work_cancel() -> FAILED  \n                        rcuwait_wait_event()  \n  \nOnce task_work_run() is running, the list of pending callbacks is  \nremoved from the task_struct and from this point on task_work_cancel()  \ncan't remove any pending and not yet started work items, hence the  \ntask_work_cancel() failure and the hang on rcuwait_wait_event().  \n  \nTask work could be changed to remove one work at a time, so a work  \nrunning on the current task can always cancel a pending one, however  \nthe wait / wake design is still subject to inverted dependencies when  \nremote targets are involved, as pictured by Oleg:  \n  \nT1                                                      T2  \n  \nfd = perf_event_open(pid => T2->pid);                  fd = perf_event_open(pid => T1->pid);  \nclose(fd)                                              close(fd)  \n                                                        \n    perf_event_overflow()                                  perf_event_overflow()  \n       task_work_add(perf_pending_task)                        task_work_add(perf_pending_task)  \n                                                       \n    fput()                                                 fput()  \n        task_work_add(____fput())                              task_work_add(____fput())  \n  \n    task_work_run()                                        task_work_run()  \n        ____fput()                                             ____fput()  \n            perf_release()                                         perf_release()  \n                perf_event_release_kernel()                            perf_event_release_kernel()  \n                    _free_event()                                          _free_event()  \n                        perf_pending_task_sync()                               perf_pending_task_sync()  \n                            rcuwait_wait_event()                                   rcuwait_wait_event()  \n  \nTherefore the only option left is to acquire the event reference count  \nupon queueing the perf task work and release it from the task work, just  \nlike it was done before 3a5465418f5f (\"perf: Fix event leak upon exec and file release\")  \nbut without the leaks it fixed.  \n  \nSome adjustments are necessary to make it work:  \n  \n* A child event might dereference its parent upon freeing. Care must be  \n  taken to release the parent last.  \n  \n* Some places assuming the event doesn't have any reference held and  \n  therefore can be freed right away must instead put the reference and  \n  let the reference counting to its job. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"01 May 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-05-01T16:30:25.000000Z"}, {"uuid": "040b3ca2-2dd5-44a2-b34d-8562cf460d87", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37743", "type": "seen", "source": "https://t.me/cvedetector/24226", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-37743 - \"Qualcomm ath12k WiFi Driver Memory Leak\"\", \n  \"Content\": \"CVE ID : CVE-2025-37743 \nPublished : May 1, 2025, 1:15 p.m. | 1\u00a0hour, 5\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nwifi: ath12k: Avoid memory leak while enabling statistics  \n  \nDriver uses monitor destination rings for extended statistics mode and  \nstandalone monitor mode. In extended statistics mode, TLVs are parsed from  \nthe buffer received from the monitor destination ring and assigned to the  \nppdu_info structure to update per-packet statistics. In standalone monitor  \nmode, along with per-packet statistics, the packet data (payload) is  \ncaptured, and the driver updates per MSDU to mac80211.  \n  \nWhen the AP interface is enabled, only extended statistics mode is  \nactivated. As part of enabling monitor rings for collecting statistics,  \nthe driver subscribes to HAL_RX_MPDU_START TLV in the filter  \nconfiguration. This TLV is received from the monitor destination ring, and  \nkzalloc for the mon_mpdu object occurs, which is not freed, leading to a  \nmemory leak. The kzalloc for the mon_mpdu object is only required while  \nenabling the standalone monitor interface. This causes a memory leak while  \nenabling extended statistics mode in the driver.  \n  \nFix this memory leak by removing the kzalloc for the mon_mpdu object in  \nthe HAL_RX_MPDU_START TLV handling. Additionally, remove the standalone  \nmonitor mode handlings in the HAL_MON_BUF_ADDR and HAL_RX_MSDU_END TLVs.  \nThese TLV tags will be handled properly when enabling standalone monitor  \nmode in the future.  \n  \nTested-on: QCN9274 hw2.0 PCI WLAN.WBE.1.3.1-00173-QCAHKSWPL_SILICONZ-1  \nTested-on: WCN7850 hw2.0 PCI WLAN.HMT.1.0.c5-00481-QCAHMTSWPL_V1.0_V2.0_SILICONZ-3 \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"01 May 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-05-01T16:30:24.000000Z"}, {"uuid": "ae15afe5-a3a4-4274-98e4-7b7e169d0905", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37752", "type": "seen", "source": "https://t.me/cvedetector/24225", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-37752 - Linux Kernel net_sched sfq Array Index Out-of-Bounds\", \n  \"Content\": \"CVE ID : CVE-2025-37752 \nPublished : May 1, 2025, 1:15 p.m. | 1\u00a0hour, 5\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nnet_sched: sch_sfq: move the limit validation  \n  \nIt is not sufficient to directly validate the limit on the data that  \nthe user passes as it can be updated based on how the other parameters  \nare changed.  \n  \nMove the check at the end of the configuration update process to also  \ncatch scenarios where the limit is indirectly updated, for example  \nwith the following configurations:  \n  \ntc qdisc add dev dummy0 handle 1: root sfq limit 2 flows 1 depth 1  \ntc qdisc add dev dummy0 handle 1: root sfq limit 2 flows 1 divisor 1  \n  \nThis fixes the following syzkaller reported crash:  \n  \n------------[ cut here ]------------  \nUBSAN: array-index-out-of-bounds in net/sched/sch_sfq.c:203:6  \nindex 65535 is out of range for type 'struct sfq_head[128]'  \nCPU: 1 UID: 0 PID: 3037 Comm: syz.2.16 Not tainted 6.14.0-rc2-syzkaller #0  \nHardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 12/27/2024  \nCall Trace:  \n   \n __dump_stack lib/dump_stack.c:94 [inline]  \n dump_stack_lvl+0x201/0x300 lib/dump_stack.c:120  \n ubsan_epilogue lib/ubsan.c:231 [inline]  \n __ubsan_handle_out_of_bounds+0xf5/0x120 lib/ubsan.c:429  \n sfq_link net/sched/sch_sfq.c:203 [inline]  \n sfq_dec+0x53c/0x610 net/sched/sch_sfq.c:231  \n sfq_dequeue+0x34e/0x8c0 net/sched/sch_sfq.c:493  \n sfq_reset+0x17/0x60 net/sched/sch_sfq.c:518  \n qdisc_reset+0x12e/0x600 net/sched/sch_generic.c:1035  \n tbf_reset+0x41/0x110 net/sched/sch_tbf.c:339  \n qdisc_reset+0x12e/0x600 net/sched/sch_generic.c:1035  \n dev_reset_queue+0x100/0x1b0 net/sched/sch_generic.c:1311  \n netdev_for_each_tx_queue include/linux/netdevice.h:2590 [inline]  \n dev_deactivate_many+0x7e5/0xe70 net/sched/sch_generic.c:1375 \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"01 May 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-05-01T16:30:24.000000Z"}, {"uuid": "7a3b7b3e-048c-4458-9d47-ca59e1c7f3f0", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37749", "type": "seen", "source": "https://t.me/cvedetector/24222", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-37749 - Linux PPP Out-of-Bounds Access Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2025-37749 \nPublished : May 1, 2025, 1:15 p.m. | 1\u00a0hour, 5\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nnet: ppp: Add bound checking for skb data on ppp_sync_txmung  \n  \nEnsure we have enough data in linear buffer from skb before accessing  \ninitial bytes. This prevents potential out-of-bounds accesses  \nwhen processing short packets.  \n  \nWhen ppp_sync_txmung receives an incoming package with an empty  \npayload:  \n(remote) gef\u27a4  p *(struct pppoe_hdr *) (skb->head + skb->network_header)  \n$18 = {  \n type = 0x1,  \n ver = 0x1,  \n code = 0x0,  \n sid = 0x2,  \n        length = 0x0,  \n tag = 0xffff8880371cdb96  \n}  \n  \nfrom the skb struct (trimmed)  \n      tail = 0x16,  \n      end = 0x140,  \n      head = 0xffff88803346f400 \"4\",  \n      data = 0xffff88803346f416 \":\\377\",  \n      truesize = 0x380,  \n      len = 0x0,  \n      data_len = 0x0,  \n      mac_len = 0xe,  \n      hdr_len = 0x0,  \n  \nit is not safe to access data[2].  \n  \n[pabeni@redhat.com: fixed subj typo] \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"01 May 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-05-01T16:30:18.000000Z"}, {"uuid": "f6e2223c-d8c2-4156-81cf-f2a48df8c229", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37748", "type": "seen", "source": "https://t.me/cvedetector/24221", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-37748 - Mediatek IOMMU NULL Pointer Dereference Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2025-37748 \nPublished : May 1, 2025, 1:15 p.m. | 1\u00a0hour, 5\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \niommu/mediatek: Fix NULL pointer deference in mtk_iommu_device_group  \n  \nCurrently, mtk_iommu calls during probe iommu_device_register before  \nthe hw_list from driver data is initialized. Since iommu probing issue  \nfix, it leads to NULL pointer dereference in mtk_iommu_device_group when  \nhw_list is accessed with list_first_entry (not null safe).  \n  \nSo, change the call order to ensure iommu_device_register is called  \nafter the driver data are initialized. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"01 May 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-05-01T16:30:18.000000Z"}, {"uuid": "8c2b2897-59f3-4b2f-b525-fc3254f43025", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37746", "type": "seen", "source": "https://t.me/cvedetector/24220", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-37746 - Linux Kernel perf dwc_pcie Duplicate Device Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2025-37746 \nPublished : May 1, 2025, 1:15 p.m. | 1\u00a0hour, 5\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nperf/dwc_pcie: fix duplicate pci_dev devices  \n  \nDuring platform_device_register, wrongly using struct device  \npci_dev as platform_data caused a kmemdup copy of pci_dev. Worse  \nstill, accessing the duplicated device leads to list corruption as its  \nmutex content (e.g., list, magic) remains the same as the original. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"01 May 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-05-01T16:30:17.000000Z"}, {"uuid": "44ff988e-1be2-463d-b3a4-ddfde2616883", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37745", "type": "seen", "source": "https://t.me/cvedetector/24218", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-37745 - Linux kernel PM: hibernate: Deadlock in hibernate_compressor_param_set\", \n  \"Content\": \"CVE ID : CVE-2025-37745 \nPublished : May 1, 2025, 1:15 p.m. | 1\u00a0hour, 5\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nPM: hibernate: Avoid deadlock in hibernate_compressor_param_set()  \n  \nsyzbot reported a deadlock in lock_system_sleep() (see below).  \n  \nThe write operation to \"/sys/module/hibernate/parameters/compressor\"  \nconflicts with the registration of ieee80211 device, resulting in a deadlock  \nwhen attempting to acquire system_transition_mutex under param_lock.  \n  \nTo avoid this deadlock, change hibernate_compressor_param_set() to use  \nmutex_trylock() for attempting to acquire system_transition_mutex and  \nreturn -EBUSY when it fails.  \n  \nTask flags need not be saved or adjusted before calling  \nmutex_trylock(&system_transition_mutex) because the caller is not going  \nto end up waiting for this mutex and if it runs concurrently with system  \nsuspend in progress, it will be frozen properly when it returns to user  \nspace.  \n  \nsyzbot report:  \n  \nsyz-executor895/5833 is trying to acquire lock:  \nffffffff8e0828c8 (system_transition_mutex){+.+.}-{4:4}, at: lock_system_sleep+0x87/0xa0 kernel/power/main.c:56  \n  \nbut task is already holding lock:  \nffffffff8e07dc68 (param_lock){+.+.}-{4:4}, at: kernel_param_lock kernel/params.c:607 [inline]  \nffffffff8e07dc68 (param_lock){+.+.}-{4:4}, at: param_attr_store+0xe6/0x300 kernel/params.c:586  \n  \nwhich lock already depends on the new lock.  \n  \nthe existing dependency chain (in reverse order) is:  \n  \n-> #3 (param_lock){+.+.}-{4:4}:  \n       __mutex_lock_common kernel/locking/mutex.c:585 [inline]  \n       __mutex_lock+0x19b/0xb10 kernel/locking/mutex.c:730  \n       ieee80211_rate_control_ops_get net/mac80211/rate.c:220 [inline]  \n       rate_control_alloc net/mac80211/rate.c:266 [inline]  \n       ieee80211_init_rate_ctrl_alg+0x18d/0x6b0 net/mac80211/rate.c:1015  \n       ieee80211_register_hw+0x20cd/0x4060 net/mac80211/main.c:1531  \n       mac80211_hwsim_new_radio+0x304e/0x54e0 drivers/net/wireless/virtual/mac80211_hwsim.c:5558  \n       init_mac80211_hwsim+0x432/0x8c0 drivers/net/wireless/virtual/mac80211_hwsim.c:6910  \n       do_one_initcall+0x128/0x700 init/main.c:1257  \n       do_initcall_level init/main.c:1319 [inline]  \n       do_initcalls init/main.c:1335 [inline]  \n       do_basic_setup init/main.c:1354 [inline]  \n       kernel_init_freeable+0x5c7/0x900 init/main.c:1568  \n       kernel_init+0x1c/0x2b0 init/main.c:1457  \n       ret_from_fork+0x45/0x80 arch/x86/kernel/process.c:148  \n       ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244  \n  \n-> #2 (rtnl_mutex){+.+.}-{4:4}:  \n       __mutex_lock_common kernel/locking/mutex.c:585 [inline]  \n       __mutex_lock+0x19b/0xb10 kernel/locking/mutex.c:730  \n       wg_pm_notification drivers/net/wireguard/device.c:80 [inline]  \n       wg_pm_notification+0x49/0x180 drivers/net/wireguard/device.c:64  \n       notifier_call_chain+0xb7/0x410 kernel/notifier.c:85  \n       notifier_call_chain_robust kernel/notifier.c:120 [inline]  \n       blocking_notifier_call_chain_robust kernel/notifier.c:345 [inline]  \n       blocking_notifier_call_chain_robust+0xc9/0x170 kernel/notifier.c:333  \n       pm_notifier_call_chain_robust+0x27/0x60 kernel/power/main.c:102  \n       snapshot_open+0x189/0x2b0 kernel/power/user.c:77  \n       misc_open+0x35a/0x420 drivers/char/misc.c:179  \n       chrdev_open+0x237/0x6a0 fs/char_dev.c:414  \n       do_dentry_open+0x735/0x1c40 fs/open.c:956  \n       vfs_open+0x82/0x3f0 fs/open.c:1086  \n       do_open fs/namei.c:3830 [inline]  \n       path_openat+0x1e88/0x2d80 fs/namei.c:3989  \n       do_filp_open+0x20c/0x470 fs/namei.c:4016  \n       do_sys_openat2+0x17a/0x1e0 fs/open.c:1428  \n       do_sys_open fs/open.c:1443 [inline]  \n       __do_sys_openat fs/open.c:1459 [inline]  \n       __se_sys_openat fs/open.c:1454 [inline]  \n       __x64_sys_openat+0x175/0x210 fs/ope[...]", "creation_timestamp": "2025-05-01T16:30:12.000000Z"}, {"uuid": "190d591d-6d2a-42eb-b046-07baf5466175", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37744", "type": "seen", "source": "https://t.me/cvedetector/24217", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-37744 - Linux Kernel Ath12k WiFi Firmware Memory Leak Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2025-37744 \nPublished : May 1, 2025, 1:15 p.m. | 1\u00a0hour, 5\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nwifi: ath12k: fix memory leak in ath12k_pci_remove()  \n  \nKmemleak reported this error:  \n  \n  unreferenced object 0xffff1c165cec3060 (size 32):  \n    comm \"insmod\", pid 560, jiffies 4296964570 (age 235.596s)  \n    backtrace:  \n      [<000000005434db68] __kmem_cache_alloc_node+0x1f4/0x2c0  \n      [<000000001203b155] kmalloc_trace+0x40/0x88  \n      [<0000000028adc9c8] _request_firmware+0xb8/0x608  \n      [<00000000cad1aef7] firmware_request_nowarn+0x50/0x80  \n      [<000000005011a682] local_pci_probe+0x48/0xd0  \n      [<00000000077cd295] pci_device_probe+0xb4/0x200  \n      [<0000000087184c94] really_probe+0x150/0x2c0  \n  \nThe firmware memory was allocated in ath12k_pci_probe(), but not  \nfreed in ath12k_pci_remove() in case ATH12K_FLAG_QMI_FAIL bit is  \nset. So call ath12k_fw_unmap() to free the memory.  \n  \nTested-on: WCN7850 hw2.0 PCI WLAN.HMT.2.0-02280-QCAHMTSWPL_V1.0_V2.0_SILICONZ-1 \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"01 May 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-05-01T16:30:11.000000Z"}, {"uuid": "5d403305-4a62-4c73-a020-dfa096deb81f", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37759", "type": "seen", "source": "https://t.me/cvedetector/24216", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-37759 - \"ublk Linux Kernel NULL Pointer Dereference Vulnerability\"\", \n  \"Content\": \"CVE ID : CVE-2025-37759 \nPublished : May 1, 2025, 1:15 p.m. | 1\u00a0hour, 5\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nublk: fix handling recovery & reissue in ublk_abort_queue()  \n  \nCommit 8284066946e6 (\"ublk: grab request reference when the request is handled  \nby userspace\") doesn't grab request reference in case of recovery reissue.  \nThen the request can be requeued & re-dispatch & failed when canceling  \nuring command.  \n  \nIf it is one zc request, the request can be freed before io_uring  \nreturns the zc buffer back, then cause kernel panic:  \n  \n[  126.773061] BUG: kernel NULL pointer dereference, address: 00000000000000c8  \n[  126.773657] #PF: supervisor read access in kernel mode  \n[  126.774052] #PF: error_code(0x0000) - not-present page  \n[  126.774455] PGD 0 P4D 0  \n[  126.774698] Oops: Oops: 0000 [#1] SMP NOPTI  \n[  126.775034] CPU: 13 UID: 0 PID: 1612 Comm: kworker/u64:55 Not tainted 6.14.0_blk+ #182 PREEMPT(full)  \n[  126.775676] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-1.fc39 04/01/2014  \n[  126.776275] Workqueue: iou_exit io_ring_exit_work  \n[  126.776651] RIP: 0010:ublk_io_release+0x14/0x130 [ublk_drv]  \n  \nFixes it by always grabbing request reference for aborting the request. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"01 May 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-05-01T16:30:10.000000Z"}, {"uuid": "af73abbd-519a-449e-9670-613316cb946c", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37757", "type": "seen", "source": "https://t.me/cvedetector/24215", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-37757 - Linux Kernel tipc Memory Leak Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2025-37757 \nPublished : May 1, 2025, 1:15 p.m. | 1\u00a0hour, 5\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \ntipc: fix memory leak in tipc_link_xmit  \n  \nIn case the backlog transmit queue for system-importance messages is overloaded,  \ntipc_link_xmit() returns -ENOBUFS but the skb list is not purged. This leads to  \nmemory leak and failure when a skb is allocated.  \n  \nThis commit fixes this issue by purging the skb list before tipc_link_xmit()  \nreturns. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"01 May 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-05-01T16:30:10.000000Z"}, {"uuid": "e8ac776d-3389-4a33-9c37-a288e3491829", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37756", "type": "seen", "source": "https://t.me/cvedetector/24214", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-37756 - Linux Kernel TLS Disconnect Disallowed\", \n  \"Content\": \"CVE ID : CVE-2025-37756 \nPublished : May 1, 2025, 1:15 p.m. | 1\u00a0hour, 5\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nnet: tls: explicitly disallow disconnect  \n  \nsyzbot discovered that it can disconnect a TLS socket and then  \nrun into all sort of unexpected corner cases. I have a vague  \nrecollection of Eric pointing this out to us a long time ago.  \nSupporting disconnect is really hard, for one thing if offload  \nis enabled we'd need to wait for all packets to be _acked_.  \nDisconnect is not commonly used, disallow it.  \n  \nThe immediate problem syzbot run into is the warning in the strp,  \nbut that's just the easiest bug to trigger:  \n  \n  WARNING: CPU: 0 PID: 5834 at net/tls/tls_strp.c:486 tls_strp_msg_load+0x72e/0xa80 net/tls/tls_strp.c:486  \n  RIP: 0010:tls_strp_msg_load+0x72e/0xa80 net/tls/tls_strp.c:486  \n  Call Trace:  \n     \n   tls_rx_rec_wait+0x280/0xa60 net/tls/tls_sw.c:1363  \n   tls_sw_recvmsg+0x85c/0x1c30 net/tls/tls_sw.c:2043  \n   inet6_recvmsg+0x2c9/0x730 net/ipv6/af_inet6.c:678  \n   sock_recvmsg_nosec net/socket.c:1023 [inline]  \n   sock_recvmsg+0x109/0x280 net/socket.c:1045  \n   __sys_recvfrom+0x202/0x380 net/socket.c:2237 \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"01 May 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-05-01T16:30:06.000000Z"}, {"uuid": "d983e43b-3eba-4bc0-8aab-2368366ba523", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37755", "type": "seen", "source": "https://t.me/cvedetector/24213", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-37755 - Linux kernel: Net Device Page Pool Allocation NULL Pointer Dereference Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2025-37755 \nPublished : May 1, 2025, 1:15 p.m. | 1\u00a0hour, 5\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nnet: libwx: handle page_pool_dev_alloc_pages error  \n  \npage_pool_dev_alloc_pages could return NULL. There was a WARN_ON(!page)  \nbut it would still proceed to use the NULL pointer and then crash.  \n  \nThis is similar to commit 001ba0902046  \n(\"net: fec: handle page_pool_dev_alloc_pages error\").  \n  \nThis is found by our static analysis tool KNighter. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"01 May 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-05-01T16:30:05.000000Z"}, {"uuid": "d2bcc77b-ec92-4a6b-811a-a30249e8f994", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37753", "type": "seen", "source": "https://t.me/cvedetector/24212", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-37753 - IBM Linux Kernel s390 Double Free Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2025-37753 \nPublished : May 1, 2025, 1:15 p.m. | 1\u00a0hour, 5\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \ns390/cpumf: Fix double free on error in cpumf_pmu_event_init()  \n  \nIn PMU event initialization functions  \n - cpumsf_pmu_event_init()  \n - cpumf_pmu_event_init()  \n - cfdiag_event_init()  \nthe partially created event had to be removed when an error was detected.  \nThe event::event_init() member function had to release all resources  \nit allocated in case of error. event::destroy() had to be called  \non freeing an event after it was successfully created and  \nevent::event_init() returned success.  \n  \nWith  \n  \ncommit c70ca298036c (\"perf/core: Simplify the perf_event_alloc() error path\")  \n  \nthis is not necessary anymore. The performance subsystem common  \ncode now always calls event::destroy() to clean up the allocated  \nresources created during event initialization.  \n  \nRemove the event::destroy() invocation in PMU event initialization  \nor that function is called twice for each event that runs into an  \nerror condition in event creation.  \n  \nThis is the kernel log entry which shows up without the fix:  \n  \n------------[ cut here ]------------  \nrefcount_t: underflow; use-after-free.  \nWARNING: CPU: 0 PID: 43388 at lib/refcount.c:87 refcount_dec_not_one+0x74/0x90  \nCPU: 0 UID: 0 PID: 43388 Comm: perf Not tainted 6.15.0-20250407.rc1.git0.300.fc41.s390x+git #1 NONE  \nHardware name: IBM 3931 A01 704 (LPAR)  \nKrnl PSW : 0704c00180000000 00000209cb2c1b88 (refcount_dec_not_one+0x78/0x90)  \n           R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:3 CC:0 PM:0 RI:0 EA:3  \nKrnl GPRS: 0000020900000027 0000020900000023 0000000000000026 0000018900000000  \n           00000004a2200a00 0000000000000000 0000000000000057 ffffffffffffffea  \n           00000002b386c600 00000002b3f5b3e0 00000209cc51f140 00000209cc7fc550  \n           0000000001449d38 ffffffffffffffff 00000209cb2c1b84 00000189d67dfb80  \nKrnl Code: 00000209cb2c1b78: c02000506727 larl %r2,00000209cbcce9c6  \n           00000209cb2c1b7e: c0e5ffbd4431 brasl %r14,00000209caa6a3e0  \n          #00000209cb2c1b84: af000000  mc 0,0  \n          >00000209cb2c1b88: a7480001  lhi %r4,1  \n           00000209cb2c1b8c: ebeff0a00004 lmg %r14,%r15,160(%r15)  \n           00000209cb2c1b92: ec243fbf0055 risbg %r2,%r4,63,191,0  \n           00000209cb2c1b98: 07fe  bcr 15,%r14  \n           00000209cb2c1b9a: 47000700  bc 0,1792  \nCall Trace:  \n [<00000209cb2c1b88] refcount_dec_not_one+0x78/0x90  \n [<00000209cb2c1dc4] refcount_dec_and_mutex_lock+0x24/0x90  \n [<00000209caa3c29e] hw_perf_event_destroy+0x2e/0x80  \n [<00000209cacaf8b4] __free_event+0x74/0x270  \n [<00000209cacb47c4] perf_event_alloc.part.0+0x4a4/0x730  \n [<00000209cacbf3e8] __do_sys_perf_event_open+0x248/0xc20  \n [<00000209cacc14a4] __s390x_sys_perf_event_open+0x44/0x50  \n [<00000209cb8114de] __do_syscall+0x12e/0x260  \n [<00000209cb81ce34] system_call+0x74/0x98  \nLast Breaking-Event-Address:  \n [<00000209caa6a4d2] __warn_printk+0xf2/0x100  \n---[ end trace 0000000000000000 ]--- \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"01 May 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-05-01T16:30:04.000000Z"}, {"uuid": "6305849b-5cf6-4f9a-9663-8ab1cd129f78", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37758", "type": "seen", "source": "https://t.me/cvedetector/24211", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-37758 - Linux ata Pata Pxa Null Pointer Dereference Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2025-37758 \nPublished : May 1, 2025, 1:15 p.m. | 1\u00a0hour, 5\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nata: pata_pxa: Fix potential NULL pointer dereference in pxa_ata_probe()  \n  \ndevm_ioremap() returns NULL on error. Currently, pxa_ata_probe() does  \nnot check for this case, which can result in a NULL pointer dereference.  \n  \nAdd NULL check after devm_ioremap() to prevent this issue. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"01 May 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-05-01T16:30:04.000000Z"}, {"uuid": "c40af9ee-ebda-4cce-b216-335231f375a6", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37754", "type": "seen", "source": "https://t.me/cvedetector/24210", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-37754 - Intel I915 DRM Fence Not Released Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2025-37754 \nPublished : May 1, 2025, 1:15 p.m. | 1\u00a0hour, 5\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \ndrm/i915/huc: Fix fence not released on early probe errors  \n  \nHuC delayed loading fence, introduced with commit 27536e03271da  \n(\"drm/i915/huc: track delayed HuC load with a fence\"), is registered with  \nobject tracker early on driver probe but unregistered only from driver  \nremove, which is not called on early probe errors.  Since its memory is  \nallocated under devres, then released anyway, it may happen to be  \nallocated again to the fence and reused on future driver probes, resulting  \nin kernel warnings that taint the kernel: <4[309.731371] ------------[ cut here ]------------ <3[309.731373] ODEBUG: init destroyed (active state 0) object: ffff88813d7dd2e0 object type: i915_sw_fence hint: sw_fence_dummy_notify+0x0/0x20 [i915] <4[309.731575] WARNING: CPU: 2 PID: 3161 at lib/debugobjects.c:612 debug_print_object+0x93/0xf0  \n... <4[309.731693] CPU: 2 UID: 0 PID: 3161 Comm: i915_module_loa Tainted: G     U             6.14.0-CI_DRM_16362-gf0fd77956987+ #1  \n... <4[309.731700] RIP: 0010:debug_print_object+0x93/0xf0  \n... <4[309.731728] Call Trace: <4[309.731730]    \n... <4[309.731949]  __debug_object_init+0x17b/0x1c0 <4[309.731957]  debug_object_init+0x34/0x50 <4[309.732126]  __i915_sw_fence_init+0x34/0x60 [i915] <4[309.732256]  intel_huc_init_early+0x4b/0x1d0 [i915] <4[309.732468]  intel_uc_init_early+0x61/0x680 [i915] <4[309.732667]  intel_gt_common_init_early+0x105/0x130 [i915] <4[309.732804]  intel_root_gt_init_early+0x63/0x80 [i915] <4[309.732938]  i915_driver_probe+0x1fa/0xeb0 [i915] <4[309.733075]  i915_pci_probe+0xe6/0x220 [i915] <4[309.733198]  local_pci_probe+0x44/0xb0 <4[309.733203]  pci_device_probe+0xf4/0x270 <4[309.733209]  really_probe+0xee/0x3c0 <4[309.733215]  __driver_probe_device+0x8c/0x180 <4[309.733219]  driver_probe_device+0x24/0xd0 <4[309.733223]  __driver_attach+0x10f/0x220 <4[309.733230]  bus_for_each_dev+0x7d/0xe0 <4[309.733236]  driver_attach+0x1e/0x30 <4[309.733239]  bus_add_driver+0x151/0x290 <4[309.733244]  driver_register+0x5e/0x130 <4[309.733247]  __pci_register_driver+0x7d/0x90 <4[309.733251]  i915_pci_register_driver+0x23/0x30 [i915] <4[309.733413]  i915_init+0x34/0x120 [i915] <4[309.733655]  do_one_initcall+0x62/0x3f0 <4[309.733667]  do_init_module+0x97/0x2a0 <4[309.733671]  load_module+0x25ff/0x2890 <4[309.733688]  init_module_from_file+0x97/0xe0 <4[309.733701]  idempotent_init_module+0x118/0x330 <4[309.733711]  __x64_sys_finit_module+0x77/0x100 <4[309.733715]  x64_sys_call+0x1f37/0x2650 <4[309.733719]  do_syscall_64+0x91/0x180 <4[309.733763]  entry_SYSCALL_64_after_hwframe+0x76/0x7e <4[309.733792]    \n... <4[309.733806] ---[ end trace 0000000000000000 ]---  \n  \nThat scenario is most easily reproducible with  \nigt@i915_module_load@reload-with-fault-injection.  \n  \nFix the issue by moving the cleanup step to driver release path.  \n  \n(cherry picked from commit 795dbde92fe5c6996a02a5b579481de73035e7bf) \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"01 May 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-05-01T16:30:03.000000Z"}, {"uuid": "61cf7d3d-e43d-4de2-818a-02f22a4cd9cd", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3725", "type": "seen", "source": "https://t.me/cvedetector/23180", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-3725 - PCMan FTP Server MIC Command Handler Buffer Overflow Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2025-3725 \nPublished : April 16, 2025, 8:15 p.m. | 1\u00a0hour, 31\u00a0minutes ago \nDescription : A vulnerability was found in PCMan FTP Server 2.0.7. It has been declared as critical. Affected by this vulnerability is an unknown functionality of the component MIC Command Handler. The manipulation leads to buffer overflow. The attack can be launched remotely. The exploit has been disclosed to the public and may be used. \nSeverity: 7.3 | HIGH \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"16 Apr 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-04-17T00:25:56.000000Z"}, {"uuid": "a46a1b68-9f13-4fa1-9290-cfc175fe52b0", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3726", "type": "seen", "source": "https://t.me/cvedetector/23181", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-3726 - PCMan FTP Server CD Command Handler Buffer Overflow Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2025-3726 \nPublished : April 16, 2025, 8:15 p.m. | 1\u00a0hour, 31\u00a0minutes ago \nDescription : A vulnerability was found in PCMan FTP Server 2.0.7. It has been rated as critical. Affected by this issue is some unknown functionality of the component CD Command Handler. The manipulation leads to buffer overflow. The attack may be launched remotely. The exploit has been disclosed to the public and may be used. \nSeverity: 7.3 | HIGH \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"16 Apr 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-04-17T00:25:56.000000Z"}, {"uuid": "77ca88af-5f72-4440-b6ed-c8c5f1020008", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3723", "type": "seen", "source": "https://t.me/cvedetector/23183", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-3723 - PCMan FTP Server MDTM Command Handler Buffer Overflow\", \n  \"Content\": \"CVE ID : CVE-2025-3723 \nPublished : April 16, 2025, 8:15 p.m. | 1\u00a0hour, 31\u00a0minutes ago \nDescription : A vulnerability was found in PCMan FTP Server 2.0.7 and classified as critical. This issue affects some unknown processing of the component MDTM Command Handler. The manipulation leads to buffer overflow. The attack may be initiated remotely. The exploit has been disclosed to the public and may be used. \nSeverity: 7.3 | HIGH \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"16 Apr 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-04-17T00:26:01.000000Z"}, {"uuid": "9e8e13c0-8030-4bc6-8b66-f0155a34b9ff", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3760", "type": "seen", "source": "https://t.me/cvedetector/23228", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-3760 - Liferay Portal Stored Cross-Site Scripting (XSS)\", \n  \"Content\": \"CVE ID : CVE-2025-3760 \nPublished : April 17, 2025, 1:15 p.m. | 58\u00a0minutes ago \nDescription : A stored cross-site scripting (XSS) vulnerability exists with radio button type custom fields in Liferay Portal 7.2.0 through 7.4.3.129, and Liferay DXP 2024.Q4.1 through 2024.Q4.7, 2024.Q3.1 through 2024.Q3.9, 2024.Q2.0 through 2024.Q2.13, 2024.Q1.1 through 2024.Q1.12, 2023.Q4.0 through 2023.Q4.10, 2023.Q3.1 through 2023.Q3.10, 7.4 GA through update 92, 7.3 GA through update 36, and 7.2 GA through fix pack 20 allows remote authenticated attackers to inject malicious JavaScript into a page. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"17 Apr 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-04-17T17:09:31.000000Z"}, {"uuid": "2d20a21c-bd03-42cc-a6dc-f0f31bdce873", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3724", "type": "seen", "source": "https://t.me/cvedetector/23184", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-3724 - PCMan FTP Server Buffer Overflow Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2025-3724 \nPublished : April 16, 2025, 8:15 p.m. | 1\u00a0hour, 31\u00a0minutes ago \nDescription : A vulnerability was found in PCMan FTP Server 2.0.7. It has been classified as critical. Affected is an unknown function of the component DIR Command Handler. The manipulation leads to buffer overflow. It is possible to launch the attack remotely. The exploit has been disclosed to the public and may be used. \nSeverity: 7.3 | HIGH \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"16 Apr 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-04-17T00:26:02.000000Z"}, {"uuid": "6f44419c-68a7-4d70-8f78-92c0e201dedf", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3730", "type": "seen", "source": "https://t.me/cvedetector/23171", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-3730 - PyTorch Denial of Service Vulnerability in torch.nn.functional.ctc_loss\", \n  \"Content\": \"CVE ID : CVE-2025-3730 \nPublished : April 16, 2025, 9:15 p.m. | 30\u00a0minutes ago \nDescription : A vulnerability, which was classified as problematic, was found in PyTorch 2.6.0. Affected is the function torch.nn.functional.ctc_loss of the file aten/src/ATen/native/LossCTC.cpp. The manipulation leads to denial of service. An attack has to be approached locally. The exploit has been disclosed to the public and may be used. The name of the patch is 46fc5d8e360127361211cb237d5f9eef0223e567. It is recommended to apply a patch to fix this issue. \nSeverity: 3.3 | LOW \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"16 Apr 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-04-17T00:25:43.000000Z"}, {"uuid": "66ce4539-a9be-427b-8e18-8b41f2f44d04", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3729", "type": "seen", "source": "https://t.me/cvedetector/23170", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-3729 - SourceCodester Web-based Pharmacy Product Management System OS Command Injection Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2025-3729 \nPublished : April 16, 2025, 9:15 p.m. | 30\u00a0minutes ago \nDescription : A vulnerability, which was classified as critical, has been found in SourceCodester Web-based Pharmacy Product Management System 1.0. This issue affects some unknown processing of the file backup.php of the component Database Backup Handler. The manipulation of the argument txtdbname leads to os command injection. The attack may be initiated remotely. The exploit has been disclosed to the public and may be used. \nSeverity: 7.3 | HIGH \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"16 Apr 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-04-17T00:25:43.000000Z"}, {"uuid": "4f506433-1561-42c3-b4f0-7e89652ddab6", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3728", "type": "seen", "source": "https://t.me/cvedetector/23169", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-3728 - SourceCodester Simple Hotel Booking System Buffer Overflow in Login\", \n  \"Content\": \"CVE ID : CVE-2025-3728 \nPublished : April 16, 2025, 9:15 p.m. | 30\u00a0minutes ago \nDescription : A vulnerability classified as critical was found in SourceCodester Simple Hotel Booking System 1.0. This vulnerability affects the function Login. The manipulation of the argument uname leads to buffer overflow. It is possible to launch the attack on the local host. The exploit has been disclosed to the public and may be used. \nSeverity: 5.3 | MEDIUM \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"16 Apr 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-04-17T00:25:42.000000Z"}, {"uuid": "29e3fc7e-e4d2-4802-a480-538e24d35d46", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3727", "type": "seen", "source": "https://t.me/cvedetector/23168", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-3727 - PCMan FTP Server Buffer Overflow Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2025-3727 \nPublished : April 16, 2025, 9:15 p.m. | 30\u00a0minutes ago \nDescription : A vulnerability classified as critical has been found in PCMan FTP Server 2.0.7. This affects an unknown part of the component STATUS Command Handler. The manipulation leads to buffer overflow. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used. \nSeverity: 7.3 | HIGH \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"16 Apr 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-04-17T00:25:41.000000Z"}, {"uuid": "236a04e4-8c12-4751-be87-284a41f6e68e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3734", "type": "seen", "source": "https://t.me/cvedetector/23138", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-3734 - Drupal Stage File Proxy Unauthenticated Flooding Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2025-3734 \nPublished : April 16, 2025, 5:15 p.m. | 28\u00a0minutes ago \nDescription : Allocation of Resources Without Limits or Throttling vulnerability in Drupal Stage File Proxy allows Flooding.This issue affects Stage File Proxy: from 0.0.0 before 3.1.5. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"16 Apr 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-04-16T20:14:30.000000Z"}, {"uuid": "04f4ada1-bc4d-41a8-8a4c-76d48a985752", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3733", "type": "seen", "source": "https://t.me/cvedetector/23137", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-3733 - Drupal baguetteBox.Js Cross-site Scripting (XSS)\", \n  \"Content\": \"CVE ID : CVE-2025-3733 \nPublished : April 16, 2025, 5:15 p.m. | 28\u00a0minutes ago \nDescription : Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Drupal baguetteBox.Js allows Cross-Site Scripting (XSS).This issue affects baguetteBox.Js: from 0.0.0 before 2.0.4, from 3.0.0 before 3.0.1. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"16 Apr 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-04-16T20:14:29.000000Z"}, {"uuid": "9161a9d6-3cf0-4368-9baa-2d0078866562", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3739", "type": "seen", "source": "https://t.me/cvedetector/23131", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-3739 - \"Drupal Google Optimize Hide Page Information Disclosure\"\", \n  \"Content\": \"CVE ID : CVE-2025-3739 \nPublished : April 16, 2025, 5:15 p.m. | 28\u00a0minutes ago \nDescription : Vulnerability in Drupal Drupal 8 Google Optimize Hide Page.This issue affects Drupal 8 Google Optimize Hide Page: *.*. \nSeverity: 5.9 | MEDIUM \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"16 Apr 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-04-16T20:14:18.000000Z"}, {"uuid": "94cd4733-931b-42e6-a7bc-0dc1ed99a121", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3737", "type": "seen", "source": "https://t.me/cvedetector/23130", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-3737 - \"Drupal Google Maps Store Locator Cross-Site Scripting Vulnerability\"\", \n  \"Content\": \"CVE ID : CVE-2025-3737 \nPublished : April 16, 2025, 5:15 p.m. | 28\u00a0minutes ago \nDescription : Vulnerability in Drupal Google Maps: Store Locator.This issue affects Google Maps: Store Locator: *.*. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"16 Apr 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-04-16T20:14:17.000000Z"}, {"uuid": "687b9e09-d4cf-4f78-8ed4-9048caa3a210", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3738", "type": "seen", "source": "https://t.me/cvedetector/23128", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-3738 - \"Drupal Google Optimize Authentication Bypass\"\", \n  \"Content\": \"CVE ID : CVE-2025-3738 \nPublished : April 16, 2025, 5:15 p.m. | 28\u00a0minutes ago \nDescription : Vulnerability in Drupal Google Optimize.This issue affects Google Optimize: *.*. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"16 Apr 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-04-16T20:14:16.000000Z"}, {"uuid": "2c61e92b-1dd0-4af8-813b-48117291baaf", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3736", "type": "seen", "source": "https://t.me/cvedetector/23129", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-3736 - \"Drupal Simple GTM Cross-Site Scripting Vulnerability\"\", \n  \"Content\": \"CVE ID : CVE-2025-3736 \nPublished : April 16, 2025, 5:15 p.m. | 28\u00a0minutes ago \nDescription : Vulnerability in Drupal Simple GTM.This issue affects Simple GTM: *.*. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"16 Apr 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-04-16T20:14:17.000000Z"}, {"uuid": "bdcf6a08-dab1-45e3-a4cc-420ae9c3a857", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3735", "type": "seen", "source": "https://t.me/cvedetector/23127", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-3735 - Drupal Panelizer Cross-Site Request Forgery\", \n  \"Content\": \"CVE ID : CVE-2025-3735 \nPublished : April 16, 2025, 5:15 p.m. | 28\u00a0minutes ago \nDescription : Vulnerability in Drupal Panelizer (obsolete).This issue affects Panelizer (obsolete): *.*. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"16 Apr 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-04-16T20:14:15.000000Z"}, {"uuid": "846b58f8-6346-4ca6-b522-f04b05f59533", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3776", "type": "published-proof-of-concept", "source": "https://t.me/TheDarkWebInformer/16782", "content": "CVE-2025-3776: Full WordPress Takeover Without Login (Critical RCE Exploit)\n\nCredit: youtube.com/@Nxploited", "creation_timestamp": "2025-05-04T01:22:00.000000Z"}, {"uuid": "1800cedc-492b-4061-9bc6-daaaca1b7e06", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3759", "type": "seen", "source": "Telegram/60cT2wlrT_hpaI2p205p7MoAi0oA9icyTsBVXTnXIGE3EPI", "content": "", "creation_timestamp": "2025-05-08T12:31:18.000000Z"}, {"uuid": "7e409f48-0509-47f3-918a-336e38267d39", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3776", "type": "published-proof-of-concept", "source": "Telegram/6rNZORcsrpIp6uXsVyLv3NgDJiB8gwaKAVRPuTsSWUoFbnM", "content": "", "creation_timestamp": "2025-04-24T13:00:07.000000Z"}, {"uuid": "087a3459-f0ae-4aae-bd6d-61ea1cd55b0c", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3711", "type": "published-proof-of-concept", "source": "Telegram/LmF-oJVU7SiGeaAkGTq-PJOHK6kdysB5ZubzAPJ_ONf_ATA", "content": "", "creation_timestamp": "2025-05-09T07:01:38.000000Z"}, {"uuid": "40fb8ff3-493c-4b00-be2d-e11ec20a24ff", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3712", "type": "published-proof-of-concept", "source": "Telegram/LmF-oJVU7SiGeaAkGTq-PJOHK6kdysB5ZubzAPJ_ONf_ATA", "content": "", "creation_timestamp": "2025-05-09T07:01:38.000000Z"}, {"uuid": "3905507c-ebcc-40f3-a244-badc2e2bbee7", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3714", "type": "published-proof-of-concept", "source": "Telegram/LmF-oJVU7SiGeaAkGTq-PJOHK6kdysB5ZubzAPJ_ONf_ATA", "content": "", "creation_timestamp": "2025-05-09T07:01:38.000000Z"}, {"uuid": "b0a3d62b-4d5e-4ab6-8c06-93c217e8ea4e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3786", "type": "published-proof-of-concept", "source": "Telegram/J6-YRih7z8cR8rFeyp9RZpIGSbXlufFD6LMHeh3O0VicODw", "content": "", "creation_timestamp": "2025-04-18T12:30:29.000000Z"}, {"uuid": "8d314d1d-9319-4e38-a472-9d6637d21407", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3785", "type": "published-proof-of-concept", "source": "Telegram/bGQgeOYEYSeYgWjnNSxEOzzS8UcdNupwNTGd2dEnarstsPY", "content": "", "creation_timestamp": "2025-04-18T11:30:43.000000Z"}, {"uuid": "14cc25b3-fbd4-4617-b95d-0e9bc9d0a1a2", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3799", "type": "published-proof-of-concept", "source": "Telegram/aQjCu2eev9i-ft2FlOvbZKQLLyqFs5R9j7h3CcERvr2hOPQ", "content": "", "creation_timestamp": "2025-04-19T13:30:16.000000Z"}, {"uuid": "984e5eb9-b2fe-4372-ba7d-7c0c47ff3d5a", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3710", "type": "published-proof-of-concept", "source": "Telegram/LmF-oJVU7SiGeaAkGTq-PJOHK6kdysB5ZubzAPJ_ONf_ATA", "content": "", "creation_timestamp": "2025-05-09T07:01:38.000000Z"}, {"uuid": "1a3b9e2f-f8a2-4ee2-9f06-750a698c5dd1", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3713", "type": "published-proof-of-concept", "source": "Telegram/LmF-oJVU7SiGeaAkGTq-PJOHK6kdysB5ZubzAPJ_ONf_ATA", "content": "", "creation_timestamp": "2025-05-09T07:01:38.000000Z"}, {"uuid": "1225cd81-830e-4068-a4f7-00de04a81736", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3709", "type": "seen", "source": "Telegram/iYh3KCKDOJhhtXUlLXzKQ0urfXGfuEgjBYvrs8SISUYckP4", "content": "", "creation_timestamp": "2025-05-02T06:00:38.000000Z"}, {"uuid": "01873d5b-391f-409f-bccc-a1d31164ff0f", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3708", "type": "seen", "source": "Telegram/iYh3KCKDOJhhtXUlLXzKQ0urfXGfuEgjBYvrs8SISUYckP4", "content": "", "creation_timestamp": "2025-05-02T06:00:38.000000Z"}, {"uuid": "94a9ed40-c238-40f3-abda-573a0d55e77c", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3746", "type": "seen", "source": "Telegram/7QEqju-jYCJkVqvbZMxXpX4ajzaYKxifFuPEzR6oDsSpQMc", "content": "", "creation_timestamp": "2025-05-02T05:01:09.000000Z"}, {"uuid": "3fee9c38-1725-4039-886d-b2acb51070f5", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37752", "type": "seen", "source": "https://t.me/proxy_bar/2613", "content": "CVE-2025-37752\n*\nTwo Bytes Of Madness: Pwning The Linux Kernel With A 0x0000 Written 262636 Bytes Out-Of-Bounds\n\n#linux #kernel", "creation_timestamp": "2025-05-12T18:41:14.000000Z"}, {"uuid": "01919dad-fe4f-4a77-9ece-808e0760a154", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2025-3756", "type": "seen", "source": "https://www.cisa.gov/news-events/ics-advisories/icsa-26-120-01", "content": "", "creation_timestamp": "2026-04-30T05:00:00.000000Z"}, {"uuid": "189f859e-a566-4bf0-93d6-2bccd1b971c7", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37899", "type": "published-proof-of-concept", "source": "https://t.me/arpsyndicate/5399", "content": "Sean Heelan discovered a critical zero-day vulnerability, CVE-2025-37899 in the Linux kernel's ksmbd module using OpenAI's o3 language model. This marks one of the first instances where a large language model has independently identified a complex kernel-level security flaw.\n\nhttps://sean.heelan.io/2025/05/22/how-i-used-o3-to-find-cve-2025-37899-a-remote-zeroday-vulnerability-in-the-linux-kernels-smb-implementation/", "creation_timestamp": "2025-05-25T04:51:16.000000Z"}, {"uuid": "740cce6d-323b-42e2-a9e0-edbace8a2087", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37899", "type": "seen", "source": "Telegram/o6I6gJFJZLRloRR7lENgRZB4w7CLwtfgPkZ1w44WPU4dGLs", "content": "", "creation_timestamp": "2025-05-24T15:59:06.000000Z"}, {"uuid": "e422430d-3790-4f77-91f0-f3ddc4603ed2", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2025-37786", "type": "seen", "source": "https://www.hkcert.org/security-bulletin/ubuntu-linux-kernel-multiple-vulnerabilities_20260803", "content": "", "creation_timestamp": "2026-08-03T04:53:07.504756Z"}, {"uuid": "8d778000-017c-4a6c-920d-440b374ccf75", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37830", "type": "seen", "source": "https://t.me/cvedetector/24792", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-37830 - Linux Kernel cpufreq scmi Null Pointer Dereference Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2025-37830 \nPublished : May 8, 2025, 7:15 a.m. | 2\u00a0hours, 2\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \ncpufreq: scmi: Fix null-ptr-deref in scmi_cpufreq_get_rate()  \n  \ncpufreq_cpu_get_raw() can return NULL when the target CPU is not present  \nin the policy->cpus mask. scmi_cpufreq_get_rate() does not check for  \nthis case, which results in a NULL pointer dereference.  \n  \nAdd NULL check after cpufreq_cpu_get_raw() to prevent this issue. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"08 May 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-05-08T11:44:46.000000Z"}, {"uuid": "8db1646a-d7b2-4375-accb-0a43bbf97da4", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37829", "type": "seen", "source": "https://t.me/cvedetector/24793", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-37829 - \"Linux cpufreq: NULL Pointer Dereference Vulnerability\"\", \n  \"Content\": \"CVE ID : CVE-2025-37829 \nPublished : May 8, 2025, 7:15 a.m. | 2\u00a0hours, 2\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \ncpufreq: scpi: Fix null-ptr-deref in scpi_cpufreq_get_rate()  \n  \ncpufreq_cpu_get_raw() can return NULL when the target CPU is not present  \nin the policy->cpus mask. scpi_cpufreq_get_rate() does not check for  \nthis case, which results in a NULL pointer dereference. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"08 May 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-05-08T11:44:46.000000Z"}, {"uuid": "71227ff2-7757-4c8a-bcfd-aab538d51b80", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2025-37945", "type": "seen", "source": "https://www.hkcert.org/security-bulletin/debian-linux-kernel-multiple-vulnerabilities_20260506", "content": "", "creation_timestamp": "2026-05-05T20:00:00.000000Z"}, {"uuid": "2a45e28a-d2b2-4dbc-b64e-af1e6eb20e95", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37826", "type": "seen", "source": "https://t.me/cvedetector/24803", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-37826 - Linux Kernel UFS SCSI Null Pointer Dereference Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2025-37826 \nPublished : May 8, 2025, 7:15 a.m. | 2\u00a0hours, 2\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nscsi: ufs: core: Add NULL check in ufshcd_mcq_compl_pending_transfer()  \n  \nAdd a NULL check for the returned hwq pointer by ufshcd_mcq_req_to_hwq().  \n  \nThis is similar to the fix in commit 74736103fb41 (\"scsi: ufs: core: Fix  \nufshcd_abort_one racing issue\"). \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"08 May 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-05-08T11:45:01.000000Z"}, {"uuid": "d9a4f55f-c614-4b9d-b35d-0d72abca093a", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37818", "type": "seen", "source": "https://t.me/cvedetector/24804", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-37818 - LoongArch Linux Kernel Invalid PMD Pointer Dereference Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2025-37818 \nPublished : May 8, 2025, 7:15 a.m. | 2\u00a0hours, 2\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nLoongArch: Return NULL from huge_pte_offset() for invalid PMD  \n  \nLoongArch's huge_pte_offset() currently returns a pointer to a PMD slot  \neven if the underlying entry points to invalid_pte_table (indicating no  \nmapping). Callers like smaps_hugetlb_range() fetch this invalid entry  \nvalue (the address of invalid_pte_table) via this pointer.  \n  \nThe generic is_swap_pte() check then incorrectly identifies this address  \nas a swap entry on LoongArch, because it satisfies the \"!pte_present()  \n&& !pte_none()\" conditions. This misinterpretation, combined with a  \ncoincidental match by is_migration_entry() on the address bits, leads to  \nkernel crashes in pfn_swap_entry_to_page().  \n  \nFix this at the architecture level by modifying huge_pte_offset() to  \ncheck the PMD entry's content using pmd_none() before returning. If the  \nentry is invalid (i.e., it points to invalid_pte_table), return NULL  \ninstead of the pointer to the slot. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"08 May 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-05-08T11:45:01.000000Z"}, {"uuid": "dfc322c2-2ac0-4765-8027-4994b19b2236", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37834", "type": "published-proof-of-concept", "source": "https://t.me/cvedetector/24791", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-37834 - Linux Kernel: Dirty Swapcache Page Reclamation Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2025-37834 \nPublished : May 8, 2025, 7:15 a.m. | 2\u00a0hours, 2\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nmm/vmscan: don't try to reclaim hwpoison folio  \n  \nSyzkaller reports a bug as follows:  \n  \nInjecting memory failure for pfn 0x18b00e at process virtual address 0x20ffd000  \nMemory failure: 0x18b00e: dirty swapcache page still referenced by 2 users  \nMemory failure: 0x18b00e: recovery action for dirty swapcache page: Failed  \npage: refcount:2 mapcount:0 mapping:0000000000000000 index:0x20ffd pfn:0x18b00e  \nmemcg:ffff0000dd6d9000  \nanon flags: 0x5ffffe00482011(locked|dirty|arch_1|swapbacked|hwpoison|node=0|zone=2|lastcpupid=0xfffff)  \nraw: 005ffffe00482011 dead000000000100 dead000000000122 ffff0000e232a7c9  \nraw: 0000000000020ffd 0000000000000000 00000002ffffffff ffff0000dd6d9000  \npage dumped because: VM_BUG_ON_FOLIO(!folio_test_uptodate(folio))  \n------------[ cut here ]------------  \nkernel BUG at mm/swap_state.c:184!  \nInternal error: Oops - BUG: 00000000f2000800 [#1] SMP  \nModules linked in:  \nCPU: 0 PID: 60 Comm: kswapd0 Not tainted 6.6.0-gcb097e7de84e #3  \nHardware name: linux,dummy-virt (DT)  \npstate: 80400005 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)  \npc : add_to_swap+0xbc/0x158  \nlr : add_to_swap+0xbc/0x158  \nsp : ffff800087f37340  \nx29: ffff800087f37340 x28: fffffc00052c0380 x27: ffff800087f37780  \nx26: ffff800087f37490 x25: ffff800087f37c78 x24: ffff800087f377a0  \nx23: ffff800087f37c50 x22: 0000000000000000 x21: fffffc00052c03b4  \nx20: 0000000000000000 x19: fffffc00052c0380 x18: 0000000000000000  \nx17: 296f696c6f662865 x16: 7461646f7470755f x15: 747365745f6f696c  \nx14: 6f6621284f494c4f x13: 0000000000000001 x12: ffff600036d8b97b  \nx11: 1fffe00036d8b97a x10: ffff600036d8b97a x9 : dfff800000000000  \nx8 : 00009fffc9274686 x7 : ffff0001b6c5cbd3 x6 : 0000000000000001  \nx5 : ffff0000c25896c0 x4 : 0000000000000000 x3 : 0000000000000000  \nx2 : 0000000000000000 x1 : ffff0000c25896c0 x0 : 0000000000000000  \nCall trace:  \n add_to_swap+0xbc/0x158  \n shrink_folio_list+0x12ac/0x2648  \n shrink_inactive_list+0x318/0x948  \n shrink_lruvec+0x450/0x720  \n shrink_node_memcgs+0x280/0x4a8  \n shrink_node+0x128/0x978  \n balance_pgdat+0x4f0/0xb20  \n kswapd+0x228/0x438  \n kthread+0x214/0x230  \n ret_from_fork+0x10/0x20  \n  \nI can reproduce this issue with the following steps:  \n  \n1) When a dirty swapcache page is isolated by reclaim process and the  \n   page isn't locked, inject memory failure for the page.   \n   me_swapcache_dirty() clears uptodate flag and tries to delete from lru,  \n   but fails.  Reclaim process will put the hwpoisoned page back to lru.  \n  \n2) The process that maps the hwpoisoned page exits, the page is deleted  \n   the page will never be freed and will be in the lru forever.  \n  \n3) If we trigger a reclaim again and tries to reclaim the page,  \n   add_to_swap() will trigger VM_BUG_ON_FOLIO due to the uptodate flag is  \n   cleared.  \n  \nTo fix it, skip the hwpoisoned page in shrink_folio_list().  Besides, the  \nhwpoison folio may not be unmapped by hwpoison_user_mappings() yet, unmap  \nit in shrink_folio_list(), otherwise the folio will fail to be unmaped by  \nhwpoison_user_mappings() since the folio isn't in lru list. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"08 May 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-05-08T11:44:45.000000Z"}, {"uuid": "b8116048-1f80-4d12-91e9-cb2d5e3f87c6", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37832", "type": "seen", "source": "https://t.me/cvedetector/24795", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-37832 - Allwinner cpufreq sun50i Linux Kernel Out-of-Bounds Read Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2025-37832 \nPublished : May 8, 2025, 7:15 a.m. | 2\u00a0hours, 2\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \ncpufreq: sun50i: prevent out-of-bounds access  \n  \nA KASAN enabled kernel reports an out-of-bounds access when handling the  \nnvmem cell in the sun50i cpufreq driver:  \n==================================================================  \nBUG: KASAN: slab-out-of-bounds in sun50i_cpufreq_nvmem_probe+0x180/0x3d4  \nRead of size 4 at addr ffff000006bf31e0 by task kworker/u16:1/38  \n  \nThis is because the DT specifies the nvmem cell as covering only two  \nbytes, but we use a u32 pointer to read the value. DTs for other SoCs  \nindeed specify 4 bytes, so we cannot just shorten the variable to a u16.  \n  \nFortunately nvmem_cell_read() allows to return the length of the nvmem  \ncell, in bytes, so we can use that information to only access the valid  \nportion of the data.  \nTo cover multiple cell sizes, use memcpy() to copy the information into a  \nzeroed u32 buffer, then also make sure we always read the data in little  \nendian fashion, as this is how the data is stored in the SID efuses. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"08 May 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-05-08T11:44:51.000000Z"}, {"uuid": "7c6747ea-d47a-42d6-bb21-89778e754918", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37833", "type": "seen", "source": "https://t.me/cvedetector/24796", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-37833 - Linux Niu PCI-MSIX Touch Entry Data Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2025-37833 \nPublished : May 8, 2025, 7:15 a.m. | 2\u00a0hours, 2\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nnet/niu: Niu requires MSIX ENTRY_DATA fields touch before entry reads  \n  \nFix niu_try_msix() to not cause a fatal trap on sparc systems.  \n  \nSet PCI_DEV_FLAGS_MSIX_TOUCH_ENTRY_DATA_FIRST on the struct pci_dev to  \nwork around a bug in the hardware or firmware.  \n  \nFor each vector entry in the msix table, niu chips will cause a fatal  \ntrap if any registers in that entry are read before that entries'  \nENTRY_DATA register is written to. Testing indicates writes to other  \nregisters are not sufficient to prevent the fatal trap, however the value  \ndoes not appear to matter. This only needs to happen once after power up,  \nso simply rebooting into a kernel lacking this fix will NOT cause the  \ntrap.  \n  \nNON-RESUMABLE ERROR: Reporting on cpu 64  \nNON-RESUMABLE ERROR: TPC [0x00000000005f6900]   \nNON-RESUMABLE ERROR: RAW [4010000000000016:00000e37f93e32ff:0000000202000080:ffffffffffffffff  \nNON-RESUMABLE ERROR:      0000000800000000:0000000000000000:0000000000000000:0000000000000000]  \nNON-RESUMABLE ERROR: handle [0x4010000000000016] stick [0x00000e37f93e32ff]  \nNON-RESUMABLE ERROR: type [precise nonresumable]  \nNON-RESUMABLE ERROR: attrs [0x02000080] < ASI sp-faulted priv >  \nNON-RESUMABLE ERROR: raddr [0xffffffffffffffff]  \nNON-RESUMABLE ERROR: insn effective address [0x000000c50020000c]  \nNON-RESUMABLE ERROR: size [0x8]  \nNON-RESUMABLE ERROR: asi [0x00]  \nCPU: 64 UID: 0 PID: 745 Comm: kworker/64:1 Not tainted 6.11.5 #63  \nWorkqueue: events work_for_cpu_fn  \nTSTATE: 0000000011001602 TPC: 00000000005f6900 TNPC: 00000000005f6904 Y: 00000000    Not tainted  \nTPC:   \ng0: 00000000000002e9 g1: 000000000000000c g2: 000000c50020000c g3: 0000000000000100  \ng4: ffff8000470307c0 g5: ffff800fec5be000 g6: ffff800047a08000 g7: 0000000000000000  \no0: ffff800014feb000 o1: ffff800047a0b620 o2: 0000000000000011 o3: ffff800047a0b620  \no4: 0000000000000080 o5: 0000000000000011 sp: ffff800047a0ad51 ret_pc: 00000000005f7128  \nRPC: <__pci_enable_msix_range+0x3ccl0: 000000000000000d l1: 000000000000c01f l2: ffff800014feb0a8 l3: 0000000000000020  \nl4: 000000000000c000 l5: 0000000000000001 l6: 0000000020000000 l7: ffff800047a0b734  \ni0: ffff800014feb000 i1: ffff800047a0b730 i2: 0000000000000001 i3: 000000000000000d  \ni4: 0000000000000000 i5: 0000000000000000 i6: ffff800047a0ae81 i7: 00000000101888b0  \nI7:   \nCall Trace:  \n[<00000000101888b0] niu_try_msix.constprop.0+0xc0/0x130 [niu]  \n[<000000001018f840] niu_get_invariants+0x183c/0x207c [niu]  \n[<00000000101902fc] niu_pci_init_one+0x27c/0x2fc [niu]  \n[<00000000005ef3e4] local_pci_probe+0x28/0x74  \n[<0000000000469240] work_for_cpu_fn+0x8/0x1c  \n[<000000000046b008] process_scheduled_works+0x144/0x210  \n[<000000000046b518] worker_thread+0x13c/0x1c0  \n[<00000000004710e0] kthread+0xb8/0xc8  \n[<00000000004060c8] ret_from_fork+0x1c/0x2c  \n[<0000000000000000] 0x0  \nKernel panic - not syncing: Non-resumable error. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"08 May 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-05-08T11:44:52.000000Z"}, {"uuid": "fc94ef0e-8b1a-4339-ab66-f9f3e8a4cff2", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37821", "type": "seen", "source": "https://t.me/cvedetector/24798", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-37821 - Linux Kernel Sched Eevdf Crash\", \n  \"Content\": \"CVE ID : CVE-2025-37821 \nPublished : May 8, 2025, 7:15 a.m. | 2\u00a0hours, 2\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nsched/eevdf: Fix se->slice being set to U64_MAX and resulting crash  \n  \nThere is a code path in dequeue_entities() that can set the slice of a  \nsched_entity to U64_MAX, which sometimes results in a crash.  \n  \nThe offending case is when dequeue_entities() is called to dequeue a  \ndelayed group entity, and then the entity's parent's dequeue is delayed.  \nIn that case:  \n  \n1. In the if (entity_is_task(se)) else block at the beginning of  \n   dequeue_entities(), slice is set to  \n   cfs_rq_min_slice(group_cfs_rq(se)). If the entity was delayed, then  \n   it has no queued tasks, so cfs_rq_min_slice() returns U64_MAX.  \n2. The first for_each_sched_entity() loop dequeues the entity.  \n3. If the entity was its parent's only child, then the next iteration  \n   tries to dequeue the parent.  \n4. If the parent's dequeue needs to be delayed, then it breaks from the  \n   first for_each_sched_entity() loop _without updating slice_.  \n5. The second for_each_sched_entity() loop sets the parent's ->slice to  \n   the saved slice, which is still U64_MAX.  \n  \nThis throws off subsequent calculations with potentially catastrophic  \nresults. A manifestation we saw in production was:  \n  \n6. In update_entity_lag(), se->slice is used to calculate limit, which  \n   ends up as a huge negative number.  \n7. limit is used in se->vlag = clamp(vlag, -limit, limit). Because limit  \n   is negative, vlag > limit, so se->vlag is set to the same huge  \n   negative number.  \n8. In place_entity(), se->vlag is scaled, which overflows and results in  \n   another huge (positive or negative) number.  \n9. The adjusted lag is subtracted from se->vruntime, which increases or  \n   decreases se->vruntime by a huge number.  \n10. pick_eevdf() calls entity_eligible()/vruntime_eligible(), which  \n    incorrectly returns false because the vruntime is so far from the  \n    other vruntimes on the queue, causing the  \n    (vruntime - cfs_rq->min_vruntime) * load calulation to overflow.  \n11. Nothing appears to be eligible, so pick_eevdf() returns NULL.  \n12. pick_next_entity() tries to dereference the return value of  \n    pick_eevdf() and crashes.  \n  \nDumping the cfs_rq states from the core dumps with drgn showed tell-tale  \nhuge vruntime ranges and bogus vlag values, and I also traced se->slice  \nbeing set to U64_MAX on live systems (which was usually \"benign\" since  \nthe rest of the runqueue needed to be in a particular state to crash).  \n  \nFix it in dequeue_entities() by always setting slice from the first  \nnon-empty cfs_rq. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"08 May 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-05-08T11:44:53.000000Z"}, {"uuid": "7df2eb40-4bbe-4123-ba03-064428c171b2", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37822", "type": "seen", "source": "https://t.me/cvedetector/24799", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-37822 - RISC-V Linux Kernel Uprobes Fence Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2025-37822 \nPublished : May 8, 2025, 7:15 a.m. | 2\u00a0hours, 2\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nriscv: uprobes: Add missing fence.i after building the XOL buffer  \n  \nThe XOL (execute out-of-line) buffer is used to single-step the  \nreplaced instruction(s) for uprobes. The RISC-V port was missing a  \nproper fence.i (i$ flushing) after constructing the XOL buffer, which  \ncan result in incorrect execution of stale/broken instructions.  \n  \nThis was found running the BPF selftests \"test_progs:  \nuprobe_autoattach, attach_probe\" on the Spacemit K1/X60, where the  \nuprobes tests randomly blew up. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"08 May 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-05-08T11:44:54.000000Z"}, {"uuid": "a28dc8bd-5f26-417f-b1fe-4d98cffc0e42", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37825", "type": "seen", "source": "https://t.me/cvedetector/24802", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-37825 - \"Nvidia Nvmet Out-of-Bounds Access Vulnerability\"\", \n  \"Content\": \"CVE ID : CVE-2025-37825 \nPublished : May 8, 2025, 7:15 a.m. | 2\u00a0hours, 2\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nnvmet: fix out-of-bounds access in nvmet_enable_port  \n  \nWhen trying to enable a port that has no transport configured yet,  \nnvmet_enable_port() uses NVMF_TRTYPE_MAX (255) to query the transports  \narray, causing an out-of-bounds access:  \n  \n[  106.058694] BUG: KASAN: global-out-of-bounds in nvmet_enable_port+0x42/0x1da  \n[  106.058719] Read of size 8 at addr ffffffff89dafa58 by task ln/632  \n[...]  \n[  106.076026] nvmet: transport type 255 not supported  \n  \nSince commit 200adac75888, NVMF_TRTYPE_MAX is the default state as configured by  \nnvmet_ports_make().  \nAvoid this by checking for NVMF_TRTYPE_MAX before proceeding. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"08 May 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-05-08T11:45:00.000000Z"}, {"uuid": "ba0426ff-6d89-44e5-88ca-f0f27112bd2f", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37828", "type": "seen", "source": "https://t.me/cvedetector/24790", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-37828 - \"ufs Linux Kernel NULL Pointer Dereference Vulnerability\"\", \n  \"Content\": \"CVE ID : CVE-2025-37828 \nPublished : May 8, 2025, 7:15 a.m. | 2\u00a0hours, 2\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nscsi: ufs: mcq: Add NULL check in ufshcd_mcq_abort()  \n  \nA race can occur between the MCQ completion path and the abort handler:  \nonce a request completes, __blk_mq_free_request() sets rq->mq_hctx to  \nNULL, meaning the subsequent ufshcd_mcq_req_to_hwq() call in  \nufshcd_mcq_abort() can return a NULL pointer. If this NULL pointer is  \ndereferenced, the kernel will crash.  \n  \nAdd a NULL check for the returned hwq pointer. If hwq is NULL, log an  \nerror and return FAILED, preventing a potential NULL-pointer  \ndereference.  As suggested by Bart, the ufshcd_cmd_inflight() check is  \nremoved.  \n  \nThis is similar to the fix in commit 74736103fb41 (\"scsi: ufs: core: Fix  \nufshcd_abort_one racing issue\").  \n  \nThis is found by our static analysis tool KNighter. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"08 May 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-05-08T11:44:44.000000Z"}, {"uuid": "fbb3c9bc-b14b-4b47-a23e-3bf61af4603b", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37831", "type": "seen", "source": "https://t.me/cvedetector/24794", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-37831 - Apple Soc cpufreq Null Pointer Dereference\", \n  \"Content\": \"CVE ID : CVE-2025-37831 \nPublished : May 8, 2025, 7:15 a.m. | 2\u00a0hours, 2\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \ncpufreq: apple-soc: Fix null-ptr-deref in apple_soc_cpufreq_get_rate()  \n  \ncpufreq_cpu_get_raw() can return NULL when the target CPU is not present  \nin the policy->cpus mask. apple_soc_cpufreq_get_rate() does not check  \nfor this case, which results in a NULL pointer dereference. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"08 May 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-05-08T11:44:47.000000Z"}, {"uuid": "2c2bac23-cdd9-4896-a5dc-e7183bb25572", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37824", "type": "seen", "source": "https://t.me/cvedetector/24800", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-37824 - Linux Kernel Tipc NULL Pointer Dereference Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2025-37824 \nPublished : May 8, 2025, 7:15 a.m. | 2\u00a0hours, 2\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \ntipc: fix NULL pointer dereference in tipc_mon_reinit_self()  \n  \nsyzbot reported:  \n  \ntipc: Node number set to 1055423674  \nOops: general protection fault, probably for non-canonical address 0xdffffc0000000000: 0000 [#1] SMP KASAN NOPTI  \nKASAN: null-ptr-deref in range [0x0000000000000000-0x0000000000000007]  \nCPU: 3 UID: 0 PID: 6017 Comm: kworker/3:5 Not tainted 6.15.0-rc1-syzkaller-00246-g900241a5cc15 #0 PREEMPT(full)  \nHardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2~bpo12+1 04/01/2014  \nWorkqueue: events tipc_net_finalize_work  \nRIP: 0010:tipc_mon_reinit_self+0x11c/0x210 net/tipc/monitor.c:719  \n...  \nRSP: 0018:ffffc9000356fb68 EFLAGS: 00010246  \nRAX: 0000000000000000 RBX: 0000000000000000 RCX: 000000003ee87cba  \nRDX: 0000000000000000 RSI: ffffffff8dbc56a7 RDI: ffff88804c2cc010  \nRBP: dffffc0000000000 R08: 0000000000000001 R09: 0000000000000000  \nR10: 0000000000000001 R11: 0000000000000000 R12: 0000000000000007  \nR13: fffffbfff2111097 R14: ffff88804ead8000 R15: ffff88804ead9010  \nFS:  0000000000000000(0000) GS:ffff888097ab9000(0000) knlGS:0000000000000000  \nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033  \nCR2: 00000000f720eb00 CR3: 000000000e182000 CR4: 0000000000352ef0  \nDR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000  \nDR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400  \nCall Trace:  \n   \n tipc_net_finalize+0x10b/0x180 net/tipc/net.c:140  \n process_one_work+0x9cc/0x1b70 kernel/workqueue.c:3238  \n process_scheduled_works kernel/workqueue.c:3319 [inline]  \n worker_thread+0x6c8/0xf10 kernel/workqueue.c:3400  \n kthread+0x3c2/0x780 kernel/kthread.c:464  \n ret_from_fork+0x45/0x80 arch/x86/kernel/process.c:153  \n ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245  \n   \n...  \nRIP: 0010:tipc_mon_reinit_self+0x11c/0x210 net/tipc/monitor.c:719  \n...  \nRSP: 0018:ffffc9000356fb68 EFLAGS: 00010246  \nRAX: 0000000000000000 RBX: 0000000000000000 RCX: 000000003ee87cba  \nRDX: 0000000000000000 RSI: ffffffff8dbc56a7 RDI: ffff88804c2cc010  \nRBP: dffffc0000000000 R08: 0000000000000001 R09: 0000000000000000  \nR10: 0000000000000001 R11: 0000000000000000 R12: 0000000000000007  \nR13: fffffbfff2111097 R14: ffff88804ead8000 R15: ffff88804ead9010  \nFS:  0000000000000000(0000) GS:ffff888097ab9000(0000) knlGS:0000000000000000  \nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033  \nCR2: 00000000f720eb00 CR3: 000000000e182000 CR4: 0000000000352ef0  \nDR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000  \nDR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400  \n  \nThere is a racing condition between workqueue created when enabling  \nbearer and another thread created when disabling bearer right after  \nthat as follow:  \n  \nenabling_bearer                          | disabling_bearer  \n---------------                          | ----------------  \ntipc_disc_timeout()                      |  \n{                                        | bearer_disable()  \n ...                                     | {  \n schedule_work(&tn->work);               |  tipc_mon_delete()  \n ...                                     |  {  \n}                                        |   ...  \n                                         |   write_lock_bh(&mon->lock);  \n                                         |   mon->self = NULL;  \n                                         |   write_unlock_bh(&mon->lock);  \n                                         |   ...  \n                                         |  }  \ntipc_net_finalize_work()                 | }  \n{                                        |  \n ...                                     |  \n tipc_net_finalize()                     |  \n {                                       |  \n  ...                     [...]", "creation_timestamp": "2025-05-08T11:44:58.000000Z"}, {"uuid": "584f0ef1-9edd-4c52-a166-c91880fd3026", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37820", "type": "seen", "source": "https://t.me/cvedetector/24805", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-37820 - Xen-netfront NULL Pointer Dereference and Memory Leak Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2025-37820 \nPublished : May 8, 2025, 7:15 a.m. | 2\u00a0hours, 2\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nxen-netfront: handle NULL returned by xdp_convert_buff_to_frame()  \n  \nThe function xdp_convert_buff_to_frame() may return NULL if it fails  \nto correctly convert the XDP buffer into an XDP frame due to memory  \nconstraints, internal errors, or invalid data. Failing to check for NULL  \nmay lead to a NULL pointer dereference if the result is used later in  \nprocessing, potentially causing crashes, data corruption, or undefined  \nbehavior.  \n  \nOn XDP redirect failure, the associated page must be released explicitly  \nif it was previously retained via get_page(). Failing to do so may result  \nin a memory leak, as the pages reference count is not decremented. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"08 May 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-05-08T11:45:05.000000Z"}, {"uuid": "2ebe0f7a-be4a-4698-982a-1f4e74932c02", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37819", "type": "published-proof-of-concept", "source": "https://t.me/cvedetector/24806", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-37819 - \"Linux Kernel GICv2m Use After Free Vulnerability in irqchip\"\", \n  \"Content\": \"CVE ID : CVE-2025-37819 \nPublished : May 8, 2025, 7:15 a.m. | 2\u00a0hours, 2\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nirqchip/gic-v2m: Prevent use after free of gicv2m_get_fwnode()  \n  \nWith ACPI in place, gicv2m_get_fwnode() is registered with the pci  \nsubsystem as pci_msi_get_fwnode_cb(), which may get invoked at runtime  \nduring a PCI host bridge probe. But, the call back is wrongly marked as  \n__init, causing it to be freed, while being registered with the PCI  \nsubsystem and could trigger:  \n  \n Unable to handle kernel paging request at virtual address ffff8000816c0400  \n  gicv2m_get_fwnode+0x0/0x58 (P)  \n  pci_set_bus_msi_domain+0x74/0x88  \n  pci_register_host_bridge+0x194/0x548  \n  \nThis is easily reproducible on a Juno board with ACPI boot.  \n  \nRetain the function for later use. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"08 May 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-05-08T11:45:06.000000Z"}, {"uuid": "c544b0b3-ae46-4d5e-93fd-9b82f683ae0b", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37827", "type": "seen", "source": "https://t.me/cvedetector/24807", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-37827 - Here is a title for the vulnerability: \"btrfs: RAID1 Profile Write Pointer Offset Mismatch NULL Pointer Dereference\"\", \n  \"Content\": \"CVE ID : CVE-2025-37827 \nPublished : May 8, 2025, 7:15 a.m. | 2\u00a0hours, 2\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nbtrfs: zoned: return EIO on RAID1 block group write pointer mismatch  \n  \nThere was a bug report about a NULL pointer dereference in  \n__btrfs_add_free_space_zoned() that ultimately happens because a  \nconversion from the default metadata profile DUP to a RAID1 profile on two  \ndisks.  \n  \nThe stack trace has the following signature:  \n  \n  BTRFS error (device sdc): zoned: write pointer offset mismatch of zones in raid1 profile  \n  BUG: kernel NULL pointer dereference, address: 0000000000000058  \n  #PF: supervisor read access in kernel mode  \n  #PF: error_code(0x0000) - not-present page  \n  PGD 0 P4D 0  \n  Oops: Oops: 0000 [#1] PREEMPT SMP NOPTI  \n  RIP: 0010:__btrfs_add_free_space_zoned.isra.0+0x61/0x1a0  \n  RSP: 0018:ffffa236b6f3f6d0 EFLAGS: 00010246  \n  RAX: 0000000000000000 RBX: ffff96c8132f3400 RCX: 0000000000000001  \n  RDX: 0000000010000000 RSI: 0000000000000000 RDI: ffff96c8132f3410  \n  RBP: 0000000010000000 R08: 0000000000000003 R09: 0000000000000000  \n  R10: 0000000000000000 R11: 00000000ffffffff R12: 0000000000000000  \n  R13: ffff96c758f65a40 R14: 0000000000000001 R15: 000011aac0000000  \n  FS: 00007fdab1cb2900(0000) GS:ffff96e60ca00000(0000) knlGS:0000000000000000  \n  CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033  \n  CR2: 0000000000000058 CR3: 00000001a05ae000 CR4: 0000000000350ef0  \n  Call Trace:  \n    \n  ? __die_body.cold+0x19/0x27  \n  ? page_fault_oops+0x15c/0x2f0  \n  ? exc_page_fault+0x7e/0x180  \n  ? asm_exc_page_fault+0x26/0x30  \n  ? __btrfs_add_free_space_zoned.isra.0+0x61/0x1a0  \n  btrfs_add_free_space_async_trimmed+0x34/0x40  \n  btrfs_add_new_free_space+0x107/0x120  \n  btrfs_make_block_group+0x104/0x2b0  \n  btrfs_create_chunk+0x977/0xf20  \n  btrfs_chunk_alloc+0x174/0x510  \n  ? srso_return_thunk+0x5/0x5f  \n  btrfs_inc_block_group_ro+0x1b1/0x230  \n  btrfs_relocate_block_group+0x9e/0x410  \n  btrfs_relocate_chunk+0x3f/0x130  \n  btrfs_balance+0x8ac/0x12b0  \n  ? srso_return_thunk+0x5/0x5f  \n  ? srso_return_thunk+0x5/0x5f  \n  ? __kmalloc_cache_noprof+0x14c/0x3e0  \n  btrfs_ioctl+0x2686/0x2a80  \n  ? srso_return_thunk+0x5/0x5f  \n  ? ioctl_has_perm.constprop.0.isra.0+0xd2/0x120  \n  __x64_sys_ioctl+0x97/0xc0  \n  do_syscall_64+0x82/0x160  \n  ? srso_return_thunk+0x5/0x5f  \n  ? __memcg_slab_free_hook+0x11a/0x170  \n  ? srso_return_thunk+0x5/0x5f  \n  ? kmem_cache_free+0x3f0/0x450  \n  ? srso_return_thunk+0x5/0x5f  \n  ? srso_return_thunk+0x5/0x5f  \n  ? syscall_exit_to_user_mode+0x10/0x210  \n  ? srso_return_thunk+0x5/0x5f  \n  ? do_syscall_64+0x8e/0x160  \n  ? sysfs_emit+0xaf/0xc0  \n  ? srso_return_thunk+0x5/0x5f  \n  ? srso_return_thunk+0x5/0x5f  \n  ? seq_read_iter+0x207/0x460  \n  ? srso_return_thunk+0x5/0x5f  \n  ? vfs_read+0x29c/0x370  \n  ? srso_return_thunk+0x5/0x5f  \n  ? srso_return_thunk+0x5/0x5f  \n  ? syscall_exit_to_user_mode+0x10/0x210  \n  ? srso_return_thunk+0x5/0x5f  \n  ? do_syscall_64+0x8e/0x160  \n  ? srso_return_thunk+0x5/0x5f  \n  ? exc_page_fault+0x7e/0x180  \n  entry_SYSCALL_64_after_hwframe+0x76/0x7e  \n  RIP: 0033:0x7fdab1e0ca6d  \n  RSP: 002b:00007ffeb2b60c80 EFLAGS: 00000246 ORIG_RAX: 0000000000000010  \n  RAX: ffffffffffffffda RBX: 0000000000000003 RCX: 00007fdab1e0ca6d  \n  RDX: 00007ffeb2b60d80 RSI: 00000000c4009420 RDI: 0000000000000003  \n  RBP: 00007ffeb2b60cd0 R08: 0000000000000000 R09: 0000000000000013  \n  R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000  \n  R13: 00007ffeb2b6343b R14: 00007ffeb2b60d80 R15: 0000000000000001  \n    \n  CR2: 0000000000000058  \n  ---[ end trace 0000000000000000 ]---  \n  \nThe 1st line is the most interesting here:  \n  \n BTRFS error (device sdc): zoned: write pointer offset mismatch of zones in raid1 profile  \n  \nWhen a RAID1 block-group is created and a writ[...]", "creation_timestamp": "2025-05-08T11:45:07.000000Z"}, {"uuid": "b1226fb9-353b-44e7-ad43-bb8661ba1675", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37823", "type": "seen", "source": "https://t.me/cvedetector/24809", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-37823 - Linux Kernel Net-Sched HFSC Use-After-Free Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2025-37823 \nPublished : May 8, 2025, 7:15 a.m. | 2\u00a0hours, 2\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nnet_sched: hfsc: Fix a potential UAF in hfsc_dequeue() too  \n  \nSimilarly to the previous patch, we need to safe guard hfsc_dequeue()  \ntoo. But for this one, we don't have a reliable reproducer. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"08 May 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-05-08T11:45:09.000000Z"}, {"uuid": "66b76c01-e516-4954-9ced-3000f64c7bc3", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37812", "type": "seen", "source": "https://t.me/cvedetector/24810", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-37812 - Linux Kernel USB cdns3 NCM Gadget Deadlock\", \n  \"Content\": \"CVE ID : CVE-2025-37812 \nPublished : May 8, 2025, 7:15 a.m. | 2\u00a0hours, 2\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nusb: cdns3: Fix deadlock when using NCM gadget  \n  \nThe cdns3 driver has the same NCM deadlock as fixed in cdnsp by commit  \n58f2fcb3a845 (\"usb: cdnsp: Fix deadlock issue during using NCM gadget\").  \n  \nUnder PREEMPT_RT the deadlock can be readily triggered by heavy network  \ntraffic, for example using \"iperf --bidir\" over NCM ethernet link.  \n  \nThe deadlock occurs because the threaded interrupt handler gets  \npreempted by a softirq, but both are protected by the same spinlock.  \nPrevent deadlock by disabling softirq during threaded irq handler. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"08 May 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-05-08T11:45:45.000000Z"}, {"uuid": "39a1bd71-3da9-4670-ab5e-85592dda02a0", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37811", "type": "seen", "source": "https://t.me/cvedetector/24811", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-37811 - \"Qualcomm Chipidea USB Driver Null Pointer Dereference\"\", \n  \"Content\": \"CVE ID : CVE-2025-37811 \nPublished : May 8, 2025, 7:15 a.m. | 2\u00a0hours, 2\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nusb: chipidea: ci_hdrc_imx: fix usbmisc handling  \n  \nusbmisc is an optional device property so it is totally valid for the  \ncorresponding data->usbmisc_data to have a NULL value.  \n  \nCheck that before dereferencing the pointer.  \n  \nFound by Linux Verification Center (linuxtesting.org) with Svace static  \nanalysis tool. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"08 May 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-05-08T11:45:46.000000Z"}, {"uuid": "e28dc54e-6884-4379-b7ba-4a407c521ada", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3758", "type": "seen", "source": "https://t.me/cvedetector/24812", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-3758 - WF2220 Information Disclosure in Western Digital Router\", \n  \"Content\": \"CVE ID : CVE-2025-3758 \nPublished : May 8, 2025, 10:15 a.m. | 1\u00a0hour, 3\u00a0minutes ago \nDescription : WF2220 exposes endpoint\u00a0/cgi-bin-igd/netcore_get.cgi\u00a0that returns configuration of the device to unauthorized users. Returned configuration includes cleartext password.  \nThe vendor was contacted early about this disclosure but did not respond in any way. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"08 May 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-05-08T13:26:00.000000Z"}, {"uuid": "e9221614-3d56-4ef5-8a35-41410c55a907", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3759", "type": "seen", "source": "https://t.me/cvedetector/24813", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-3759 - Netgear IGD Unauthenticated Configuration Change Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2025-3759 \nPublished : May 8, 2025, 10:15 a.m. | 1\u00a0hour, 3\u00a0minutes ago \nDescription : Endpoint\u00a0/cgi-bin-igd/netcore_set.cgi\u00a0which is used for changing device configuration is accessible without authentication. This poses a significant security threat allowing for e.g: administrator account hijacking or AP password changing.  \nThe vendor was contacted early about this disclosure but did not respond in any way. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"08 May 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-05-08T13:26:01.000000Z"}, {"uuid": "b7000f87-ae46-487c-8a1c-6d777d3874fa", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3707", "type": "seen", "source": "https://t.me/cvedetector/24312", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-3707 - Sunnet eHDR CTMS SQL Injection\", \n  \"Content\": \"CVE ID : CVE-2025-3707 \nPublished : May 2, 2025, 4:15 a.m. | 33\u00a0minutes ago \nDescription : The eHDR CTMS from Sunnet has a SQL Injection vulnerability, allowing remote attackers with regular privileges to inject arbitrary SQL command to read database contents. \nSeverity: 6.5 | MEDIUM \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"02 May 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-05-02T07:34:35.000000Z"}, {"uuid": "cc953fd5-9fd3-4bb7-aaad-37fea10a1514", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3708", "type": "seen", "source": "https://t.me/cvedetector/24313", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-3708 - Le-Yan Le-Show Medical SQL Injection Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2025-3708 \nPublished : May 2, 2025, 4:15 a.m. | 33\u00a0minutes ago \nDescription : Le-show medical practice management system from Le-yan has a SQL Injection vulnerability, allowing unauthenticated remote attackers to inject arbitrary SQL commands to read, modify, and delete database contents. \nSeverity: 9.8 | CRITICAL \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"02 May 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-05-02T07:34:36.000000Z"}, {"uuid": "1faaf7fa-fb22-49f2-9dfe-9f409799af3b", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3709", "type": "seen", "source": "https://t.me/cvedetector/24314", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-3709 - Agentflow from Flowring Technology Account Lockout Bypass Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2025-3709 \nPublished : May 2, 2025, 4:15 a.m. | 33\u00a0minutes ago \nDescription : Agentflow from Flowring Technology has an Account Lockout Bypass vulnerability, allowing unauthenticated remote attackers to exploit this vulnerability to perform password brute force attack. \nSeverity: 9.8 | CRITICAL \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"02 May 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-05-02T07:34:37.000000Z"}, {"uuid": "272104e0-92a1-4fc3-9df4-3ac3b8c8540a", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3748", "type": "seen", "source": "https://t.me/cvedetector/24315", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-3748 - WordPress Taxonomy Chain Menu Stored Cross-Site Scripting\", \n  \"Content\": \"CVE ID : CVE-2025-3748 \nPublished : May 2, 2025, 4:15 a.m. | 33\u00a0minutes ago \nDescription : The Taxonomy Chain Menu plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's pn_chain_menu shortcode in all versions up to, and including, 1.0.8 due to insufficient input sanitization and output escaping on user supplied attributes. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. \nSeverity: 6.4 | MEDIUM \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"02 May 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-05-02T07:34:38.000000Z"}, {"uuid": "7ba688ed-19a1-4b87-abbf-fbee781c504b", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3746", "type": "seen", "source": "https://t.me/cvedetector/24329", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-3746 - WordPress One Tap Signin Plugin Authentication Bypass\", \n  \"Content\": \"CVE ID : CVE-2025-3746 \nPublished : May 2, 2025, 3:15 a.m. | 1\u00a0hour, 33\u00a0minutes ago \nDescription : The OTP-less one tap Sign in plugin for WordPress is vulnerable to privilege escalation via account takeover in versions 2.0.14 to 2.0.59. This is due to the plugin not properly validating a user's identity prior to updating their details, like email. This makes it possible for unauthenticated attackers to change arbitrary users' email addresses, including administrators, and leverage that to reset the user's password and gain access to their account.  \nAdditionally, the plugin returns authentication cookies in the response, which can be used to access the account directly. \nSeverity: 9.8 | CRITICAL \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"02 May 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-05-02T07:34:58.000000Z"}, {"uuid": "d98afaaa-4fa1-47c0-88e9-623da6cae1a3", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37799", "type": "seen", "source": "https://t.me/cvedetector/24398", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-37799 - vmxnet3 Linux Kernel Malformed Packet Sizing Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2025-37799 \nPublished : May 3, 2025, 12:15 p.m. | 1\u00a0hour, 44\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nvmxnet3: Fix malformed packet sizing in vmxnet3_process_xdp  \n  \nvmxnet3 driver's XDP handling is buggy for packet sizes using ring0 (that  \nis, packet sizes between 128 - 3k bytes).  \n  \nWe noticed MTU-related connectivity issues with Cilium's service load-  \nbalancing in case of vmxnet3 as NIC underneath. A simple curl to a HTTP  \nbackend service where the XDP LB was doing IPIP encap led to overly large  \npacket sizes but only for *some* of the packets (e.g. HTTP GET request)  \nwhile others (e.g. the prior TCP 3WHS) looked completely fine on the wire.  \n  \nIn fact, the pcap recording on the backend node actually revealed that the  \nnode with the XDP LB was leaking uninitialized kernel data onto the wire  \nfor the affected packets, for example, while the packets should have been  \n152 bytes their actual size was 1482 bytes, so the remainder after 152 bytes  \nwas padded with whatever other data was in that page at the time (e.g. we  \nsaw user/payload data from prior processed packets).  \n  \nWe only noticed this through an MTU issue, e.g. when the XDP LB node and  \nthe backend node both had the same MTU (e.g. 1500) then the curl request  \ngot dropped on the backend node's NIC given the packet was too large even  \nthough the IPIP-encapped packet normally would never even come close to  \nthe MTU limit. Lowering the MTU on the XDP LB (e.g. 1480) allowed to let  \nthe curl request succeed (which also indicates that the kernel ignored the  \npadding, and thus the issue wasn't very user-visible).  \n  \nCommit e127ce7699c1 (\"vmxnet3: Fix missing reserved tailroom\") was too eager  \nto also switch xdp_prepare_buff() from rcd->len to rbi->len. It really needs  \nto stick to rcd->len which is the actual packet length from the descriptor.  \nThe latter we also feed into vmxnet3_process_xdp_small(), by the way, and  \nit indicates the correct length needed to initialize the xdp->{data,data_end}  \nparts. For e127ce7699c1 (\"vmxnet3: Fix missing reserved tailroom\") the  \nrelevant part was adapting xdp_init_buff() to address the warning given the  \nxdp_data_hard_end() depends on xdp->frame_sz. With that fixed, traffic on  \nthe wire looks good again. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"03 May 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-05-03T16:12:25.000000Z"}, {"uuid": "6c2c655d-a77e-4594-ac54-5e68c39ef9d9", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3779", "type": "seen", "source": "https://t.me/cvedetector/24393", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-3779 - WordPress Personizely Stored Cross-Site Scripting\", \n  \"Content\": \"CVE ID : CVE-2025-3779 \nPublished : May 3, 2025, 3:15 a.m. | 27\u00a0minutes ago \nDescription : The Personizely plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the \u2018widgetId\u2019 parameter in all versions up to, and including, 0.10 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with Contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. \nSeverity: 6.4 | MEDIUM \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"03 May 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-05-03T06:10:26.000000Z"}, {"uuid": "fe2ed12f-eda7-4418-8fd4-1d6373f53f23", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3782", "type": "seen", "source": "https://t.me/cvedetector/24600", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-3782 - Cision Block Stored Cross-Site Scripting Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2025-3782 \nPublished : May 6, 2025, 10:15 a.m. | 1\u00a0hour, 45\u00a0minutes ago \nDescription : The Cision Block plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the \u2018id\u2019 parameter in all versions up to, and including, 4.3.0 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with Contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. \nSeverity: 6.4 | MEDIUM \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"06 May 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-05-06T14:29:08.000000Z"}, {"uuid": "e52e0236-aa3d-437c-ac02-bf76195d5f37", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37730", "type": "seen", "source": "https://t.me/cvedetector/24643", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-37730 - Logstash SSL Verification MitM Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2025-37730 \nPublished : May 6, 2025, 6:15 p.m. | 1\u00a0hour, 58\u00a0minutes ago \nDescription : Improper certificate validation in Logstash's TCP output could lead to a man-in-the-middle (MitM) attack in \u201cclient\u201d mode, as hostname verification in TCP output was not being performed when the ssl_verification_mode => full was set. \nSeverity: 6.5 | MEDIUM \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"06 May 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-05-06T22:51:07.000000Z"}, {"uuid": "5aa3903e-e958-4450-951d-1624e4ca2f17", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-3766", "type": "seen", "source": "https://t.me/cvedetector/24675", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-3766 - WordPress Login Lockdown & Protection Unauthorized Nonce Access Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2025-3766 \nPublished : May 7, 2025, 5:15 a.m. | 1\u00a0hour, 12\u00a0minutes ago \nDescription : The Login Lockdown & Protection plugin for WordPress is vulnerable to unauthorized nonce access due to a missing capability check on the ajax_run_tool function in all versions up to, and including, 2.11. This makes it possible for authenticated attackers, with Subscriber-level access and above, to obtain a valid nonce that can be used to generate a global unlock key, which can in turn be used to add arbitrary IP address to the plugin allowlist. This can only by exploited on new installations where the site administrator hasn't visited the loginlockdown page yet. \nSeverity: 5.4 | MEDIUM \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"07 May 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-05-07T08:53:11.000000Z"}, {"uuid": "3615c905-1940-45e5-b8ca-c877f07d6a02", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37947", "type": "published-proof-of-concept", "source": "https://t.me/reverseame/5424", "content": "ksmbd - Exploiting CVE-2025-37947 (3/3) #CVE202537947 #ksmbd #OOBWrite #PrivilegeEscalation #LinuxKernel https://blog.doyensec.com/2025/10/08/ksmbd-3.html", "creation_timestamp": "2026-08-01T23:00:04.349609Z"}, {"uuid": "2c80fa02-a516-4bbf-826c-17e35ef9e7a5", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37164", "type": "exploited", "source": "https://t.me/CyberDispatch/525", "content": "Check Point says CVE-2025-37164 is being mass-exploited to spread the RondoDox botnet, with 40,000+ attacks on Jan 7.\n\nThe activity targeted government, finance, and industrial sectors, prompting same-day KEV inclusion.", "creation_timestamp": "2026-08-31T00:00:10.670720Z"}, {"uuid": "516bdca9-0dac-4e45-93bd-bb73f8b147bf", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37947", "type": "published-proof-of-concept", "source": "https://t.me/reverseame/5424", "content": "ksmbd - Exploiting CVE-2025-37947 (3/3) #CVE202537947 #ksmbd #OOBWrite #PrivilegeEscalation #LinuxKernel https://blog.doyensec.com/2025/10/08/ksmbd-3.html", "creation_timestamp": "2026-08-02T00:00:09.209999Z"}, {"uuid": "f03dada5-8148-4ec2-b742-2e232c3f30f3", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2025-37980", "type": "seen", "source": "https://www.hkcert.org/security-bulletin/debian-linux-kernel-multiple-vulnerabilities_20260506", "content": "", "creation_timestamp": "2026-05-05T20:00:00.000000Z"}, {"uuid": "77223cef-d9c6-41d9-9342-372a51c04f20", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37899", "type": "published-proof-of-concept", "source": "https://t.me/hn_best_comments/24847", "content": "Re: I used o3 to find a remote zeroday in the Linux SM...\n        \nA small thing, but I found the author's project-organization practices useful \u2013 creating individual .prompt files for system prompt, background information, and auxiliary instructions [1], and then running it through `llm`.\n\nIt reveals how good LLM use, like any other engineering tool, requires good engineering thinking \u2013 methodical, and oriented around thoughtful specifications that balance design constraints \u2013 for best results.\n\n[1] https://github.com/SeanHeelan/o3_finds_cve-2025-37899\n        \nnxobject, 1 day ago", "creation_timestamp": "2026-08-02T00:01:12.105290Z"}, {"uuid": "100e2dc0-72ca-4a51-b2f9-8b07b5fb4cb8", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37861", "type": "seen", "source": "https://bsky.app/profile/o2cloud.bsky.social/post/3mlbgryvtcx2q", "content": "\ud83d\udd17 CVE : CVE-2024-41073, CVE-2024-53216, CVE-2025-37861, CVE-2025-40252, CVE-2025-68724, CVE-2025-68741, CVE-2025-71238, CVE-2026-23097, CVE-2026-23136, CVE-2026-23191, CVE-2026-23193, CVE-2026-23243, CVE-2026-23270, CVE-2026-23401, CVE-2026-31402, CVE-2026-31419, CVE-2026-31431, CVE-2026-31532", "creation_timestamp": "2026-05-07T14:35:10.309973Z"}, {"uuid": "ecc8e633-b433-421d-9879-048373e1a8d9", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2025-37861", "type": "seen", "source": "https://www.hkcert.org/security-bulletin/redhat-linux-kernel-multiple-vulnerabilities_20260508", "content": "", "creation_timestamp": "2026-05-07T20:00:00.000000Z"}, {"uuid": "1d996174-92eb-44af-a404-e9e2f4aa5e06", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2025-37849", "type": "seen", "source": "https://www.hkcert.org/security-bulletin/ubuntu-linux-kernel-multiple-vulnerabilities_20260511", "content": "", "creation_timestamp": "2026-05-10T18:00:00.000000Z"}, {"uuid": "d0c08498-a17e-4ce9-8736-960853870b82", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2025-37860", "type": "seen", "source": "https://www.hkcert.org/security-bulletin/ubuntu-linux-kernel-multiple-vulnerabilities_20260511", "content": "", "creation_timestamp": "2026-05-10T18:00:00.000000Z"}, {"uuid": "60d49f1e-3047-4d17-8f10-f72093dd2901", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37931", "type": "seen", "source": "https://www.cisa.gov/news-events/ics-advisories/icsa-26-134-10", "content": "View CSAF\n\nSummary\n\nSIMATIC CN 4100 contains multiple vulnerabilities which could potentially lead to a compromise in availability, integrity and confidentiality. Siemens has released a new version for SIMATIC CN 4100 and recommends to update to the latest version.\n\nThe following versions of Siemens SIMATIC are affected:\n\n\n\nSIMATIC CN 4100 vers:intdot/<5.0 \n\n<div class=\"csaf-table\">\n\n\n\n\nCVSS\nVendor\nEquipment\nVulnerabilities\n\n\n\n\nv3 9.6\nSiemens\nSiemens SIMATIC\nNULL Pointer Dereference, Reachable Assertion, Use After Free, Out-of-bounds Write, Integer Overflow or Wraparound, Allocation of Resources Without Limits or Throttling, Out-of-bounds Read, Covert Timing Channel, Stack-based Buffer Overflow, Inefficient Algorithmic Complexity, Missing Release of Memory after Effective Lifetime, Improper Restriction of Operations within the Bounds of a Memory Buffer, Improper Input Validation, Improper Locking, Uncontrolled Recursion, Buffer Access with Incorrect Length Value, Race Condition within a Thread, Missing Synchronization, Use of Uninitialized Resource, Double Free, Missing Release of Resource after Effective Lifetime, Loop with Unreachable Exit Condition ('Infinite Loop'), Improper Update of Reference Count, Improper Control of a Resource Through its Lifetime, Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition'), Unexpected Status Code or Return Value, Divide By Zero, Improper Validation of Specified Index, Position, or Offset in Input, Comparison Using Wrong Factors, Observable Timing Discrepancy, Improper Validation of Syntactic Correctness of Input, Deadlock, Signal Handler Race Condition, Improper Following of Specification by Caller, Improper Check for Dropped Privileges, Transmission of Private Resources into a New Sphere ('Resource Leak'), Improper Resource Shutdown or Release, Improper Access Control, Exposure of Sensitive Information to an Unauthorized Actor, Relative Path Traversal, Improper Neutralization of Escape, Meta, or Control Sequences, Selection of Less-Secure Algorithm During Negotiation ('Algorithm Downgrade'), Uncontrolled Resource Consumption, Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting'), Missing Authentication for Critical Function, Improper Check for Unusual or Exceptional Conditions\n\n\n\n</div>\n\nBackground\n\n\n\nCritical Infrastructure Sectors: Critical Manufacturing\n\nCountries/Areas Deployed: Worldwide\n\nCompany Headquarters Location: Germany\n\n\n\n\nVulnerabilities\n<div class=\"csaf-accordion\">\n\nExpand All +\n<div class=\"csaf-accordion-item\">\n\nCVE-2024-47704\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Check link_res->hpo_dp_link_enc before using it [WHAT & HOW] Functions dp_enable_link_phy and dp_disable_link_phy can pass link_res without initializing hpo_dp_link_enc and it is necessary to check for null before dereferencing. This fixes 2 FORWARD_NULL issues reported by Coverity.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-476 NULL Pointer Dereference\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2024-57924\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: fs: relax assertions on failure to encode file handles Encoding file handles is usually performed by a filesystem >encode_fh() method that may fail for various reasons. The legacy users of exportfs_encode_fh(), namely, nfsd and name_to_handle_at(2) syscall are ready to cope with the possibility of failure to encode a file handle. There are a few other users of exportfs_encode_{fh,fid}() that currently have a WARN_ON() assertion when ->encode_fh() fails. Relax those assertions because they are wrong. The second linked bug report states commit 16aac5ad1fa9 (\"ovl: support encoding non-decodable file handles\") in v6.6 as the regressing commit, but this is not accurate. The aforementioned commit only increases the chances of the assertion and allows triggering the assertion with the reproducer using overlayfs, inotify and drop_caches. Triggering this assertion was always possible with other filesystems and other reasons of ->encode_fh() failures and more particularly, it was also possible with the exact same reproducer using overlayfs that is mounted with options index=on,nfs_export=on also on kernels < v6.6. Therefore, I am not listing the aforementioned commit as a Fixes commit. Backport hint: this patch will have a trivial conflict applying to v6.6.y, and other trivial conflicts applying to stable kernels < v6.6.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-617 Reachable Assertion\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2024-58240\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: tls: separate no-async decryption request handling from async If we're not doing async, the handling is much simpler. There's no reference counting, we just need to wait for the completion to wake us up and return its result. We should preferably also use a separate crypto_wait. I'm not seeing a UAF as I did in the past, I think aec7961916f3 (\"tls: fix race between async notify and socket close\") took care of it. This will make the next fix easier.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-416 Use After Free\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n7.3\nHIGH\nCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-6021\n<div class=\"csaf-accordion-content\">\n\nA flaw was found in libxml2's xmlBuildQName function, where integer overflows in buffer size calculations can lead to a stack-based buffer overflow. This issue can result in memory corruption or a denial of service when processing crafted input.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-787 Out-of-bounds Write\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n7.5\nHIGH\nCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-6052\n<div class=\"csaf-accordion-content\">\n\nA flaw was found in how GLib\u2019s GString manages memory when adding data to strings. If a string is already very large, combining it with more input can cause a hidden overflow in the size calculation. This makes the system think it has enough memory when it doesn\u2019t. As a result, data may be written past the end of the allocated memory, leading to crashes or memory corruption.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-190 Integer Overflow or Wraparound\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n3.7\nLOW\nCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-7425\n<div class=\"csaf-accordion-content\">\n\nA flaw was found in libxslt where the attribute type, atype, flags are modified in a way that corrupts internal memory management. When XSLT functions, such as the key() process, result in tree fragments, this corruption prevents the proper cleanup of ID attributes. As a result, the system may access freed memory, causing crashes or enabling attackers to trigger heap corruption.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-416 Use After Free\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n7.8\nHIGH\nCVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:C/C:N/I:H/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-8916\n<div class=\"csaf-accordion-content\">\n\nAllocation of Resources Without Limits or Throttling vulnerability in Legion of the Bouncy Castle Inc. BC Java bcpkix on All (API modules), Legion of the Bouncy Castle Inc. BC Java bcprov on All (API modules), Legion of the Bouncy Castle Inc. BCPKIX FIPS bcpkix-fips on All (API modules) allows Excessive Allocation. This vulnerability is associated with program files https://github.Com/bcgit/bc-java/blob/main/pkix/src/main/java/org/bouncycastle/pkix/jcajce/PKIXCertPathReviewer.Java, https://github.Com/bcgit/bc-java/blob/main/prov/src/main/java/org/bouncycastle/x509/PKIXCertPathReviewer.Java. This issue affects BC Java: from 1.44 through 1.78; BC Java: from 1.44 through 1.78; BCPKIX FIPS: from 1.0.0 through 1.0.7, from 2.0.0 through 2.0.7.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-770 Allocation of Resources Without Limits or Throttling\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.3\nMEDIUM\nCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-9230\n<div class=\"csaf-accordion-content\">\n\nIssue summary: An application trying to decrypt CMS messages encrypted using password based encryption can trigger an out-of-bounds read and write. Impact summary: This out-of-bounds read may trigger a crash which leads to Denial of Service for an application. The out-of-bounds write can cause a memory corruption which can have various consequences including a Denial of Service or Execution of attacker-supplied code. Although the consequences of a successful exploit of this vulnerability could be severe, the probability that the attacker would be able to perform it is low. Besides, password based (PWRI) encryption support in CMS messages is very rarely used. For that reason the issue was assessed as Moderate severity according to our Security Policy. The FIPS modules in 3.5, 3.4, 3.3, 3.2, 3.1 and 3.0 are not affected by this issue, as the CMS implementation is outside the OpenSSL FIPS module boundary.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-125 Out-of-bounds Read\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n7.5\nHIGH\nCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-9231\n<div class=\"csaf-accordion-content\">\n\nIssue summary: A timing side-channel which could potentially allow remote recovery of the private key exists in the SM2 algorithm implementation on 64 bit ARM platforms. Impact summary: A timing side-channel in SM2 signature computations on 64 bit ARM platforms could allow recovering the private key by an attacker.. While remote key recovery over a network was not attempted by the reporter, timing measurements revealed a timing signal which may allow such an attack. OpenSSL does not directly support certificates with SM2 keys in TLS, and so this CVE is not relevant in most TLS contexts. However, given that it is possible to add support for such certificates via a custom provider, coupled with the fact that in such a custom provider context the private key may be recoverable via remote timing measurements, we consider this to be a Moderate severity issue. The FIPS modules in 3.5, 3.4, 3.3, 3.2, 3.1 and 3.0 are not affected by this issue, as SM2 is not an approved algorithm.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-385 Covert Timing Channel\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n6.5\nMEDIUM\nCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:L\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-9232\n<div class=\"csaf-accordion-content\">\n\nIssue summary: An application using the OpenSSL HTTP client API functions may trigger an out-of-bounds read if the 'no_proxy' environment variable is set and the host portion of the authority component of the HTTP URL is an IPv6 address. Impact summary: An out-of-bounds read can trigger a crash which leads to Denial of Service for an application. The OpenSSL HTTP client API functions can be used directly by applications but they are also used by the OCSP client functions and CMP (Certificate Management Protocol) client implementation in OpenSSL. However the URLs used by these implementations are unlikely to be controlled by an attacker. In this vulnerable code the out of bounds read can only trigger a crash. Furthermore the vulnerability requires an attacker-controlled URL to be passed from an application to the OpenSSL function and the user has to have a 'no_proxy' environment variable set. For the aforementioned reasons the issue was assessed as Low severity. The vulnerable code was introduced in the following patch releases: 3.0.16, 3.1.8, 3.2.4, 3.3.3, 3.4.0 and 3.5.0. The FIPS modules in 3.5, 3.4, 3.3, 3.2, 3.1 and 3.0 are not affected by this issue, as the HTTP client implementation is outside the OpenSSL FIPS module boundary.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-125 Out-of-bounds Read\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.9\nMEDIUM\nCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-9820\n<div class=\"csaf-accordion-content\">\n\nA flaw was found in the GnuTLS library, specifically in the gnutls_pkcs11_token_init() function that handles PKCS#11 token initialization. When a token label longer than expected is processed, the function writes past the end of a fixed-size stack buffer. This programming error can cause the application using GnuTLS to crash or, in certain conditions, be exploited for code execution. As a result, systems or applications relying on GnuTLS may be vulnerable to a denial of service or local privilege escalation attacks.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-121 Stack-based Buffer Overflow\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n4\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-14831\n<div class=\"csaf-accordion-content\">\n\nA flaw was found in GnuTLS. This vulnerability allows a denial of service (DoS) by excessive CPU (Central Processing Unit) and memory consumption via specially crafted malicious certificates containing a large number of name constraints and subject alternative names (SANs).\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-407 Inefficient Algorithmic Complexity\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.3\nMEDIUM\nCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-23143\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: net: Fix null-ptr-deref by sock_lock_init_class_and_name() and rmmod. When I ran the repro [0] and waited a few seconds, I observed two LOCKDEP splats: a warning immediately followed by a null-ptr-deref. [1] Reproduction Steps: 1) Mount CIFS 2) Add an iptables rule to drop incoming FIN packets for CIFS 3) Unmount CIFS 4) Unload the CIFS module 5) Remove the iptables rule At step 3), the CIFS module calls sock_release() for the underlying TCP socket, and it returns quickly. However, the socket remains in FIN_WAIT_1 because incoming FIN packets are dropped. At this point, the module's refcnt is 0 while the socket is still alive, so the following rmmod command succeeds. # ss -tan State Recv-Q Send-Q Local Address:Port Peer Address:Port FIN-WAIT-1 0 477 10.0.2.15:51062 10.0.0.137:445 # lsmod | grep cifs cifs 1159168 0 This highlights a discrepancy between the lifetime of the CIFS module and the underlying TCP socket. Even after CIFS calls sock_release() and it returns, the TCP socket does not die immediately in order to close the connection gracefully. While this is generally fine, it causes an issue with LOCKDEP because CIFS assigns a different lock class to the TCP socket's sk->sk_lock using sock_lock_init_class_and_name(). Once an incoming packet is processed for the socket or a timer fires, sk->sk_lock is acquired. Then, LOCKDEP checks the lock context in check_wait_context(), where hlock_class() is called to retrieve the lock class. However, since the module has already been unloaded, hlock_class() logs a warning and returns NULL, triggering the null-ptr-deref. If LOCKDEP is enabled, we must ensure that a module calling sock_lock_init_class_and_name() (CIFS, NFS, etc) cannot be unloaded while such a socket is still alive to prevent this issue. Let's hold the module reference in sock_lock_init_class_and_name() and release it when the socket is freed in sk_prot_free(). Note that sock_lock_init() clears sk->sk_owner for svc_create_socket() that calls sock_lock_init_class_and_name() for a listening socket, which clones a socket by sk_clone_lock() without GFP_ZERO. [0]: CIFS_SERVER=\"10.0.0.137\" CIFS_PATH=\"//${CIFS_SERVER}/Users/Administrator/Desktop/CIFS_TEST\" DEV=\"enp0s3\" CRED=\"/root/WindowsCredential.txt\" MNT=$(mktemp -d /tmp/XXXXXX) mount -t cifs ${CIFS_PATH} ${MNT} -o vers=3.0,credentials=${CRED},cache=none,echo_interval=1 iptables -A INPUT -s ${CIFS_SERVER} -j DROP for i in $(seq 10); do umount ${MNT} rmmod cifs sleep 1 done rm -r ${MNT} iptables -D INPUT -s ${CIFS_SERVER} -j DROP [1]: DEBUG_LOCKS_WARN_ON(1) WARNING: CPU: 10 PID: 0 at kernel/locking/lockdep.c:234 hlock_class (kernel/locking/lockdep.c:234 kernel/locking/lockdep.c:223) Modules linked in: cifs_arc4 nls_ucs2_utils cifs_md4 [last unloaded: cifs] CPU: 10 UID: 0 PID: 0 Comm: swapper/10 Not tainted 6.14.0 #36 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.16.0-0-gd239552ce722-prebuilt.qemu.org 04/01/2014 RIP: 0010:hlock_class (kernel/locking/lockdep.c:234 kernel/locking/lockdep.c:223) ... Call Trace: __lock_acquire (kernel/locking/lockdep.c:4853 kernel/locking/lockdep.c:5178) lock_acquire (kernel/locking/lockdep.c:469 kernel/locking/lockdep.c:5853 kernel/locking/lockdep.c:5816) _raw_spin_lock_nested (kernel/locking/spinlock.c:379) tcp_v4_rcv (./include/linux/skbuff.h:1678 ./include/net/tcp.h:2547 net/ipv4/tcp_ipv4.c:2350) ... BUG: kernel NULL pointer dereference, address: 00000000000000c4 PF: supervisor read access in kernel mode PF: error_code(0x0000) - not-present page PGD 0 Oops: Oops: 0000 [#1] PREEMPT SMP NOPTI CPU: 10 UID: 0 PID: 0 Comm: swapper/10 Tainted: G W 6.14.0 #36 Tainted: [W]=WARN Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.16.0-0-gd239552ce722-prebuilt.qemu.org 04/01/2014 RIP: 0010:__lock_acquire (kernel/ ---truncated---\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-476 NULL Pointer Dereference\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-23160\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: media: mediatek: vcodec: Fix a resource leak related to the scp device in FW initialization On Mediatek devices with a system companion processor (SCP) the mtk_scp structure has to be removed explicitly to avoid a resource leak. Free the structure in case the allocation of the firmware structure fails during the firmware initialization.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-401 Missing Release of Memory after Effective Lifetime\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-31257\n<div class=\"csaf-accordion-content\">\n\nThis issue was addressed with improved memory handling. This issue is fixed in Safari 18.5, iOS 18.5 and iPadOS 18.5, macOS Sequoia 15.5, tvOS 18.5, visionOS 2.5, watchOS 11.5. Processing maliciously crafted web content may lead to an unexpected Safari crash.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n4.7\nMEDIUM\nCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:N/I:N/A:L\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-37931\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: btrfs: adjust subpage bit start based on sectorsize When running machines with 64k page size and a 16k nodesize we started seeing tree log corruption in production. This turned out to be because we were not writing out dirty blocks sometimes, so this in fact affects all metadata writes. When writing out a subpage EB we scan the subpage bitmap for a dirty range. If the range isn't dirty we do bit_start++; to move onto the next bit. The problem is the bitmap is based on the number of sectors that an EB has. So in this case, we have a 64k pagesize, 16k nodesize, but a 4k sectorsize. This means our bitmap is 4 bits for every node. With a 64k page size we end up with 4 nodes per page. To make this easier this is how everything looks [0 16k 32k 48k ] logical address [0 4 8 12 ] radix tree offset [ 64k page ] folio [ 16k eb ][ 16k eb ][ 16k eb ][ 16k eb ] extent buffers [ | | | | | | | | | | | | | | | | ] bitmap Now we use all of our addressing based on fs_info->sectorsize_bits, so as you can see the above our 16k eb->start turns into radix entry 4. When we find a dirty range for our eb, we correctly do bit_start += sectors_per_node, because if we start at bit 0, the next bit for the next eb is 4, to correspond to eb->start 16k. However if our range is clean, we will do bit_start++, which will now put us offset from our radix tree entries. In our case, assume that the first time we check the bitmap the block is not dirty, we increment bit_start so now it == 1, and then we loop around and check again. This time it is dirty, and we go to find that start using the following equation start = folio_start + bit_start * fs_info->sectorsize; so in the case above, eb->start 0 is now dirty, and we calculate start as 0 + 1 * fs_info->sectorsize = 4096 4096 >> 12 = 1 Now we're looking up the radix tree for 1, and we won't find an eb. What's worse is now we're using bit_start == 1, so we do bit_start += sectors_per_node, which is now 5. If that eb is dirty we will run into the same thing, we will look at an offset that is not populated in the radix tree, and now we're skipping the writeout of dirty extent buffers. The best fix for this is to not use sectorsize_bits to address nodes, but that's a larger change. Since this is a fs corruption problem fix it simply by always using sectors_per_node to increment the start bit.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-20 Improper Input Validation\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-37968\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: iio: light: opt3001: fix deadlock due to concurrent flag access The threaded IRQ function in this driver is reading the flag twice: once to lock a mutex and once to unlock it. Even though the code setting the flag is designed to prevent it, there are subtle cases where the flag could be true at the mutex_lock stage and false at the mutex_unlock stage. This results in the mutex not being unlocked, resulting in a deadlock. Fix it by making the opt3001_irq() code generally more robust, reading the flag into a variable and using the variable value at both stages.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-667 Improper Locking\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-38322\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: perf/x86/intel: Fix crash in icl_update_topdown_event() The perf_fuzzer found a hard-lockup crash on a RaptorLake machine: Oops: general protection fault, maybe for address 0xffff89aeceab400: 0000 CPU: 23 UID: 0 PID: 0 Comm: swapper/23 Tainted: [W]=WARN Hardware name: Dell Inc. Precision 9660/0VJ762 RIP: 0010:native_read_pmc+0x7/0x40 Code: cc e8 8d a9 01 00 48 89 03 5b cd cc cc cc cc 0f 1f ... RSP: 000:fffb03100273de8 EFLAGS: 00010046 .... Call Trace: icl_update_topdown_event+0x165/0x190 ? ktime_get+0x38/0xd0 intel_pmu_read_event+0xf9/0x210 __perf_event_read+0xf9/0x210 CPUs 16-23 are E-core CPUs that don't support the perf metrics feature. The icl_update_topdown_event() should not be invoked on these CPUs. It's a regression of commit: f9bdf1f95339 (\"perf/x86/intel: Avoid disable PMU if !cpuc->enabled in sample read\") The bug introduced by that commit is that the is_topdown_event() function is mistakenly used to replace the is_topdown_count() call to check if the topdown functions for the perf metrics feature should be invoked. Fix it.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-20 Improper Input Validation\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-38347\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: f2fs: fix to do sanity check on ino and xnid syzbot reported a f2fs bug as below: INFO: task syz-executor140:5308 blocked for more than 143 seconds. Not tainted 6.14.0-rc7-syzkaller-00069-g81e4f8d68c66 #0 \"echo 0 > /proc/sys/kernel/hung_task_timeout_secs\" disables this message. task:syz-executor140 state:D stack:24016 pid:5308 tgid:5308 ppid:5306 task_flags:0x400140 flags:0x00000006 Call Trace: context_switch kernel/sched/core.c:5378 [inline] __schedule+0x190e/0x4c90 kernel/sched/core.c:6765 __schedule_loop kernel/sched/core.c:6842 [inline] schedule+0x14b/0x320 kernel/sched/core.c:6857 io_schedule+0x8d/0x110 kernel/sched/core.c:7690 folio_wait_bit_common+0x839/0xee0 mm/filemap.c:1317 __folio_lock mm/filemap.c:1664 [inline] folio_lock include/linux/pagemap.h:1163 [inline] __filemap_get_folio+0x147/0xb40 mm/filemap.c:1917 pagecache_get_page+0x2c/0x130 mm/folio-compat.c:87 find_get_page_flags include/linux/pagemap.h:842 [inline] f2fs_grab_cache_page+0x2b/0x320 fs/f2fs/f2fs.h:2776 __get_node_page+0x131/0x11b0 fs/f2fs/node.c:1463 read_xattr_block+0xfb/0x190 fs/f2fs/xattr.c:306 lookup_all_xattrs fs/f2fs/xattr.c:355 [inline] f2fs_getxattr+0x676/0xf70 fs/f2fs/xattr.c:533 __f2fs_get_acl+0x52/0x870 fs/f2fs/acl.c:179 f2fs_acl_create fs/f2fs/acl.c:375 [inline] f2fs_init_acl+0xd7/0x9b0 fs/f2fs/acl.c:418 f2fs_init_inode_metadata+0xa0f/0x1050 fs/f2fs/dir.c:539 f2fs_add_inline_entry+0x448/0x860 fs/f2fs/inline.c:666 f2fs_add_dentry+0xba/0x1e0 fs/f2fs/dir.c:765 f2fs_do_add_link+0x28c/0x3a0 fs/f2fs/dir.c:808 f2fs_add_link fs/f2fs/f2fs.h:3616 [inline] f2fs_mknod+0x2e8/0x5b0 fs/f2fs/namei.c:766 vfs_mknod+0x36d/0x3b0 fs/namei.c:4191 unix_bind_bsd net/unix/af_unix.c:1286 [inline] unix_bind+0x563/0xe30 net/unix/af_unix.c:1379 __sys_bind_socket net/socket.c:1817 [inline] __sys_bind+0x1e4/0x290 net/socket.c:1848 __do_sys_bind net/socket.c:1853 [inline] __se_sys_bind net/socket.c:1851 [inline] __x64_sys_bind+0x7a/0x90 net/socket.c:1851 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f Let's dump and check metadata of corrupted inode, it shows its xattr_nid is the same to its i_ino. dump.f2fs -i 3 chaseyu.img.raw i_xattr_nid [0x 3 : 3] So that, during mknod in the corrupted directory, it tries to get and lock inode page twice, result in deadlock. - f2fs_mknod - f2fs_add_inline_entry - f2fs_get_inode_page --- lock dir's inode page - f2fs_init_acl - f2fs_acl_create(dir,..) - __f2fs_get_acl - f2fs_getxattr - lookup_all_xattrs - __get_node_page --- try to lock dir's inode page In order to fix this, let's add sanity check on ino and xnid.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-20 Improper Input Validation\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-38491\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: mptcp: make fallback action and fallback decision atomic Syzkaller reported the following splat: WARNING: CPU: 1 PID: 7704 at net/mptcp/protocol.h:1223 __mptcp_do_fallback net/mptcp/protocol.h:1223 [inline] WARNING: CPU: 1 PID: 7704 at net/mptcp/protocol.h:1223 mptcp_do_fallback net/mptcp/protocol.h:1244 [inline] WARNING: CPU: 1 PID: 7704 at net/mptcp/protocol.h:1223 check_fully_established net/mptcp/options.c:982 [inline] WARNING: CPU: 1 PID: 7704 at net/mptcp/protocol.h:1223 mptcp_incoming_options+0x21a8/0x2510 net/mptcp/options.c:1153 Modules linked in: CPU: 1 UID: 0 PID: 7704 Comm: syz.3.1419 Not tainted 6.16.0-rc3-gbd5ce2324dba #20 PREEMPT(voluntary) Hardware name: QEMU Ubuntu 24.04 PC (i440FX + PIIX, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014 RIP: 0010:__mptcp_do_fallback net/mptcp/protocol.h:1223 [inline] RIP: 0010:mptcp_do_fallback net/mptcp/protocol.h:1244 [inline] RIP: 0010:check_fully_established net/mptcp/options.c:982 [inline] RIP: 0010:mptcp_incoming_options+0x21a8/0x2510 net/mptcp/options.c:1153 Code: 24 18 e8 bb 2a 00 fd e9 1b df ff ff e8 b1 21 0f 00 e8 ec 5f c4 fc 44 0f b7 ac 24 b0 00 00 00 e9 54 f1 ff ff e8 d9 5f c4 fc 90 <0f> 0b 90 e9 b8 f4 ff ff e8 8b 2a 00 fd e9 8d e6 ff ff e8 81 2a 00 RSP: 0018:ffff8880a3f08448 EFLAGS: 00010246 RAX: 0000000000000000 RBX: ffff8880180a8000 RCX: ffffffff84afcf45 RDX: ffff888090223700 RSI: ffffffff84afdaa7 RDI: 0000000000000001 RBP: ffff888017955780 R08: 0000000000000001 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000 R13: ffff8880180a8910 R14: ffff8880a3e9d058 R15: 0000000000000000 FS: 00005555791b8500(0000) GS:ffff88811c495000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 000000110c2800b7 CR3: 0000000058e44000 CR4: 0000000000350ef0 Call Trace: tcp_reset+0x26f/0x2b0 net/ipv4/tcp_input.c:4432 tcp_validate_incoming+0x1057/0x1b60 net/ipv4/tcp_input.c:5975 tcp_rcv_established+0x5b5/0x21f0 net/ipv4/tcp_input.c:6166 tcp_v4_do_rcv+0x5dc/0xa70 net/ipv4/tcp_ipv4.c:1925 tcp_v4_rcv+0x3473/0x44a0 net/ipv4/tcp_ipv4.c:2363 ip_protocol_deliver_rcu+0xba/0x480 net/ipv4/ip_input.c:205 ip_local_deliver_finish+0x2f1/0x500 net/ipv4/ip_input.c:233 NF_HOOK include/linux/netfilter.h:317 [inline] NF_HOOK include/linux/netfilter.h:311 [inline] ip_local_deliver+0x1be/0x560 net/ipv4/ip_input.c:254 dst_input include/net/dst.h:469 [inline] ip_rcv_finish net/ipv4/ip_input.c:447 [inline] NF_HOOK include/linux/netfilter.h:317 [inline] NF_HOOK include/linux/netfilter.h:311 [inline] ip_rcv+0x514/0x810 net/ipv4/ip_input.c:567 __netif_receive_skb_one_core+0x197/0x1e0 net/core/dev.c:5975 __netif_receive_skb+0x1f/0x120 net/core/dev.c:6088 process_backlog+0x301/0x1360 net/core/dev.c:6440 __napi_poll.constprop.0+0xba/0x550 net/core/dev.c:7453 napi_poll net/core/dev.c:7517 [inline] net_rx_action+0xb44/0x1010 net/core/dev.c:7644 handle_softirqs+0x1d0/0x770 kernel/softirq.c:579 do_softirq+0x3f/0x90 kernel/softirq.c:480 __local_bh_enable_ip+0xed/0x110 kernel/softirq.c:407 local_bh_enable include/linux/bottom_half.h:33 [inline] inet_csk_listen_stop+0x2c5/0x1070 net/ipv4/inet_connection_sock.c:1524 mptcp_check_listen_stop.part.0+0x1cc/0x220 net/mptcp/protocol.c:2985 mptcp_check_listen_stop net/mptcp/mib.h:118 [inline] __mptcp_close+0x9b9/0xbd0 net/mptcp/protocol.c:3000 mptcp_close+0x2f/0x140 net/mptcp/protocol.c:3066 inet_release+0xed/0x200 net/ipv4/af_inet.c:435 inet6_release+0x4f/0x70 net/ipv6/af_inet6.c:487 __sock_release+0xb3/0x270 net/socket.c:649 sock_close+0x1c/0x30 net/socket.c:1439 __fput+0x402/0xb70 fs/file_table.c:465 task_work_run+0x150/0x240 kernel/task_work.c:227 resume_user_mode_work include/linux/resume_user_mode.h:50 [inline] exit_to_user_mode_loop+0xd4 ---truncated---\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-667 Improper Locking\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-38502\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: bpf: Fix oob access in cgroup local storage Lonial reported that an out-of-bounds access in cgroup local storage can be crafted via tail calls. Given two programs each utilizing a cgroup local storage with a different value size, and one program doing a tail call into the other. The verifier will validate each of the indivial programs just fine. However, in the runtime context the bpf_cg_run_ctx holds an bpf_prog_array_item which contains the BPF program as well as any cgroup local storage flavor the program uses. Helpers such as bpf_get_local_storage() pick this up from the runtime context: ctx = container_of(current->bpf_ctx, struct bpf_cg_run_ctx, run_ctx); storage = ctx->prog_item->cgroup_storage[stype]; if (stype == BPF_CGROUP_STORAGE_SHARED) ptr = &READ_ONCE(storage->buf)->data[0]; else ptr = this_cpu_ptr(storage->percpu_buf); For the second program which was called from the originally attached one, this means bpf_get_local_storage() will pick up the former program's map, not its own. With mismatching sizes, this can result in an unintended out-of-bounds access. To fix this issue, we need to extend bpf_map_owner with an array of storage_cookie[] to match on i) the exact maps from the original program if the second program was using bpf_get_local_storage(), or ii) allow the tail call combination if the second program was not using any of the cgroup local storage maps.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-125 Out-of-bounds Read\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n4\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-38552\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: mptcp: plug races between subflow fail and subflow creation We have races similar to the one addressed by the previous patch between subflow failing and additional subflow creation. They are just harder to trigger. The solution is similar. Use a separate flag to track the condition 'socket state prevent any additional subflow creation' protected by the fallback lock. The socket fallback makes such flag true, and also receiving or sending an MP_FAIL option. The field 'allow_infinite_fallback' is now always touched under the relevant lock, we can drop the ONCE annotation on write.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-20 Improper Input Validation\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.3\nMEDIUM\nCVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-38614\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: eventpoll: Fix semi-unbounded recursion Ensure that epoll instances can never form a graph deeper than EP_MAX_NESTS+1 links. Currently, ep_loop_check_proc() ensures that the graph is loop-free and does some recursion depth checks, but those recursion depth checks don't limit the depth of the resulting tree for two reasons: - They don't look upwards in the tree. - If there are multiple downwards paths of different lengths, only one of the paths is actually considered for the depth check since commit 28d82dc1c4ed (\"epoll: limit paths\"). Essentially, the current recursion depth check in ep_loop_check_proc() just serves to prevent it from recursing too deeply while checking for loops. A more thorough check is done in reverse_path_check() after the new graph edge has already been created; this checks, among other things, that no paths going upwards from any non-epoll file with a length of more than 5 edges exist. However, this check does not apply to non-epoll files. As a result, it is possible to recurse to a depth of at least roughly 500, tested on v6.15. (I am unsure if deeper recursion is possible; and this may have changed with commit 8c44dac8add7 (\"eventpoll: Fix priority inversion problem\").) To fix it: 1. In ep_loop_check_proc(), note the subtree depth of each visited node, and use subtree depths for the total depth calculation even when a subtree has already been visited. 2. Add ep_get_upwards_depth_proc() for similarly determining the maximum depth of an upwards walk. 3. In ep_loop_check(), use these values to limit the total path length between epoll nodes to EP_MAX_NESTS edges.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-674 Uncontrolled Recursion\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-38670\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: arm64/entry: Mask DAIF in cpu_switch_to(), call_on_irq_stack() `cpu_switch_to()` and `call_on_irq_stack()` manipulate SP to change to different stacks along with the Shadow Call Stack if it is enabled. Those two stack changes cannot be done atomically and both functions can be interrupted by SErrors or Debug Exceptions which, though unlikely, is very much broken : if interrupted, we can end up with mismatched stacks and Shadow Call Stack leading to clobbered stacks. In `cpu_switch_to()`, it can happen when SP_EL0 points to the new task, but x18 stills points to the old task's SCS. When the interrupt handler tries to save the task's SCS pointer, it will save the old task SCS pointer (x18) into the new task struct (pointed to by SP_EL0), clobbering it. In `call_on_irq_stack()`, it can happen when switching from the task stack to the IRQ stack and when switching back. In both cases, we can be interrupted when the SCS pointer points to the IRQ SCS, but SP points to the task stack. The nested interrupt handler pushes its return addresses on the IRQ SCS. It then detects that SP points to the task stack, calls `call_on_irq_stack()` and clobbers the task SCS pointer with the IRQ SCS pointer, which it will also use ! This leads to tasks returning to addresses on the wrong SCS, or even on the IRQ SCS, triggering kernel panics via CONFIG_VMAP_STACK or FPAC if enabled. This is possible on a default config, but unlikely. However, when enabling CONFIG_ARM64_PSEUDO_NMI, DAIF is unmasked and instead the GIC is responsible for filtering what interrupts the CPU should receive based on priority. Given the goal of emulating NMIs, pseudo-NMIs can be received by the CPU even in `cpu_switch_to()` and `call_on_irq_stack()`, possibly *very* frequently depending on the system configuration and workload, leading to unpredictable kernel panics. Completely mask DAIF in `cpu_switch_to()` and restore it when returning. Do the same in `call_on_irq_stack()`, but restore and mask around the branch. Mask DAIF even if CONFIG_SHADOW_CALL_STACK is not enabled for consistency of behaviour between all configurations. Introduce and use an assembly macro for saving and masking DAIF, as the existing one saves but only masks IF.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-20 Improper Input Validation\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-38676\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: iommu/amd: Avoid stack buffer overflow from kernel cmdline While the kernel command line is considered trusted in most environments, avoid writing 1 byte past the end of \"acpiid\" if the \"str\" argument is maximum length.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-805 Buffer Access with Incorrect Length Value\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n6\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-38677\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: f2fs: fix to avoid out-of-boundary access in dnode page As Jiaming Zhang reported: __dump_stack lib/dump_stack.c:94 [inline] dump_stack_lvl+0x1c1/0x2a0 lib/dump_stack.c:120 print_address_description mm/kasan/report.c:378 [inline] print_report+0x17e/0x800 mm/kasan/report.c:480 kasan_report+0x147/0x180 mm/kasan/report.c:593 data_blkaddr fs/f2fs/f2fs.h:3053 [inline] f2fs_data_blkaddr fs/f2fs/f2fs.h:3058 [inline] f2fs_get_dnode_of_data+0x1a09/0x1c40 fs/f2fs/node.c:855 f2fs_reserve_block+0x53/0x310 fs/f2fs/data.c:1195 prepare_write_begin fs/f2fs/data.c:3395 [inline] f2fs_write_begin+0xf39/0x2190 fs/f2fs/data.c:3594 generic_perform_write+0x2c7/0x910 mm/filemap.c:4112 f2fs_buffered_write_iter fs/f2fs/file.c:4988 [inline] f2fs_file_write_iter+0x1ec8/0x2410 fs/f2fs/file.c:5216 new_sync_write fs/read_write.c:593 [inline] vfs_write+0x546/0xa90 fs/read_write.c:686 ksys_write+0x149/0x250 fs/read_write.c:738 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xf3/0x3d0 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f The root cause is in the corrupted image, there is a dnode has the same node id w/ its inode, so during f2fs_get_dnode_of_data(), it tries to access block address in dnode at offset 934, however it parses the dnode as inode node, so that get_dnode_addr() returns 360, then it tries to access page address from 360 + 934 * 4 = 4096 w/ 4 bytes. To fix this issue, let's add sanity check for node id of all direct nodes during f2fs_get_dnode_of_data().\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-20 Improper Input Validation\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-38679\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: media: venus: Fix OOB read due to missing payload bound check Currently, The event_seq_changed() handler processes a variable number of properties sent by the firmware. The number of properties is indicated by the firmware and used to iterate over the payload. However, the payload size is not being validated against the actual message length. This can lead to out-of-bounds memory access if the firmware provides a property count that exceeds the data available in the payload. Such a condition can result in kernel crashes or potential information leaks if memory beyond the buffer is accessed. Fix this by properly validating the remaining size of the payload before each property access and updating bounds accordingly as properties are parsed. This ensures that property parsing is safely bounded within the received message buffer and protects against malformed or malicious firmware behavior.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-20 Improper Input Validation\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-38680\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: media: uvcvideo: Fix 1-byte out-of-bounds read in uvc_parse_format() The buffer length check before calling uvc_parse_format() only ensured that the buffer has at least 3 bytes (buflen > 2), buf the function accesses buffer[3], requiring at least 4 bytes. This can lead to an out-of-bounds read if the buffer has exactly 3 bytes. Fix it by checking that the buffer has at least 4 bytes in uvc_parse_format().\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-125 Out-of-bounds Read\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-38681\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: mm/ptdump: take the memory hotplug lock inside ptdump_walk_pgd() Memory hot remove unmaps and tears down various kernel page table regions as required. The ptdump code can race with concurrent modifications of the kernel page tables. When leaf entries are modified concurrently, the dump code may log stale or inconsistent information for a VA range, but this is otherwise not harmful. But when intermediate levels of kernel page table are freed, the dump code will continue to use memory that has been freed and potentially reallocated for another purpose. In such cases, the ptdump code may dereference bogus addresses, leading to a number of potential problems. To avoid the above mentioned race condition, platforms such as arm64, riscv and s390 take memory hotplug lock, while dumping kernel page table via the sysfs interface /sys/kernel/debug/kernel_page_tables. Similar race condition exists while checking for pages that might have been marked W+X via /sys/kernel/debug/kernel_page_tables/check_wx_pages which in turn calls ptdump_check_wx(). Instead of solving this race condition again, let's just move the memory hotplug lock inside generic ptdump_check_wx() which will benefit both the scenarios. Drop get_online_mems() and put_online_mems() combination from all existing platform ptdump code paths.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-366 Race Condition within a Thread\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n6.5\nMEDIUM\nCVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:L/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-38683\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: hv_netvsc: Fix panic during namespace deletion with VF The existing code move the VF NIC to new namespace when NETDEV_REGISTER is received on netvsc NIC. During deletion of the namespace, default_device_exit_batch() >> default_device_exit_net() is called. When netvsc NIC is moved back and registered to the default namespace, it automatically brings VF NIC back to the default namespace. This will cause the default_device_exit_net() >> for_each_netdev_safe loop unable to detect the list end, and hit NULL ptr: [ 231.449420] mana 7870:00:00.0 enP30832s1: Moved VF to namespace with: eth0 [ 231.449656] BUG: kernel NULL pointer dereference, address: 0000000000000010 [ 231.450246] #PF: supervisor read access in kernel mode [ 231.450579] #PF: error_code(0x0000) - not-present page [ 231.450916] PGD 17b8a8067 P4D 0 [ 231.451163] Oops: Oops: 0000 [#1] SMP NOPTI [ 231.451450] CPU: 82 UID: 0 PID: 1394 Comm: kworker/u768:1 Not tainted 6.16.0-rc4+ #3 VOLUNTARY [ 231.452042] Hardware name: Microsoft Corporation Virtual Machine/Virtual Machine, BIOS Hyper-V UEFI Release v4.1 11/21/2024 [ 231.452692] Workqueue: netns cleanup_net [ 231.452947] RIP: 0010:default_device_exit_batch+0x16c/0x3f0 [ 231.453326] Code: c0 0c f5 b3 e8 d5 db fe ff 48 85 c0 74 15 48 c7 c2 f8 fd ca b2 be 10 00 00 00 48 8d 7d c0 e8 7b 77 25 00 49 8b 86 28 01 00 00 <48> 8b 50 10 4c 8b 2a 4c 8d 62 f0 49 83 ed 10 4c 39 e0 0f 84 d6 00 [ 231.454294] RSP: 0018:ff75fc7c9bf9fd00 EFLAGS: 00010246 [ 231.454610] RAX: 0000000000000000 RBX: 0000000000000002 RCX: 61c8864680b583eb [ 231.455094] RDX: ff1fa9f71462d800 RSI: ff75fc7c9bf9fd38 RDI: 0000000030766564 [ 231.455686] RBP: ff75fc7c9bf9fd78 R08: 0000000000000000 R09: 0000000000000000 [ 231.456126] R10: 0000000000000001 R11: 0000000000000004 R12: ff1fa9f70088e340 [ 231.456621] R13: ff1fa9f70088e340 R14: ffffffffb3f50c20 R15: ff1fa9f7103e6340 [ 231.457161] FS: 0000000000000000(0000) GS:ff1faa6783a08000(0000) knlGS:0000000000000000 [ 231.457707] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 231.458031] CR2: 0000000000000010 CR3: 0000000179ab2006 CR4: 0000000000b73ef0 [ 231.458434] Call Trace: [ 231.458600] [ 231.458777] ops_undo_list+0x100/0x220 [ 231.459015] cleanup_net+0x1b8/0x300 [ 231.459285] process_one_work+0x184/0x340 To fix it, move the ns change to a workqueue, and take rtnl_lock to avoid changing the netdev list when default_device_exit_net() is using it.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-820 Missing Synchronization\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.2\nMEDIUM\nCVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:L/I:L/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-38684\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: net/sched: ets: use old 'nbands' while purging unused classes Shuang reported sch_ets test-case [1] crashing in ets_class_qlen_notify() after recent changes from Lion [2]. The problem is: in ets_qdisc_change() we purge unused DWRR queues; the value of 'q->nbands' is the new one, and the cleanup should be done with the old one. The problem is here since my first attempts to fix ets_qdisc_change(), but it surfaced again after the recent qdisc len accounting fixes. Fix it purging idle DWRR queues before assigning a new value of 'q->nbands', so that all purge operations find a consistent configuration: - old 'q->nbands' because it's needed by ets_class_find() - old 'q->nstrict' because it's needed by ets_class_is_strict() BUG: kernel NULL pointer dereference, address: 0000000000000000 #PF: supervisor read access in kernel mode #PF: error_code(0x0000) - not-present page PGD 0 P4D 0 Oops: Oops: 0000 [#1] SMP NOPTI CPU: 62 UID: 0 PID: 39457 Comm: tc Kdump: loaded Not tainted 6.12.0-116.el10.x86_64 #1 PREEMPT(voluntary) Hardware name: Dell Inc. PowerEdge R640/06DKY5, BIOS 2.12.2 07/09/2021 RIP: 0010:__list_del_entry_valid_or_report+0x4/0x80 Code: ff 4c 39 c7 0f 84 39 19 8e ff b8 01 00 00 00 c3 cc cc cc cc 66 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 f3 0f 1e fa <48> 8b 17 48 8b 4f 08 48 85 d2 0f 84 56 19 8e ff 48 85 c9 0f 84 ab RSP: 0018:ffffba186009f400 EFLAGS: 00010202 RAX: 00000000000000d6 RBX: 0000000000000000 RCX: 0000000000000004 RDX: ffff9f0fa29b69c0 RSI: 0000000000000000 RDI: 0000000000000000 RBP: ffffffffc12c2400 R08: 0000000000000008 R09: 0000000000000004 R10: ffffffffffffffff R11: 0000000000000004 R12: 0000000000000000 R13: ffff9f0f8cfe0000 R14: 0000000000100005 R15: 0000000000000000 FS: 00007f2154f37480(0000) GS:ffff9f269c1c0000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000000000000000 CR3: 00000001530be001 CR4: 00000000007726f0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 PKRU: 55555554 Call Trace: ets_class_qlen_notify+0x65/0x90 [sch_ets] qdisc_tree_reduce_backlog+0x74/0x110 ets_qdisc_change+0x630/0xa40 [sch_ets] __tc_modify_qdisc.constprop.0+0x216/0x7f0 tc_modify_qdisc+0x7c/0x120 rtnetlink_rcv_msg+0x145/0x3f0 netlink_rcv_skb+0x53/0x100 netlink_unicast+0x245/0x390 netlink_sendmsg+0x21b/0x470 ____sys_sendmsg+0x39d/0x3d0 ___sys_sendmsg+0x9a/0xe0 __sys_sendmsg+0x7a/0xd0 do_syscall_64+0x7d/0x160 entry_SYSCALL_64_after_hwframe+0x76/0x7e RIP: 0033:0x7f2155114084 Code: 89 02 b8 ff ff ff ff eb bb 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 00 f3 0f 1e fa 80 3d 25 f0 0c 00 00 74 13 b8 2e 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 54 c3 0f 1f 00 48 83 ec 28 89 54 24 1c 48 89 RSP: 002b:00007fff1fd7a988 EFLAGS: 00000202 ORIG_RAX: 000000000000002e RAX: ffffffffffffffda RBX: 0000560ec063e5e0 RCX: 00007f2155114084 RDX: 0000000000000000 RSI: 00007fff1fd7a9f0 RDI: 0000000000000003 RBP: 00007fff1fd7aa60 R08: 0000000000000010 R09: 000000000000003f R10: 0000560ee9b3a010 R11: 0000000000000202 R12: 00007fff1fd7aae0 R13: 000000006891ccde R14: 0000560ec063e5e0 R15: 00007fff1fd7aad0 [1] https://lore.kernel.org/netdev/e08c7f4a6882f260011909a868311c6e9b54f3e4.1639153474.git.dcaratti@redhat.com/ [2] https://lore.kernel.org/netdev/d912cbd7-193b-4269-9857-525bee8bbb6a@gmail.com/\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-476 NULL Pointer Dereference\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.2\nMEDIUM\nCVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:L/I:L/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-38685\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: fbdev: Fix vmalloc out-of-bounds write in fast_imageblit This issue triggers when a userspace program does an ioctl FBIOPUT_CON2FBMAP by passing console number and frame buffer number. Ideally this maps console to frame buffer and updates the screen if console is visible. As part of mapping it has to do resize of console according to frame buffer info. if this resize fails and returns from vc_do_resize() and continues further. At this point console and new frame buffer are mapped and sets display vars. Despite failure still it continue to proceed updating the screen at later stages where vc_data is related to previous frame buffer and frame buffer info and display vars are mapped to new frame buffer and eventully leading to out-of-bounds write in fast_imageblit(). This bheviour is excepted only when fg_console is equal to requested console which is a visible console and updates screen with invalid struct references in fbcon_putcs().\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-787 Out-of-bounds Write\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n7.8\nHIGH\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-38687\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: comedi: fix race between polling and detaching syzbot reports a use-after-free in comedi in the below link, which is due to comedi gladly removing the allocated async area even though poll requests are still active on the wait_queue_head inside of it. This can cause a use-after-free when the poll entries are later triggered or removed, as the memory for the wait_queue_head has been freed. We need to check there are no tasks queued on any of the subdevices' wait queues before allowing the device to be detached by the `COMEDI_DEVCONFIG` ioctl. Tasks will read-lock `dev->attach_lock` before adding themselves to the subdevice wait queue, so fix the problem in the `COMEDI_DEVCONFIG` ioctl handler by write-locking `dev->attach_lock` before checking that all of the subdevices are safe to be deleted. This includes testing for any sleepers on the subdevices' wait queues. It remains locked until the device has been detached. This requires the `comedi_device_detach()` function to be refactored slightly, moving the bulk of it into new function `comedi_device_detach_locked()`. Note that the refactor of `comedi_device_detach()` results in `comedi_device_cancel_all()` now being called while `dev->attach_lock` is write-locked, which wasn't the case previously, but that does not matter. Thanks to Jens Axboe for diagnosing the problem and co-developing this patch.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-20 Improper Input Validation\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-38691\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: pNFS: Fix uninited ptr deref in block/scsi layout The error occurs on the third attempt to encode extents. When function ext_tree_prepare_commit() reallocates a larger buffer to retry encoding extents, the \"layoutupdate_pages\" page array is initialized only after the retry loop. But ext_tree_free_commitdata() is called on every iteration and tries to put pages in the array, thus dereferencing uninitialized pointers. An additional problem is that there is no limit on the maximum possible buffer_size. When there are too many extents, the client may create a layoutcommit that is larger than the maximum possible RPC size accepted by the server. During testing, we observed two typical scenarios. First, one memory page for extents is enough when we work with small files, append data to the end of the file, or preallocate extents before writing. But when we fill a new large file without preallocating, the number of extents can be huge, and counting the number of written extents in ext_tree_encode_commit() does not help much. Since this number increases even more between unlocking and locking of ext_tree, the reallocated buffer may not be large enough again and again.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-908 Use of Uninitialized Resource\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-38693\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: media: dvb-frontends: w7090p: fix null-ptr-deref in w7090p_tuner_write_serpar and w7090p_tuner_read_serpar In w7090p_tuner_write_serpar, msg is controlled by user. When msg[0].buf is null and msg[0].len is zero, former checks on msg[0].buf would be passed. If accessing msg[0].buf[2] without sanity check, null pointer deref would happen. We add check on msg[0].len to prevent crash. Similar commit: commit 0ed554fd769a (\"media: dvb-usb: az6027: fix null-ptr-deref in az6027_i2c_xfer()\")\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-20 Improper Input Validation\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n7\nHIGH\nCVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-38694\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: media: dvb-frontends: dib7090p: fix null-ptr-deref in dib7090p_rw_on_apb() In dib7090p_rw_on_apb, msg is controlled by user. When msg[0].buf is null and msg[0].len is zero, former checks on msg[0].buf would be passed. If accessing msg[0].buf[2] without sanity check, null pointer deref would happen. We add check on msg[0].len to prevent crash. Similar issue occurs when access msg[1].buf[0] and msg[1].buf[1]. Similar commit: commit 0ed554fd769a (\"media: dvb-usb: az6027: fix null-ptr-deref in az6027_i2c_xfer()\")\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-476 NULL Pointer Dereference\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-38695\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: scsi: lpfc: Check for hdwq null ptr when cleaning up lpfc_vport structure If a call to lpfc_sli4_read_rev() from lpfc_sli4_hba_setup() fails, the resultant cleanup routine lpfc_sli4_vport_delete_fcp_xri_aborted() may occur before sli4_hba.hdwqs are allocated. This may result in a null pointer dereference when attempting to take the abts_io_buf_list_lock for the first hardware queue. Fix by adding a null ptr check on phba->sli4_hba.hdwq and early return because this situation means there must have been an error during port initialization.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-476 NULL Pointer Dereference\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n7\nHIGH\nCVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-38696\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: MIPS: Don't crash in stack_top() for tasks without ABI or vDSO Not all tasks have an ABI associated or vDSO mapped, for example kthreads never do. If such a task ever ends up calling stack_top(), it will derefence the NULL ABI pointer and crash. This can for example happen when using kunit: mips_stack_top+0x28/0xc0 arch_pick_mmap_layout+0x190/0x220 kunit_vm_mmap_init+0xf8/0x138 __kunit_add_resource+0x40/0xa8 kunit_vm_mmap+0x88/0xd8 usercopy_test_init+0xb8/0x240 kunit_try_run_case+0x5c/0x1a8 kunit_generic_run_threadfn_adapter+0x28/0x50 kthread+0x118/0x240 ret_from_kernel_thread+0x14/0x1c Only dereference the ABI point if it is set. The GIC page is also included as it is specific to the vDSO. Also move the randomization adjustment into the same conditional.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-20 Improper Input Validation\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-38697\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: jfs: upper bound check of tree index in dbAllocAG When computing the tree index in dbAllocAG, we never check if we are out of bounds realative to the size of the stree. This could happen in a scenario where the filesystem metadata are corrupted.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-20 Improper Input Validation\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n7\nHIGH\nCVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-38698\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: jfs: Regular file corruption check The reproducer builds a corrupted file on disk with a negative i_size value. Add a check when opening this file to avoid subsequent operation failures.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-20 Improper Input Validation\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n7\nHIGH\nCVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-38699\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: scsi: bfa: Double-free fix When the bfad_im_probe() function fails during initialization, the memory pointed to by bfad->im is freed without setting bfad->im to NULL. Subsequently, during driver uninstallation, when the state machine enters the bfad_sm_stopping state and calls the bfad_im_probe_undo() function, it attempts to free the memory pointed to by bfad->im again, thereby triggering a double-free vulnerability. Set bfad->im to NULL if probing fails.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-415 Double Free\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n6.4\nMEDIUM\nCVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-38700\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: scsi: libiscsi: Initialize iscsi_conn->dd_data only if memory is allocated In case of an ib_fast_reg_mr allocation failure during iSER setup, the machine hits a panic because iscsi_conn->dd_data is initialized unconditionally, even when no memory is allocated (dd_size == 0). This leads invalid pointer dereference during connection teardown. Fix by setting iscsi_conn->dd_data only if memory is actually allocated. Panic trace: ------------ iser: iser_create_fastreg_desc: Failed to allocate ib_fast_reg_mr err=-12 iser: iser_alloc_rx_descriptors: failed allocating rx descriptors / data buffers BUG: unable to handle page fault for address: fffffffffffffff8 RIP: 0010:swake_up_locked.part.5+0xa/0x40 Call Trace: complete+0x31/0x40 iscsi_iser_conn_stop+0x88/0xb0 [ib_iser] iscsi_stop_conn+0x66/0xc0 [scsi_transport_iscsi] iscsi_if_stop_conn+0x14a/0x150 [scsi_transport_iscsi] iscsi_if_rx+0x1135/0x1834 [scsi_transport_iscsi] ? netlink_lookup+0x12f/0x1b0 ? netlink_deliver_tap+0x2c/0x200 netlink_unicast+0x1ab/0x280 netlink_sendmsg+0x257/0x4f0 ? _copy_from_user+0x29/0x60 sock_sendmsg+0x5f/0x70\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-20 Improper Input Validation\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n7\nHIGH\nCVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-38701\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: ext4: do not BUG when INLINE_DATA_FL lacks system.data xattr A syzbot fuzzed image triggered a BUG_ON in ext4_update_inline_data() when an inode had the INLINE_DATA_FL flag set but was missing the system.data extended attribute. Since this can happen due to a maiciouly fuzzed file system, we shouldn't BUG, but rather, report it as a corrupted file system. Add similar replacements of BUG_ON with EXT4_ERROR_INODE() ii ext4_create_inline_data() and ext4_inline_data_truncate().\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-617 Reachable Assertion\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-38702\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: fbdev: fix potential buffer overflow in do_register_framebuffer() The current implementation may lead to buffer overflow when: 1. Unregistration creates NULL gaps in registered_fb[] 2. All array slots become occupied despite num_registered_fb < FB_MAX 3. The registration loop exceeds array bounds Add boundary check to prevent registered_fb[FB_MAX] access.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-787 Out-of-bounds Write\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n7.8\nHIGH\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-38706\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: ASoC: core: Check for rtd == NULL in snd_soc_remove_pcm_runtime() snd_soc_remove_pcm_runtime() might be called with rtd == NULL which will leads to null pointer dereference. This was reproduced with topology loading and marking a link as ignore due to missing hardware component on the system. On module removal the soc_tplg_remove_link() would call snd_soc_remove_pcm_runtime() with rtd == NULL since the link was ignored, no runtime was created.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-476 NULL Pointer Dereference\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-38707\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: fs/ntfs3: Add sanity check for file name The length of the file name should be smaller than the directory entry size.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-20 Improper Input Validation\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-38708\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: drbd: add missing kref_get in handle_write_conflicts With `two-primaries` enabled, DRBD tries to detect \"concurrent\" writes and handle write conflicts, so that even if you write to the same sector simultaneously on both nodes, they end up with the identical data once the writes are completed. In handling \"superseeded\" writes, we forgot a kref_get, resulting in a premature drbd_destroy_device and use after free, and further to kernel crashes with symptoms. Relevance: No one should use DRBD as a random data generator, and apparently all users of \"two-primaries\" handle concurrent writes correctly on layer up. That is cluster file systems use some distributed lock manager, and live migration in virtualization environments stops writes on one node before starting writes on the other node. Which means that other than for \"test cases\", this code path is never taken in real life. FYI, in DRBD 9, things are handled differently nowadays. We still detect \"write conflicts\", but no longer try to be smart about them. We decided to disconnect hard instead: upper layers must not submit concurrent writes. If they do, that's their fault.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-416 Use After Free\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n7.8\nHIGH\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-38711\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: smb/server: avoid deadlock when linking with ReplaceIfExists If smb2_create_link() is called with ReplaceIfExists set and the name does exist then a deadlock will happen. ksmbd_vfs_kern_path_locked() will return with success and the parent directory will be locked. ksmbd_vfs_remove_file() will then remove the file. ksmbd_vfs_link() will then be called while the parent is still locked. It will try to lock the same parent and will deadlock. This patch moves the ksmbd_vfs_kern_path_unlock() call to *before* ksmbd_vfs_link() and then simplifies the code, removing the file_present flag variable.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-20 Improper Input Validation\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-38712\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: hfsplus: don't use BUG_ON() in hfsplus_create_attributes_file() When the volume header contains erroneous values that do not reflect the actual state of the filesystem, hfsplus_fill_super() assumes that the attributes file is not yet created, which later results in hitting BUG_ON() when hfsplus_create_attributes_file() is called. Replace this BUG_ON() with -EIO error with a message to suggest running fsck tool.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-20 Improper Input Validation\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-38713\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: hfsplus: fix slab-out-of-bounds read in hfsplus_uni2asc() The hfsplus_readdir() method is capable to crash by calling hfsplus_uni2asc(): [ 667.121659][ T9805] ================================================================== [ 667.122651][ T9805] BUG: KASAN: slab-out-of-bounds in hfsplus_uni2asc+0x902/0xa10 [ 667.123627][ T9805] Read of size 2 at addr ffff88802592f40c by task repro/9805 [ 667.124578][ T9805] [ 667.124876][ T9805] CPU: 3 UID: 0 PID: 9805 Comm: repro Not tainted 6.16.0-rc3 #1 PREEMPT(full) [ 667.124886][ T9805] Hardware name: QEMU Ubuntu 24.04 PC (i440FX + PIIX, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014 [ 667.124890][ T9805] Call Trace: [ 667.124893][ T9805] [ 667.124896][ T9805] dump_stack_lvl+0x10e/0x1f0 [ 667.124911][ T9805] print_report+0xd0/0x660 [ 667.124920][ T9805] ? __virt_addr_valid+0x81/0x610 [ 667.124928][ T9805] ? __phys_addr+0xe8/0x180 [ 667.124934][ T9805] ? hfsplus_uni2asc+0x902/0xa10 [ 667.124942][ T9805] kasan_report+0xc6/0x100 [ 667.124950][ T9805] ? hfsplus_uni2asc+0x902/0xa10 [ 667.124959][ T9805] hfsplus_uni2asc+0x902/0xa10 [ 667.124966][ T9805] ? hfsplus_bnode_read+0x14b/0x360 [ 667.124974][ T9805] hfsplus_readdir+0x845/0xfc0 [ 667.124984][ T9805] ? __pfx_hfsplus_readdir+0x10/0x10 [ 667.124994][ T9805] ? stack_trace_save+0x8e/0xc0 [ 667.125008][ T9805] ? iterate_dir+0x18b/0xb20 [ 667.125015][ T9805] ? trace_lock_acquire+0x85/0xd0 [ 667.125022][ T9805] ? lock_acquire+0x30/0x80 [ 667.125029][ T9805] ? iterate_dir+0x18b/0xb20 [ 667.125037][ T9805] ? down_read_killable+0x1ed/0x4c0 [ 667.125044][ T9805] ? putname+0x154/0x1a0 [ 667.125051][ T9805] ? __pfx_down_read_killable+0x10/0x10 [ 667.125058][ T9805] ? apparmor_file_permission+0x239/0x3e0 [ 667.125069][ T9805] iterate_dir+0x296/0xb20 [ 667.125076][ T9805] __x64_sys_getdents64+0x13c/0x2c0 [ 667.125084][ T9805] ? __pfx___x64_sys_getdents64+0x10/0x10 [ 667.125091][ T9805] ? __x64_sys_openat+0x141/0x200 [ 667.125126][ T9805] ? __pfx_filldir64+0x10/0x10 [ 667.125134][ T9805] ? do_user_addr_fault+0x7fe/0x12f0 [ 667.125143][ T9805] do_syscall_64+0xc9/0x480 [ 667.125151][ T9805] entry_SYSCALL_64_after_hwframe+0x77/0x7f [ 667.125158][ T9805] RIP: 0033:0x7fa8753b2fc9 [ 667.125164][ T9805] Code: 00 c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 48 [ 667.125172][ T9805] RSP: 002b:00007ffe96f8e0f8 EFLAGS: 00000217 ORIG_RAX: 00000000000000d9 [ 667.125181][ T9805] RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007fa8753b2fc9 [ 667.125185][ T9805] RDX: 0000000000000400 RSI: 00002000000063c0 RDI: 0000000000000004 [ 667.125190][ T9805] RBP: 00007ffe96f8e110 R08: 00007ffe96f8e110 R09: 00007ffe96f8e110 [ 667.125195][ T9805] R10: 0000000000000000 R11: 0000000000000217 R12: 0000556b1e3b4260 [ 667.125199][ T9805] R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000 [ 667.125207][ T9805] [ 667.125210][ T9805] [ 667.145632][ T9805] Allocated by task 9805: [ 667.145991][ T9805] kasan_save_stack+0x20/0x40 [ 667.146352][ T9805] kasan_save_track+0x14/0x30 [ 667.146717][ T9805] __kasan_kmalloc+0xaa/0xb0 [ 667.147065][ T9805] __kmalloc_noprof+0x205/0x550 [ 667.147448][ T9805] hfsplus_find_init+0x95/0x1f0 [ 667.147813][ T9805] hfsplus_readdir+0x220/0xfc0 [ 667.148174][ T9805] iterate_dir+0x296/0xb20 [ 667.148549][ T9805] __x64_sys_getdents64+0x13c/0x2c0 [ 667.148937][ T9805] do_syscall_64+0xc9/0x480 [ 667.149291][ T9805] entry_SYSCALL_64_after_hwframe+0x77/0x7f [ 667.149809][ T9805] [ 667.150030][ T9805] The buggy address belongs to the object at ffff88802592f000 [ 667.150030][ T9805] which belongs to the cache kmalloc-2k of size 2048 [ 667.151282][ T9805] The buggy address is located 0 bytes to the right of [ 667.151282][ T9805] allocated 1036-byte region [ffff88802592f000, ffff88802592f40c) [ 667.1 ---truncated---\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-20 Improper Input Validation\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n7\nHIGH\nCVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-38714\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: hfsplus: fix slab-out-of-bounds in hfsplus_bnode_read() The hfsplus_bnode_read() method can trigger the issue: [ 174.852007][ T9784] ================================================================== [ 174.852709][ T9784] BUG: KASAN: slab-out-of-bounds in hfsplus_bnode_read+0x2f4/0x360 [ 174.853412][ T9784] Read of size 8 at addr ffff88810b5fc6c0 by task repro/9784 [ 174.854059][ T9784] [ 174.854272][ T9784] CPU: 1 UID: 0 PID: 9784 Comm: repro Not tainted 6.16.0-rc3 #7 PREEMPT(full) [ 174.854281][ T9784] Hardware name: QEMU Ubuntu 24.04 PC (i440FX + PIIX, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014 [ 174.854286][ T9784] Call Trace: [ 174.854289][ T9784] [ 174.854292][ T9784] dump_stack_lvl+0x10e/0x1f0 [ 174.854305][ T9784] print_report+0xd0/0x660 [ 174.854315][ T9784] ? __virt_addr_valid+0x81/0x610 [ 174.854323][ T9784] ? __phys_addr+0xe8/0x180 [ 174.854330][ T9784] ? hfsplus_bnode_read+0x2f4/0x360 [ 174.854337][ T9784] kasan_report+0xc6/0x100 [ 174.854346][ T9784] ? hfsplus_bnode_read+0x2f4/0x360 [ 174.854354][ T9784] hfsplus_bnode_read+0x2f4/0x360 [ 174.854362][ T9784] hfsplus_bnode_dump+0x2ec/0x380 [ 174.854370][ T9784] ? __pfx_hfsplus_bnode_dump+0x10/0x10 [ 174.854377][ T9784] ? hfsplus_bnode_write_u16+0x83/0xb0 [ 174.854385][ T9784] ? srcu_gp_start+0xd0/0x310 [ 174.854393][ T9784] ? __mark_inode_dirty+0x29e/0xe40 [ 174.854402][ T9784] hfsplus_brec_remove+0x3d2/0x4e0 [ 174.854411][ T9784] __hfsplus_delete_attr+0x290/0x3a0 [ 174.854419][ T9784] ? __pfx_hfs_find_1st_rec_by_cnid+0x10/0x10 [ 174.854427][ T9784] ? __pfx___hfsplus_delete_attr+0x10/0x10 [ 174.854436][ T9784] ? __asan_memset+0x23/0x50 [ 174.854450][ T9784] hfsplus_delete_all_attrs+0x262/0x320 [ 174.854459][ T9784] ? __pfx_hfsplus_delete_all_attrs+0x10/0x10 [ 174.854469][ T9784] ? rcu_is_watching+0x12/0xc0 [ 174.854476][ T9784] ? __mark_inode_dirty+0x29e/0xe40 [ 174.854483][ T9784] hfsplus_delete_cat+0x845/0xde0 [ 174.854493][ T9784] ? __pfx_hfsplus_delete_cat+0x10/0x10 [ 174.854507][ T9784] hfsplus_unlink+0x1ca/0x7c0 [ 174.854516][ T9784] ? __pfx_hfsplus_unlink+0x10/0x10 [ 174.854525][ T9784] ? down_write+0x148/0x200 [ 174.854532][ T9784] ? __pfx_down_write+0x10/0x10 [ 174.854540][ T9784] vfs_unlink+0x2fe/0x9b0 [ 174.854549][ T9784] do_unlinkat+0x490/0x670 [ 174.854557][ T9784] ? __pfx_do_unlinkat+0x10/0x10 [ 174.854565][ T9784] ? __might_fault+0xbc/0x130 [ 174.854576][ T9784] ? getname_flags.part.0+0x1c5/0x550 [ 174.854584][ T9784] __x64_sys_unlink+0xc5/0x110 [ 174.854592][ T9784] do_syscall_64+0xc9/0x480 [ 174.854600][ T9784] entry_SYSCALL_64_after_hwframe+0x77/0x7f [ 174.854608][ T9784] RIP: 0033:0x7f6fdf4c3167 [ 174.854614][ T9784] Code: f0 ff ff 73 01 c3 48 8b 0d 26 0d 0e 00 f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 08 [ 174.854622][ T9784] RSP: 002b:00007ffcb948bca8 EFLAGS: 00000206 ORIG_RAX: 0000000000000057 [ 174.854630][ T9784] RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007f6fdf4c3167 [ 174.854636][ T9784] RDX: 00007ffcb948bcc0 RSI: 00007ffcb948bcc0 RDI: 00007ffcb948bd50 [ 174.854641][ T9784] RBP: 00007ffcb948cd90 R08: 0000000000000001 R09: 00007ffcb948bb40 [ 174.854645][ T9784] R10: 00007f6fdf564fc0 R11: 0000000000000206 R12: 0000561e1bc9c2d0 [ 174.854650][ T9784] R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000 [ 174.854658][ T9784] [ 174.854661][ T9784] [ 174.879281][ T9784] Allocated by task 9784: [ 174.879664][ T9784] kasan_save_stack+0x20/0x40 [ 174.880082][ T9784] kasan_save_track+0x14/0x30 [ 174.880500][ T9784] __kasan_kmalloc+0xaa/0xb0 [ 174.880908][ T9784] __kmalloc_noprof+0x205/0x550 [ 174.881337][ T9784] __hfs_bnode_create+0x107/0x890 [ 174.881779][ T9784] hfsplus_bnode_find+0x2d0/0xd10 [ 174.882222][ T9784] hfsplus_brec_find+0x2b0/0x520 [ 174.882659][ T9784] hfsplus_delete_all_attrs+0x23b/0x3 ---truncated---\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-20 Improper Input Validation\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n7\nHIGH\nCVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-38715\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: hfs: fix slab-out-of-bounds in hfs_bnode_read() This patch introduces is_bnode_offset_valid() method that checks the requested offset value. Also, it introduces check_and_correct_requested_length() method that checks and correct the requested length (if it is necessary). These methods are used in hfs_bnode_read(), hfs_bnode_write(), hfs_bnode_clear(), hfs_bnode_copy(), and hfs_bnode_move() with the goal to prevent the access out of allocated memory and triggering the crash.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-20 Improper Input Validation\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-38721\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: netfilter: ctnetlink: fix refcount leak on table dump There is a reference count leak in ctnetlink_dump_table(): if (res < 0) { nf_conntrack_get(&ct->ct_general); // HERE cb->args[1] = (unsigned long)ct; ... While its very unlikely, its possible that ct == last. If this happens, then the refcount of ct was already incremented. This 2nd increment is never undone. This prevents the conntrack object from being released, which in turn keeps prevents cnet->count from dropping back to 0. This will then block the netns dismantle (or conntrack rmmod) as nf_conntrack_cleanup_net_list() will wait forever. This can be reproduced by running conntrack_resize.sh selftest in a loop. It takes ~20 minutes for me on a preemptible kernel on average before I see a runaway kworker spinning in nf_conntrack_cleanup_net_list. One fix would to change this to: if (res < 0) { if (ct != last) nf_conntrack_get(&ct->ct_general); But this reference counting isn't needed in the first place. We can just store a cookie value instead. A followup patch will do the same for ctnetlink_exp_dump_table, it looks to me as if this has the same problem and like ctnetlink_dump_table, we only need a 'skip hint', not the actual object so we can apply the same cookie strategy there as well.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-772 Missing Release of Resource after Effective Lifetime\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-38723\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: LoongArch: BPF: Fix jump offset calculation in tailcall The extra pass of bpf_int_jit_compile() skips JIT context initialization which essentially skips offset calculation leaving out_offset = -1, so the jmp_offset in emit_bpf_tail_call is calculated by \"#define jmp_offset (out_offset - (cur_offset))\" is a negative number, which is wrong. The final generated assembly are as follow. 54: bgeu $a2, $t1, -8 # 0x0000004c 58: addi.d $a6, $s5, -1 5c: bltz $a6, -16 # 0x0000004c 60: alsl.d $t2, $a2, $a1, 0x3 64: ld.d $t2, $t2, 264 68: beq $t2, $zero, -28 # 0x0000004c Before apply this patch, the follow test case will reveal soft lock issues. cd tools/testing/selftests/bpf/ ./test_progs --allow=tailcalls/tailcall_bpf2bpf_1 dmesg: watchdog: BUG: soft lockup - CPU#2 stuck for 26s! [test_progs:25056]\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-20 Improper Input Validation\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-38724\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: nfsd: handle get_client_locked() failure in nfsd4_setclientid_confirm() Lei Lu recently reported that nfsd4_setclientid_confirm() did not check the return value from get_client_locked(). a SETCLIENTID_CONFIRM could race with a confirmed client expiring and fail to get a reference. That could later lead to a UAF. Fix this by getting a reference early in the case where there is an extant confirmed client. If that fails then treat it as if there were no confirmed client found at all. In the case where the unconfirmed client is expiring, just fail and return the result from get_client_locked().\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-416 Use After Free\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n7.8\nHIGH\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-38725\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: net: usb: asix_devices: add phy_mask for ax88772 mdio bus Without setting phy_mask for ax88772 mdio bus, current driver may create at most 32 mdio phy devices with phy address range from 0x00 ~ 0x1f. DLink DUB-E100 H/W Ver B1 is such a device. However, only one main phy device will bind to net phy driver. This is creating issue during system suspend/resume since phy_polling_mode() in phy_state_machine() will directly deference member of phydev->drv for non-main phy devices. Then NULL pointer dereference issue will occur. Due to only external phy or internal phy is necessary, add phy_mask for ax88772 mdio bus to workarnoud the issue.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-20 Improper Input Validation\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n7\nHIGH\nCVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-38727\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: netlink: avoid infinite retry looping in netlink_unicast() netlink_attachskb() checks for the socket's read memory allocation constraints. Firstly, it has: rmem < READ_ONCE(sk->sk_rcvbuf) to check if the just increased rmem value fits into the socket's receive buffer. If not, it proceeds and tries to wait for the memory under: rmem + skb->truesize > READ_ONCE(sk->sk_rcvbuf) The checks don't cover the case when skb->truesize + sk->sk_rmem_alloc is equal to sk->sk_rcvbuf. Thus the function neither successfully accepts these conditions, nor manages to reschedule the task - and is called in retry loop for indefinite time which is caught as: rcu: INFO: rcu_sched self-detected stall on CPU rcu: 0-....: (25999 ticks this GP) idle=ef2/1/0x4000000000000000 softirq=262269/262269 fqs=6212 (t=26000 jiffies g=230833 q=259957) NMI backtrace for cpu 0 CPU: 0 PID: 22 Comm: kauditd Not tainted 5.10.240 #68 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.17.0-4.fc42 04/01/2014 Call Trace: dump_stack lib/dump_stack.c:120 nmi_cpu_backtrace.cold lib/nmi_backtrace.c:105 nmi_trigger_cpumask_backtrace lib/nmi_backtrace.c:62 rcu_dump_cpu_stacks kernel/rcu/tree_stall.h:335 rcu_sched_clock_irq.cold kernel/rcu/tree.c:2590 update_process_times kernel/time/timer.c:1953 tick_sched_handle kernel/time/tick-sched.c:227 tick_sched_timer kernel/time/tick-sched.c:1399 __hrtimer_run_queues kernel/time/hrtimer.c:1652 hrtimer_interrupt kernel/time/hrtimer.c:1717 __sysvec_apic_timer_interrupt arch/x86/kernel/apic/apic.c:1113 asm_call_irq_on_stack arch/x86/entry/entry_64.S:808 netlink_attachskb net/netlink/af_netlink.c:1234 netlink_unicast net/netlink/af_netlink.c:1349 kauditd_send_queue kernel/audit.c:776 kauditd_thread kernel/audit.c:897 kthread kernel/kthread.c:328 ret_from_fork arch/x86/entry/entry_64.S:304 Restore the original behavior of the check which commit in Fixes accidentally missed when restructuring the code. Found by Linux Verification Center (linuxtesting.org).\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-835 Loop with Unreachable Exit Condition ('Infinite Loop')\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-38728\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: smb3: fix for slab out of bounds on mount to ksmbd With KASAN enabled, it is possible to get a slab out of bounds during mount to ksmbd due to missing check in parse_server_interfaces() (see below): BUG: KASAN: slab-out-of-bounds in parse_server_interfaces+0x14ee/0x1880 [cifs] Read of size 4 at addr ffff8881433dba98 by task mount/9827 CPU: 5 UID: 0 PID: 9827 Comm: mount Tainted: G OE 6.16.0-rc2-kasan #2 PREEMPT(voluntary) Tainted: [O]=OOT_MODULE, [E]=UNSIGNED_MODULE Hardware name: Dell Inc. Precision Tower 3620/0MWYPT, BIOS 2.13.1 06/14/2019 Call Trace: dump_stack_lvl+0x9f/0xf0 print_report+0xd1/0x670 __virt_addr_valid+0x22c/0x430 ? parse_server_interfaces+0x14ee/0x1880 [cifs] ? kasan_complete_mode_report_info+0x2a/0x1f0 ? parse_server_interfaces+0x14ee/0x1880 [cifs] kasan_report+0xd6/0x110 parse_server_interfaces+0x14ee/0x1880 [cifs] __asan_report_load_n_noabort+0x13/0x20 parse_server_interfaces+0x14ee/0x1880 [cifs] ? __pfx_parse_server_interfaces+0x10/0x10 [cifs] ? trace_hardirqs_on+0x51/0x60 SMB3_request_interfaces+0x1ad/0x3f0 [cifs] ? __pfx_SMB3_request_interfaces+0x10/0x10 [cifs] ? SMB2_tcon+0x23c/0x15d0 [cifs] smb3_qfs_tcon+0x173/0x2b0 [cifs] ? __pfx_smb3_qfs_tcon+0x10/0x10 [cifs] ? cifs_get_tcon+0x105d/0x2120 [cifs] ? do_raw_spin_unlock+0x5d/0x200 ? cifs_get_tcon+0x105d/0x2120 [cifs] ? __pfx_smb3_qfs_tcon+0x10/0x10 [cifs] cifs_mount_get_tcon+0x369/0xb90 [cifs] ? dfs_cache_find+0xe7/0x150 [cifs] dfs_mount_share+0x985/0x2970 [cifs] ? check_path.constprop.0+0x28/0x50 ? save_trace+0x54/0x370 ? __pfx_dfs_mount_share+0x10/0x10 [cifs] ? __lock_acquire+0xb82/0x2ba0 ? __kasan_check_write+0x18/0x20 cifs_mount+0xbc/0x9e0 [cifs] ? __pfx_cifs_mount+0x10/0x10 [cifs] ? do_raw_spin_unlock+0x5d/0x200 ? cifs_setup_cifs_sb+0x29d/0x810 [cifs] cifs_smb3_do_mount+0x263/0x1990 [cifs]\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-125 Out-of-bounds Read\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-38729\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: ALSA: usb-audio: Validate UAC3 power domain descriptors, too UAC3 power domain descriptors need to be verified with its variable bLength for avoiding the unexpected OOB accesses by malicious firmware, too.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-125 Out-of-bounds Read\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n7.1\nHIGH\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-38732\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: netfilter: nf_reject: don't leak dst refcount for loopback packets recent patches to add a WARN() when replacing skb dst entry found an old bug: WARNING: include/linux/skbuff.h:1165 skb_dst_check_unset include/linux/skbuff.h:1164 [inline] WARNING: include/linux/skbuff.h:1165 skb_dst_set include/linux/skbuff.h:1210 [inline] WARNING: include/linux/skbuff.h:1165 nf_reject_fill_skb_dst+0x2a4/0x330 net/ipv4/netfilter/nf_reject_ipv4.c:234 [..] Call Trace: nf_send_unreach+0x17b/0x6e0 net/ipv4/netfilter/nf_reject_ipv4.c:325 nft_reject_inet_eval+0x4bc/0x690 net/netfilter/nft_reject_inet.c:27 expr_call_ops_eval net/netfilter/nf_tables_core.c:237 [inline] .. This is because blamed commit forgot about loopback packets. Such packets already have a dst_entry attached, even at PRE_ROUTING stage. Instead of checking hook just check if the skb already has a route attached to it.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-911 Improper Update of Reference Count\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.8\nMEDIUM\nCVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-38735\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: gve: prevent ethtool ops after shutdown A crash can occur if an ethtool operation is invoked after shutdown() is called. shutdown() is invoked during system shutdown to stop DMA operations without performing expensive deallocations. It is discouraged to unregister the netdev in this path, so the device may still be visible to userspace and kernel helpers. In gve, shutdown() tears down most internal data structures. If an ethtool operation is dispatched after shutdown(), it will dereference freed or NULL pointers, leading to a kernel panic. While graceful shutdown normally quiesces userspace before invoking the reboot syscall, forced shutdowns (as observed on GCP VMs) can still trigger this path. Fix by calling netif_device_detach() in shutdown(). This marks the device as detached so the ethtool ioctl handler will skip dispatching operations to the driver.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-664 Improper Control of a Resource Through its Lifetime\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-38736\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: net: usb: asix_devices: Fix PHY address mask in MDIO bus initialization Syzbot reported shift-out-of-bounds exception on MDIO bus initialization. The PHY address should be masked to 5 bits (0-31). Without this mask, invalid PHY addresses could be used, potentially causing issues with MDIO bus operations. Fix this by masking the PHY address with 0x1f (31 decimal) to ensure it stays within the valid range.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-20 Improper Input Validation\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39673\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: ppp: fix race conditions in ppp_fill_forward_path ppp_fill_forward_path() has two race conditions: 1. The ppp->channels list can change between list_empty() and list_first_entry(), as ppp_lock() is not held. If the only channel is deleted in ppp_disconnect_channel(), list_first_entry() may access an empty head or a freed entry, and trigger a panic. 2. pch->chan can be NULL. When ppp_unregister_channel() is called, pch->chan is set to NULL before pch is removed from ppp->channels. Fix these by using a lockless RCU approach: - Use list_first_or_null_rcu() to safely test and access the first list entry. - Convert list modifications on ppp->channels to their RCU variants and add synchronize_net() after removal. - Check for a NULL pch->chan before dereferencing it.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-362 Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.9\nMEDIUM\nCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39675\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Add null pointer check in mod_hdcp_hdcp1_create_session() The function mod_hdcp_hdcp1_create_session() calls the function get_first_active_display(), but does not check its return value. The return value is a null pointer if the display list is empty. This will lead to a null pointer dereference. Add a null pointer check for get_first_active_display() and return MOD_HDCP_STATUS_DISPLAY_NOT_FOUND if the function return null. This is similar to the commit c3e9826a2202 (\"drm/amd/display: Add null pointer check for get_first_active_display()\"). (cherry picked from commit 5e43eb3cd731649c4f8b9134f857be62a416c893)\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-20 Improper Input Validation\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39676\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: scsi: qla4xxx: Prevent a potential error pointer dereference The qla4xxx_get_ep_fwdb() function is supposed to return NULL on error, but qla4xxx_ep_connect() returns error pointers. Propagating the error pointers will lead to an Oops in the caller, so change the error pointers to NULL.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-394 Unexpected Status Code or Return Value\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.1\nMEDIUM\nCVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39681\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: x86/cpu/hygon: Add missing resctrl_cpu_detect() in bsp_init helper Since 923f3a2b48bd (\"x86/resctrl: Query LLC monitoring properties once during boot\") resctrl_cpu_detect() has been moved from common CPU initialization code to the vendor-specific BSP init helper, while Hygon didn't put that call in their code. This triggers a division by zero fault during early booting stage on our machines with X86_FEATURE_CQM* supported, where get_rdt_mon_resources() tries to calculate mon_l3_config with uninitialized boot_cpu_data.x86_cache_occ_scale. Add the missing resctrl_cpu_detect() in the Hygon BSP init helper. [ bp: Massage commit message. ]\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-369 Divide By Zero\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39682\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: tls: fix handling of zero-length records on the rx_list Each recvmsg() call must process either - only contiguous DATA records (any number of them) - one non-DATA record If the next record has different type than what has already been processed we break out of the main processing loop. If the record has already been decrypted (which may be the case for TLS 1.3 where we don't know type until decryption) we queue the pending record to the rx_list. Next recvmsg() will pick it up from there. Queuing the skb to rx_list after zero-copy decrypt is not possible, since in that case we decrypted directly to the user space buffer, and we don't have an skb to queue (darg.skb points to the ciphertext skb for access to metadata like length). Only data records are allowed zero-copy, and we break the processing loop after each non-data record. So we should never zero-copy and then find out that the record type has changed. The corner case we missed is when the initial record comes from rx_list, and it's zero length.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-20 Improper Input Validation\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n7\nHIGH\nCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39683\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: tracing: Limit access to parser->buffer when trace_get_user failed When the length of the string written to set_ftrace_filter exceeds FTRACE_BUFF_MAX, the following KASAN alarm will be triggered: BUG: KASAN: slab-out-of-bounds in strsep+0x18c/0x1b0 Read of size 1 at addr ffff0000d00bd5ba by task ash/165 CPU: 1 UID: 0 PID: 165 Comm: ash Not tainted 6.16.0-g6bcdbd62bd56-dirty Hardware name: linux,dummy-virt (DT) Call trace: show_stack+0x34/0x50 (C) dump_stack_lvl+0xa0/0x158 print_address_description.constprop.0+0x88/0x398 print_report+0xb0/0x280 kasan_report+0xa4/0xf0 __asan_report_load1_noabort+0x20/0x30 strsep+0x18c/0x1b0 ftrace_process_regex.isra.0+0x100/0x2d8 ftrace_regex_release+0x484/0x618 __fput+0x364/0xa58 ____fput+0x28/0x40 task_work_run+0x154/0x278 do_notify_resume+0x1f0/0x220 el0_svc+0xec/0xf0 el0t_64_sync_handler+0xa0/0xe8 el0t_64_sync+0x1ac/0x1b0 The reason is that trace_get_user will fail when processing a string longer than FTRACE_BUFF_MAX, but not set the end of parser->buffer to 0. Then an OOB access will be triggered in ftrace_regex_release-> ftrace_process_regex->strsep->strpbrk. We can solve this problem by limiting access to parser->buffer when trace_get_user failed.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-125 Out-of-bounds Read\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n7.1\nHIGH\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39684\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: comedi: Fix use of uninitialized memory in do_insn_ioctl() and do_insnlist_ioctl() syzbot reports a KMSAN kernel-infoleak in `do_insn_ioctl()`. A kernel buffer is allocated to hold `insn->n` samples (each of which is an `unsigned int`). For some instruction types, `insn->n` samples are copied back to user-space, unless an error code is being returned. The problem is that not all the instruction handlers that need to return data to userspace fill in the whole `insn->n` samples, so that there is an information leak. There is a similar syzbot report for `do_insnlist_ioctl()`, although it does not have a reproducer for it at the time of writing. One culprit is `insn_rw_emulate_bits()` which is used as the handler for `INSN_READ` or `INSN_WRITE` instructions for subdevices that do not have a specific handler for that instruction, but do have an `INSN_BITS` handler. For `INSN_READ` it only fills in at most 1 sample, so if `insn->n` is greater than 1, the remaining `insn->n - 1` samples copied to userspace will be uninitialized kernel data. Another culprit is `vm80xx_ai_insn_read()` in the \"vm80xx\" driver. It never returns an error, even if it fails to fill the buffer. Fix it in `do_insn_ioctl()` and `do_insnlist_ioctl()` by making sure that uninitialized parts of the allocated buffer are zeroed before handling each instruction. Thanks to Arnaud Lecomte for their fix to `do_insn_ioctl()`. That fix replaced the call to `kmalloc_array()` with `kcalloc()`, but it is not always necessary to clear the whole buffer.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-20 Improper Input Validation\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39685\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: comedi: pcl726: Prevent invalid irq number The reproducer passed in an irq number(0x80008000) that was too large, which triggered the oob. Added an interrupt number check to prevent users from passing in an irq number that was too large. If `it->options[1]` is 31, then `1 << it->options[1]` is still invalid because it shifts a 1-bit into the sign bit (which is UB in C). Possible solutions include reducing the upper bound on the `it->options[1]` value to 30 or lower, or using `1U << it->options[1]`. The old code would just not attempt to request the IRQ if the `options[1]` value were invalid. And it would still configure the device without interrupts even if the call to `request_irq` returned an error. So it would be better to combine this test with the test below.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-20 Improper Input Validation\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39686\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: comedi: Make insn_rw_emulate_bits() do insn->n samples The `insn_rw_emulate_bits()` function is used as a default handler for `INSN_READ` instructions for subdevices that have a handler for `INSN_BITS` but not for `INSN_READ`. Similarly, it is used as a default handler for `INSN_WRITE` instructions for subdevices that have a handler for `INSN_BITS` but not for `INSN_WRITE`. It works by emulating the `INSN_READ` or `INSN_WRITE` instruction handling with a constructed `INSN_BITS` instruction. However, `INSN_READ` and `INSN_WRITE` instructions are supposed to be able read or write multiple samples, indicated by the `insn->n` value, but `insn_rw_emulate_bits()` currently only handles a single sample. For `INSN_READ`, the comedi core will copy `insn->n` samples back to user-space. (That triggered KASAN kernel-infoleak errors when `insn->n` was greater than 1, but that is being fixed more generally elsewhere in the comedi core.) Make `insn_rw_emulate_bits()` either handle `insn->n` samples, or return an error, to conform to the general expectation for `INSN_READ` and `INSN_WRITE` handlers.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-20 Improper Input Validation\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39687\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: iio: light: as73211: Ensure buffer holes are zeroed Given that the buffer is copied to a kfifo that ultimately user space can read, ensure we zero it.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-20 Improper Input Validation\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39689\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: ftrace: Also allocate and copy hash for reading of filter files Currently the reader of set_ftrace_filter and set_ftrace_notrace just adds the pointer to the global tracer hash to its iterator. Unlike the writer that allocates a copy of the hash, the reader keeps the pointer to the filter hashes. This is problematic because this pointer is static across function calls that release the locks that can update the global tracer hashes. This can cause UAF and similar bugs. Allocate and copy the hash for reading the filter files like it is done for the writers. This not only fixes UAF bugs, but also makes the code a bit simpler as it doesn't have to differentiate when to free the iterator's hash between writers and readers.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-416 Use After Free\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n7.8\nHIGH\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39691\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: fs/buffer: fix use-after-free when call bh_read() helper There's issue as follows: BUG: KASAN: stack-out-of-bounds in end_buffer_read_sync+0xe3/0x110 Read of size 8 at addr ffffc9000168f7f8 by task swapper/3/0 CPU: 3 UID: 0 PID: 0 Comm: swapper/3 Not tainted 6.16.0-862.14.0.6.x86_64 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996) Call Trace: dump_stack_lvl+0x55/0x70 print_address_description.constprop.0+0x2c/0x390 print_report+0xb4/0x270 kasan_report+0xb8/0xf0 end_buffer_read_sync+0xe3/0x110 end_bio_bh_io_sync+0x56/0x80 blk_update_request+0x30a/0x720 scsi_end_request+0x51/0x2b0 scsi_io_completion+0xe3/0x480 ? scsi_device_unbusy+0x11e/0x160 blk_complete_reqs+0x7b/0x90 handle_softirqs+0xef/0x370 irq_exit_rcu+0xa5/0xd0 sysvec_apic_timer_interrupt+0x6e/0x90 Above issue happens when do ntfs3 filesystem mount, issue may happens as follows: mount IRQ ntfs_fill_super read_cache_page do_read_cache_folio filemap_read_folio mpage_read_folio do_mpage_readpage ntfs_get_block_vbo bh_read submit_bh wait_on_buffer(bh); blk_complete_reqs scsi_io_completion scsi_end_request blk_update_request end_bio_bh_io_sync end_buffer_read_sync __end_buffer_read_notouch unlock_buffer wait_on_buffer(bh);--> return will return to caller put_bh --> trigger stack-out-of-bounds In the mpage_read_folio() function, the stack variable 'map_bh' is passed to ntfs_get_block_vbo(). Once unlock_buffer() unlocks and wait_on_buffer() returns to continue processing, the stack variable is likely to be reclaimed. Consequently, during the end_buffer_read_sync() process, calling put_bh() may result in stack overrun. If the bh is not allocated on the stack, it belongs to a folio. Freeing a buffer head which belongs to a folio is done by drop_buffers() which will fail to free buffers which are still locked. So it is safe to call put_bh() before __end_buffer_read_notouch().\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-416 Use After Free\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n4.4\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39692\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: smb: server: split ksmbd_rdma_stop_listening() out of ksmbd_rdma_destroy() We can't call destroy_workqueue(smb_direct_wq); before stop_sessions()! Otherwise already existing connections try to use smb_direct_wq as a NULL pointer.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-20 Improper Input Validation\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39693\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Avoid a NULL pointer dereference [WHY] Although unlikely drm_atomic_get_new_connector_state() or drm_atomic_get_old_connector_state() can return NULL. [HOW] Check returns before dereference. (cherry picked from commit 1e5e8d672fec9f2ab352be121be971877bff2af9)\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-476 NULL Pointer Dereference\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n4.7\nMEDIUM\nCVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39694\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: s390/sclp: Fix SCCB present check Tracing code called by the SCLP interrupt handler contains early exits if the SCCB address associated with an interrupt is NULL. This check is performed after physical to virtual address translation. If the kernel identity mapping does not start at address zero, the resulting virtual address is never zero, so that the NULL checks won't work. Subsequently this may result in incorrect accesses to the first page of the identity mapping. Fix this by introducing a function that handles the NULL case before address translation.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-1285 Improper Validation of Specified Index, Position, or Offset in Input\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n7\nHIGH\nCVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39697\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: NFS: Fix a race when updating an existing write After nfs_lock_and_join_requests() tests for whether the request is still attached to the mapping, nothing prevents a call to nfs_inode_remove_request() from succeeding until we actually lock the page group. The reason is that whoever called nfs_inode_remove_request() doesn't necessarily have a lock on the page group head. So in order to avoid races, let's take the page group lock earlier in nfs_lock_and_join_requests(), and hold it across the removal of the request in nfs_inode_remove_request().\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-362 Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n4.7\nMEDIUM\nCVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39701\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: ACPI: pfr_update: Fix the driver update version check The security-version-number check should be used rather than the runtime version check for driver updates. Otherwise, the firmware update would fail when the update binary had a lower runtime version number than the current one. [ rjw: Changelog edits ]\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-1025 Comparison Using Wrong Factors\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39702\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: ipv6: sr: Fix MAC comparison to be constant-time To prevent timing attacks, MACs need to be compared in constant time. Use the appropriate helper function for this.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-208 Observable Timing Discrepancy\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n7.1\nHIGH\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39703\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: net, hsr: reject HSR frame if skb can't hold tag Receiving HSR frame with insufficient space to hold HSR tag in the skb can result in a crash (kernel BUG): [ 45.390915] skbuff: skb_under_panic: text:ffffffff86f32cac len:26 put:14 head:ffff888042418000 data:ffff888042417ff4 tail:0xe end:0x180 dev:bridge_slave_1 [ 45.392559] ------------[ cut here ]------------ [ 45.392912] kernel BUG at net/core/skbuff.c:211! [ 45.393276] Oops: invalid opcode: 0000 [#1] SMP DEBUG_PAGEALLOC KASAN NOPTI [ 45.393809] CPU: 1 UID: 0 PID: 2496 Comm: reproducer Not tainted 6.15.0 #12 PREEMPT(undef) [ 45.394433] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.16.3-0-ga6ed6b701f0a-prebuilt.qemu.org 04/01/2014 [ 45.395273] RIP: 0010:skb_panic+0x15b/0x1d0 [ 45.402911] Call Trace: [ 45.403105] [ 45.404470] skb_push+0xcd/0xf0 [ 45.404726] br_dev_queue_push_xmit+0x7c/0x6c0 [ 45.406513] br_forward_finish+0x128/0x260 [ 45.408483] __br_forward+0x42d/0x590 [ 45.409464] maybe_deliver+0x2eb/0x420 [ 45.409763] br_flood+0x174/0x4a0 [ 45.410030] br_handle_frame_finish+0xc7c/0x1bc0 [ 45.411618] br_handle_frame+0xac3/0x1230 [ 45.413674] __netif_receive_skb_core.constprop.0+0x808/0x3df0 [ 45.422966] __netif_receive_skb_one_core+0xb4/0x1f0 [ 45.424478] __netif_receive_skb+0x22/0x170 [ 45.424806] process_backlog+0x242/0x6d0 [ 45.425116] __napi_poll+0xbb/0x630 [ 45.425394] net_rx_action+0x4d1/0xcc0 [ 45.427613] handle_softirqs+0x1a4/0x580 [ 45.427926] do_softirq+0x74/0x90 [ 45.428196] This issue was found by syzkaller. The panic happens in br_dev_queue_push_xmit() once it receives a corrupted skb with ETH header already pushed in linear data. When it attempts the skb_push() call, there's not enough headroom and skb_push() panics. The corrupted skb is put on the queue by HSR layer, which makes a sequence of unintended transformations when it receives a specific corrupted HSR frame (with incomplete TAG). Fix it by dropping and consuming frames that are not long enough to contain both ethernet and hsr headers. Alternative fix would be to check for enough headroom before skb_push() in br_dev_queue_push_xmit(). In the reproducer, this is injected via AF_PACKET, but I don't easily see why it couldn't be sent over the wire from adjacent network. Further Details: In the reproducer, the following network interface chain is set up: \u250c\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2510 \u250c\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2510 \u2502 veth0_to_hsr \u251c\u2500\u2500\u2500\u2524 hsr_slave0 \u253c\u2500\u2500\u2500\u2510 \u2514\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2518 \u2514\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2518 \u2502 \u2502 \u250c\u2500\u2500\u2500\u2500\u2500\u2500\u2510 \u251c\u2500\u2524 hsr0 \u251c\u2500\u2500\u2500\u2510 \u2502 \u2514\u2500\u2500\u2500\u2500\u2500\u2500\u2518 \u2502 \u250c\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2510 \u250c\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2510 \u2502 \u2502\u250c\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2510 \u2502 veth1_to_hsr \u253c\u2500\u2500\u2500\u2524 hsr_slave1 \u251c\u2500\u2500\u2500\u2518 \u2514\u2524 \u2502 \u2514\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2518 \u2514\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2518 \u250c\u253c bridge \u2502 \u2502\u2502 \u2502 \u2502\u2514\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2518 \u2502 \u250c\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2510 \u2502 \u2502 ... \u251c\u2500\u2500\u2500\u2500\u2500\u2500\u2518 \u2514\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2518 To trigger the events leading up to crash, reproducer sends a corrupted HSR fr ---truncated---\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-1286 Improper Validation of Syntactic Correctness of Input\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n6.5\nMEDIUM\nCVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39706\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: drm/amdkfd: Destroy KFD debugfs after destroy KFD wq Since KFD proc content was moved to kernel debugfs, we can't destroy KFD debugfs before kfd_process_destroy_wq. Move kfd_process_destroy_wq prior to kfd_debugfs_fini to fix a kernel NULL pointer problem. It happens when /sys/kernel/debug/kfd was already destroyed in kfd_debugfs_fini but kfd_process_destroy_wq calls kfd_debugfs_remove_process. This line debugfs_remove_recursive(entry->proc_dentry); tries to remove /sys/kernel/debug/kfd/proc/ while /sys/kernel/debug/kfd is already gone. It hangs the kernel by kernel NULL pointer. (cherry picked from commit 0333052d90683d88531558dcfdbf2525cc37c233)\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-20 Improper Input Validation\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39709\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: media: venus: protect against spurious interrupts during probe Make sure the interrupt handler is initialized before the interrupt is registered. If the IRQ is registered before hfi_create(), it's possible that an interrupt fires before the handler setup is complete, leading to a NULL dereference. This error condition has been observed during system boot on Rb3Gen2.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-20 Improper Input Validation\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39710\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: media: venus: Add a check for packet size after reading from shared memory Add a check to ensure that the packet size does not exceed the number of available words after reading the packet header from shared memory. This ensures that the size provided by the firmware is safe to process and prevent potential out-of-bounds memory access.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-20 Improper Input Validation\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39713\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: media: rainshadow-cec: fix TOCTOU race condition in rain_interrupt() In the interrupt handler rain_interrupt(), the buffer full check on rain->buf_len is performed before acquiring rain->buf_lock. This creates a Time-of-Check to Time-of-Use (TOCTOU) race condition, as rain->buf_len is concurrently accessed and modified in the work handler rain_irq_work_handler() under the same lock. Multiple interrupt invocations can race, with each reading buf_len before it becomes full and then proceeding. This can lead to both interrupts attempting to write to the buffer, incrementing buf_len beyond its capacity (DATA_SIZE) and causing a buffer overflow. Fix this bug by moving the spin_lock() to before the buffer full check. This ensures that the check and the subsequent buffer modification are performed atomically, preventing the race condition. An corresponding spin_unlock() is added to the overflow path to correctly release the lock. This possible bug was found by an experimental static analysis tool developed by our team.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-20 Improper Input Validation\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39714\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: media: usbtv: Lock resolution while streaming When an program is streaming (ffplay) and another program (qv4l2) changes the TV standard from NTSC to PAL, the kernel crashes due to trying to copy to unmapped memory. Changing from NTSC to PAL increases the resolution in the usbtv struct, but the video plane buffer isn't adjusted, so it overflows. [hverkuil: call vb2_is_busy instead of vb2_is_streaming]\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-20 Improper Input Validation\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39715\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: parisc: Revise gateway LWS calls to probe user read access We use load and stbys,e instructions to trigger memory reference interruptions without writing to memory. Because of the way read access support is implemented, read access interruptions are only triggered at privilege levels 2 and 3. The kernel and gateway page execute at privilege level 0, so this code never triggers a read access interruption. Thus, it is currently possible for user code to execute a LWS compare and swap operation at an address that is read protected at privilege level 3 (PRIV_USER). Fix this by probing read access rights at privilege level 3 and branching to lws_fault if access isn't allowed.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-20 Improper Input Validation\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39716\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: parisc: Revise __get_user() to probe user read access Because of the way read access support is implemented, read access interruptions are only triggered at privilege levels 2 and 3. The kernel executes at privilege level 0, so __get_user() never triggers a read access interruption (code 26). Thus, it is currently possible for user code to access a read protected address via a system call. Fix this by probing read access rights at privilege level 3 (PRIV_USER) and setting __gu_err to -EFAULT (-14) if access isn't allowed. Note the cmpiclr instruction does a 32-bit compare because COND macro doesn't work inside asm.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-20 Improper Input Validation\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39718\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: vsock/virtio: Validate length in packet header before skb_put() When receiving a vsock packet in the guest, only the virtqueue buffer size is validated prior to virtio_vsock_skb_rx_put(). Unfortunately, virtio_vsock_skb_rx_put() uses the length from the packet header as the length argument to skb_put(), potentially resulting in SKB overflow if the host has gone wonky. Validate the length as advertised by the packet header before calling virtio_vsock_skb_rx_put().\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-787 Out-of-bounds Write\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n7.6\nHIGH\nCVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39719\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: iio: imu: bno055: fix OOB access of hw_xlate array Fix a potential out-of-bounds array access of the hw_xlate array in bno055.c. In bno055_get_regmask(), hw_xlate was iterated over the length of the vals array instead of the length of the hw_xlate array. In the case of bno055_gyr_scale, the vals array is larger than the hw_xlate array, so this could result in an out-of-bounds access. In practice, this shouldn't happen though because a match should always be found which breaks out of the for loop before it iterates beyond the end of the hw_xlate array. By adding a new hw_xlate_len field to the bno055_sysfs_attr, we can be sure we are iterating over the correct length.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-20 Improper Input Validation\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39724\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: serial: 8250: fix panic due to PSLVERR When the PSLVERR_RESP_EN parameter is set to 1, the device generates an error response if an attempt is made to read an empty RBR (Receive Buffer Register) while the FIFO is enabled. In serial8250_do_startup(), calling serial_port_out(port, UART_LCR, UART_LCR_WLEN8) triggers dw8250_check_lcr(), which invokes dw8250_force_idle() and serial8250_clear_and_reinit_fifos(). The latter function enables the FIFO via serial_out(p, UART_FCR, p->fcr). Execution proceeds to the serial_port_in(port, UART_RX). This satisfies the PSLVERR trigger condition. When another CPU (e.g., using printk()) is accessing the UART (UART is busy), the current CPU fails the check (value & ~UART_LCR_SPAR) == (lcr & ~UART_LCR_SPAR) in dw8250_check_lcr(), causing it to enter dw8250_force_idle(). Put serial_port_out(port, UART_LCR, UART_LCR_WLEN8) under the port->lock to fix this issue. Panic backtrace: [ 0.442336] Oops - unknown exception [#1] [ 0.442343] epc : dw8250_serial_in32+0x1e/0x4a [ 0.442351] ra : serial8250_do_startup+0x2c8/0x88e ... [ 0.442416] console_on_rootfs+0x26/0x70\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-362 Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39736\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: mm/kmemleak: avoid deadlock by moving pr_warn() outside kmemleak_lock When netpoll is enabled, calling pr_warn_once() while holding kmemleak_lock in mem_pool_alloc() can cause a deadlock due to lock inversion with the netconsole subsystem. This occurs because pr_warn_once() may trigger netpoll, which eventually leads to __alloc_skb() and back into kmemleak code, attempting to reacquire kmemleak_lock. This is the path for the deadlock. mem_pool_alloc() -> raw_spin_lock_irqsave(&kmemleak_lock, flags); -> pr_warn_once() -> netconsole subsystem -> netpoll -> __alloc_skb -> __create_object -> raw_spin_lock_irqsave(&kmemleak_lock, flags); Fix this by setting a flag and issuing the pr_warn_once() after kmemleak_lock is released.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-833 Deadlock\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39737\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: mm/kmemleak: avoid soft lockup in __kmemleak_do_cleanup() A soft lockup warning was observed on a relative small system x86-64 system with 16 GB of memory when running a debug kernel with kmemleak enabled. watchdog: BUG: soft lockup - CPU#8 stuck for 33s! [kworker/8:1:134] The test system was running a workload with hot unplug happening in parallel. Then kemleak decided to disable itself due to its inability to allocate more kmemleak objects. The debug kernel has its CONFIG_DEBUG_KMEMLEAK_MEM_POOL_SIZE set to 40,000. The soft lockup happened in kmemleak_do_cleanup() when the existing kmemleak objects were being removed and deleted one-by-one in a loop via a workqueue. In this particular case, there are at least 40,000 objects that need to be processed and given the slowness of a debug kernel and the fact that a raw_spinlock has to be acquired and released in __delete_object(), it could take a while to properly handle all these objects. As kmemleak has been disabled in this case, the object removal and deletion process can be further optimized as locking isn't really needed. However, it is probably not worth the effort to optimize for such an edge case that should rarely happen. So the simple solution is to call cond_resched() at periodic interval in the iteration loop to avoid soft lockup.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-20 Improper Input Validation\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39738\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: btrfs: do not allow relocation of partially dropped subvolumes [BUG] There is an internal report that balance triggered transaction abort, with the following call trace: item 85 key (594509824 169 0) itemoff 12599 itemsize 33 extent refs 1 gen 197740 flags 2 ref#0: tree block backref root 7 item 86 key (594558976 169 0) itemoff 12566 itemsize 33 extent refs 1 gen 197522 flags 2 ref#0: tree block backref root 7 ... BTRFS error (device loop0): extent item not found for insert, bytenr 594526208 num_bytes 16384 parent 449921024 root_objectid 934 owner 1 offset 0 BTRFS error (device loop0): failed to run delayed ref for logical 594526208 num_bytes 16384 type 182 action 1 ref_mod 1: -117 ------------[ cut here ]------------ BTRFS: Transaction aborted (error -117) WARNING: CPU: 1 PID: 6963 at ../fs/btrfs/extent-tree.c:2168 btrfs_run_delayed_refs+0xfa/0x110 [btrfs] And btrfs check doesn't report anything wrong related to the extent tree. [CAUSE] The cause is a little complex, firstly the extent tree indeed doesn't have the backref for 594526208. The extent tree only have the following two backrefs around that bytenr on-disk: item 65 key (594509824 METADATA_ITEM 0) itemoff 13880 itemsize 33 refs 1 gen 197740 flags TREE_BLOCK tree block skinny level 0 (176 0x7) tree block backref root CSUM_TREE item 66 key (594558976 METADATA_ITEM 0) itemoff 13847 itemsize 33 refs 1 gen 197522 flags TREE_BLOCK tree block skinny level 0 (176 0x7) tree block backref root CSUM_TREE But the such missing backref item is not an corruption on disk, as the offending delayed ref belongs to subvolume 934, and that subvolume is being dropped: item 0 key (934 ROOT_ITEM 198229) itemoff 15844 itemsize 439 generation 198229 root_dirid 256 bytenr 10741039104 byte_limit 0 bytes_used 345571328 last_snapshot 198229 flags 0x1000000000001(RDONLY) refs 0 drop_progress key (206324 EXTENT_DATA 2711650304) drop_level 2 level 2 generation_v2 198229 And that offending tree block 594526208 is inside the dropped range of that subvolume. That explains why there is no backref item for that bytenr and why btrfs check is not reporting anything wrong. But this also shows another problem, as btrfs will do all the orphan subvolume cleanup at a read-write mount. So half-dropped subvolume should not exist after an RW mount, and balance itself is also exclusive to subvolume cleanup, meaning we shouldn't hit a subvolume half-dropped during relocation. The root cause is, there is no orphan item for this subvolume. In fact there are 5 subvolumes from around 2021 that have the same problem. It looks like the original report has some older kernels running, and caused those zombie subvolumes. Thankfully upstream commit 8d488a8c7ba2 (\"btrfs: fix subvolume/snapshot deletion not triggered on mount\") has long fixed the bug. [ENHANCEMENT] For repairing such old fs, btrfs-progs will be enhanced. Considering how delayed the problem will show up (at run delayed ref time) and at that time we have to abort transaction already, it is too late. Instead here we reject any half-dropped subvolume for reloc tree at the earliest time, preventing confusion and extra time wasted on debugging similar bugs.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-20 Improper Input Validation\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39742\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: RDMA: hfi1: fix possible divide-by-zero in find_hw_thread_mask() The function divides number of online CPUs by num_core_siblings, and later checks the divider by zero. This implies a possibility to get and divide-by-zero runtime error. Fix it by moving the check prior to division. This also helps to save one indentation level.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-369 Divide By Zero\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39743\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: jfs: truncate good inode pages when hard link is 0 The fileset value of the inode copy from the disk by the reproducer is AGGR_RESERVED_I. When executing evict, its hard link number is 0, so its inode pages are not truncated. This causes the bugon to be triggered when executing clear_inode() because nrpages is greater than 0.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-20 Improper Input Validation\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n7\nHIGH\nCVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39749\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: rcu: Protect ->defer_qs_iw_pending from data race On kernels built with CONFIG_IRQ_WORK=y, when rcu_read_unlock() is invoked within an interrupts-disabled region of code [1], it will invoke rcu_read_unlock_special(), which uses an irq-work handler to force the system to notice when the RCU read-side critical section actually ends. That end won't happen until interrupts are enabled at the soonest. In some kernels, such as those booted with rcutree.use_softirq=y, the irq-work handler is used unconditionally. The per-CPU rcu_data structure's ->defer_qs_iw_pending field is updated by the irq-work handler and is both read and updated by rcu_read_unlock_special(). This resulted in the following KCSAN splat: ------------------------------------------------------------------------ BUG: KCSAN: data-race in rcu_preempt_deferred_qs_handler / rcu_read_unlock_special read to 0xffff96b95f42d8d8 of 1 bytes by task 90 on cpu 8: rcu_read_unlock_special+0x175/0x260 __rcu_read_unlock+0x92/0xa0 rt_spin_unlock+0x9b/0xc0 __local_bh_enable+0x10d/0x170 __local_bh_enable_ip+0xfb/0x150 rcu_do_batch+0x595/0xc40 rcu_cpu_kthread+0x4e9/0x830 smpboot_thread_fn+0x24d/0x3b0 kthread+0x3bd/0x410 ret_from_fork+0x35/0x40 ret_from_fork_asm+0x1a/0x30 write to 0xffff96b95f42d8d8 of 1 bytes by task 88 on cpu 8: rcu_preempt_deferred_qs_handler+0x1e/0x30 irq_work_single+0xaf/0x160 run_irq_workd+0x91/0xc0 smpboot_thread_fn+0x24d/0x3b0 kthread+0x3bd/0x410 ret_from_fork+0x35/0x40 ret_from_fork_asm+0x1a/0x30 no locks held by irq_work/8/88. irq event stamp: 200272 hardirqs last enabled at (200272): [] finish_task_switch+0x131/0x320 hardirqs last disabled at (200271): [] __schedule+0x129/0xd70 softirqs last enabled at (0): [] copy_process+0x4df/0x1cc0 softirqs last disabled at (0): [<0000000000000000>] 0x0 ------------------------------------------------------------------------ The problem is that irq-work handlers run with interrupts enabled, which means that rcu_preempt_deferred_qs_handler() could be interrupted, and that interrupt handler might contain an RCU read-side critical section, which might invoke rcu_read_unlock_special(). In the strict KCSAN mode of operation used by RCU, this constitutes a data race on the ->defer_qs_iw_pending field. This commit therefore disables interrupts across the portion of the rcu_preempt_deferred_qs_handler() that updates the ->defer_qs_iw_pending field. This suffices because this handler is not a fast path.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-20 Improper Input Validation\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39752\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: ARM: rockchip: fix kernel hang during smp initialization In order to bring up secondary CPUs main CPU write trampoline code to SRAM. The trampoline code is written while secondary CPUs are powered on (at least that true for RK3188 CPU). Sometimes that leads to kernel hang. Probably because secondary CPU execute trampoline code while kernel doesn't expect. The patch moves SRAM initialization step to the point where all secondary CPUs are powered down. That fixes rarely hangs on RK3188: [ 0.091568] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000 [ 0.091996] rockchip_smp_prepare_cpus: ncores 4\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-364 Signal Handler Race Condition\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39756\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: fs: Prevent file descriptor table allocations exceeding INT_MAX When sysctl_nr_open is set to a very high value (for example, 1073741816 as set by systemd), processes attempting to use file descriptors near the limit can trigger massive memory allocation attempts that exceed INT_MAX, resulting in a WARNING in mm/slub.c: WARNING: CPU: 0 PID: 44 at mm/slub.c:5027 __kvmalloc_node_noprof+0x21a/0x288 This happens because kvmalloc_array() and kvmalloc() check if the requested size exceeds INT_MAX and emit a warning when the allocation is not flagged with __GFP_NOWARN. Specifically, when nr_open is set to 1073741816 (0x3ffffff8) and a process calls dup2(oldfd, 1073741880), the kernel attempts to allocate: - File descriptor array: 1073741880 * 8 bytes = 8,589,935,040 bytes - Multiple bitmaps: ~400MB - Total allocation size: > 8GB (exceeding INT_MAX = 2,147,483,647) Reproducer: 1. Set /proc/sys/fs/nr_open to 1073741816: # echo 1073741816 > /proc/sys/fs/nr_open 2. Run a program that uses a high file descriptor: #include #include int main() { struct rlimit rlim = {1073741824, 1073741824}; setrlimit(RLIMIT_NOFILE, &rlim); dup2(2, 1073741880); // Triggers the warning return 0; } 3. Observe WARNING in dmesg at mm/slub.c:5027 systemd commit a8b627a introduced automatic bumping of fs.nr_open to the maximum possible value. The rationale was that systems with memory control groups (memcg) no longer need separate file descriptor limits since memory is properly accounted. However, this change overlooked that: 1. The kernel's allocation functions still enforce INT_MAX as a maximum size regardless of memcg accounting 2. Programs and tests that legitimately test file descriptor limits can inadvertently trigger massive allocations 3. The resulting allocations (>8GB) are impractical and will always fail systemd's algorithm starts with INT_MAX and keeps halving the value until the kernel accepts it. On most systems, this results in nr_open being set to 1073741816 (0x3ffffff8), which is just under 1GB of file descriptors. While processes rarely use file descriptors near this limit in normal operation, certain selftests (like tools/testing/selftests/core/unshare_test.c) and programs that test file descriptor limits can trigger this issue. Fix this by adding a check in alloc_fdtable() to ensure the requested allocation size does not exceed INT_MAX. This causes the operation to fail with -EMFILE instead of triggering a kernel warning and avoids the impractical >8GB memory allocation request.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-401 Missing Release of Memory after Effective Lifetime\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39757\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: ALSA: usb-audio: Validate UAC3 cluster segment descriptors UAC3 class segment descriptors need to be verified whether their sizes match with the declared lengths and whether they fit with the allocated buffer sizes, too. Otherwise malicious firmware may lead to the unexpected OOB accesses.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-20 Improper Input Validation\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n7.1\nHIGH\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39759\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: btrfs: qgroup: fix race between quota disable and quota rescan ioctl There's a race between a task disabling quotas and another running the rescan ioctl that can result in a use-after-free of qgroup records from the fs_info->qgroup_tree rbtree. This happens as follows: 1) Task A enters btrfs_ioctl_quota_rescan() -> btrfs_qgroup_rescan(); 2) Task B enters btrfs_quota_disable() and calls btrfs_qgroup_wait_for_completion(), which does nothing because at that point fs_info->qgroup_rescan_running is false (it wasn't set yet by task A); 3) Task B calls btrfs_free_qgroup_config() which starts freeing qgroups from fs_info->qgroup_tree without taking the lock fs_info->qgroup_lock; 4) Task A enters qgroup_rescan_zero_tracking() which starts iterating the fs_info->qgroup_tree tree while holding fs_info->qgroup_lock, but task B is freeing qgroup records from that tree without holding the lock, resulting in a use-after-free. Fix this by taking fs_info->qgroup_lock at btrfs_free_qgroup_config(). Also at btrfs_qgroup_rescan() don't start the rescan worker if quotas were already disabled.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-20 Improper Input Validation\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39760\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: usb: core: config: Prevent OOB read in SS endpoint companion parsing usb_parse_ss_endpoint_companion() checks descriptor type before length, enabling a potentially odd read outside of the buffer size. Fix this up by checking the size first before looking at any of the fields in the descriptor.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-20 Improper Input Validation\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39766\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: net/sched: Make cake_enqueue return NET_XMIT_CN when past buffer_limit The following setup can trigger a WARNING in htb_activate due to the condition: !cl->leaf.q->q.qlen tc qdisc del dev lo root tc qdisc add dev lo root handle 1: htb default 1 tc class add dev lo parent 1: classid 1:1 \\ htb rate 64bit tc qdisc add dev lo parent 1:1 handle f: \\ cake memlimit 1b ping -I lo -f -c1 -s64 -W0.001 127.0.0.1 This is because the low memlimit leads to a low buffer_limit, which causes packet dropping. However, cake_enqueue still returns NET_XMIT_SUCCESS, causing htb_enqueue to call htb_activate with an empty child qdisc. We should return NET_XMIT_CN when packets are dropped from the same tin and flow. I do not believe return value of NET_XMIT_CN is necessary for packet drops in the case of ack filtering, as that is meant to optimize performance, not to signal congestion.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-20 Improper Input Validation\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n7\nHIGH\nCVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39770\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: net: gso: Forbid IPv6 TSO with extensions on devices with only IPV6_CSUM When performing Generic Segmentation Offload (GSO) on an IPv6 packet that contains extension headers, the kernel incorrectly requests checksum offload if the egress device only advertises NETIF_F_IPV6_CSUM feature, which has a strict contract: it supports checksum offload only for plain TCP or UDP over IPv6 and explicitly does not support packets with extension headers. The current GSO logic violates this contract by failing to disable the feature for packets with extension headers, such as those used in GREoIPv6 tunnels. This violation results in the device being asked to perform an operation it cannot support, leading to a `skb_warn_bad_offload` warning and a collapse of network throughput. While device TSO/USO is correctly bypassed in favor of software GSO for these packets, the GSO stack must be explicitly told not to request checksum offload. Mask NETIF_F_IPV6_CSUM, NETIF_F_TSO6 and NETIF_F_GSO_UDP_L4 in gso_features_check if the IPv6 header contains extension headers to compute checksum in software. The exception is a BIG TCP extension, which, as stated in commit 68e068cabd2c6c53 (\"net: reenable NETIF_F_IPV6_CSUM offload for BIG TCP packets\"): \"The feature is only enabled on devices that support BIG TCP TSO. The header is only present for PF_PACKET taps like tcpdump, and not transmitted by physical devices.\" kernel log output (truncated): WARNING: CPU: 1 PID: 5273 at net/core/dev.c:3535 skb_warn_bad_offload+0x81/0x140 ... Call Trace: skb_checksum_help+0x12a/0x1f0 validate_xmit_skb+0x1a3/0x2d0 validate_xmit_skb_list+0x4f/0x80 sch_direct_xmit+0x1a2/0x380 __dev_xmit_skb+0x242/0x670 __dev_queue_xmit+0x3fc/0x7f0 ip6_finish_output2+0x25e/0x5d0 ip6_finish_output+0x1fc/0x3f0 ip6_tnl_xmit+0x608/0xc00 [ip6_tunnel] ip6gre_tunnel_xmit+0x1c0/0x390 [ip6_gre] dev_hard_start_xmit+0x63/0x1c0 __dev_queue_xmit+0x6d0/0x7f0 ip6_finish_output2+0x214/0x5d0 ip6_finish_output+0x1fc/0x3f0 ip6_xmit+0x2ca/0x6f0 ip6_finish_output+0x1fc/0x3f0 ip6_xmit+0x2ca/0x6f0 inet6_csk_xmit+0xeb/0x150 __tcp_transmit_skb+0x555/0xa80 tcp_write_xmit+0x32a/0xe90 tcp_sendmsg_locked+0x437/0x1110 tcp_sendmsg+0x2f/0x50 ... skb linear: 00000000: e4 3d 1a 7d ec 30 e4 3d 1a 7e 5d 90 86 dd 60 0e skb linear: 00000010: 00 0a 1b 34 3c 40 20 11 00 00 00 00 00 00 00 00 skb linear: 00000020: 00 00 00 00 00 12 20 11 00 00 00 00 00 00 00 00 skb linear: 00000030: 00 00 00 00 00 11 2f 00 04 01 04 01 01 00 00 00 skb linear: 00000040: 86 dd 60 0e 00 0a 1b 00 06 40 20 23 00 00 00 00 skb linear: 00000050: 00 00 00 00 00 00 00 00 00 12 20 23 00 00 00 00 skb linear: 00000060: 00 00 00 00 00 00 00 00 00 11 bf 96 14 51 13 f9 skb linear: 00000070: ae 27 a0 a8 2b e3 80 18 00 40 5b 6f 00 00 01 01 skb linear: 00000080: 08 0a 42 d4 50 d5 4b 70 f8 1a\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-573 Improper Following of Specification by Caller\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39772\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: drm/hisilicon/hibmc: fix the hibmc loaded failed bug When hibmc loaded failed, the driver use hibmc_unload to free the resource, but the mutexes in mode.config are not init, which will access an NULL pointer. Just change goto statement to return, because hibnc_hw_init() doesn't need to free anything.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-20 Improper Input Validation\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39773\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: net: bridge: fix soft lockup in br_multicast_query_expired() When set multicast_query_interval to a large value, the local variable 'time' in br_multicast_send_query() may overflow. If the time is smaller than jiffies, the timer will expire immediately, and then call mod_timer() again, which creates a loop and may trigger the following soft lockup issue. watchdog: BUG: soft lockup - CPU#1 stuck for 221s! [rb_consumer:66] CPU: 1 UID: 0 PID: 66 Comm: rb_consumer Not tainted 6.16.0+ #259 PREEMPT(none) Call Trace: __netdev_alloc_skb+0x2e/0x3a0 br_ip6_multicast_alloc_query+0x212/0x1b70 __br_multicast_send_query+0x376/0xac0 br_multicast_send_query+0x299/0x510 br_multicast_query_expired.constprop.0+0x16d/0x1b0 call_timer_fn+0x3b/0x2a0 __run_timers+0x619/0x950 run_timer_softirq+0x11c/0x220 handle_softirqs+0x18e/0x560 __irq_exit_rcu+0x158/0x1a0 sysvec_apic_timer_interrupt+0x76/0x90 This issue can be reproduced with: ip link add br0 type bridge echo 1 > /sys/class/net/br0/bridge/multicast_querier echo 0xffffffffffffffff > /sys/class/net/br0/bridge/multicast_query_interval ip link set dev br0 up The multicast_startup_query_interval can also cause this issue. Similar to the commit 99b40610956a (\"net: bridge: mcast: add and enforce query interval minimum\"), add check for the query interval maximum to fix this issue.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-667 Improper Locking\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39776\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: mm/debug_vm_pgtable: clear page table entries at destroy_args() The mm/debug_vm_pagetable test allocates manually page table entries for the tests it runs, using also its manually allocated mm_struct. That in itself is ok, but when it exits, at destroy_args() it fails to clear those entries with the *_clear functions. The problem is that leaves stale entries. If another process allocates an mm_struct with a pgd at the same address, it may end up running into the stale entry. This is happening in practice on a debug kernel with CONFIG_DEBUG_VM_PGTABLE=y, for example this is the output with some extra debugging I added (it prints a warning trace if pgtables_bytes goes negative, in addition to the warning at check_mm() function): [ 2.539353] debug_vm_pgtable: [get_random_vaddr ]: random_vaddr is 0x7ea247140000 [ 2.539366] kmem_cache info [ 2.539374] kmem_cachep 0x000000002ce82385 - freelist 0x0000000000000000 - offset 0x508 [ 2.539447] debug_vm_pgtable: [init_args ]: args->mm is 0x000000002267cc9e (...) [ 2.552800] WARNING: CPU: 5 PID: 116 at include/linux/mm.h:2841 free_pud_range+0x8bc/0x8d0 [ 2.552816] Modules linked in: [ 2.552843] CPU: 5 UID: 0 PID: 116 Comm: modprobe Not tainted 6.12.0-105.debug_vm2.el10.ppc64le+debug #1 VOLUNTARY [ 2.552859] Hardware name: IBM,9009-41A POWER9 (architected) 0x4e0202 0xf000005 of:IBM,FW910.00 (VL910_062) hv:phyp pSeries [ 2.552872] NIP: c0000000007eef3c LR: c0000000007eef30 CTR: c0000000003d8c90 [ 2.552885] REGS: c0000000622e73b0 TRAP: 0700 Not tainted (6.12.0-105.debug_vm2.el10.ppc64le+debug) [ 2.552899] MSR: 800000000282b033 CR: 24002822 XER: 0000000a [ 2.552954] CFAR: c0000000008f03f0 IRQMASK: 0 [ 2.552954] GPR00: c0000000007eef30 c0000000622e7650 c000000002b1ac00 0000000000000001 [ 2.552954] GPR04: 0000000000000008 0000000000000000 c0000000007eef30 ffffffffffffffff [ 2.552954] GPR08: 00000000ffff00f5 0000000000000001 0000000000000048 0000000000004000 [ 2.552954] GPR12: 00000003fa440000 c000000017ffa300 c0000000051d9f80 ffffffffffffffdb [ 2.552954] GPR16: 0000000000000000 0000000000000008 000000000000000a 60000000000000e0 [ 2.552954] GPR20: 4080000000000000 c0000000113af038 00007fffcf130000 0000700000000000 [ 2.552954] GPR24: c000000062a6a000 0000000000000001 8000000062a68000 0000000000000001 [ 2.552954] GPR28: 000000000000000a c000000062ebc600 0000000000002000 c000000062ebc760 [ 2.553170] NIP [c0000000007eef3c] free_pud_range+0x8bc/0x8d0 [ 2.553185] LR [c0000000007eef30] free_pud_range+0x8b0/0x8d0 [ 2.553199] Call Trace: [ 2.553207] [c0000000622e7650] [c0000000007eef30] free_pud_range+0x8b0/0x8d0 (unreliable) [ 2.553229] [c0000000622e7750] [c0000000007f40b4] free_pgd_range+0x284/0x3b0 [ 2.553248] [c0000000622e7800] [c0000000007f4630] free_pgtables+0x450/0x570 [ 2.553274] [c0000000622e78e0] [c0000000008161c0] exit_mmap+0x250/0x650 [ 2.553292] [c0000000622e7a30] [c0000000001b95b8] __mmput+0x98/0x290 [ 2.558344] [c0000000622e7a80] [c0000000001d1018] exit_mm+0x118/0x1b0 [ 2.558361] [c0000000622e7ac0] [c0000000001d141c] do_exit+0x2ec/0x870 [ 2.558376] [c0000000622e7b60] [c0000000001d1ca8] do_group_exit+0x88/0x150 [ 2.558391] [c0000000622e7bb0] [c0000000001d1db8] sys_exit_group+0x48/0x50 [ 2.558407] [c0000000622e7be0] [c00000000003d810] system_call_exception+0x1e0/0x4c0 [ 2.558423] [c0000000622e7e50] [c00000000000d05c] system_call_vectored_common+0x15c/0x2ec (...) [ 2.558892] ---[ end trace 0000000000000000 ]--- [ 2.559022] BUG: Bad rss-counter state mm:000000002267cc9e type:MM_ANONPAGES val:1 [ 2.559037] BUG: non-zero pgtables_bytes on freeing mm: -6144 Here the modprobe process ended up with an allocated mm_struct from the mm_struct slab that was used before by the debug_vm_pgtable test. That is not a problem, since the mm_stru ---truncated---\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-20 Improper Input Validation\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39782\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: jbd2: prevent softlockup in jbd2_log_do_checkpoint() Both jbd2_log_do_checkpoint() and jbd2_journal_shrink_checkpoint_list() periodically release j_list_lock after processing a batch of buffers to avoid long hold times on the j_list_lock. However, since both functions contend for j_list_lock, the combined time spent waiting and processing can be significant. jbd2_journal_shrink_checkpoint_list() explicitly calls cond_resched() when need_resched() is true to avoid softlockups during prolonged operations. But jbd2_log_do_checkpoint() only exits its loop when need_resched() is true, relying on potentially sleeping functions like __flush_batch() or wait_on_buffer() to trigger rescheduling. If those functions do not sleep, the kernel may hit a softlockup. watchdog: BUG: soft lockup - CPU#3 stuck for 156s! [kworker/u129:2:373] CPU: 3 PID: 373 Comm: kworker/u129:2 Kdump: loaded Not tainted 6.6.0+ #10 Hardware name: Huawei TaiShan 2280 /BC11SPCD, BIOS 1.27 06/13/2017 Workqueue: writeback wb_workfn (flush-7:2) pstate: 20000005 (nzCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--) pc : native_queued_spin_lock_slowpath+0x358/0x418 lr : jbd2_log_do_checkpoint+0x31c/0x438 [jbd2] Call trace: native_queued_spin_lock_slowpath+0x358/0x418 jbd2_log_do_checkpoint+0x31c/0x438 [jbd2] __jbd2_log_wait_for_space+0xfc/0x2f8 [jbd2] add_transaction_credits+0x3bc/0x418 [jbd2] start_this_handle+0xf8/0x560 [jbd2] jbd2__journal_start+0x118/0x228 [jbd2] __ext4_journal_start_sb+0x110/0x188 [ext4] ext4_do_writepages+0x3dc/0x740 [ext4] ext4_writepages+0xa4/0x190 [ext4] do_writepages+0x94/0x228 __writeback_single_inode+0x48/0x318 writeback_sb_inodes+0x204/0x590 __writeback_inodes_wb+0x54/0xf8 wb_writeback+0x2cc/0x3d8 wb_do_writeback+0x2e0/0x2f8 wb_workfn+0x80/0x2a8 process_one_work+0x178/0x3e8 worker_thread+0x234/0x3b8 kthread+0xf0/0x108 ret_from_fork+0x10/0x20 So explicitly call cond_resched() in jbd2_log_do_checkpoint() to avoid softlockup.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-20 Improper Input Validation\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39783\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: PCI: endpoint: Fix configfs group list head handling Doing a list_del() on the epf_group field of struct pci_epf_driver in pci_epf_remove_cfs() is not correct as this field is a list head, not a list entry. This list_del() call triggers a KASAN warning when an endpoint function driver which has a configfs attribute group is torn down: ================================================================== BUG: KASAN: slab-use-after-free in pci_epf_remove_cfs+0x17c/0x198 Write of size 8 at addr ffff00010f4a0d80 by task rmmod/319 CPU: 3 UID: 0 PID: 319 Comm: rmmod Not tainted 6.16.0-rc2 #1 NONE Hardware name: Radxa ROCK 5B (DT) Call trace: show_stack+0x2c/0x84 (C) dump_stack_lvl+0x70/0x98 print_report+0x17c/0x538 kasan_report+0xb8/0x190 __asan_report_store8_noabort+0x20/0x2c pci_epf_remove_cfs+0x17c/0x198 pci_epf_unregister_driver+0x18/0x30 nvmet_pci_epf_cleanup_module+0x24/0x30 [nvmet_pci_epf] __arm64_sys_delete_module+0x264/0x424 invoke_syscall+0x70/0x260 el0_svc_common.constprop.0+0xac/0x230 do_el0_svc+0x40/0x58 el0_svc+0x48/0xdc el0t_64_sync_handler+0x10c/0x138 el0t_64_sync+0x198/0x19c ... Remove this incorrect list_del() call from pci_epf_remove_cfs().\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-787 Out-of-bounds Write\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n7.8\nHIGH\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39787\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: soc: qcom: mdt_loader: Ensure we don't read past the ELF header When the MDT loader is used in remoteproc, the ELF header is sanitized beforehand, but that's not necessary the case for other clients. Validate the size of the firmware buffer to ensure that we don't read past the end as we iterate over the header. e_phentsize and e_shentsize are validated as well, to ensure that the assumptions about step size in the traversal are valid.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-125 Out-of-bounds Read\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39788\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: scsi: ufs: exynos: Fix programming of HCI_UTRL_NEXUS_TYPE On Google gs101, the number of UTP transfer request slots (nutrs) is 32, and in this case the driver ends up programming the UTRL_NEXUS_TYPE incorrectly as 0. This is because the left hand side of the shift is 1, which is of type int, i.e. 31 bits wide. Shifting by more than that width results in undefined behaviour. Fix this by switching to the BIT() macro, which applies correct type casting as required. This ensures the correct value is written to UTRL_NEXUS_TYPE (0xffffffff on gs101), and it also fixes a UBSAN shift warning: UBSAN: shift-out-of-bounds in drivers/ufs/host/ufs-exynos.c:1113:21 shift exponent 32 is too large for 32-bit type 'int' For consistency, apply the same change to the nutmrs / UTMRL_NEXUS_TYPE write.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-20 Improper Input Validation\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39790\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: bus: mhi: host: Detect events pointing to unexpected TREs When a remote device sends a completion event to the host, it contains a pointer to the consumed TRE. The host uses this pointer to process all of the TREs between it and the host's local copy of the ring's read pointer. This works when processing completion for chained transactions, but can lead to nasty results if the device sends an event for a single-element transaction with a read pointer that is multiple elements ahead of the host's read pointer. For instance, if the host accesses an event ring while the device is updating it, the pointer inside of the event might still point to an old TRE. If the host uses the channel's xfer_cb() to directly free the buffer pointed to by the TRE, the buffer will be double-freed. This behavior was observed on an ep that used upstream EP stack without 'commit 6f18d174b73d (\"bus: mhi: ep: Update read pointer only after buffer is written\")'. Where the device updated the events ring pointer before updating the event contents, so it left a window where the host was able to access the stale data the event pointed to, before the device had the chance to update them. The usual pattern was that the host received an event pointing to a TRE that is not immediately after the last processed one, so it got treated as if it was a chained transaction, processing all of the TREs in between the two read pointers. This commit aims to harden the host by ensuring transactions where the event points to a TRE that isn't local_rp + 1 are chained. [mani: added stable tag and reworded commit message]\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-415 Double Free\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n6.7\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39794\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: ARM: tegra: Use I/O memcpy to write to IRAM Kasan crashes the kernel trying to check boundaries when using the normal memcpy.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-20 Improper Input Validation\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n7.1\nHIGH\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39795\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: block: avoid possible overflow for chunk_sectors check in blk_stack_limits() In blk_stack_limits(), we check that the t->chunk_sectors value is a multiple of the t->physical_block_size value. However, by finding the chunk_sectors value in bytes, we may overflow the unsigned int which holds chunk_sectors, so change the check to be based on sectors.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-674 Uncontrolled Recursion\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39798\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: NFS: Fix the setting of capabilities when automounting a new filesystem Capabilities cannot be inherited when we cross into a new filesystem. They need to be reset to the minimal defaults, and then probed for again.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-273 Improper Check for Dropped Privileges\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39800\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: btrfs: abort transaction on unexpected eb generation at btrfs_copy_root() If we find an unexpected generation for the extent buffer we are cloning at btrfs_copy_root(), we just WARN_ON() and don't error out and abort the transaction, meaning we allow to persist metadata with an unexpected generation. Instead of warning only, abort the transaction and return -EUCLEAN.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-20 Improper Input Validation\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39801\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: usb: dwc3: Remove WARN_ON for device endpoint command timeouts This commit addresses a rarely observed endpoint command timeout which causes kernel panic due to warn when 'panic_on_warn' is enabled and unnecessary call trace prints when 'panic_on_warn' is disabled. It is seen during fast software-controlled connect/disconnect testcases. The following is one such endpoint command timeout that we observed: 1. Connect ======= ->dwc3_thread_interrupt ->dwc3_ep0_interrupt ->configfs_composite_setup ->composite_setup ->usb_ep_queue ->dwc3_gadget_ep0_queue ->__dwc3_gadget_ep0_queue ->__dwc3_ep0_do_control_data ->dwc3_send_gadget_ep_cmd 2. Disconnect ========== ->dwc3_thread_interrupt ->dwc3_gadget_disconnect_interrupt ->dwc3_ep0_reset_state ->dwc3_ep0_end_control_data ->dwc3_send_gadget_ep_cmd In the issue scenario, in Exynos platforms, we observed that control transfers for the previous connect have not yet been completed and end transfer command sent as a part of the disconnect sequence and processing of USB_ENDPOINT_HALT feature request from the host timeout. This maybe an expected scenario since the controller is processing EP commands sent as a part of the previous connect. It maybe better to remove WARN_ON in all places where device endpoint commands are sent to avoid unnecessary kernel panic due to warn.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-20 Improper Input Validation\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39806\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: HID: multitouch: fix slab out-of-bounds access in mt_report_fixup() A malicious HID device can trigger a slab out-of-bounds during mt_report_fixup() by passing in report descriptor smaller than 607 bytes. mt_report_fixup() attempts to patch byte offset 607 of the descriptor with 0x25 by first checking if byte offset 607 is 0x15 however it lacks bounds checks to verify if the descriptor is big enough before conducting this check. Fix this bug by ensuring the descriptor size is at least 608 bytes before accessing it. Below is the KASAN splat after the out of bounds access happens: [ 13.671954] ================================================================== [ 13.672667] BUG: KASAN: slab-out-of-bounds in mt_report_fixup+0x103/0x110 [ 13.673297] Read of size 1 at addr ffff888103df39df by task kworker/0:1/10 [ 13.673297] [ 13.673297] CPU: 0 UID: 0 PID: 10 Comm: kworker/0:1 Not tainted 6.15.0-00005-gec5d573d83f4-dirty #3 [ 13.673297] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.2-debian-1.16.2-1 04/04 [ 13.673297] Call Trace: [ 13.673297] [ 13.673297] dump_stack_lvl+0x5f/0x80 [ 13.673297] print_report+0xd1/0x660 [ 13.673297] kasan_report+0xe5/0x120 [ 13.673297] __asan_report_load1_noabort+0x18/0x20 [ 13.673297] mt_report_fixup+0x103/0x110 [ 13.673297] hid_open_report+0x1ef/0x810 [ 13.673297] mt_probe+0x422/0x960 [ 13.673297] hid_device_probe+0x2e2/0x6f0 [ 13.673297] really_probe+0x1c6/0x6b0 [ 13.673297] __driver_probe_device+0x24f/0x310 [ 13.673297] driver_probe_device+0x4e/0x220 [ 13.673297] __device_attach_driver+0x169/0x320 [ 13.673297] bus_for_each_drv+0x11d/0x1b0 [ 13.673297] __device_attach+0x1b8/0x3e0 [ 13.673297] device_initial_probe+0x12/0x20 [ 13.673297] bus_probe_device+0x13d/0x180 [ 13.673297] device_add+0xe3a/0x1670 [ 13.673297] hid_add_device+0x31d/0xa40 [...]\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-20 Improper Input Validation\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n7\nHIGH\nCVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39808\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: HID: hid-ntrig: fix unable to handle page fault in ntrig_report_version() in ntrig_report_version(), hdev parameter passed from hid_probe(). sending descriptor to /dev/uhid can make hdev->dev.parent->parent to null if hdev->dev.parent->parent is null, usb_dev has invalid address(0xffffffffffffff58) that hid_to_usb_dev(hdev) returned when usb_rcvctrlpipe() use usb_dev,it trigger page fault error for address(0xffffffffffffff58) add null check logic to ntrig_report_version() before calling hid_to_usb_dev()\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-20 Improper Input Validation\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39812\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: sctp: initialize more fields in sctp_v6_from_sk() syzbot found that sin6_scope_id was not properly initialized, leading to undefined behavior. Clear sin6_scope_id and sin6_flowinfo. BUG: KMSAN: uninit-value in __sctp_v6_cmp_addr+0x887/0x8c0 net/sctp/ipv6.c:649 __sctp_v6_cmp_addr+0x887/0x8c0 net/sctp/ipv6.c:649 sctp_inet6_cmp_addr+0x4f2/0x510 net/sctp/ipv6.c:983 sctp_bind_addr_conflict+0x22a/0x3b0 net/sctp/bind_addr.c:390 sctp_get_port_local+0x21eb/0x2440 net/sctp/socket.c:8452 sctp_get_port net/sctp/socket.c:8523 [inline] sctp_listen_start net/sctp/socket.c:8567 [inline] sctp_inet_listen+0x710/0xfd0 net/sctp/socket.c:8636 __sys_listen_socket net/socket.c:1912 [inline] __sys_listen net/socket.c:1927 [inline] __do_sys_listen net/socket.c:1932 [inline] __se_sys_listen net/socket.c:1930 [inline] __x64_sys_listen+0x343/0x4c0 net/socket.c:1930 x64_sys_call+0x271d/0x3e20 arch/x86/include/generated/asm/syscalls_64.h:51 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xd9/0x210 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f Local variable addr.i.i created at: sctp_get_port net/sctp/socket.c:8515 [inline] sctp_listen_start net/sctp/socket.c:8567 [inline] sctp_inet_listen+0x650/0xfd0 net/sctp/socket.c:8636 __sys_listen_socket net/socket.c:1912 [inline] __sys_listen net/socket.c:1927 [inline] __do_sys_listen net/socket.c:1932 [inline] __se_sys_listen net/socket.c:1930 [inline] __x64_sys_listen+0x343/0x4c0 net/socket.c:1930\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-20 Improper Input Validation\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39813\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: ftrace: Fix potential warning in trace_printk_seq during ftrace_dump When calling ftrace_dump_one() concurrently with reading trace_pipe, a WARN_ON_ONCE() in trace_printk_seq() can be triggered due to a race condition. The issue occurs because: CPU0 (ftrace_dump) CPU1 (reader) echo z > /proc/sysrq-trigger !trace_empty(&iter) trace_iterator_reset(&iter) <- len = size = 0 cat /sys/kernel/tracing/trace_pipe trace_find_next_entry_inc(&iter) __find_next_entry ring_buffer_empty_cpu <- all empty return NULL trace_printk_seq(&iter.seq) WARN_ON_ONCE(s->seq.len >= s->seq.size) In the context between trace_empty() and trace_find_next_entry_inc() during ftrace_dump, the ring buffer data was consumed by other readers. This caused trace_find_next_entry_inc to return NULL, failing to populate `iter.seq`. At this point, due to the prior trace_iterator_reset, both `iter.seq.len` and `iter.seq.size` were set to 0. Since they are equal, the WARN_ON_ONCE condition is triggered. Move the trace_printk_seq() into the if block that checks to make sure the return value of trace_find_next_entry_inc() is non-NULL in ftrace_dump_one(), ensuring the 'iter.seq' is properly populated before subsequent operations.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-20 Improper Input Validation\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39817\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: efivarfs: Fix slab-out-of-bounds in efivarfs_d_compare Observed on kernel 6.6 (present on master as well): BUG: KASAN: slab-out-of-bounds in memcmp+0x98/0xd0 Call trace: kasan_check_range+0xe8/0x190 __asan_loadN+0x1c/0x28 memcmp+0x98/0xd0 efivarfs_d_compare+0x68/0xd8 __d_lookup_rcu_op_compare+0x178/0x218 __d_lookup_rcu+0x1f8/0x228 d_alloc_parallel+0x150/0x648 lookup_open.isra.0+0x5f0/0x8d0 open_last_lookups+0x264/0x828 path_openat+0x130/0x3f8 do_filp_open+0x114/0x248 do_sys_openat2+0x340/0x3c0 __arm64_sys_openat+0x120/0x1a0 If dentry->d_name.len < EFI_VARIABLE_GUID_LEN , 'guid' can become negative, leadings to oob. The issue can be triggered by parallel lookups using invalid filename: T1 T2 lookup_open ->lookup simple_lookup d_add // invalid dentry is added to hash list lookup_open d_alloc_parallel __d_lookup_rcu __d_lookup_rcu_op_compare hlist_bl_for_each_entry_rcu // invalid dentry can be retrieved ->d_compare efivarfs_d_compare // oob Fix it by checking 'guid' before cmp.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-20 Improper Input Validation\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n7\nHIGH\nCVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39819\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: fs/smb: Fix inconsistent refcnt update A possible inconsistent update of refcount was identified in `smb2_compound_op`. Such inconsistent update could lead to possible resource leaks. Why it is a possible bug: 1. In the comment section of the function, it clearly states that the reference to `cfile` should be dropped after calling this function. 2. Every control flow path would check and drop the reference to `cfile`, except the patched one. 3. Existing callers would not handle refcount update of `cfile` if -ENOMEM is returned. To fix the bug, an extra goto label \"out\" is added, to make sure that the cleanup logic would always be respected. As the problem is caused by the allocation failure of `vars`, the cleanup logic between label \"finished\" and \"out\" can be safely ignored. According to the definition of function `is_replayable_error`, the error code of \"-ENOMEM\" is not recoverable. Therefore, the replay logic also gets ignored.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-20 Improper Input Validation\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39823\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: KVM: x86: use array_index_nospec with indices that come from guest min and dest_id are guest-controlled indices. Using array_index_nospec() after the bounds checks clamps these values to mitigate speculative execution side-channels.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-20 Improper Input Validation\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n7\nHIGH\nCVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39824\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: HID: asus: fix UAF via HID_CLAIMED_INPUT validation After hid_hw_start() is called hidinput_connect() will eventually be called to set up the device with the input layer since the HID_CONNECT_DEFAULT connect mask is used. During hidinput_connect() all input and output reports are processed and corresponding hid_inputs are allocated and configured via hidinput_configure_usages(). This process involves slot tagging report fields and configuring usages by setting relevant bits in the capability bitmaps. However it is possible that the capability bitmaps are not set at all leading to the subsequent hidinput_has_been_populated() check to fail leading to the freeing of the hid_input and the underlying input device. This becomes problematic because a malicious HID device like a ASUS ROG N-Key keyboard can trigger the above scenario via a specially crafted descriptor which then leads to a user-after-free when the name of the freed input device is written to later on after hid_hw_start(). Below, report 93 intentionally utilises the HID_UP_UNDEFINED Usage Page which is skipped during usage configuration, leading to the frees. 0x05, 0x0D, // Usage Page (Digitizer) 0x09, 0x05, // Usage (Touch Pad) 0xA1, 0x01, // Collection (Application) 0x85, 0x0D, // Report ID (13) 0x06, 0x00, 0xFF, // Usage Page (Vendor Defined 0xFF00) 0x09, 0xC5, // Usage (0xC5) 0x15, 0x00, // Logical Minimum (0) 0x26, 0xFF, 0x00, // Logical Maximum (255) 0x75, 0x08, // Report Size (8) 0x95, 0x04, // Report Count (4) 0xB1, 0x02, // Feature (Data,Var,Abs) 0x85, 0x5D, // Report ID (93) 0x06, 0x00, 0x00, // Usage Page (Undefined) 0x09, 0x01, // Usage (0x01) 0x15, 0x00, // Logical Minimum (0) 0x26, 0xFF, 0x00, // Logical Maximum (255) 0x75, 0x08, // Report Size (8) 0x95, 0x1B, // Report Count (27) 0x81, 0x02, // Input (Data,Var,Abs) 0xC0, // End Collection Below is the KASAN splat after triggering the UAF: [ 21.672709] ================================================================== [ 21.673700] BUG: KASAN: slab-use-after-free in asus_probe+0xeeb/0xf80 [ 21.673700] Write of size 8 at addr ffff88810a0ac000 by task kworker/1:2/54 [ 21.673700] [ 21.673700] CPU: 1 UID: 0 PID: 54 Comm: kworker/1:2 Not tainted 6.16.0-rc4-g9773391cf4dd-dirty #36 PREEMPT(voluntary) [ 21.673700] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.2-debian-1.16.2-1 04/01/2014 [ 21.673700] Call Trace: [ 21.673700] [ 21.673700] dump_stack_lvl+0x5f/0x80 [ 21.673700] print_report+0xd1/0x660 [ 21.673700] kasan_report+0xe5/0x120 [ 21.673700] __asan_report_store8_noabort+0x1b/0x30 [ 21.673700] asus_probe+0xeeb/0xf80 [ 21.673700] hid_device_probe+0x2ee/0x700 [ 21.673700] really_probe+0x1c6/0x6b0 [ 21.673700] __driver_probe_device+0x24f/0x310 [ 21.673700] driver_probe_device+0x4e/0x220 [...] [ 21.673700] [ 21.673700] Allocated by task 54: [ 21.673700] kasan_save_stack+0x3d/0x60 [ 21.673700] kasan_save_track+0x18/0x40 [ 21.673700] kasan_save_alloc_info+0x3b/0x50 [ 21.673700] __kasan_kmalloc+0x9c/0xa0 [ 21.673700] __kmalloc_cache_noprof+0x139/0x340 [ 21.673700] input_allocate_device+0x44/0x370 [ 21.673700] hidinput_connect+0xcb6/0x2630 [ 21.673700] hid_connect+0xf74/0x1d60 [ 21.673700] hid_hw_start+0x8c/0x110 [ 21.673700] asus_probe+0x5a3/0xf80 [ 21.673700] hid_device_probe+0x2ee/0x700 [ 21.673700] really_probe+0x1c6/0x6b0 [ 21.673700] __driver_probe_device+0x24f/0x310 [ 21.673700] driver_probe_device+0x4e/0x220 [...] [ 21.673700] [ 21.673700] Freed by task 54: [ 21.673700] kasan_save_stack+0x3d/0x60 [ 21.673700] kasan_save_track+0x18/0x40 [ 21.673700] kasan_save_free_info+0x3f/0x60 [ 21.673700] __kasan_slab_free+0x3c/0x50 [ 21.673700] kfre ---truncated---\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-20 Improper Input Validation\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n7\nHIGH\nCVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39825\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: smb: client: fix race with concurrent opens in rename(2) Besides sending the rename request to the server, the rename process also involves closing any deferred close, waiting for outstanding I/O to complete as well as marking all existing open handles as deleted to prevent them from deferring closes, which increases the race window for potential concurrent opens on the target file. Fix this by unhashing the dentry in advance to prevent any concurrent opens on the target.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-20 Improper Input Validation\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n7\nHIGH\nCVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39826\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: net: rose: convert 'use' field to refcount_t The 'use' field in struct rose_neigh is used as a reference counter but lacks atomicity. This can lead to race conditions where a rose_neigh structure is freed while still being referenced by other code paths. For example, when rose_neigh->use becomes zero during an ioctl operation via rose_rt_ioctl(), the structure may be removed while its timer is still active, potentially causing use-after-free issues. This patch changes the type of 'use' from unsigned short to refcount_t and updates all code paths to use rose_neigh_hold() and rose_neigh_put() which operate reference counts atomically.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-20 Improper Input Validation\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39827\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: net: rose: include node references in rose_neigh refcount Current implementation maintains two separate reference counting mechanisms: the 'count' field in struct rose_neigh tracks references from rose_node structures, while the 'use' field (now refcount_t) tracks references from rose_sock. This patch merges these two reference counting systems using 'use' field for proper reference management. Specifically, this patch adds incrementing and decrementing of rose_neigh->use when rose_neigh->count is incremented or decremented. This patch also modifies rose_rt_free(), rose_rt_device_down() and rose_clear_route() to properly release references to rose_neigh objects before freeing a rose_node through rose_remove_node(). These changes ensure rose_neigh structures are properly freed only when all references, including those from rose_node structures, are released. As a result, this resolves a slab-use-after-free issue reported by Syzbot.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-20 Improper Input Validation\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39828\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: atm: atmtcp: Prevent arbitrary write in atmtcp_recv_control(). syzbot reported the splat below. [0] When atmtcp_v_open() or atmtcp_v_close() is called via connect() or close(), atmtcp_send_control() is called to send an in-kernel special message. The message has ATMTCP_HDR_MAGIC in atmtcp_control.hdr.length. Also, a pointer of struct atm_vcc is set to atmtcp_control.vcc. The notable thing is struct atmtcp_control is uAPI but has a space for an in-kernel pointer. struct atmtcp_control { struct atmtcp_hdr hdr; /* must be first */ ... atm_kptr_t vcc; /* both directions */ ... } __ATM_API_ALIGN; typedef struct { unsigned char _[8]; } __ATM_API_ALIGN atm_kptr_t; The special message is processed in atmtcp_recv_control() called from atmtcp_c_send(). atmtcp_c_send() is vcc->dev->ops->send() and called from 2 paths: 1. .ndo_start_xmit() (vcc->send() == atm_send_aal0()) 2. vcc_sendmsg() The problem is sendmsg() does not validate the message length and userspace can abuse atmtcp_recv_control() to overwrite any kptr by atmtcp_control. Let's add a new ->pre_send() hook to validate messages from sendmsg(). [0]: Oops: general protection fault, probably for non-canonical address 0xdffffc00200000ab: 0000 [#1] SMP KASAN PTI KASAN: probably user-memory-access in range [0x0000000100000558-0x000000010000055f] CPU: 0 UID: 0 PID: 5865 Comm: syz-executor331 Not tainted 6.17.0-rc1-syzkaller-00215-gbab3ce404553 #0 PREEMPT(full) Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/12/2025 RIP: 0010:atmtcp_recv_control drivers/atm/atmtcp.c:93 [inline] RIP: 0010:atmtcp_c_send+0x1da/0x950 drivers/atm/atmtcp.c:297 Code: 4d 8d 75 1a 4c 89 f0 48 c1 e8 03 42 0f b6 04 20 84 c0 0f 85 15 06 00 00 41 0f b7 1e 4d 8d b7 60 05 00 00 4c 89 f0 48 c1 e8 03 <42> 0f b6 04 20 84 c0 0f 85 13 06 00 00 66 41 89 1e 4d 8d 75 1c 4c RSP: 0018:ffffc90003f5f810 EFLAGS: 00010203 RAX: 00000000200000ab RBX: 0000000000000000 RCX: 0000000000000000 RDX: ffff88802a510000 RSI: 00000000ffffffff RDI: ffff888030a6068c RBP: ffff88802699fb40 R08: ffff888030a606eb R09: 1ffff1100614c0dd R10: dffffc0000000000 R11: ffffffff8718fc40 R12: dffffc0000000000 R13: ffff888030a60680 R14: 000000010000055f R15: 00000000ffffffff FS: 00007f8d7e9236c0(0000) GS:ffff888125c1c000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 000000000045ad50 CR3: 0000000075bde000 CR4: 00000000003526f0 Call Trace: vcc_sendmsg+0xa10/0xc60 net/atm/common.c:645 sock_sendmsg_nosec net/socket.c:714 [inline] __sock_sendmsg+0x219/0x270 net/socket.c:729 ____sys_sendmsg+0x505/0x830 net/socket.c:2614 ___sys_sendmsg+0x21f/0x2a0 net/socket.c:2668 __sys_sendmsg net/socket.c:2700 [inline] __do_sys_sendmsg net/socket.c:2705 [inline] __se_sys_sendmsg net/socket.c:2703 [inline] __x64_sys_sendmsg+0x19b/0x260 net/socket.c:2703 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xfa/0x3b0 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7f8d7e96a4a9 Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 51 18 00 00 90 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b0 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007f8d7e923198 EFLAGS: 00000246 ORIG_RAX: 000000000000002e RAX: ffffffffffffffda RBX: 00007f8d7e9f4308 RCX: 00007f8d7e96a4a9 RDX: 0000000000000000 RSI: 0000200000000240 RDI: 0000000000000005 RBP: 00007f8d7e9f4300 R08: 65732f636f72702f R09: 65732f636f72702f R10: 65732f636f72702f R11: 0000000000000246 R12: 00007f8d7e9c10ac R13: 00007f8d7e9231a0 R14: 0000200000000200 R15: 0000200000000250 Modules linked in:\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-20 Improper Input Validation\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n7\nHIGH\nCVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39835\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: xfs: do not propagate ENODATA disk errors into xattr code ENODATA (aka ENOATTR) has a very specific meaning in the xfs xattr code; namely, that the requested attribute name could not be found. However, a medium error from disk may also return ENODATA. At best, this medium error may escape to userspace as \"attribute not found\" when in fact it's an IO (disk) error. At worst, we may oops in xfs_attr_leaf_get() when we do: error = xfs_attr_leaf_hasname(args, &bp); if (error == -ENOATTR) { xfs_trans_brelse(args->trans, bp); return error; } because an ENODATA/ENOATTR error from disk leaves us with a null bp, and the xfs_trans_brelse will then null-deref it. As discussed on the list, we really need to modify the lower level IO functions to trap all disk errors and ensure that we don't let unique errors like this leak up into higher xfs functions - many like this should be remapped to EIO. However, this patch directly addresses a reported bug in the xattr code, and should be safe to backport to stable kernels. A larger-scope patch to handle more unique errors at lower levels can follow later. (Note, prior to 07120f1abdff we did not oops, but we did return the wrong error code to userspace.)\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-20 Improper Input Validation\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39838\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: cifs: prevent NULL pointer dereference in UTF16 conversion There can be a NULL pointer dereference bug here. NULL is passed to __cifs_sfu_make_node without checks, which passes it unchecked to cifs_strndup_to_utf16, which in turn passes it to cifs_local_to_utf16_bytes where '*from' is dereferenced, causing a crash. This patch adds a check for NULL 'src' in cifs_strndup_to_utf16 and returns NULL early to prevent dereferencing NULL pointer. Found by Linux Verification Center (linuxtesting.org) with SVACE\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-20 Improper Input Validation\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n7\nHIGH\nCVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39839\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: batman-adv: fix OOB read/write in network-coding decode batadv_nc_skb_decode_packet() trusts coded_len and checks only against skb->len. XOR starts at sizeof(struct batadv_unicast_packet), reducing payload headroom, and the source skb length is not verified, allowing an out-of-bounds read and a small out-of-bounds write. Validate that coded_len fits within the payload area of both destination and source sk_buffs before XORing.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-20 Improper Input Validation\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39841\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: scsi: lpfc: Fix buffer free/clear order in deferred receive path Fix a use-after-free window by correcting the buffer release sequence in the deferred receive path. The code freed the RQ buffer first and only then cleared the context pointer under the lock. Concurrent paths (e.g., ABTS and the repost path) also inspect and release the same pointer under the lock, so the old order could lead to double-free/UAF. Note that the repost path already uses the correct pattern: detach the pointer under the lock, then free it after dropping the lock. The deferred path should do the same.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-20 Improper Input Validation\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n7.8\nHIGH\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39842\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: ocfs2: prevent release journal inode after journal shutdown Before calling ocfs2_delete_osb(), ocfs2_journal_shutdown() has already been executed in ocfs2_dismount_volume(), so osb->journal must be NULL. Therefore, the following calltrace will inevitably fail when it reaches jbd2_journal_release_jbd_inode(). ocfs2_dismount_volume()-> ocfs2_delete_osb()-> ocfs2_free_slot_info()-> __ocfs2_free_slot_info()-> evict()-> ocfs2_evict_inode()-> ocfs2_clear_inode()-> jbd2_journal_release_jbd_inode(osb->journal->j_journal, Adding osb->journal checks will prevent null-ptr-deref during the above execution path.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-20 Improper Input Validation\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39843\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: mm: slub: avoid wake up kswapd in set_track_prepare set_track_prepare() can incur lock recursion. The issue is that it is called from hrtimer_start_range_ns holding the per_cpu(hrtimer_bases)[n].lock, but when enabled CONFIG_DEBUG_OBJECTS_TIMERS, may wake up kswapd in set_track_prepare, and try to hold the per_cpu(hrtimer_bases)[n].lock. Avoid deadlock caused by implicitly waking up kswapd by passing in allocation flags, which do not contain __GFP_KSWAPD_RECLAIM in the debug_objects_fill_pool() case. Inside stack depot they are processed by gfp_nested_mask(). Since ___slab_alloc() has preemption disabled, we mask out __GFP_DIRECT_RECLAIM from the flags there. The oops looks something like: BUG: spinlock recursion on CPU#3, swapper/3/0 lock: 0xffffff8a4bf29c80, .magic: dead4ead, .owner: swapper/3/0, .owner_cpu: 3 Hardware name: Qualcomm Technologies, Inc. Popsicle based on SM8850 (DT) Call trace: spin_bug+0x0 _raw_spin_lock_irqsave+0x80 hrtimer_try_to_cancel+0x94 task_contending+0x10c enqueue_dl_entity+0x2a4 dl_server_start+0x74 enqueue_task_fair+0x568 enqueue_task+0xac do_activate_task+0x14c ttwu_do_activate+0xcc try_to_wake_up+0x6c8 default_wake_function+0x20 autoremove_wake_function+0x1c __wake_up+0xac wakeup_kswapd+0x19c wake_all_kswapds+0x78 __alloc_pages_slowpath+0x1ac __alloc_pages_noprof+0x298 stack_depot_save_flags+0x6b0 stack_depot_save+0x14 set_track_prepare+0x5c ___slab_alloc+0xccc __kmalloc_cache_noprof+0x470 __set_page_owner+0x2bc post_alloc_hook[jt]+0x1b8 prep_new_page+0x28 get_page_from_freelist+0x1edc __alloc_pages_noprof+0x13c alloc_slab_page+0x244 allocate_slab+0x7c ___slab_alloc+0x8e8 kmem_cache_alloc_noprof+0x450 debug_objects_fill_pool+0x22c debug_object_activate+0x40 enqueue_hrtimer[jt]+0xdc hrtimer_start_range_ns+0x5f8 ...\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-20 Improper Input Validation\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n7\nHIGH\nCVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39844\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: mm: move page table sync declarations to linux/pgtable.h During our internal testing, we started observing intermittent boot failures when the machine uses 4-level paging and has a large amount of persistent memory: BUG: unable to handle page fault for address: ffffe70000000034 #PF: supervisor write access in kernel mode #PF: error_code(0x0002) - not-present page PGD 0 P4D 0 Oops: 0002 [#1] SMP NOPTI RIP: 0010:__init_single_page+0x9/0x6d Call Trace: __init_zone_device_page+0x17/0x5d memmap_init_zone_device+0x154/0x1bb pagemap_range+0x2e0/0x40f memremap_pages+0x10b/0x2f0 devm_memremap_pages+0x1e/0x60 dev_dax_probe+0xce/0x2ec [device_dax] dax_bus_probe+0x6d/0xc9 [... snip ...] It turns out that the kernel panics while initializing vmemmap (struct page array) when the vmemmap region spans two PGD entries, because the new PGD entry is only installed in init_mm.pgd, but not in the page tables of other tasks. And looking at __populate_section_memmap(): if (vmemmap_can_optimize(altmap, pgmap)) // does not sync top level page tables r = vmemmap_populate_compound_pages(pfn, start, end, nid, pgmap); else // sync top level page tables in x86 r = vmemmap_populate(start, end, nid, altmap); In the normal path, vmemmap_populate() in arch/x86/mm/init_64.c synchronizes the top level page table (See commit 9b861528a801 (\"x86-64, mem: Update all PGDs for direct mapping and vmemmap mapping changes\")) so that all tasks in the system can see the new vmemmap area. However, when vmemmap_can_optimize() returns true, the optimized path skips synchronization of top-level page tables. This is because vmemmap_populate_compound_pages() is implemented in core MM code, which does not handle synchronization of the top-level page tables. Instead, the core MM has historically relied on each architecture to perform this synchronization manually. We're not the first party to encounter a crash caused by not-sync'd top level page tables: earlier this year, Gwan-gyeong Mun attempted to address the issue [1] [2] after hitting a kernel panic when x86 code accessed the vmemmap area before the corresponding top-level entries were synced. At that time, the issue was believed to be triggered only when struct page was enlarged for debugging purposes, and the patch did not get further updates. It turns out that current approach of relying on each arch to handle the page table sync manually is fragile because 1) it's easy to forget to sync the top level page table, and 2) it's also easy to overlook that the kernel should not access the vmemmap and direct mapping areas before the sync. # The solution: Make page table sync more code robust and harder to miss To address this, Dave Hansen suggested [3] [4] introducing {pgd,p4d}_populate_kernel() for updating kernel portion of the page tables and allow each architecture to explicitly perform synchronization when installing top-level entries. With this approach, we no longer need to worry about missing the sync step, reducing the risk of future regressions. The new interface reuses existing ARCH_PAGE_TABLE_SYNC_MASK, PGTBL_P*D_MODIFIED and arch_sync_kernel_mappings() facility used by vmalloc and ioremap to synchronize page tables. pgd_populate_kernel() looks like this: static inline void pgd_populate_kernel(unsigned long addr, pgd_t *pgd, p4d_t *p4d) { pgd_populate(&init_mm, pgd, p4d); if (ARCH_PAGE_TABLE_SYNC_MASK & PGTBL_PGD_MODIFIED) arch_sync_kernel_mappings(addr, addr); } It is worth noting that vmalloc() and apply_to_range() carefully synchronizes page tables by calling p*d_alloc_track() and arch_sync_kernel_mappings(), and thus they are not affected by ---truncated---\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-20 Improper Input Validation\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39845\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: x86/mm/64: define ARCH_PAGE_TABLE_SYNC_MASK and arch_sync_kernel_mappings() Define ARCH_PAGE_TABLE_SYNC_MASK and arch_sync_kernel_mappings() to ensure page tables are properly synchronized when calling p*d_populate_kernel(). For 5-level paging, synchronization is performed via pgd_populate_kernel(). In 4-level paging, pgd_populate() is a no-op, so synchronization is instead performed at the P4D level via p4d_populate_kernel(). This fixes intermittent boot failures on systems using 4-level paging and a large amount of persistent memory: BUG: unable to handle page fault for address: ffffe70000000034 #PF: supervisor write access in kernel mode #PF: error_code(0x0002) - not-present page PGD 0 P4D 0 Oops: 0002 [#1] SMP NOPTI RIP: 0010:__init_single_page+0x9/0x6d Call Trace: __init_zone_device_page+0x17/0x5d memmap_init_zone_device+0x154/0x1bb pagemap_range+0x2e0/0x40f memremap_pages+0x10b/0x2f0 devm_memremap_pages+0x1e/0x60 dev_dax_probe+0xce/0x2ec [device_dax] dax_bus_probe+0x6d/0xc9 [... snip ...] It also fixes a crash in vmemmap_set_pmd() caused by accessing vmemmap before sync_global_pgds() [1]: BUG: unable to handle page fault for address: ffffeb3ff1200000 #PF: supervisor write access in kernel mode #PF: error_code(0x0002) - not-present page PGD 0 P4D 0 Oops: Oops: 0002 [#1] PREEMPT SMP NOPTI Tainted: [W]=WARN RIP: 0010:vmemmap_set_pmd+0xff/0x230 vmemmap_populate_hugepages+0x176/0x180 vmemmap_populate+0x34/0x80 __populate_section_memmap+0x41/0x90 sparse_add_section+0x121/0x3e0 __add_pages+0xba/0x150 add_pages+0x1d/0x70 memremap_pages+0x3dc/0x810 devm_memremap_pages+0x1c/0x60 xe_devm_add+0x8b/0x100 [xe] xe_tile_init_noalloc+0x6a/0x70 [xe] xe_device_probe+0x48c/0x740 [xe] [... snip ...]\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-20 Improper Input Validation\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39846\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: pcmcia: Fix a NULL pointer dereference in __iodyn_find_io_region() In __iodyn_find_io_region(), pcmcia_make_resource() is assigned to res and used in pci_bus_alloc_resource(). There is a dereference of res in pci_bus_alloc_resource(), which could lead to a NULL pointer dereference on failure of pcmcia_make_resource(). Fix this bug by adding a check of res.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-20 Improper Input Validation\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39847\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: ppp: fix memory leak in pad_compress_skb If alloc_skb() fails in pad_compress_skb(), it returns NULL without releasing the old skb. The caller does: skb = pad_compress_skb(ppp, skb); if (!skb) goto drop; drop: kfree_skb(skb); When pad_compress_skb() returns NULL, the reference to the old skb is lost and kfree_skb(skb) ends up doing nothing, leading to a memory leak. Align pad_compress_skb() semantics with realloc(): only free the old skb if allocation and compression succeed. At the call site, use the new_skb variable so the original skb is not lost when pad_compress_skb() fails.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-772 Missing Release of Resource after Effective Lifetime\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39848\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: ax25: properly unshare skbs in ax25_kiss_rcv() Bernard Pidoux reported a regression apparently caused by commit c353e8983e0d (\"net: introduce per netns packet chains\"). skb->dev becomes NULL and we crash in __netif_receive_skb_core(). Before above commit, different kind of bugs or corruptions could happen without a major crash. But the root cause is that ax25_kiss_rcv() can queue/mangle input skb without checking if this skb is shared or not. Many thanks to Bernard Pidoux for his help, diagnosis and tests. We had a similar issue years ago fixed with commit 7aaed57c5c28 (\"phonet: properly unshare skbs in phonet_rcv()\").\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-20 Improper Input Validation\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39849\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: wifi: cfg80211: sme: cap SSID length in __cfg80211_connect_result() If the ssid->datalen is more than IEEE80211_MAX_SSID_LEN (32) it would lead to memory corruption so add some bounds checking.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-20 Improper Input Validation\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39853\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: i40e: Fix potential invalid access when MAC list is empty list_first_entry() never returns NULL - if the list is empty, it still returns a pointer to an invalid object, leading to potential invalid memory access when dereferenced. Fix this by using list_first_entry_or_null instead of list_first_entry.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-20 Improper Input Validation\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39857\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: net/smc: fix one NULL pointer dereference in smc_ib_is_sg_need_sync() BUG: kernel NULL pointer dereference, address: 00000000000002ec PGD 0 P4D 0 Oops: Oops: 0000 [#1] SMP PTI CPU: 28 UID: 0 PID: 343 Comm: kworker/28:1 Kdump: loaded Tainted: G OE 6.17.0-rc2+ #9 NONE Tainted: [O]=OOT_MODULE, [E]=UNSIGNED_MODULE Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.15.0-1 04/01/2014 Workqueue: smc_hs_wq smc_listen_work [smc] RIP: 0010:smc_ib_is_sg_need_sync+0x9e/0xd0 [smc] ... Call Trace: smcr_buf_map_link+0x211/0x2a0 [smc] __smc_buf_create+0x522/0x970 [smc] smc_buf_create+0x3a/0x110 [smc] smc_find_rdma_v2_device_serv+0x18f/0x240 [smc] ? smc_vlan_by_tcpsk+0x7e/0xe0 [smc] smc_listen_find_device+0x1dd/0x2b0 [smc] smc_listen_work+0x30f/0x580 [smc] process_one_work+0x18c/0x340 worker_thread+0x242/0x360 kthread+0xe7/0x220 ret_from_fork+0x13a/0x160 ret_from_fork_asm+0x1a/0x30 If the software RoCE device is used, ibdev->dma_device is a null pointer. As a result, the problem occurs. Null pointer detection is added to prevent problems.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-20 Improper Input Validation\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n7\nHIGH\nCVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39860\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: Bluetooth: Fix use-after-free in l2cap_sock_cleanup_listen() syzbot reported the splat below without a repro. In the splat, a single thread calling bt_accept_dequeue() freed sk and touched it after that. The root cause would be the racy l2cap_sock_cleanup_listen() call added by the cited commit. bt_accept_dequeue() is called under lock_sock() except for l2cap_sock_release(). Two threads could see the same socket during the list iteration in bt_accept_dequeue(): CPU1 CPU2 (close()) ---- ---- sock_hold(sk) sock_hold(sk); lock_sock(sk) <-- block close() sock_put(sk) bt_accept_unlink(sk) sock_put(sk) <-- refcnt by bt_accept_enqueue() release_sock(sk) lock_sock(sk) sock_put(sk) bt_accept_unlink(sk) sock_put(sk) <-- last refcnt bt_accept_unlink(sk) <-- UAF Depending on the timing, the other thread could show up in the \"Freed by task\" part. Let's call l2cap_sock_cleanup_listen() under lock_sock() in l2cap_sock_release(). [0]: BUG: KASAN: slab-use-after-free in debug_spin_lock_before kernel/locking/spinlock_debug.c:86 [inline] BUG: KASAN: slab-use-after-free in do_raw_spin_lock+0x26f/0x2b0 kernel/locking/spinlock_debug.c:115 Read of size 4 at addr ffff88803b7eb1c4 by task syz.5.3276/16995 CPU: 3 UID: 0 PID: 16995 Comm: syz.5.3276 Not tainted syzkaller #0 PREEMPT(full) Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2~bpo12+1 04/01/2014 Call Trace: __dump_stack lib/dump_stack.c:94 [inline] dump_stack_lvl+0x116/0x1f0 lib/dump_stack.c:120 print_address_description mm/kasan/report.c:378 [inline] print_report+0xcd/0x630 mm/kasan/report.c:482 kasan_report+0xe0/0x110 mm/kasan/report.c:595 debug_spin_lock_before kernel/locking/spinlock_debug.c:86 [inline] do_raw_spin_lock+0x26f/0x2b0 kernel/locking/spinlock_debug.c:115 spin_lock_bh include/linux/spinlock.h:356 [inline] release_sock+0x21/0x220 net/core/sock.c:3746 bt_accept_dequeue+0x505/0x600 net/bluetooth/af_bluetooth.c:312 l2cap_sock_cleanup_listen+0x5c/0x2a0 net/bluetooth/l2cap_sock.c:1451 l2cap_sock_release+0x5c/0x210 net/bluetooth/l2cap_sock.c:1425 __sock_release+0xb3/0x270 net/socket.c:649 sock_close+0x1c/0x30 net/socket.c:1439 __fput+0x3ff/0xb70 fs/file_table.c:468 task_work_run+0x14d/0x240 kernel/task_work.c:227 resume_user_mode_work include/linux/resume_user_mode.h:50 [inline] exit_to_user_mode_loop+0xeb/0x110 kernel/entry/common.c:43 exit_to_user_mode_prepare include/linux/irq-entry-common.h:225 [inline] syscall_exit_to_user_mode_work include/linux/entry-common.h:175 [inline] syscall_exit_to_user_mode include/linux/entry-common.h:210 [inline] do_syscall_64+0x3f6/0x4c0 arch/x86/entry/syscall_64.c:100 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7f2accf8ebe9 Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 a8 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007ffdb6cb1378 EFLAGS: 00000246 ORIG_RAX: 00000000000001b4 RAX: 0000000000000000 RBX: 00000000000426fb RCX: 00007f2accf8ebe9 RDX: 0000000000000000 RSI: 000000000000001e RDI: 0000000000000003 RBP: 00007f2acd1b7da0 R08: 0000000000000001 R09: 00000012b6cb166f R10: 0000001b30e20000 R11: 0000000000000246 R12: 00007f2acd1b609c R13: 00007f2acd1b6090 R14: ffffffffffffffff R15: 00007ffdb6cb1490 Allocated by task 5326: kasan_save_stack+0x33/0x60 mm/kasan/common.c:47 kasan_save_track+0x14/0x30 mm/kasan/common.c:68 poison_kmalloc_redzone mm/kasan/common.c:388 [inline] __kasan_kmalloc+0xaa/0xb0 mm/kasan/common.c:405 kasan_kmalloc include/linux/kasan.h:260 [inline] __do_kmalloc_node mm/slub.c:4365 [inline] __kmalloc_nopro ---truncated---\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-20 Improper Input Validation\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n7.1\nHIGH\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39864\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: wifi: cfg80211: fix use-after-free in cmp_bss() Following bss_free() quirk introduced in commit 776b3580178f (\"cfg80211: track hidden SSID networks properly\"), adjust cfg80211_update_known_bss() to free the last beacon frame elements only if they're not shared via the corresponding 'hidden_beacon_bss' pointer.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-20 Improper Input Validation\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n7.8\nHIGH\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39865\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: tee: fix NULL pointer dereference in tee_shm_put tee_shm_put have NULL pointer dereference: __optee_disable_shm_cache --> shm = reg_pair_to_ptr(...);//shm maybe return NULL tee_shm_free(shm); --> tee_shm_put(shm);//crash Add check in tee_shm_put to fix it. panic log: Unable to handle kernel paging request at virtual address 0000000000100cca Mem abort info: ESR = 0x0000000096000004 EC = 0x25: DABT (current EL), IL = 32 bits SET = 0, FnV = 0 EA = 0, S1PTW = 0 FSC = 0x04: level 0 translation fault Data abort info: ISV = 0, ISS = 0x00000004, ISS2 = 0x00000000 CM = 0, WnR = 0, TnD = 0, TagAccess = 0 GCS = 0, Overlay = 0, DirtyBit = 0, Xs = 0 user pgtable: 4k pages, 48-bit VAs, pgdp=0000002049d07000 [0000000000100cca] pgd=0000000000000000, p4d=0000000000000000 Internal error: Oops: 0000000096000004 [#1] SMP CPU: 2 PID: 14442 Comm: systemd-sleep Tainted: P OE ------- ---- 6.6.0-39-generic #38 Source Version: 938b255f6cb8817c95b0dd5c8c2944acfce94b07 Hardware name: greatwall GW-001Y1A-FTH, BIOS Great Wall BIOS V3.0 10/26/2022 pstate: 80000005 (Nzcv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--) pc : tee_shm_put+0x24/0x188 lr : tee_shm_free+0x14/0x28 sp : ffff001f98f9faf0 x29: ffff001f98f9faf0 x28: ffff0020df543cc0 x27: 0000000000000000 x26: ffff001f811344a0 x25: ffff8000818dac00 x24: ffff800082d8d048 x23: ffff001f850fcd18 x22: 0000000000000001 x21: ffff001f98f9fb88 x20: ffff001f83e76218 x19: ffff001f83e761e0 x18: 000000000000ffff x17: 303a30303a303030 x16: 0000000000000000 x15: 0000000000000003 x14: 0000000000000001 x13: 0000000000000000 x12: 0101010101010101 x11: 0000000000000001 x10: 0000000000000001 x9 : ffff800080e08d0c x8 : ffff001f98f9fb88 x7 : 0000000000000000 x6 : 0000000000000000 x5 : 0000000000000000 x4 : 0000000000000000 x3 : 0000000000000000 x2 : ffff001f83e761e0 x1 : 00000000ffff001f x0 : 0000000000100cca Call trace: tee_shm_put+0x24/0x188 tee_shm_free+0x14/0x28 __optee_disable_shm_cache+0xa8/0x108 optee_shutdown+0x28/0x38 platform_shutdown+0x28/0x40 device_shutdown+0x144/0x2b0 kernel_power_off+0x3c/0x80 hibernate+0x35c/0x388 state_store+0x64/0x80 kobj_attr_store+0x14/0x28 sysfs_kf_write+0x48/0x60 kernfs_fop_write_iter+0x128/0x1c0 vfs_write+0x270/0x370 ksys_write+0x6c/0x100 __arm64_sys_write+0x20/0x30 invoke_syscall+0x4c/0x120 el0_svc_common.constprop.0+0x44/0xf0 do_el0_svc+0x24/0x38 el0_svc+0x24/0x88 el0t_64_sync_handler+0x134/0x150 el0t_64_sync+0x14c/0x15\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-20 Improper Input Validation\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n7\nHIGH\nCVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39866\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: fs: writeback: fix use-after-free in __mark_inode_dirty() An use-after-free issue occurred when __mark_inode_dirty() get the bdi_writeback that was in the progress of switching. CPU: 1 PID: 562 Comm: systemd-random- Not tainted 6.6.56-gb4403bd46a8e #1 ...... pstate: 60400005 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) pc : __mark_inode_dirty+0x124/0x418 lr : __mark_inode_dirty+0x118/0x418 sp : ffffffc08c9dbbc0 ........ Call trace: __mark_inode_dirty+0x124/0x418 generic_update_time+0x4c/0x60 file_modified+0xcc/0xd0 ext4_buffered_write_iter+0x58/0x124 ext4_file_write_iter+0x54/0x704 vfs_write+0x1c0/0x308 ksys_write+0x74/0x10c __arm64_sys_write+0x1c/0x28 invoke_syscall+0x48/0x114 el0_svc_common.constprop.0+0xc0/0xe0 do_el0_svc+0x1c/0x28 el0_svc+0x40/0xe4 el0t_64_sync_handler+0x120/0x12c el0t_64_sync+0x194/0x198 Root cause is: systemd-random-seed kworker ---------------------------------------------------------------------- ___mark_inode_dirty inode_switch_wbs_work_fn spin_lock(&inode->i_lock); inode_attach_wb locked_inode_to_wb_and_lock_list get inode->i_wb spin_unlock(&inode->i_lock); spin_lock(&wb->list_lock) spin_lock(&inode->i_lock) inode_io_list_move_locked spin_unlock(&wb->list_lock) spin_unlock(&inode->i_lock) spin_lock(&old_wb->list_lock) inode_do_switch_wbs spin_lock(&inode->i_lock) inode->i_wb = new_wb spin_unlock(&inode->i_lock) spin_unlock(&old_wb->list_lock) wb_put_many(old_wb, nr_switched) cgwb_release old wb released wb_wakeup_delayed() accesses wb, then trigger the use-after-free issue Fix this race condition by holding inode spinlock until wb_wakeup_delayed() finished.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-416 Use After Free\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n7.8\nHIGH\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-40300\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: x86/vmscape: Add conditional IBPB mitigation VMSCAPE is a vulnerability that exploits insufficient branch predictor isolation between a guest and a userspace hypervisor (like QEMU). Existing mitigations already protect kernel/KVM from a malicious guest. Userspace can additionally be protected by flushing the branch predictors after a VMexit. Since it is the userspace that consumes the poisoned branch predictors, conditionally issue an IBPB after a VMexit and before returning to userspace. Workloads that frequently switch between hypervisor and userspace will incur the most overhead from the new IBPB. This new IBPB is not integrated with the existing IBPB sites. For instance, a task can use the existing speculation control prctl() to get an IBPB at context switch time. With this implementation, the IBPB is doubled up: one at context switch and another before running userspace. The intent is to integrate and optimize these cases post-embargo. [ dhansen: elaborate on suboptimal IBPB solution ]\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-402 Transmission of Private Resources into a New Sphere ('Resource Leak')\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n6.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-43368\n<div class=\"csaf-accordion-content\">\n\nA use-after-free issue was addressed with improved memory management. This issue is fixed in Safari 26, iOS 26 and iPadOS 26, macOS Tahoe 26. Processing maliciously crafted web content may lead to an unexpected Safari crash.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-416 Use After Free\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n4.3\nMEDIUM\nCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-47219\n<div class=\"csaf-accordion-content\">\n\nIn GStreamer through 1.26.1, the isomp4 plugin's qtdemux_parse_trak function may read past the end of a heap buffer while parsing an MP4 file, possibly leading to information disclosure.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-125 Out-of-bounds Read\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n8.1\nHIGH\nCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-48989\n<div class=\"csaf-accordion-content\">\n\nImproper Resource Shutdown or Release vulnerability in Apache Tomcat made Tomcat vulnerable to the made you reset attack. This issue affects Apache Tomcat: from 11.0.0-M1 through 11.0.9, from 10.1.0-M1 through 10.1.43 and from 9.0.0.M1 through 9.0.107. Older, EOL versions may also be affected. Users are recommended to upgrade to one of versions 11.0.10, 10.1.44 or 9.0.108 which fix the issue.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-404 Improper Resource Shutdown or Release\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n7.5\nHIGH\nCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-53057\n<div class=\"csaf-accordion-content\">\n\nVulnerability in the Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition product of Oracle Java SE (component: Security). Supported versions that are affected are Oracle Java SE: 8u461, 8u461-perf, 11.0.28, 17.0.16, 21.0.8, 25; Oracle GraalVM for JDK: 17.0.16 and 21.0.8; Oracle GraalVM Enterprise Edition: 21.3.15. Difficult to exploit vulnerability allows unauthenticated attacker with network access via multiple protocols to compromise Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition. Successful attacks of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition accessible data. Note: This vulnerability can be exploited by using APIs in the specified Component, e.g., through a web service which supplies data to the APIs. This vulnerability also applies to Java deployments, typically in clients running sandboxed Java Web Start applications or sandboxed Java applets, that load and run untrusted code (e.g., code that comes from the internet) and rely on the Java sandbox for security. CVSS 3.1 Base Score 5.9 (Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N).\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-284 Improper Access Control\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.9\nMEDIUM\nCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-53066\n<div class=\"csaf-accordion-content\">\n\nVulnerability in the Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition product of Oracle Java SE (component: JAXP). Supported versions that are affected are Oracle Java SE: 8u461, 8u461-perf, 11.0.28, 17.0.16, 21.0.8, 25; Oracle GraalVM for JDK: 17.0.16 and 21.0.8; Oracle GraalVM Enterprise Edition: 21.3.15. Easily exploitable vulnerability allows unauthenticated attacker with network access via multiple protocols to compromise Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition. Successful attacks of this vulnerability can result in unauthorized access to critical data or complete access to all Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition accessible data. Note: This vulnerability can be exploited by using APIs in the specified Component, e.g., through a web service which supplies data to the APIs. This vulnerability also applies to Java deployments, typically in clients running sandboxed Java Web Start applications or sandboxed Java applets, that load and run untrusted code (e.g., code that comes from the internet) and rely on the Java sandbox for security. CVSS 3.1 Base Score 7.5 (Confidentiality impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N).\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-200 Exposure of Sensitive Information to an Unauthorized Actor\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n7.5\nHIGH\nCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-55752\n<div class=\"csaf-accordion-content\">\n\nRelative Path Traversal vulnerability in Apache Tomcat. The fix for bug 60013 introduced a regression where the rewritten URL was normalized before it was decoded. This introduced the possibility that, for rewrite rules that rewrite query parameters to the URL, an attacker could manipulate the request URI to bypass security constraints including the protection for /WEB-INF/ and /META-INF/. If PUT requests were also enabled then malicious files could be uploaded leading to remote code execution. PUT requests are normally limited to trusted users and it is considered unlikely that PUT requests would be enabled in conjunction with a rewrite that manipulated the URI. This issue affects Apache Tomcat: from 11.0.0-M1 through 11.0.10, from 10.1.0-M1 through 10.1.44, from 9.0.0.M11 through 9.0.108. The following versions were EOL at the time the CVE was created but are known to be affected: 8.5.6 though 8.5.100. Other, older, EOL versions may also be affected. Users are recommended to upgrade to version 11.0.11 or later, 10.1.45 or later or 9.0.109 or later, which fix the issue.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-23 Relative Path Traversal\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n7.5\nHIGH\nCVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-55754\n<div class=\"csaf-accordion-content\">\n\nImproper Neutralization of Escape, Meta, or Control Sequences vulnerability in Apache Tomcat. Tomcat did not escape ANSI escape sequences in log messages. If Tomcat was running in a console on a Windows operating system, and the console supported ANSI escape sequences, it was possible for an attacker to use a specially crafted URL to inject ANSI escape sequences to manipulate the console and the clipboard and attempt to trick an administrator into running an attacker controlled command. While no attack vector was found, it may have been possible to mount this attack on other operating systems. This issue affects Apache Tomcat: from 11.0.0-M1 through 11.0.10, from 10.1.0-M1 through 10.1.44, from 9.0.40 through 9.0.108. The following versions were EOL at the time the CVE was created but are known to be affected: 8.5.60 though 8.5.100. Other, older, EOL versions may also be affected. Users are recommended to upgrade to version 11.0.11 or later, 10.1.45 or later or 9.0.109 or later, which fix the issue.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-150 Improper Neutralization of Escape, Meta, or Control Sequences\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n9.6\nCRITICAL\nCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-61748\n<div class=\"csaf-accordion-content\">\n\nVulnerability in the Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition product of Oracle Java SE (component: Libraries). Supported versions that are affected are Oracle Java SE: 21.0.8 and 25; Oracle GraalVM for JDK: 21.0.8; Oracle GraalVM Enterprise Edition: 21.3.15. Difficult to exploit vulnerability allows unauthenticated attacker with network access via multiple protocols to compromise Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition. Successful attacks of this vulnerability can result in unauthorized update, insert or delete access to some of Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition accessible data. Note: This vulnerability can be exploited by using APIs in the specified Component, e.g., through a web service which supplies data to the APIs. This vulnerability also applies to Java deployments, typically in clients running sandboxed Java Web Start applications or sandboxed Java applets, that load and run untrusted code (e.g., code that comes from the internet) and rely on the Java sandbox for security. CVSS 3.1 Base Score 3.7 (Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N).\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-284 Improper Access Control\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n3.7\nLOW\nCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-61795\n<div class=\"csaf-accordion-content\">\n\nImproper Resource Shutdown or Release vulnerability in Apache Tomcat. If an error occurred (including exceeding limits) during the processing of a multipart upload, temporary copies of the uploaded parts written to disc were not cleaned up immediately but left for the garbage collection process to delete. Depending on JVM settings, application memory usage and application load, it was possible that space for the temporary copies of uploaded parts would be filled faster than GC cleared it, leading to a DoS. This issue affects Apache Tomcat: from 11.0.0-M1 through 11.0.11, from 10.1.0-M1 through 10.1.46, from 9.0.0.M1 through 9.0.109. The following versions were EOL at the time the CVE was created but are known to be affected: 8.5.0 though 8.5.100. Other, older, EOL versions may also be affected. Users are recommended to upgrade to version 11.0.12 or later, 10.1.47 or later or 9.0.110 or later which fixes the issue.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-404 Improper Resource Shutdown or Release\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.3\nMEDIUM\nCVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2026-2673\n<div class=\"csaf-accordion-content\">\n\nIssue summary: An OpenSSL TLS 1.3 server may fail to negotiate the expected preferred key exchange group when its key exchange group configuration includes the default by using the 'DEFAULT' keyword. Impact summary: A less preferred key exchange may be used even when a more preferred group is supported by both client and server, if the group was not included among the client's initial predicated keyshares. This will sometimes be the case with the new hybrid post-quantum groups, if the client chooses to defer their use until specifically requested by the server. If an OpenSSL TLS 1.3 server's configuration uses the 'DEFAULT' keyword to interpolate the built-in default group list into its own configuration, perhaps adding or removing specific elements, then an implementation defect causes the 'DEFAULT' list to lose its 'tuple' structure, and all server-supported groups were treated as a single sufficiently secure 'tuple', with the server not sending a Hello Retry Request (HRR) even when a group in a more preferred tuple was mutually supported. As a result, the client and server might fail to negotiate a mutually supported post-quantum key agreement group, such as 'X25519MLKEM768', if the client's configuration results in only 'classical' groups (such as 'X25519' being the only ones in the client's initial keyshare prediction). OpenSSL 3.5 and later support a new syntax for selecting the most preferred TLS 1.3 key agreement group on TLS servers. The old syntax had a single 'flat' list of groups, and treated all the supported groups as sufficiently secure. If any of the keyshares predicted by the client were supported by the server the most preferred among these was selected, even if other groups supported by the client, but not included in the list of predicted keyshares would have been more preferred, if included. The new syntax partitions the groups into distinct 'tuples' of roughly equivalent security. Within each tuple the most preferred group included among the client's predicted keyshares is chosen, but if the client supports a group from a more preferred tuple, but did not predict any corresponding keyshares, the server will ask the client to retry the ClientHello (by issuing a Hello Retry Request or HRR) with the most preferred mutually supported group. The above works as expected when the server's configuration uses the built-in default group list, or explicitly defines its own list by directly defining the various desired groups and group 'tuples'. No OpenSSL FIPS modules are affected by this issue, the code in question lies outside the FIPS boundary. OpenSSL 3.6 and 3.5 are vulnerable to this issue. OpenSSL 3.6 users should upgrade to OpenSSL 3.6.2 once it is released. OpenSSL 3.5 users should upgrade to OpenSSL 3.5.6 once it is released. OpenSSL 3.4, 3.3, 3.0, 1.0.2 and 1.1.1 are not affected by this issue.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-757 Selection of Less-Secure Algorithm During Negotiation ('Algorithm Downgrade')\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n7.5\nHIGH\nCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2026-21925\n<div class=\"csaf-accordion-content\">\n\nVulnerability in the Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition product of Oracle Java SE (component: RMI). Supported versions that are affected are Oracle Java SE: 8u471, 8u471-b50, 8u471-perf, 11.0.29, 17.0.17, 21.0.9, 25.0.1; Oracle GraalVM for JDK: 17.0.17 and 21.0.9; Oracle GraalVM Enterprise Edition: 21.3.16. Difficult to exploit vulnerability allows unauthenticated attacker with network access via multiple protocols to compromise Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition. Successful attacks of this vulnerability can result in unauthorized update, insert or delete access to some of Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition accessible data as well as unauthorized read access to a subset of Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition accessible data. Note: This vulnerability can be exploited by using APIs in the specified Component, e.g., through a web service which supplies data to the APIs. This vulnerability also applies to Java deployments, typically in clients running sandboxed Java Web Start applications or sandboxed Java applets, that load and run untrusted code (e.g., code that comes from the internet) and rely on the Java sandbox for security. CVSS 3.1 Base Score 4.8 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N).\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-20 Improper Input Validation\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n4.8\nMEDIUM\nCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2026-21932\n<div class=\"csaf-accordion-content\">\n\nVulnerability in the Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition product of Oracle Java SE (component: AWT, JavaFX). Supported versions that are affected are Oracle Java SE: 8u471, 8u471-b50, 8u471-perf, 11.0.29, 17.0.17, 21.0.9, 25.0.1; Oracle GraalVM for JDK: 17.0.17 and 21.0.9; Oracle GraalVM Enterprise Edition: 21.3.16. Easily exploitable vulnerability allows unauthenticated attacker with network access via multiple protocols to compromise Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition. Successful attacks require human interaction from a person other than the attacker and while the vulnerability is in Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition accessible data. Note: This vulnerability applies to Java deployments, typically in clients running sandboxed Java Web Start applications or sandboxed Java applets, that load and run untrusted code (e.g., code that comes from the internet) and rely on the Java sandbox for security. This vulnerability does not apply to Java deployments, typically in servers, that load and run only trusted code (e.g., code installed by an administrator). CVSS 3.1 Base Score 7.4 (Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:N/I:H/A:N).\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-20 Improper Input Validation\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n7.4\nHIGH\nCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:N/I:H/A:N\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2026-21933\n<div class=\"csaf-accordion-content\">\n\nVulnerability in the Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition product of Oracle Java SE (component: Networking). Supported versions that are affected are Oracle Java SE: 8u471, 8u471-b50, 8u471-perf, 11.0.29, 17.0.17, 21.0.9, 25.0.1; Oracle GraalVM for JDK: 17.0.17 and 21.0.9; Oracle GraalVM Enterprise Edition: 21.3.16. Easily exploitable vulnerability allows unauthenticated attacker with network access via multiple protocols to compromise Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition. Successful attacks require human interaction from a person other than the attacker and while the vulnerability is in Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in unauthorized update, insert or delete access to some of Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition accessible data as well as unauthorized read access to a subset of Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition accessible data. Note: This vulnerability can be exploited by using APIs in the specified Component, e.g., through a web service which supplies data to the APIs. This vulnerability also applies to Java deployments, typically in clients running sandboxed Java Web Start applications or sandboxed Java applets, that load and run untrusted code (e.g., code that comes from the internet) and rely on the Java sandbox for security. CVSS 3.1 Base Score 6.1 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N).\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-20 Improper Input Validation\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n6.1\nMEDIUM\nCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2026-21945\n<div class=\"csaf-accordion-content\">\n\nVulnerability in the Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition product of Oracle Java SE (component: Security). Supported versions that are affected are Oracle Java SE: 8u471, 8u471-b50, 8u471-perf, 11.0.29, 17.0.17, 21.0.9, 25.0.1; Oracle GraalVM for JDK: 17.0.17 and 21.0.9; Oracle GraalVM Enterprise Edition: 21.3.16. Easily exploitable vulnerability allows unauthenticated attacker with network access via multiple protocols to compromise Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition. Successful attacks of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition. Note: This vulnerability applies to Java deployments, typically in clients running sandboxed Java Web Start applications or sandboxed Java applets, that load and run untrusted code (e.g., code that comes from the internet) and rely on the Java sandbox for security. This vulnerability does not apply to Java deployments, typically in servers, that load and run only trusted code (e.g., code installed by an administrator). CVSS 3.1 Base Score 7.5 (Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H).\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-400 Uncontrolled Resource Consumption\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n7.5\nHIGH\nCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2026-21947\n<div class=\"csaf-accordion-content\">\n\nVulnerability in Oracle Java SE (component: JavaFX). Supported versions that are affected are Oracle Java SE: 8u471-b50. Difficult to exploit vulnerability allows unauthenticated attacker with network access via multiple protocols to compromise Oracle Java SE. Successful attacks require human interaction from a person other than the attacker. Successful attacks of this vulnerability can result in unauthorized update, insert or delete access to some of Oracle Java SE accessible data. Note: This vulnerability applies to Java deployments, typically in clients running sandboxed Java Web Start applications or sandboxed Java applets, that load and run untrusted code (e.g., code that comes from the internet) and rely on the Java sandbox for security. This vulnerability does not apply to Java deployments, typically in servers, that load and run only trusted code (e.g., code installed by an administrator). CVSS 3.1 Base Score 3.1 (Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:L/A:N).\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-79 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n3.1\nLOW\nCVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:L/A:N\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2026-22924\n<div class=\"csaf-accordion-content\">\n\nThe affected application does not properly restrict unauthenticated connections and is susceptible to resource exhaustion conditions. This could allow an attacker to disrupt normal operations or perform unauthorized actions, potentially impacting system availability and integrity.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-306 Missing Authentication for Critical Function\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n9.1\nCRITICAL\nCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2026-22925\n<div class=\"csaf-accordion-content\">\n\nThe affected application is susceptible to resource exhaustion when subjected to high volume of TCP SYN packets This could allow an attacker to render the service unavailable and cause denial-of-service conditions by overwhelming system resources.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-770 Allocation of Resources Without Limits or Throttling\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n7.5\nHIGH\nCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2026-28387\n<div class=\"csaf-accordion-content\">\n\nIssue summary: An uncommon configuration of clients performing DANE TLSA-based server authentication, when paired with uncommon server DANE TLSA records, may result in a use-after-free and/or double-free on the client side. Impact summary: A use after free can have a range of potential consequences such as the corruption of valid data, crashes or execution of arbitrary code. However, the issue only affects clients that make use of TLSA records with both the PKIX-TA(0/PKIX-EE(1) certificate usages and the DANE-TA(2) certificate usage. By far the most common deployment of DANE is in SMTP MTAs for which RFC7672 recommends that clients treat as 'unusable' any TLSA records that have the PKIX certificate usages. These SMTP (or other similar) clients are not vulnerable to this issue. Conversely, any clients that support only the PKIX usages, and ignore the DANE-TA(2) usage are also not vulnerable. The client would also need to be communicating with a server that publishes a TLSA RRset with both types of TLSA records. No FIPS modules are affected by this issue, the problem code is outside the FIPS module boundary.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-416 Use After Free\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n7\nHIGH\nCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2026-28388\n<div class=\"csaf-accordion-content\">\n\nIssue summary: When a delta CRL that contains a Delta CRL Indicator extension is processed a NULL pointer dereference might happen if the required CRL Number extension is missing. Impact summary: A NULL pointer dereference can trigger a crash which leads to a Denial of Service for an application. When CRL processing and delta CRL processing is enabled during X.509 certificate verification, the delta CRL processing does not check whether the CRL Number extension is NULL before dereferencing it. When a malformed delta CRL file is being processed, this parameter can be NULL, causing a NULL pointer dereference. Exploiting this issue requires the X509_V_FLAG_USE_DELTAS flag to be enabled in the verification context, the certificate being verified to contain a freshestCRL extension or the base CRL to have the EXFLAG_FRESHEST flag set, and an attacker to provide a malformed CRL to an application that processes it. The vulnerability is limited to Denial of Service and cannot be escalated to achieve code execution or memory disclosure. For that reason the issue was assessed as Low severity according to our Security Policy. The FIPS modules in 3.6, 3.5, 3.4, 3.3 and 3.0 are not affected by this issue, as the affected code is outside the OpenSSL FIPS module boundary.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-476 NULL Pointer Dereference\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n7.5\nHIGH\nCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2026-28389\n<div class=\"csaf-accordion-content\">\n\nIssue summary: During processing of a crafted CMS EnvelopedData message with KeyAgreeRecipientInfo a NULL pointer dereference can happen. Impact summary: Applications that process attacker-controlled CMS data may crash before authentication or cryptographic operations occur resulting in Denial of Service. When a CMS EnvelopedData message that uses KeyAgreeRecipientInfo is processed, the optional parameters field of KeyEncryptionAlgorithmIdentifier is examined without checking for its presence. This results in a NULL pointer dereference if the field is missing. Applications and services that call CMS_decrypt() on untrusted input (e.g., S/MIME processing or CMS-based protocols) are vulnerable. The FIPS modules in 3.6, 3.5, 3.4, 3.3 and 3.0 are not affected by this issue, as the affected code is outside the OpenSSL FIPS module boundary.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-476 NULL Pointer Dereference\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n7.5\nHIGH\nCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2026-28390\n<div class=\"csaf-accordion-content\">\n\nIssue summary: During processing of a crafted CMS EnvelopedData message with KeyTransportRecipientInfo a NULL pointer dereference can happen. Impact summary: Applications that process attacker-controlled CMS data may crash before authentication or cryptographic operations occur resulting in Denial of Service. When a CMS EnvelopedData message that uses KeyTransportRecipientInfo with RSA-OAEP encryption is processed, the optional parameters field of RSA-OAEP SourceFunc algorithm identifier is examined without checking for its presence. This results in a NULL pointer dereference if the field is missing. Applications and services that call CMS_decrypt() on untrusted input (e.g., S/MIME processing or CMS-based protocols) are vulnerable. The FIPS modules in 3.6, 3.5, 3.4, 3.3 and 3.0 are not affected by this issue, as the affected code is outside the OpenSSL FIPS module boundary.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-476 NULL Pointer Dereference\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n7.5\nHIGH\nCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2026-31789\n<div class=\"csaf-accordion-content\">\n\nIssue summary: Converting an excessively large OCTET STRING value to a hexadecimal string leads to a heap buffer overflow on 32 bit platforms. Impact summary: A heap buffer overflow may lead to a crash or possibly an attacker controlled code execution or other undefined behavior. If an attacker can supply a crafted X.509 certificate with an excessively large OCTET STRING value in extensions such as the Subject Key Identifier (SKID) or Authority Key Identifier (AKID) which are being converted to hex, the size of the buffer needed for the result is calculated as multiplication of the input length by 3. On 32 bit platforms, this multiplication may overflow resulting in the allocation of a smaller buffer and a heap buffer overflow. Applications and services that print or log contents of untrusted X.509 certificates are vulnerable to this issue. As the certificates would have to have sizes of over 1 Gigabyte, printing or logging such certificates is a fairly unlikely operation and only 32 bit platforms are affected, this issue was assigned Low severity. The FIPS modules in 3.6, 3.5, 3.4, 3.3 and 3.0 are not affected by this issue, as the affected code is outside the OpenSSL FIPS module boundary.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-787 Out-of-bounds Write\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n7\nHIGH\nCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2026-31790\n<div class=\"csaf-accordion-content\">\n\nIssue summary: Applications using RSASVE key encapsulation to establish a secret encryption key can send contents of an uninitialized memory buffer to a malicious peer. Impact summary: The uninitialized buffer might contain sensitive data from the previous execution of the application process which leads to sensitive data leakage to an attacker. RSA_public_encrypt() returns the number of bytes written on success and -1 on error. The affected code tests only whether the return value is non-zero. As a result, if RSA encryption fails, encapsulation can still return success to the caller, set the output lengths, and leave the caller to use the contents of the ciphertext buffer as if a valid KEM ciphertext had been produced. If applications use EVP_PKEY_encapsulate() with RSA/RSASVE on an attacker-supplied invalid RSA public key without first validating that key, then this may cause stale or uninitialized contents of the caller-provided ciphertext buffer to be disclosed to the attacker in place of the KEM ciphertext. As a workaround calling EVP_PKEY_public_check() or EVP_PKEY_public_check_quick() before EVP_PKEY_encapsulate() will mitigate the issue. The FIPS modules in 3.6, 3.5, 3.4, 3.3, 3.1 and 3.0 are affected by this issue.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-754 Improper Check for Unusual or Exceptional Conditions\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n7.5\nHIGH\nCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N\n\n\n\n</div>\n</div>\n</div>\n</div>\n\n\n\nAcknowledgments\n\n\n\nSiemens ProductCERT reported these vulnerabilities to CISA.\n\n\n\n\nGeneral Recommendations\n\nAs a general security measure, Siemens strongly recommends to protect network access to devices with appropriate mechanisms. In order to operate the devices in a protected IT environment, Siemens recommends to configure the environment according to Siemens' operational guidelines for Industrial Security (Download: https://www.siemens.com/cert/operational-guidelines-industrial-security), and to follow the recommendations in the product manuals. Additional information on Industrial Security by Siemens can be found at: https://www.siemens.com/industrialsecurity\n\n\n\nAdditional Resources\n\nFor further inquiries on security vulnerabilities in Siemens products and solutions, please contact the Siemens ProductCERT: https://www.siemens.com/cert/advisories\n\n\n\nTerms of Use\n\nThe use of Siemens Security Advisories is subject to the terms and conditions listed on: https://www.siemens.com/productcert/terms-of-use.\n\n\n\nLegal Notice and Terms of Use\n\nThis product is provided subject to this Notification (https://www.cisa.gov/notification) and this Privacy & Use policy (https://www.cisa.gov/privacy-policy).\n\n\n\nRecommended Practices\n\nCISA recommends users take defensive measures to minimize the exploitation risk of this vulnerability.\n\nMinimize network exposure for all control system devices and/or systems, and ensure they are not accessible from the internet.\n\nLocate control system networks and remote devices behind firewalls and isolate them from business networks.\n\nWhen remote access is required, use more secure methods, such as Virtual Private Networks (VPNs), recognizing VPNs may have vulnerabilities and should be updated to the most recent version available. Also recognize VPN is only as secure as its connected devices.\n\nCISA reminds organizations to perform proper impact analysis and risk assessment prior to deploying defensive measures.\n\nCISA also provides a section for control systems security recommended practices on the ICS webpage on cisa.gov. Several CISA products detailing cyber defense best practices are available for reading and download, including Improving Industrial Control Systems Cybersecurity with Defense-in-Depth Strategies.\n\nCISA encourages organizations to implement recommended cybersecurity strategies for proactive defense of ICS assets. Additional mitigation guidance and recommended practices are publicly available on the ICS webpage at cisa.gov in the technical information paper, ICS-TIP-12-146-01B--Targeted Cyber Intrusion Detection and Mitigation Strategies.\n\nOrganizations observing suspected malicious activity should follow established internal procedures and report findings to CISA for tracking and correlation against other incidents.\n\n\n\nAdvisory Conversion Disclaimer\n\nThis ICSA is a verbatim republication of Siemens ProductCERT SSA-032379 from a direct conversion of the vendor's Common Security Advisory Framework (CSAF) advisory. This is republished to CISA's website as a means of increasing visibility and is provided \"as-is\" for informational purposes only. CISA is not responsible for the editorial or technical accuracy of republished advisories and provides no warranties of any kind regarding any information contained within this advisory. Further, CISA does not endorse any commercial product or service. Please contact Siemens ProductCERT directly for any questions regarding this advisory.\n\nRevision History\n\n\n\nInitial Release Date: 2026-05-12\n\n\n\n\n\nDate\nRevision\nSummary\n\n\n\n\n2026-05-12\n1\nPublication Date\n\n\n2026-05-14\n2\nInitial CISA Republication of Siemens ProductCERT SSA-032379 advisory\n\n\n\n\n\n\nLegal Notice and Terms of Use", "creation_timestamp": "2026-05-14T10:00:00.000000Z"}, {"uuid": "78301fec-5383-45a4-927a-74e3ca455385", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37968", "type": "seen", "source": "https://www.cisa.gov/news-events/ics-advisories/icsa-26-134-10", "content": "View CSAF\n\nSummary\n\nSIMATIC CN 4100 contains multiple vulnerabilities which could potentially lead to a compromise in availability, integrity and confidentiality. Siemens has released a new version for SIMATIC CN 4100 and recommends to update to the latest version.\n\nThe following versions of Siemens SIMATIC are affected:\n\n\n\nSIMATIC CN 4100 vers:intdot/<5.0 \n\n<div class=\"csaf-table\">\n\n\n\n\nCVSS\nVendor\nEquipment\nVulnerabilities\n\n\n\n\nv3 9.6\nSiemens\nSiemens SIMATIC\nNULL Pointer Dereference, Reachable Assertion, Use After Free, Out-of-bounds Write, Integer Overflow or Wraparound, Allocation of Resources Without Limits or Throttling, Out-of-bounds Read, Covert Timing Channel, Stack-based Buffer Overflow, Inefficient Algorithmic Complexity, Missing Release of Memory after Effective Lifetime, Improper Restriction of Operations within the Bounds of a Memory Buffer, Improper Input Validation, Improper Locking, Uncontrolled Recursion, Buffer Access with Incorrect Length Value, Race Condition within a Thread, Missing Synchronization, Use of Uninitialized Resource, Double Free, Missing Release of Resource after Effective Lifetime, Loop with Unreachable Exit Condition ('Infinite Loop'), Improper Update of Reference Count, Improper Control of a Resource Through its Lifetime, Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition'), Unexpected Status Code or Return Value, Divide By Zero, Improper Validation of Specified Index, Position, or Offset in Input, Comparison Using Wrong Factors, Observable Timing Discrepancy, Improper Validation of Syntactic Correctness of Input, Deadlock, Signal Handler Race Condition, Improper Following of Specification by Caller, Improper Check for Dropped Privileges, Transmission of Private Resources into a New Sphere ('Resource Leak'), Improper Resource Shutdown or Release, Improper Access Control, Exposure of Sensitive Information to an Unauthorized Actor, Relative Path Traversal, Improper Neutralization of Escape, Meta, or Control Sequences, Selection of Less-Secure Algorithm During Negotiation ('Algorithm Downgrade'), Uncontrolled Resource Consumption, Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting'), Missing Authentication for Critical Function, Improper Check for Unusual or Exceptional Conditions\n\n\n\n</div>\n\nBackground\n\n\n\nCritical Infrastructure Sectors: Critical Manufacturing\n\nCountries/Areas Deployed: Worldwide\n\nCompany Headquarters Location: Germany\n\n\n\n\nVulnerabilities\n<div class=\"csaf-accordion\">\n\nExpand All +\n<div class=\"csaf-accordion-item\">\n\nCVE-2024-47704\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Check link_res->hpo_dp_link_enc before using it [WHAT & HOW] Functions dp_enable_link_phy and dp_disable_link_phy can pass link_res without initializing hpo_dp_link_enc and it is necessary to check for null before dereferencing. This fixes 2 FORWARD_NULL issues reported by Coverity.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-476 NULL Pointer Dereference\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2024-57924\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: fs: relax assertions on failure to encode file handles Encoding file handles is usually performed by a filesystem >encode_fh() method that may fail for various reasons. The legacy users of exportfs_encode_fh(), namely, nfsd and name_to_handle_at(2) syscall are ready to cope with the possibility of failure to encode a file handle. There are a few other users of exportfs_encode_{fh,fid}() that currently have a WARN_ON() assertion when ->encode_fh() fails. Relax those assertions because they are wrong. The second linked bug report states commit 16aac5ad1fa9 (\"ovl: support encoding non-decodable file handles\") in v6.6 as the regressing commit, but this is not accurate. The aforementioned commit only increases the chances of the assertion and allows triggering the assertion with the reproducer using overlayfs, inotify and drop_caches. Triggering this assertion was always possible with other filesystems and other reasons of ->encode_fh() failures and more particularly, it was also possible with the exact same reproducer using overlayfs that is mounted with options index=on,nfs_export=on also on kernels < v6.6. Therefore, I am not listing the aforementioned commit as a Fixes commit. Backport hint: this patch will have a trivial conflict applying to v6.6.y, and other trivial conflicts applying to stable kernels < v6.6.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-617 Reachable Assertion\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2024-58240\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: tls: separate no-async decryption request handling from async If we're not doing async, the handling is much simpler. There's no reference counting, we just need to wait for the completion to wake us up and return its result. We should preferably also use a separate crypto_wait. I'm not seeing a UAF as I did in the past, I think aec7961916f3 (\"tls: fix race between async notify and socket close\") took care of it. This will make the next fix easier.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-416 Use After Free\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n7.3\nHIGH\nCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-6021\n<div class=\"csaf-accordion-content\">\n\nA flaw was found in libxml2's xmlBuildQName function, where integer overflows in buffer size calculations can lead to a stack-based buffer overflow. This issue can result in memory corruption or a denial of service when processing crafted input.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-787 Out-of-bounds Write\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n7.5\nHIGH\nCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-6052\n<div class=\"csaf-accordion-content\">\n\nA flaw was found in how GLib\u2019s GString manages memory when adding data to strings. If a string is already very large, combining it with more input can cause a hidden overflow in the size calculation. This makes the system think it has enough memory when it doesn\u2019t. As a result, data may be written past the end of the allocated memory, leading to crashes or memory corruption.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-190 Integer Overflow or Wraparound\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n3.7\nLOW\nCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-7425\n<div class=\"csaf-accordion-content\">\n\nA flaw was found in libxslt where the attribute type, atype, flags are modified in a way that corrupts internal memory management. When XSLT functions, such as the key() process, result in tree fragments, this corruption prevents the proper cleanup of ID attributes. As a result, the system may access freed memory, causing crashes or enabling attackers to trigger heap corruption.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-416 Use After Free\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n7.8\nHIGH\nCVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:C/C:N/I:H/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-8916\n<div class=\"csaf-accordion-content\">\n\nAllocation of Resources Without Limits or Throttling vulnerability in Legion of the Bouncy Castle Inc. BC Java bcpkix on All (API modules), Legion of the Bouncy Castle Inc. BC Java bcprov on All (API modules), Legion of the Bouncy Castle Inc. BCPKIX FIPS bcpkix-fips on All (API modules) allows Excessive Allocation. This vulnerability is associated with program files https://github.Com/bcgit/bc-java/blob/main/pkix/src/main/java/org/bouncycastle/pkix/jcajce/PKIXCertPathReviewer.Java, https://github.Com/bcgit/bc-java/blob/main/prov/src/main/java/org/bouncycastle/x509/PKIXCertPathReviewer.Java. This issue affects BC Java: from 1.44 through 1.78; BC Java: from 1.44 through 1.78; BCPKIX FIPS: from 1.0.0 through 1.0.7, from 2.0.0 through 2.0.7.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-770 Allocation of Resources Without Limits or Throttling\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.3\nMEDIUM\nCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-9230\n<div class=\"csaf-accordion-content\">\n\nIssue summary: An application trying to decrypt CMS messages encrypted using password based encryption can trigger an out-of-bounds read and write. Impact summary: This out-of-bounds read may trigger a crash which leads to Denial of Service for an application. The out-of-bounds write can cause a memory corruption which can have various consequences including a Denial of Service or Execution of attacker-supplied code. Although the consequences of a successful exploit of this vulnerability could be severe, the probability that the attacker would be able to perform it is low. Besides, password based (PWRI) encryption support in CMS messages is very rarely used. For that reason the issue was assessed as Moderate severity according to our Security Policy. The FIPS modules in 3.5, 3.4, 3.3, 3.2, 3.1 and 3.0 are not affected by this issue, as the CMS implementation is outside the OpenSSL FIPS module boundary.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-125 Out-of-bounds Read\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n7.5\nHIGH\nCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-9231\n<div class=\"csaf-accordion-content\">\n\nIssue summary: A timing side-channel which could potentially allow remote recovery of the private key exists in the SM2 algorithm implementation on 64 bit ARM platforms. Impact summary: A timing side-channel in SM2 signature computations on 64 bit ARM platforms could allow recovering the private key by an attacker.. While remote key recovery over a network was not attempted by the reporter, timing measurements revealed a timing signal which may allow such an attack. OpenSSL does not directly support certificates with SM2 keys in TLS, and so this CVE is not relevant in most TLS contexts. However, given that it is possible to add support for such certificates via a custom provider, coupled with the fact that in such a custom provider context the private key may be recoverable via remote timing measurements, we consider this to be a Moderate severity issue. The FIPS modules in 3.5, 3.4, 3.3, 3.2, 3.1 and 3.0 are not affected by this issue, as SM2 is not an approved algorithm.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-385 Covert Timing Channel\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n6.5\nMEDIUM\nCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:L\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-9232\n<div class=\"csaf-accordion-content\">\n\nIssue summary: An application using the OpenSSL HTTP client API functions may trigger an out-of-bounds read if the 'no_proxy' environment variable is set and the host portion of the authority component of the HTTP URL is an IPv6 address. Impact summary: An out-of-bounds read can trigger a crash which leads to Denial of Service for an application. The OpenSSL HTTP client API functions can be used directly by applications but they are also used by the OCSP client functions and CMP (Certificate Management Protocol) client implementation in OpenSSL. However the URLs used by these implementations are unlikely to be controlled by an attacker. In this vulnerable code the out of bounds read can only trigger a crash. Furthermore the vulnerability requires an attacker-controlled URL to be passed from an application to the OpenSSL function and the user has to have a 'no_proxy' environment variable set. For the aforementioned reasons the issue was assessed as Low severity. The vulnerable code was introduced in the following patch releases: 3.0.16, 3.1.8, 3.2.4, 3.3.3, 3.4.0 and 3.5.0. The FIPS modules in 3.5, 3.4, 3.3, 3.2, 3.1 and 3.0 are not affected by this issue, as the HTTP client implementation is outside the OpenSSL FIPS module boundary.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-125 Out-of-bounds Read\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.9\nMEDIUM\nCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-9820\n<div class=\"csaf-accordion-content\">\n\nA flaw was found in the GnuTLS library, specifically in the gnutls_pkcs11_token_init() function that handles PKCS#11 token initialization. When a token label longer than expected is processed, the function writes past the end of a fixed-size stack buffer. This programming error can cause the application using GnuTLS to crash or, in certain conditions, be exploited for code execution. As a result, systems or applications relying on GnuTLS may be vulnerable to a denial of service or local privilege escalation attacks.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-121 Stack-based Buffer Overflow\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n4\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-14831\n<div class=\"csaf-accordion-content\">\n\nA flaw was found in GnuTLS. This vulnerability allows a denial of service (DoS) by excessive CPU (Central Processing Unit) and memory consumption via specially crafted malicious certificates containing a large number of name constraints and subject alternative names (SANs).\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-407 Inefficient Algorithmic Complexity\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.3\nMEDIUM\nCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-23143\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: net: Fix null-ptr-deref by sock_lock_init_class_and_name() and rmmod. When I ran the repro [0] and waited a few seconds, I observed two LOCKDEP splats: a warning immediately followed by a null-ptr-deref. [1] Reproduction Steps: 1) Mount CIFS 2) Add an iptables rule to drop incoming FIN packets for CIFS 3) Unmount CIFS 4) Unload the CIFS module 5) Remove the iptables rule At step 3), the CIFS module calls sock_release() for the underlying TCP socket, and it returns quickly. However, the socket remains in FIN_WAIT_1 because incoming FIN packets are dropped. At this point, the module's refcnt is 0 while the socket is still alive, so the following rmmod command succeeds. # ss -tan State Recv-Q Send-Q Local Address:Port Peer Address:Port FIN-WAIT-1 0 477 10.0.2.15:51062 10.0.0.137:445 # lsmod | grep cifs cifs 1159168 0 This highlights a discrepancy between the lifetime of the CIFS module and the underlying TCP socket. Even after CIFS calls sock_release() and it returns, the TCP socket does not die immediately in order to close the connection gracefully. While this is generally fine, it causes an issue with LOCKDEP because CIFS assigns a different lock class to the TCP socket's sk->sk_lock using sock_lock_init_class_and_name(). Once an incoming packet is processed for the socket or a timer fires, sk->sk_lock is acquired. Then, LOCKDEP checks the lock context in check_wait_context(), where hlock_class() is called to retrieve the lock class. However, since the module has already been unloaded, hlock_class() logs a warning and returns NULL, triggering the null-ptr-deref. If LOCKDEP is enabled, we must ensure that a module calling sock_lock_init_class_and_name() (CIFS, NFS, etc) cannot be unloaded while such a socket is still alive to prevent this issue. Let's hold the module reference in sock_lock_init_class_and_name() and release it when the socket is freed in sk_prot_free(). Note that sock_lock_init() clears sk->sk_owner for svc_create_socket() that calls sock_lock_init_class_and_name() for a listening socket, which clones a socket by sk_clone_lock() without GFP_ZERO. [0]: CIFS_SERVER=\"10.0.0.137\" CIFS_PATH=\"//${CIFS_SERVER}/Users/Administrator/Desktop/CIFS_TEST\" DEV=\"enp0s3\" CRED=\"/root/WindowsCredential.txt\" MNT=$(mktemp -d /tmp/XXXXXX) mount -t cifs ${CIFS_PATH} ${MNT} -o vers=3.0,credentials=${CRED},cache=none,echo_interval=1 iptables -A INPUT -s ${CIFS_SERVER} -j DROP for i in $(seq 10); do umount ${MNT} rmmod cifs sleep 1 done rm -r ${MNT} iptables -D INPUT -s ${CIFS_SERVER} -j DROP [1]: DEBUG_LOCKS_WARN_ON(1) WARNING: CPU: 10 PID: 0 at kernel/locking/lockdep.c:234 hlock_class (kernel/locking/lockdep.c:234 kernel/locking/lockdep.c:223) Modules linked in: cifs_arc4 nls_ucs2_utils cifs_md4 [last unloaded: cifs] CPU: 10 UID: 0 PID: 0 Comm: swapper/10 Not tainted 6.14.0 #36 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.16.0-0-gd239552ce722-prebuilt.qemu.org 04/01/2014 RIP: 0010:hlock_class (kernel/locking/lockdep.c:234 kernel/locking/lockdep.c:223) ... Call Trace: __lock_acquire (kernel/locking/lockdep.c:4853 kernel/locking/lockdep.c:5178) lock_acquire (kernel/locking/lockdep.c:469 kernel/locking/lockdep.c:5853 kernel/locking/lockdep.c:5816) _raw_spin_lock_nested (kernel/locking/spinlock.c:379) tcp_v4_rcv (./include/linux/skbuff.h:1678 ./include/net/tcp.h:2547 net/ipv4/tcp_ipv4.c:2350) ... BUG: kernel NULL pointer dereference, address: 00000000000000c4 PF: supervisor read access in kernel mode PF: error_code(0x0000) - not-present page PGD 0 Oops: Oops: 0000 [#1] PREEMPT SMP NOPTI CPU: 10 UID: 0 PID: 0 Comm: swapper/10 Tainted: G W 6.14.0 #36 Tainted: [W]=WARN Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.16.0-0-gd239552ce722-prebuilt.qemu.org 04/01/2014 RIP: 0010:__lock_acquire (kernel/ ---truncated---\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-476 NULL Pointer Dereference\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-23160\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: media: mediatek: vcodec: Fix a resource leak related to the scp device in FW initialization On Mediatek devices with a system companion processor (SCP) the mtk_scp structure has to be removed explicitly to avoid a resource leak. Free the structure in case the allocation of the firmware structure fails during the firmware initialization.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-401 Missing Release of Memory after Effective Lifetime\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-31257\n<div class=\"csaf-accordion-content\">\n\nThis issue was addressed with improved memory handling. This issue is fixed in Safari 18.5, iOS 18.5 and iPadOS 18.5, macOS Sequoia 15.5, tvOS 18.5, visionOS 2.5, watchOS 11.5. Processing maliciously crafted web content may lead to an unexpected Safari crash.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n4.7\nMEDIUM\nCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:N/I:N/A:L\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-37931\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: btrfs: adjust subpage bit start based on sectorsize When running machines with 64k page size and a 16k nodesize we started seeing tree log corruption in production. This turned out to be because we were not writing out dirty blocks sometimes, so this in fact affects all metadata writes. When writing out a subpage EB we scan the subpage bitmap for a dirty range. If the range isn't dirty we do bit_start++; to move onto the next bit. The problem is the bitmap is based on the number of sectors that an EB has. So in this case, we have a 64k pagesize, 16k nodesize, but a 4k sectorsize. This means our bitmap is 4 bits for every node. With a 64k page size we end up with 4 nodes per page. To make this easier this is how everything looks [0 16k 32k 48k ] logical address [0 4 8 12 ] radix tree offset [ 64k page ] folio [ 16k eb ][ 16k eb ][ 16k eb ][ 16k eb ] extent buffers [ | | | | | | | | | | | | | | | | ] bitmap Now we use all of our addressing based on fs_info->sectorsize_bits, so as you can see the above our 16k eb->start turns into radix entry 4. When we find a dirty range for our eb, we correctly do bit_start += sectors_per_node, because if we start at bit 0, the next bit for the next eb is 4, to correspond to eb->start 16k. However if our range is clean, we will do bit_start++, which will now put us offset from our radix tree entries. In our case, assume that the first time we check the bitmap the block is not dirty, we increment bit_start so now it == 1, and then we loop around and check again. This time it is dirty, and we go to find that start using the following equation start = folio_start + bit_start * fs_info->sectorsize; so in the case above, eb->start 0 is now dirty, and we calculate start as 0 + 1 * fs_info->sectorsize = 4096 4096 >> 12 = 1 Now we're looking up the radix tree for 1, and we won't find an eb. What's worse is now we're using bit_start == 1, so we do bit_start += sectors_per_node, which is now 5. If that eb is dirty we will run into the same thing, we will look at an offset that is not populated in the radix tree, and now we're skipping the writeout of dirty extent buffers. The best fix for this is to not use sectorsize_bits to address nodes, but that's a larger change. Since this is a fs corruption problem fix it simply by always using sectors_per_node to increment the start bit.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-20 Improper Input Validation\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-37968\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: iio: light: opt3001: fix deadlock due to concurrent flag access The threaded IRQ function in this driver is reading the flag twice: once to lock a mutex and once to unlock it. Even though the code setting the flag is designed to prevent it, there are subtle cases where the flag could be true at the mutex_lock stage and false at the mutex_unlock stage. This results in the mutex not being unlocked, resulting in a deadlock. Fix it by making the opt3001_irq() code generally more robust, reading the flag into a variable and using the variable value at both stages.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-667 Improper Locking\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-38322\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: perf/x86/intel: Fix crash in icl_update_topdown_event() The perf_fuzzer found a hard-lockup crash on a RaptorLake machine: Oops: general protection fault, maybe for address 0xffff89aeceab400: 0000 CPU: 23 UID: 0 PID: 0 Comm: swapper/23 Tainted: [W]=WARN Hardware name: Dell Inc. Precision 9660/0VJ762 RIP: 0010:native_read_pmc+0x7/0x40 Code: cc e8 8d a9 01 00 48 89 03 5b cd cc cc cc cc 0f 1f ... RSP: 000:fffb03100273de8 EFLAGS: 00010046 .... Call Trace: icl_update_topdown_event+0x165/0x190 ? ktime_get+0x38/0xd0 intel_pmu_read_event+0xf9/0x210 __perf_event_read+0xf9/0x210 CPUs 16-23 are E-core CPUs that don't support the perf metrics feature. The icl_update_topdown_event() should not be invoked on these CPUs. It's a regression of commit: f9bdf1f95339 (\"perf/x86/intel: Avoid disable PMU if !cpuc->enabled in sample read\") The bug introduced by that commit is that the is_topdown_event() function is mistakenly used to replace the is_topdown_count() call to check if the topdown functions for the perf metrics feature should be invoked. Fix it.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-20 Improper Input Validation\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-38347\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: f2fs: fix to do sanity check on ino and xnid syzbot reported a f2fs bug as below: INFO: task syz-executor140:5308 blocked for more than 143 seconds. Not tainted 6.14.0-rc7-syzkaller-00069-g81e4f8d68c66 #0 \"echo 0 > /proc/sys/kernel/hung_task_timeout_secs\" disables this message. task:syz-executor140 state:D stack:24016 pid:5308 tgid:5308 ppid:5306 task_flags:0x400140 flags:0x00000006 Call Trace: context_switch kernel/sched/core.c:5378 [inline] __schedule+0x190e/0x4c90 kernel/sched/core.c:6765 __schedule_loop kernel/sched/core.c:6842 [inline] schedule+0x14b/0x320 kernel/sched/core.c:6857 io_schedule+0x8d/0x110 kernel/sched/core.c:7690 folio_wait_bit_common+0x839/0xee0 mm/filemap.c:1317 __folio_lock mm/filemap.c:1664 [inline] folio_lock include/linux/pagemap.h:1163 [inline] __filemap_get_folio+0x147/0xb40 mm/filemap.c:1917 pagecache_get_page+0x2c/0x130 mm/folio-compat.c:87 find_get_page_flags include/linux/pagemap.h:842 [inline] f2fs_grab_cache_page+0x2b/0x320 fs/f2fs/f2fs.h:2776 __get_node_page+0x131/0x11b0 fs/f2fs/node.c:1463 read_xattr_block+0xfb/0x190 fs/f2fs/xattr.c:306 lookup_all_xattrs fs/f2fs/xattr.c:355 [inline] f2fs_getxattr+0x676/0xf70 fs/f2fs/xattr.c:533 __f2fs_get_acl+0x52/0x870 fs/f2fs/acl.c:179 f2fs_acl_create fs/f2fs/acl.c:375 [inline] f2fs_init_acl+0xd7/0x9b0 fs/f2fs/acl.c:418 f2fs_init_inode_metadata+0xa0f/0x1050 fs/f2fs/dir.c:539 f2fs_add_inline_entry+0x448/0x860 fs/f2fs/inline.c:666 f2fs_add_dentry+0xba/0x1e0 fs/f2fs/dir.c:765 f2fs_do_add_link+0x28c/0x3a0 fs/f2fs/dir.c:808 f2fs_add_link fs/f2fs/f2fs.h:3616 [inline] f2fs_mknod+0x2e8/0x5b0 fs/f2fs/namei.c:766 vfs_mknod+0x36d/0x3b0 fs/namei.c:4191 unix_bind_bsd net/unix/af_unix.c:1286 [inline] unix_bind+0x563/0xe30 net/unix/af_unix.c:1379 __sys_bind_socket net/socket.c:1817 [inline] __sys_bind+0x1e4/0x290 net/socket.c:1848 __do_sys_bind net/socket.c:1853 [inline] __se_sys_bind net/socket.c:1851 [inline] __x64_sys_bind+0x7a/0x90 net/socket.c:1851 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f Let's dump and check metadata of corrupted inode, it shows its xattr_nid is the same to its i_ino. dump.f2fs -i 3 chaseyu.img.raw i_xattr_nid [0x 3 : 3] So that, during mknod in the corrupted directory, it tries to get and lock inode page twice, result in deadlock. - f2fs_mknod - f2fs_add_inline_entry - f2fs_get_inode_page --- lock dir's inode page - f2fs_init_acl - f2fs_acl_create(dir,..) - __f2fs_get_acl - f2fs_getxattr - lookup_all_xattrs - __get_node_page --- try to lock dir's inode page In order to fix this, let's add sanity check on ino and xnid.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-20 Improper Input Validation\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-38491\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: mptcp: make fallback action and fallback decision atomic Syzkaller reported the following splat: WARNING: CPU: 1 PID: 7704 at net/mptcp/protocol.h:1223 __mptcp_do_fallback net/mptcp/protocol.h:1223 [inline] WARNING: CPU: 1 PID: 7704 at net/mptcp/protocol.h:1223 mptcp_do_fallback net/mptcp/protocol.h:1244 [inline] WARNING: CPU: 1 PID: 7704 at net/mptcp/protocol.h:1223 check_fully_established net/mptcp/options.c:982 [inline] WARNING: CPU: 1 PID: 7704 at net/mptcp/protocol.h:1223 mptcp_incoming_options+0x21a8/0x2510 net/mptcp/options.c:1153 Modules linked in: CPU: 1 UID: 0 PID: 7704 Comm: syz.3.1419 Not tainted 6.16.0-rc3-gbd5ce2324dba #20 PREEMPT(voluntary) Hardware name: QEMU Ubuntu 24.04 PC (i440FX + PIIX, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014 RIP: 0010:__mptcp_do_fallback net/mptcp/protocol.h:1223 [inline] RIP: 0010:mptcp_do_fallback net/mptcp/protocol.h:1244 [inline] RIP: 0010:check_fully_established net/mptcp/options.c:982 [inline] RIP: 0010:mptcp_incoming_options+0x21a8/0x2510 net/mptcp/options.c:1153 Code: 24 18 e8 bb 2a 00 fd e9 1b df ff ff e8 b1 21 0f 00 e8 ec 5f c4 fc 44 0f b7 ac 24 b0 00 00 00 e9 54 f1 ff ff e8 d9 5f c4 fc 90 <0f> 0b 90 e9 b8 f4 ff ff e8 8b 2a 00 fd e9 8d e6 ff ff e8 81 2a 00 RSP: 0018:ffff8880a3f08448 EFLAGS: 00010246 RAX: 0000000000000000 RBX: ffff8880180a8000 RCX: ffffffff84afcf45 RDX: ffff888090223700 RSI: ffffffff84afdaa7 RDI: 0000000000000001 RBP: ffff888017955780 R08: 0000000000000001 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000 R13: ffff8880180a8910 R14: ffff8880a3e9d058 R15: 0000000000000000 FS: 00005555791b8500(0000) GS:ffff88811c495000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 000000110c2800b7 CR3: 0000000058e44000 CR4: 0000000000350ef0 Call Trace: tcp_reset+0x26f/0x2b0 net/ipv4/tcp_input.c:4432 tcp_validate_incoming+0x1057/0x1b60 net/ipv4/tcp_input.c:5975 tcp_rcv_established+0x5b5/0x21f0 net/ipv4/tcp_input.c:6166 tcp_v4_do_rcv+0x5dc/0xa70 net/ipv4/tcp_ipv4.c:1925 tcp_v4_rcv+0x3473/0x44a0 net/ipv4/tcp_ipv4.c:2363 ip_protocol_deliver_rcu+0xba/0x480 net/ipv4/ip_input.c:205 ip_local_deliver_finish+0x2f1/0x500 net/ipv4/ip_input.c:233 NF_HOOK include/linux/netfilter.h:317 [inline] NF_HOOK include/linux/netfilter.h:311 [inline] ip_local_deliver+0x1be/0x560 net/ipv4/ip_input.c:254 dst_input include/net/dst.h:469 [inline] ip_rcv_finish net/ipv4/ip_input.c:447 [inline] NF_HOOK include/linux/netfilter.h:317 [inline] NF_HOOK include/linux/netfilter.h:311 [inline] ip_rcv+0x514/0x810 net/ipv4/ip_input.c:567 __netif_receive_skb_one_core+0x197/0x1e0 net/core/dev.c:5975 __netif_receive_skb+0x1f/0x120 net/core/dev.c:6088 process_backlog+0x301/0x1360 net/core/dev.c:6440 __napi_poll.constprop.0+0xba/0x550 net/core/dev.c:7453 napi_poll net/core/dev.c:7517 [inline] net_rx_action+0xb44/0x1010 net/core/dev.c:7644 handle_softirqs+0x1d0/0x770 kernel/softirq.c:579 do_softirq+0x3f/0x90 kernel/softirq.c:480 __local_bh_enable_ip+0xed/0x110 kernel/softirq.c:407 local_bh_enable include/linux/bottom_half.h:33 [inline] inet_csk_listen_stop+0x2c5/0x1070 net/ipv4/inet_connection_sock.c:1524 mptcp_check_listen_stop.part.0+0x1cc/0x220 net/mptcp/protocol.c:2985 mptcp_check_listen_stop net/mptcp/mib.h:118 [inline] __mptcp_close+0x9b9/0xbd0 net/mptcp/protocol.c:3000 mptcp_close+0x2f/0x140 net/mptcp/protocol.c:3066 inet_release+0xed/0x200 net/ipv4/af_inet.c:435 inet6_release+0x4f/0x70 net/ipv6/af_inet6.c:487 __sock_release+0xb3/0x270 net/socket.c:649 sock_close+0x1c/0x30 net/socket.c:1439 __fput+0x402/0xb70 fs/file_table.c:465 task_work_run+0x150/0x240 kernel/task_work.c:227 resume_user_mode_work include/linux/resume_user_mode.h:50 [inline] exit_to_user_mode_loop+0xd4 ---truncated---\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-667 Improper Locking\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-38502\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: bpf: Fix oob access in cgroup local storage Lonial reported that an out-of-bounds access in cgroup local storage can be crafted via tail calls. Given two programs each utilizing a cgroup local storage with a different value size, and one program doing a tail call into the other. The verifier will validate each of the indivial programs just fine. However, in the runtime context the bpf_cg_run_ctx holds an bpf_prog_array_item which contains the BPF program as well as any cgroup local storage flavor the program uses. Helpers such as bpf_get_local_storage() pick this up from the runtime context: ctx = container_of(current->bpf_ctx, struct bpf_cg_run_ctx, run_ctx); storage = ctx->prog_item->cgroup_storage[stype]; if (stype == BPF_CGROUP_STORAGE_SHARED) ptr = &READ_ONCE(storage->buf)->data[0]; else ptr = this_cpu_ptr(storage->percpu_buf); For the second program which was called from the originally attached one, this means bpf_get_local_storage() will pick up the former program's map, not its own. With mismatching sizes, this can result in an unintended out-of-bounds access. To fix this issue, we need to extend bpf_map_owner with an array of storage_cookie[] to match on i) the exact maps from the original program if the second program was using bpf_get_local_storage(), or ii) allow the tail call combination if the second program was not using any of the cgroup local storage maps.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-125 Out-of-bounds Read\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n4\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-38552\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: mptcp: plug races between subflow fail and subflow creation We have races similar to the one addressed by the previous patch between subflow failing and additional subflow creation. They are just harder to trigger. The solution is similar. Use a separate flag to track the condition 'socket state prevent any additional subflow creation' protected by the fallback lock. The socket fallback makes such flag true, and also receiving or sending an MP_FAIL option. The field 'allow_infinite_fallback' is now always touched under the relevant lock, we can drop the ONCE annotation on write.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-20 Improper Input Validation\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.3\nMEDIUM\nCVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-38614\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: eventpoll: Fix semi-unbounded recursion Ensure that epoll instances can never form a graph deeper than EP_MAX_NESTS+1 links. Currently, ep_loop_check_proc() ensures that the graph is loop-free and does some recursion depth checks, but those recursion depth checks don't limit the depth of the resulting tree for two reasons: - They don't look upwards in the tree. - If there are multiple downwards paths of different lengths, only one of the paths is actually considered for the depth check since commit 28d82dc1c4ed (\"epoll: limit paths\"). Essentially, the current recursion depth check in ep_loop_check_proc() just serves to prevent it from recursing too deeply while checking for loops. A more thorough check is done in reverse_path_check() after the new graph edge has already been created; this checks, among other things, that no paths going upwards from any non-epoll file with a length of more than 5 edges exist. However, this check does not apply to non-epoll files. As a result, it is possible to recurse to a depth of at least roughly 500, tested on v6.15. (I am unsure if deeper recursion is possible; and this may have changed with commit 8c44dac8add7 (\"eventpoll: Fix priority inversion problem\").) To fix it: 1. In ep_loop_check_proc(), note the subtree depth of each visited node, and use subtree depths for the total depth calculation even when a subtree has already been visited. 2. Add ep_get_upwards_depth_proc() for similarly determining the maximum depth of an upwards walk. 3. In ep_loop_check(), use these values to limit the total path length between epoll nodes to EP_MAX_NESTS edges.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-674 Uncontrolled Recursion\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-38670\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: arm64/entry: Mask DAIF in cpu_switch_to(), call_on_irq_stack() `cpu_switch_to()` and `call_on_irq_stack()` manipulate SP to change to different stacks along with the Shadow Call Stack if it is enabled. Those two stack changes cannot be done atomically and both functions can be interrupted by SErrors or Debug Exceptions which, though unlikely, is very much broken : if interrupted, we can end up with mismatched stacks and Shadow Call Stack leading to clobbered stacks. In `cpu_switch_to()`, it can happen when SP_EL0 points to the new task, but x18 stills points to the old task's SCS. When the interrupt handler tries to save the task's SCS pointer, it will save the old task SCS pointer (x18) into the new task struct (pointed to by SP_EL0), clobbering it. In `call_on_irq_stack()`, it can happen when switching from the task stack to the IRQ stack and when switching back. In both cases, we can be interrupted when the SCS pointer points to the IRQ SCS, but SP points to the task stack. The nested interrupt handler pushes its return addresses on the IRQ SCS. It then detects that SP points to the task stack, calls `call_on_irq_stack()` and clobbers the task SCS pointer with the IRQ SCS pointer, which it will also use ! This leads to tasks returning to addresses on the wrong SCS, or even on the IRQ SCS, triggering kernel panics via CONFIG_VMAP_STACK or FPAC if enabled. This is possible on a default config, but unlikely. However, when enabling CONFIG_ARM64_PSEUDO_NMI, DAIF is unmasked and instead the GIC is responsible for filtering what interrupts the CPU should receive based on priority. Given the goal of emulating NMIs, pseudo-NMIs can be received by the CPU even in `cpu_switch_to()` and `call_on_irq_stack()`, possibly *very* frequently depending on the system configuration and workload, leading to unpredictable kernel panics. Completely mask DAIF in `cpu_switch_to()` and restore it when returning. Do the same in `call_on_irq_stack()`, but restore and mask around the branch. Mask DAIF even if CONFIG_SHADOW_CALL_STACK is not enabled for consistency of behaviour between all configurations. Introduce and use an assembly macro for saving and masking DAIF, as the existing one saves but only masks IF.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-20 Improper Input Validation\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-38676\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: iommu/amd: Avoid stack buffer overflow from kernel cmdline While the kernel command line is considered trusted in most environments, avoid writing 1 byte past the end of \"acpiid\" if the \"str\" argument is maximum length.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-805 Buffer Access with Incorrect Length Value\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n6\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-38677\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: f2fs: fix to avoid out-of-boundary access in dnode page As Jiaming Zhang reported: __dump_stack lib/dump_stack.c:94 [inline] dump_stack_lvl+0x1c1/0x2a0 lib/dump_stack.c:120 print_address_description mm/kasan/report.c:378 [inline] print_report+0x17e/0x800 mm/kasan/report.c:480 kasan_report+0x147/0x180 mm/kasan/report.c:593 data_blkaddr fs/f2fs/f2fs.h:3053 [inline] f2fs_data_blkaddr fs/f2fs/f2fs.h:3058 [inline] f2fs_get_dnode_of_data+0x1a09/0x1c40 fs/f2fs/node.c:855 f2fs_reserve_block+0x53/0x310 fs/f2fs/data.c:1195 prepare_write_begin fs/f2fs/data.c:3395 [inline] f2fs_write_begin+0xf39/0x2190 fs/f2fs/data.c:3594 generic_perform_write+0x2c7/0x910 mm/filemap.c:4112 f2fs_buffered_write_iter fs/f2fs/file.c:4988 [inline] f2fs_file_write_iter+0x1ec8/0x2410 fs/f2fs/file.c:5216 new_sync_write fs/read_write.c:593 [inline] vfs_write+0x546/0xa90 fs/read_write.c:686 ksys_write+0x149/0x250 fs/read_write.c:738 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xf3/0x3d0 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f The root cause is in the corrupted image, there is a dnode has the same node id w/ its inode, so during f2fs_get_dnode_of_data(), it tries to access block address in dnode at offset 934, however it parses the dnode as inode node, so that get_dnode_addr() returns 360, then it tries to access page address from 360 + 934 * 4 = 4096 w/ 4 bytes. To fix this issue, let's add sanity check for node id of all direct nodes during f2fs_get_dnode_of_data().\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-20 Improper Input Validation\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-38679\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: media: venus: Fix OOB read due to missing payload bound check Currently, The event_seq_changed() handler processes a variable number of properties sent by the firmware. The number of properties is indicated by the firmware and used to iterate over the payload. However, the payload size is not being validated against the actual message length. This can lead to out-of-bounds memory access if the firmware provides a property count that exceeds the data available in the payload. Such a condition can result in kernel crashes or potential information leaks if memory beyond the buffer is accessed. Fix this by properly validating the remaining size of the payload before each property access and updating bounds accordingly as properties are parsed. This ensures that property parsing is safely bounded within the received message buffer and protects against malformed or malicious firmware behavior.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-20 Improper Input Validation\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-38680\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: media: uvcvideo: Fix 1-byte out-of-bounds read in uvc_parse_format() The buffer length check before calling uvc_parse_format() only ensured that the buffer has at least 3 bytes (buflen > 2), buf the function accesses buffer[3], requiring at least 4 bytes. This can lead to an out-of-bounds read if the buffer has exactly 3 bytes. Fix it by checking that the buffer has at least 4 bytes in uvc_parse_format().\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-125 Out-of-bounds Read\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-38681\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: mm/ptdump: take the memory hotplug lock inside ptdump_walk_pgd() Memory hot remove unmaps and tears down various kernel page table regions as required. The ptdump code can race with concurrent modifications of the kernel page tables. When leaf entries are modified concurrently, the dump code may log stale or inconsistent information for a VA range, but this is otherwise not harmful. But when intermediate levels of kernel page table are freed, the dump code will continue to use memory that has been freed and potentially reallocated for another purpose. In such cases, the ptdump code may dereference bogus addresses, leading to a number of potential problems. To avoid the above mentioned race condition, platforms such as arm64, riscv and s390 take memory hotplug lock, while dumping kernel page table via the sysfs interface /sys/kernel/debug/kernel_page_tables. Similar race condition exists while checking for pages that might have been marked W+X via /sys/kernel/debug/kernel_page_tables/check_wx_pages which in turn calls ptdump_check_wx(). Instead of solving this race condition again, let's just move the memory hotplug lock inside generic ptdump_check_wx() which will benefit both the scenarios. Drop get_online_mems() and put_online_mems() combination from all existing platform ptdump code paths.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-366 Race Condition within a Thread\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n6.5\nMEDIUM\nCVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:L/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-38683\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: hv_netvsc: Fix panic during namespace deletion with VF The existing code move the VF NIC to new namespace when NETDEV_REGISTER is received on netvsc NIC. During deletion of the namespace, default_device_exit_batch() >> default_device_exit_net() is called. When netvsc NIC is moved back and registered to the default namespace, it automatically brings VF NIC back to the default namespace. This will cause the default_device_exit_net() >> for_each_netdev_safe loop unable to detect the list end, and hit NULL ptr: [ 231.449420] mana 7870:00:00.0 enP30832s1: Moved VF to namespace with: eth0 [ 231.449656] BUG: kernel NULL pointer dereference, address: 0000000000000010 [ 231.450246] #PF: supervisor read access in kernel mode [ 231.450579] #PF: error_code(0x0000) - not-present page [ 231.450916] PGD 17b8a8067 P4D 0 [ 231.451163] Oops: Oops: 0000 [#1] SMP NOPTI [ 231.451450] CPU: 82 UID: 0 PID: 1394 Comm: kworker/u768:1 Not tainted 6.16.0-rc4+ #3 VOLUNTARY [ 231.452042] Hardware name: Microsoft Corporation Virtual Machine/Virtual Machine, BIOS Hyper-V UEFI Release v4.1 11/21/2024 [ 231.452692] Workqueue: netns cleanup_net [ 231.452947] RIP: 0010:default_device_exit_batch+0x16c/0x3f0 [ 231.453326] Code: c0 0c f5 b3 e8 d5 db fe ff 48 85 c0 74 15 48 c7 c2 f8 fd ca b2 be 10 00 00 00 48 8d 7d c0 e8 7b 77 25 00 49 8b 86 28 01 00 00 <48> 8b 50 10 4c 8b 2a 4c 8d 62 f0 49 83 ed 10 4c 39 e0 0f 84 d6 00 [ 231.454294] RSP: 0018:ff75fc7c9bf9fd00 EFLAGS: 00010246 [ 231.454610] RAX: 0000000000000000 RBX: 0000000000000002 RCX: 61c8864680b583eb [ 231.455094] RDX: ff1fa9f71462d800 RSI: ff75fc7c9bf9fd38 RDI: 0000000030766564 [ 231.455686] RBP: ff75fc7c9bf9fd78 R08: 0000000000000000 R09: 0000000000000000 [ 231.456126] R10: 0000000000000001 R11: 0000000000000004 R12: ff1fa9f70088e340 [ 231.456621] R13: ff1fa9f70088e340 R14: ffffffffb3f50c20 R15: ff1fa9f7103e6340 [ 231.457161] FS: 0000000000000000(0000) GS:ff1faa6783a08000(0000) knlGS:0000000000000000 [ 231.457707] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 231.458031] CR2: 0000000000000010 CR3: 0000000179ab2006 CR4: 0000000000b73ef0 [ 231.458434] Call Trace: [ 231.458600] [ 231.458777] ops_undo_list+0x100/0x220 [ 231.459015] cleanup_net+0x1b8/0x300 [ 231.459285] process_one_work+0x184/0x340 To fix it, move the ns change to a workqueue, and take rtnl_lock to avoid changing the netdev list when default_device_exit_net() is using it.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-820 Missing Synchronization\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.2\nMEDIUM\nCVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:L/I:L/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-38684\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: net/sched: ets: use old 'nbands' while purging unused classes Shuang reported sch_ets test-case [1] crashing in ets_class_qlen_notify() after recent changes from Lion [2]. The problem is: in ets_qdisc_change() we purge unused DWRR queues; the value of 'q->nbands' is the new one, and the cleanup should be done with the old one. The problem is here since my first attempts to fix ets_qdisc_change(), but it surfaced again after the recent qdisc len accounting fixes. Fix it purging idle DWRR queues before assigning a new value of 'q->nbands', so that all purge operations find a consistent configuration: - old 'q->nbands' because it's needed by ets_class_find() - old 'q->nstrict' because it's needed by ets_class_is_strict() BUG: kernel NULL pointer dereference, address: 0000000000000000 #PF: supervisor read access in kernel mode #PF: error_code(0x0000) - not-present page PGD 0 P4D 0 Oops: Oops: 0000 [#1] SMP NOPTI CPU: 62 UID: 0 PID: 39457 Comm: tc Kdump: loaded Not tainted 6.12.0-116.el10.x86_64 #1 PREEMPT(voluntary) Hardware name: Dell Inc. PowerEdge R640/06DKY5, BIOS 2.12.2 07/09/2021 RIP: 0010:__list_del_entry_valid_or_report+0x4/0x80 Code: ff 4c 39 c7 0f 84 39 19 8e ff b8 01 00 00 00 c3 cc cc cc cc 66 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 f3 0f 1e fa <48> 8b 17 48 8b 4f 08 48 85 d2 0f 84 56 19 8e ff 48 85 c9 0f 84 ab RSP: 0018:ffffba186009f400 EFLAGS: 00010202 RAX: 00000000000000d6 RBX: 0000000000000000 RCX: 0000000000000004 RDX: ffff9f0fa29b69c0 RSI: 0000000000000000 RDI: 0000000000000000 RBP: ffffffffc12c2400 R08: 0000000000000008 R09: 0000000000000004 R10: ffffffffffffffff R11: 0000000000000004 R12: 0000000000000000 R13: ffff9f0f8cfe0000 R14: 0000000000100005 R15: 0000000000000000 FS: 00007f2154f37480(0000) GS:ffff9f269c1c0000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000000000000000 CR3: 00000001530be001 CR4: 00000000007726f0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 PKRU: 55555554 Call Trace: ets_class_qlen_notify+0x65/0x90 [sch_ets] qdisc_tree_reduce_backlog+0x74/0x110 ets_qdisc_change+0x630/0xa40 [sch_ets] __tc_modify_qdisc.constprop.0+0x216/0x7f0 tc_modify_qdisc+0x7c/0x120 rtnetlink_rcv_msg+0x145/0x3f0 netlink_rcv_skb+0x53/0x100 netlink_unicast+0x245/0x390 netlink_sendmsg+0x21b/0x470 ____sys_sendmsg+0x39d/0x3d0 ___sys_sendmsg+0x9a/0xe0 __sys_sendmsg+0x7a/0xd0 do_syscall_64+0x7d/0x160 entry_SYSCALL_64_after_hwframe+0x76/0x7e RIP: 0033:0x7f2155114084 Code: 89 02 b8 ff ff ff ff eb bb 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 00 f3 0f 1e fa 80 3d 25 f0 0c 00 00 74 13 b8 2e 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 54 c3 0f 1f 00 48 83 ec 28 89 54 24 1c 48 89 RSP: 002b:00007fff1fd7a988 EFLAGS: 00000202 ORIG_RAX: 000000000000002e RAX: ffffffffffffffda RBX: 0000560ec063e5e0 RCX: 00007f2155114084 RDX: 0000000000000000 RSI: 00007fff1fd7a9f0 RDI: 0000000000000003 RBP: 00007fff1fd7aa60 R08: 0000000000000010 R09: 000000000000003f R10: 0000560ee9b3a010 R11: 0000000000000202 R12: 00007fff1fd7aae0 R13: 000000006891ccde R14: 0000560ec063e5e0 R15: 00007fff1fd7aad0 [1] https://lore.kernel.org/netdev/e08c7f4a6882f260011909a868311c6e9b54f3e4.1639153474.git.dcaratti@redhat.com/ [2] https://lore.kernel.org/netdev/d912cbd7-193b-4269-9857-525bee8bbb6a@gmail.com/\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-476 NULL Pointer Dereference\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.2\nMEDIUM\nCVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:L/I:L/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-38685\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: fbdev: Fix vmalloc out-of-bounds write in fast_imageblit This issue triggers when a userspace program does an ioctl FBIOPUT_CON2FBMAP by passing console number and frame buffer number. Ideally this maps console to frame buffer and updates the screen if console is visible. As part of mapping it has to do resize of console according to frame buffer info. if this resize fails and returns from vc_do_resize() and continues further. At this point console and new frame buffer are mapped and sets display vars. Despite failure still it continue to proceed updating the screen at later stages where vc_data is related to previous frame buffer and frame buffer info and display vars are mapped to new frame buffer and eventully leading to out-of-bounds write in fast_imageblit(). This bheviour is excepted only when fg_console is equal to requested console which is a visible console and updates screen with invalid struct references in fbcon_putcs().\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-787 Out-of-bounds Write\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n7.8\nHIGH\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-38687\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: comedi: fix race between polling and detaching syzbot reports a use-after-free in comedi in the below link, which is due to comedi gladly removing the allocated async area even though poll requests are still active on the wait_queue_head inside of it. This can cause a use-after-free when the poll entries are later triggered or removed, as the memory for the wait_queue_head has been freed. We need to check there are no tasks queued on any of the subdevices' wait queues before allowing the device to be detached by the `COMEDI_DEVCONFIG` ioctl. Tasks will read-lock `dev->attach_lock` before adding themselves to the subdevice wait queue, so fix the problem in the `COMEDI_DEVCONFIG` ioctl handler by write-locking `dev->attach_lock` before checking that all of the subdevices are safe to be deleted. This includes testing for any sleepers on the subdevices' wait queues. It remains locked until the device has been detached. This requires the `comedi_device_detach()` function to be refactored slightly, moving the bulk of it into new function `comedi_device_detach_locked()`. Note that the refactor of `comedi_device_detach()` results in `comedi_device_cancel_all()` now being called while `dev->attach_lock` is write-locked, which wasn't the case previously, but that does not matter. Thanks to Jens Axboe for diagnosing the problem and co-developing this patch.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-20 Improper Input Validation\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-38691\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: pNFS: Fix uninited ptr deref in block/scsi layout The error occurs on the third attempt to encode extents. When function ext_tree_prepare_commit() reallocates a larger buffer to retry encoding extents, the \"layoutupdate_pages\" page array is initialized only after the retry loop. But ext_tree_free_commitdata() is called on every iteration and tries to put pages in the array, thus dereferencing uninitialized pointers. An additional problem is that there is no limit on the maximum possible buffer_size. When there are too many extents, the client may create a layoutcommit that is larger than the maximum possible RPC size accepted by the server. During testing, we observed two typical scenarios. First, one memory page for extents is enough when we work with small files, append data to the end of the file, or preallocate extents before writing. But when we fill a new large file without preallocating, the number of extents can be huge, and counting the number of written extents in ext_tree_encode_commit() does not help much. Since this number increases even more between unlocking and locking of ext_tree, the reallocated buffer may not be large enough again and again.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-908 Use of Uninitialized Resource\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-38693\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: media: dvb-frontends: w7090p: fix null-ptr-deref in w7090p_tuner_write_serpar and w7090p_tuner_read_serpar In w7090p_tuner_write_serpar, msg is controlled by user. When msg[0].buf is null and msg[0].len is zero, former checks on msg[0].buf would be passed. If accessing msg[0].buf[2] without sanity check, null pointer deref would happen. We add check on msg[0].len to prevent crash. Similar commit: commit 0ed554fd769a (\"media: dvb-usb: az6027: fix null-ptr-deref in az6027_i2c_xfer()\")\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-20 Improper Input Validation\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n7\nHIGH\nCVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-38694\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: media: dvb-frontends: dib7090p: fix null-ptr-deref in dib7090p_rw_on_apb() In dib7090p_rw_on_apb, msg is controlled by user. When msg[0].buf is null and msg[0].len is zero, former checks on msg[0].buf would be passed. If accessing msg[0].buf[2] without sanity check, null pointer deref would happen. We add check on msg[0].len to prevent crash. Similar issue occurs when access msg[1].buf[0] and msg[1].buf[1]. Similar commit: commit 0ed554fd769a (\"media: dvb-usb: az6027: fix null-ptr-deref in az6027_i2c_xfer()\")\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-476 NULL Pointer Dereference\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-38695\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: scsi: lpfc: Check for hdwq null ptr when cleaning up lpfc_vport structure If a call to lpfc_sli4_read_rev() from lpfc_sli4_hba_setup() fails, the resultant cleanup routine lpfc_sli4_vport_delete_fcp_xri_aborted() may occur before sli4_hba.hdwqs are allocated. This may result in a null pointer dereference when attempting to take the abts_io_buf_list_lock for the first hardware queue. Fix by adding a null ptr check on phba->sli4_hba.hdwq and early return because this situation means there must have been an error during port initialization.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-476 NULL Pointer Dereference\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n7\nHIGH\nCVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-38696\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: MIPS: Don't crash in stack_top() for tasks without ABI or vDSO Not all tasks have an ABI associated or vDSO mapped, for example kthreads never do. If such a task ever ends up calling stack_top(), it will derefence the NULL ABI pointer and crash. This can for example happen when using kunit: mips_stack_top+0x28/0xc0 arch_pick_mmap_layout+0x190/0x220 kunit_vm_mmap_init+0xf8/0x138 __kunit_add_resource+0x40/0xa8 kunit_vm_mmap+0x88/0xd8 usercopy_test_init+0xb8/0x240 kunit_try_run_case+0x5c/0x1a8 kunit_generic_run_threadfn_adapter+0x28/0x50 kthread+0x118/0x240 ret_from_kernel_thread+0x14/0x1c Only dereference the ABI point if it is set. The GIC page is also included as it is specific to the vDSO. Also move the randomization adjustment into the same conditional.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-20 Improper Input Validation\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-38697\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: jfs: upper bound check of tree index in dbAllocAG When computing the tree index in dbAllocAG, we never check if we are out of bounds realative to the size of the stree. This could happen in a scenario where the filesystem metadata are corrupted.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-20 Improper Input Validation\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n7\nHIGH\nCVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-38698\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: jfs: Regular file corruption check The reproducer builds a corrupted file on disk with a negative i_size value. Add a check when opening this file to avoid subsequent operation failures.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-20 Improper Input Validation\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n7\nHIGH\nCVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-38699\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: scsi: bfa: Double-free fix When the bfad_im_probe() function fails during initialization, the memory pointed to by bfad->im is freed without setting bfad->im to NULL. Subsequently, during driver uninstallation, when the state machine enters the bfad_sm_stopping state and calls the bfad_im_probe_undo() function, it attempts to free the memory pointed to by bfad->im again, thereby triggering a double-free vulnerability. Set bfad->im to NULL if probing fails.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-415 Double Free\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n6.4\nMEDIUM\nCVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-38700\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: scsi: libiscsi: Initialize iscsi_conn->dd_data only if memory is allocated In case of an ib_fast_reg_mr allocation failure during iSER setup, the machine hits a panic because iscsi_conn->dd_data is initialized unconditionally, even when no memory is allocated (dd_size == 0). This leads invalid pointer dereference during connection teardown. Fix by setting iscsi_conn->dd_data only if memory is actually allocated. Panic trace: ------------ iser: iser_create_fastreg_desc: Failed to allocate ib_fast_reg_mr err=-12 iser: iser_alloc_rx_descriptors: failed allocating rx descriptors / data buffers BUG: unable to handle page fault for address: fffffffffffffff8 RIP: 0010:swake_up_locked.part.5+0xa/0x40 Call Trace: complete+0x31/0x40 iscsi_iser_conn_stop+0x88/0xb0 [ib_iser] iscsi_stop_conn+0x66/0xc0 [scsi_transport_iscsi] iscsi_if_stop_conn+0x14a/0x150 [scsi_transport_iscsi] iscsi_if_rx+0x1135/0x1834 [scsi_transport_iscsi] ? netlink_lookup+0x12f/0x1b0 ? netlink_deliver_tap+0x2c/0x200 netlink_unicast+0x1ab/0x280 netlink_sendmsg+0x257/0x4f0 ? _copy_from_user+0x29/0x60 sock_sendmsg+0x5f/0x70\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-20 Improper Input Validation\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n7\nHIGH\nCVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-38701\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: ext4: do not BUG when INLINE_DATA_FL lacks system.data xattr A syzbot fuzzed image triggered a BUG_ON in ext4_update_inline_data() when an inode had the INLINE_DATA_FL flag set but was missing the system.data extended attribute. Since this can happen due to a maiciouly fuzzed file system, we shouldn't BUG, but rather, report it as a corrupted file system. Add similar replacements of BUG_ON with EXT4_ERROR_INODE() ii ext4_create_inline_data() and ext4_inline_data_truncate().\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-617 Reachable Assertion\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-38702\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: fbdev: fix potential buffer overflow in do_register_framebuffer() The current implementation may lead to buffer overflow when: 1. Unregistration creates NULL gaps in registered_fb[] 2. All array slots become occupied despite num_registered_fb < FB_MAX 3. The registration loop exceeds array bounds Add boundary check to prevent registered_fb[FB_MAX] access.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-787 Out-of-bounds Write\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n7.8\nHIGH\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-38706\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: ASoC: core: Check for rtd == NULL in snd_soc_remove_pcm_runtime() snd_soc_remove_pcm_runtime() might be called with rtd == NULL which will leads to null pointer dereference. This was reproduced with topology loading and marking a link as ignore due to missing hardware component on the system. On module removal the soc_tplg_remove_link() would call snd_soc_remove_pcm_runtime() with rtd == NULL since the link was ignored, no runtime was created.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-476 NULL Pointer Dereference\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-38707\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: fs/ntfs3: Add sanity check for file name The length of the file name should be smaller than the directory entry size.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-20 Improper Input Validation\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-38708\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: drbd: add missing kref_get in handle_write_conflicts With `two-primaries` enabled, DRBD tries to detect \"concurrent\" writes and handle write conflicts, so that even if you write to the same sector simultaneously on both nodes, they end up with the identical data once the writes are completed. In handling \"superseeded\" writes, we forgot a kref_get, resulting in a premature drbd_destroy_device and use after free, and further to kernel crashes with symptoms. Relevance: No one should use DRBD as a random data generator, and apparently all users of \"two-primaries\" handle concurrent writes correctly on layer up. That is cluster file systems use some distributed lock manager, and live migration in virtualization environments stops writes on one node before starting writes on the other node. Which means that other than for \"test cases\", this code path is never taken in real life. FYI, in DRBD 9, things are handled differently nowadays. We still detect \"write conflicts\", but no longer try to be smart about them. We decided to disconnect hard instead: upper layers must not submit concurrent writes. If they do, that's their fault.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-416 Use After Free\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n7.8\nHIGH\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-38711\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: smb/server: avoid deadlock when linking with ReplaceIfExists If smb2_create_link() is called with ReplaceIfExists set and the name does exist then a deadlock will happen. ksmbd_vfs_kern_path_locked() will return with success and the parent directory will be locked. ksmbd_vfs_remove_file() will then remove the file. ksmbd_vfs_link() will then be called while the parent is still locked. It will try to lock the same parent and will deadlock. This patch moves the ksmbd_vfs_kern_path_unlock() call to *before* ksmbd_vfs_link() and then simplifies the code, removing the file_present flag variable.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-20 Improper Input Validation\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-38712\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: hfsplus: don't use BUG_ON() in hfsplus_create_attributes_file() When the volume header contains erroneous values that do not reflect the actual state of the filesystem, hfsplus_fill_super() assumes that the attributes file is not yet created, which later results in hitting BUG_ON() when hfsplus_create_attributes_file() is called. Replace this BUG_ON() with -EIO error with a message to suggest running fsck tool.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-20 Improper Input Validation\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-38713\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: hfsplus: fix slab-out-of-bounds read in hfsplus_uni2asc() The hfsplus_readdir() method is capable to crash by calling hfsplus_uni2asc(): [ 667.121659][ T9805] ================================================================== [ 667.122651][ T9805] BUG: KASAN: slab-out-of-bounds in hfsplus_uni2asc+0x902/0xa10 [ 667.123627][ T9805] Read of size 2 at addr ffff88802592f40c by task repro/9805 [ 667.124578][ T9805] [ 667.124876][ T9805] CPU: 3 UID: 0 PID: 9805 Comm: repro Not tainted 6.16.0-rc3 #1 PREEMPT(full) [ 667.124886][ T9805] Hardware name: QEMU Ubuntu 24.04 PC (i440FX + PIIX, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014 [ 667.124890][ T9805] Call Trace: [ 667.124893][ T9805] [ 667.124896][ T9805] dump_stack_lvl+0x10e/0x1f0 [ 667.124911][ T9805] print_report+0xd0/0x660 [ 667.124920][ T9805] ? __virt_addr_valid+0x81/0x610 [ 667.124928][ T9805] ? __phys_addr+0xe8/0x180 [ 667.124934][ T9805] ? hfsplus_uni2asc+0x902/0xa10 [ 667.124942][ T9805] kasan_report+0xc6/0x100 [ 667.124950][ T9805] ? hfsplus_uni2asc+0x902/0xa10 [ 667.124959][ T9805] hfsplus_uni2asc+0x902/0xa10 [ 667.124966][ T9805] ? hfsplus_bnode_read+0x14b/0x360 [ 667.124974][ T9805] hfsplus_readdir+0x845/0xfc0 [ 667.124984][ T9805] ? __pfx_hfsplus_readdir+0x10/0x10 [ 667.124994][ T9805] ? stack_trace_save+0x8e/0xc0 [ 667.125008][ T9805] ? iterate_dir+0x18b/0xb20 [ 667.125015][ T9805] ? trace_lock_acquire+0x85/0xd0 [ 667.125022][ T9805] ? lock_acquire+0x30/0x80 [ 667.125029][ T9805] ? iterate_dir+0x18b/0xb20 [ 667.125037][ T9805] ? down_read_killable+0x1ed/0x4c0 [ 667.125044][ T9805] ? putname+0x154/0x1a0 [ 667.125051][ T9805] ? __pfx_down_read_killable+0x10/0x10 [ 667.125058][ T9805] ? apparmor_file_permission+0x239/0x3e0 [ 667.125069][ T9805] iterate_dir+0x296/0xb20 [ 667.125076][ T9805] __x64_sys_getdents64+0x13c/0x2c0 [ 667.125084][ T9805] ? __pfx___x64_sys_getdents64+0x10/0x10 [ 667.125091][ T9805] ? __x64_sys_openat+0x141/0x200 [ 667.125126][ T9805] ? __pfx_filldir64+0x10/0x10 [ 667.125134][ T9805] ? do_user_addr_fault+0x7fe/0x12f0 [ 667.125143][ T9805] do_syscall_64+0xc9/0x480 [ 667.125151][ T9805] entry_SYSCALL_64_after_hwframe+0x77/0x7f [ 667.125158][ T9805] RIP: 0033:0x7fa8753b2fc9 [ 667.125164][ T9805] Code: 00 c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 48 [ 667.125172][ T9805] RSP: 002b:00007ffe96f8e0f8 EFLAGS: 00000217 ORIG_RAX: 00000000000000d9 [ 667.125181][ T9805] RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007fa8753b2fc9 [ 667.125185][ T9805] RDX: 0000000000000400 RSI: 00002000000063c0 RDI: 0000000000000004 [ 667.125190][ T9805] RBP: 00007ffe96f8e110 R08: 00007ffe96f8e110 R09: 00007ffe96f8e110 [ 667.125195][ T9805] R10: 0000000000000000 R11: 0000000000000217 R12: 0000556b1e3b4260 [ 667.125199][ T9805] R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000 [ 667.125207][ T9805] [ 667.125210][ T9805] [ 667.145632][ T9805] Allocated by task 9805: [ 667.145991][ T9805] kasan_save_stack+0x20/0x40 [ 667.146352][ T9805] kasan_save_track+0x14/0x30 [ 667.146717][ T9805] __kasan_kmalloc+0xaa/0xb0 [ 667.147065][ T9805] __kmalloc_noprof+0x205/0x550 [ 667.147448][ T9805] hfsplus_find_init+0x95/0x1f0 [ 667.147813][ T9805] hfsplus_readdir+0x220/0xfc0 [ 667.148174][ T9805] iterate_dir+0x296/0xb20 [ 667.148549][ T9805] __x64_sys_getdents64+0x13c/0x2c0 [ 667.148937][ T9805] do_syscall_64+0xc9/0x480 [ 667.149291][ T9805] entry_SYSCALL_64_after_hwframe+0x77/0x7f [ 667.149809][ T9805] [ 667.150030][ T9805] The buggy address belongs to the object at ffff88802592f000 [ 667.150030][ T9805] which belongs to the cache kmalloc-2k of size 2048 [ 667.151282][ T9805] The buggy address is located 0 bytes to the right of [ 667.151282][ T9805] allocated 1036-byte region [ffff88802592f000, ffff88802592f40c) [ 667.1 ---truncated---\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-20 Improper Input Validation\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n7\nHIGH\nCVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-38714\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: hfsplus: fix slab-out-of-bounds in hfsplus_bnode_read() The hfsplus_bnode_read() method can trigger the issue: [ 174.852007][ T9784] ================================================================== [ 174.852709][ T9784] BUG: KASAN: slab-out-of-bounds in hfsplus_bnode_read+0x2f4/0x360 [ 174.853412][ T9784] Read of size 8 at addr ffff88810b5fc6c0 by task repro/9784 [ 174.854059][ T9784] [ 174.854272][ T9784] CPU: 1 UID: 0 PID: 9784 Comm: repro Not tainted 6.16.0-rc3 #7 PREEMPT(full) [ 174.854281][ T9784] Hardware name: QEMU Ubuntu 24.04 PC (i440FX + PIIX, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014 [ 174.854286][ T9784] Call Trace: [ 174.854289][ T9784] [ 174.854292][ T9784] dump_stack_lvl+0x10e/0x1f0 [ 174.854305][ T9784] print_report+0xd0/0x660 [ 174.854315][ T9784] ? __virt_addr_valid+0x81/0x610 [ 174.854323][ T9784] ? __phys_addr+0xe8/0x180 [ 174.854330][ T9784] ? hfsplus_bnode_read+0x2f4/0x360 [ 174.854337][ T9784] kasan_report+0xc6/0x100 [ 174.854346][ T9784] ? hfsplus_bnode_read+0x2f4/0x360 [ 174.854354][ T9784] hfsplus_bnode_read+0x2f4/0x360 [ 174.854362][ T9784] hfsplus_bnode_dump+0x2ec/0x380 [ 174.854370][ T9784] ? __pfx_hfsplus_bnode_dump+0x10/0x10 [ 174.854377][ T9784] ? hfsplus_bnode_write_u16+0x83/0xb0 [ 174.854385][ T9784] ? srcu_gp_start+0xd0/0x310 [ 174.854393][ T9784] ? __mark_inode_dirty+0x29e/0xe40 [ 174.854402][ T9784] hfsplus_brec_remove+0x3d2/0x4e0 [ 174.854411][ T9784] __hfsplus_delete_attr+0x290/0x3a0 [ 174.854419][ T9784] ? __pfx_hfs_find_1st_rec_by_cnid+0x10/0x10 [ 174.854427][ T9784] ? __pfx___hfsplus_delete_attr+0x10/0x10 [ 174.854436][ T9784] ? __asan_memset+0x23/0x50 [ 174.854450][ T9784] hfsplus_delete_all_attrs+0x262/0x320 [ 174.854459][ T9784] ? __pfx_hfsplus_delete_all_attrs+0x10/0x10 [ 174.854469][ T9784] ? rcu_is_watching+0x12/0xc0 [ 174.854476][ T9784] ? __mark_inode_dirty+0x29e/0xe40 [ 174.854483][ T9784] hfsplus_delete_cat+0x845/0xde0 [ 174.854493][ T9784] ? __pfx_hfsplus_delete_cat+0x10/0x10 [ 174.854507][ T9784] hfsplus_unlink+0x1ca/0x7c0 [ 174.854516][ T9784] ? __pfx_hfsplus_unlink+0x10/0x10 [ 174.854525][ T9784] ? down_write+0x148/0x200 [ 174.854532][ T9784] ? __pfx_down_write+0x10/0x10 [ 174.854540][ T9784] vfs_unlink+0x2fe/0x9b0 [ 174.854549][ T9784] do_unlinkat+0x490/0x670 [ 174.854557][ T9784] ? __pfx_do_unlinkat+0x10/0x10 [ 174.854565][ T9784] ? __might_fault+0xbc/0x130 [ 174.854576][ T9784] ? getname_flags.part.0+0x1c5/0x550 [ 174.854584][ T9784] __x64_sys_unlink+0xc5/0x110 [ 174.854592][ T9784] do_syscall_64+0xc9/0x480 [ 174.854600][ T9784] entry_SYSCALL_64_after_hwframe+0x77/0x7f [ 174.854608][ T9784] RIP: 0033:0x7f6fdf4c3167 [ 174.854614][ T9784] Code: f0 ff ff 73 01 c3 48 8b 0d 26 0d 0e 00 f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 08 [ 174.854622][ T9784] RSP: 002b:00007ffcb948bca8 EFLAGS: 00000206 ORIG_RAX: 0000000000000057 [ 174.854630][ T9784] RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007f6fdf4c3167 [ 174.854636][ T9784] RDX: 00007ffcb948bcc0 RSI: 00007ffcb948bcc0 RDI: 00007ffcb948bd50 [ 174.854641][ T9784] RBP: 00007ffcb948cd90 R08: 0000000000000001 R09: 00007ffcb948bb40 [ 174.854645][ T9784] R10: 00007f6fdf564fc0 R11: 0000000000000206 R12: 0000561e1bc9c2d0 [ 174.854650][ T9784] R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000 [ 174.854658][ T9784] [ 174.854661][ T9784] [ 174.879281][ T9784] Allocated by task 9784: [ 174.879664][ T9784] kasan_save_stack+0x20/0x40 [ 174.880082][ T9784] kasan_save_track+0x14/0x30 [ 174.880500][ T9784] __kasan_kmalloc+0xaa/0xb0 [ 174.880908][ T9784] __kmalloc_noprof+0x205/0x550 [ 174.881337][ T9784] __hfs_bnode_create+0x107/0x890 [ 174.881779][ T9784] hfsplus_bnode_find+0x2d0/0xd10 [ 174.882222][ T9784] hfsplus_brec_find+0x2b0/0x520 [ 174.882659][ T9784] hfsplus_delete_all_attrs+0x23b/0x3 ---truncated---\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-20 Improper Input Validation\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n7\nHIGH\nCVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-38715\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: hfs: fix slab-out-of-bounds in hfs_bnode_read() This patch introduces is_bnode_offset_valid() method that checks the requested offset value. Also, it introduces check_and_correct_requested_length() method that checks and correct the requested length (if it is necessary). These methods are used in hfs_bnode_read(), hfs_bnode_write(), hfs_bnode_clear(), hfs_bnode_copy(), and hfs_bnode_move() with the goal to prevent the access out of allocated memory and triggering the crash.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-20 Improper Input Validation\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-38721\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: netfilter: ctnetlink: fix refcount leak on table dump There is a reference count leak in ctnetlink_dump_table(): if (res < 0) { nf_conntrack_get(&ct->ct_general); // HERE cb->args[1] = (unsigned long)ct; ... While its very unlikely, its possible that ct == last. If this happens, then the refcount of ct was already incremented. This 2nd increment is never undone. This prevents the conntrack object from being released, which in turn keeps prevents cnet->count from dropping back to 0. This will then block the netns dismantle (or conntrack rmmod) as nf_conntrack_cleanup_net_list() will wait forever. This can be reproduced by running conntrack_resize.sh selftest in a loop. It takes ~20 minutes for me on a preemptible kernel on average before I see a runaway kworker spinning in nf_conntrack_cleanup_net_list. One fix would to change this to: if (res < 0) { if (ct != last) nf_conntrack_get(&ct->ct_general); But this reference counting isn't needed in the first place. We can just store a cookie value instead. A followup patch will do the same for ctnetlink_exp_dump_table, it looks to me as if this has the same problem and like ctnetlink_dump_table, we only need a 'skip hint', not the actual object so we can apply the same cookie strategy there as well.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-772 Missing Release of Resource after Effective Lifetime\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-38723\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: LoongArch: BPF: Fix jump offset calculation in tailcall The extra pass of bpf_int_jit_compile() skips JIT context initialization which essentially skips offset calculation leaving out_offset = -1, so the jmp_offset in emit_bpf_tail_call is calculated by \"#define jmp_offset (out_offset - (cur_offset))\" is a negative number, which is wrong. The final generated assembly are as follow. 54: bgeu $a2, $t1, -8 # 0x0000004c 58: addi.d $a6, $s5, -1 5c: bltz $a6, -16 # 0x0000004c 60: alsl.d $t2, $a2, $a1, 0x3 64: ld.d $t2, $t2, 264 68: beq $t2, $zero, -28 # 0x0000004c Before apply this patch, the follow test case will reveal soft lock issues. cd tools/testing/selftests/bpf/ ./test_progs --allow=tailcalls/tailcall_bpf2bpf_1 dmesg: watchdog: BUG: soft lockup - CPU#2 stuck for 26s! [test_progs:25056]\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-20 Improper Input Validation\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-38724\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: nfsd: handle get_client_locked() failure in nfsd4_setclientid_confirm() Lei Lu recently reported that nfsd4_setclientid_confirm() did not check the return value from get_client_locked(). a SETCLIENTID_CONFIRM could race with a confirmed client expiring and fail to get a reference. That could later lead to a UAF. Fix this by getting a reference early in the case where there is an extant confirmed client. If that fails then treat it as if there were no confirmed client found at all. In the case where the unconfirmed client is expiring, just fail and return the result from get_client_locked().\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-416 Use After Free\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n7.8\nHIGH\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-38725\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: net: usb: asix_devices: add phy_mask for ax88772 mdio bus Without setting phy_mask for ax88772 mdio bus, current driver may create at most 32 mdio phy devices with phy address range from 0x00 ~ 0x1f. DLink DUB-E100 H/W Ver B1 is such a device. However, only one main phy device will bind to net phy driver. This is creating issue during system suspend/resume since phy_polling_mode() in phy_state_machine() will directly deference member of phydev->drv for non-main phy devices. Then NULL pointer dereference issue will occur. Due to only external phy or internal phy is necessary, add phy_mask for ax88772 mdio bus to workarnoud the issue.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-20 Improper Input Validation\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n7\nHIGH\nCVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-38727\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: netlink: avoid infinite retry looping in netlink_unicast() netlink_attachskb() checks for the socket's read memory allocation constraints. Firstly, it has: rmem < READ_ONCE(sk->sk_rcvbuf) to check if the just increased rmem value fits into the socket's receive buffer. If not, it proceeds and tries to wait for the memory under: rmem + skb->truesize > READ_ONCE(sk->sk_rcvbuf) The checks don't cover the case when skb->truesize + sk->sk_rmem_alloc is equal to sk->sk_rcvbuf. Thus the function neither successfully accepts these conditions, nor manages to reschedule the task - and is called in retry loop for indefinite time which is caught as: rcu: INFO: rcu_sched self-detected stall on CPU rcu: 0-....: (25999 ticks this GP) idle=ef2/1/0x4000000000000000 softirq=262269/262269 fqs=6212 (t=26000 jiffies g=230833 q=259957) NMI backtrace for cpu 0 CPU: 0 PID: 22 Comm: kauditd Not tainted 5.10.240 #68 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.17.0-4.fc42 04/01/2014 Call Trace: dump_stack lib/dump_stack.c:120 nmi_cpu_backtrace.cold lib/nmi_backtrace.c:105 nmi_trigger_cpumask_backtrace lib/nmi_backtrace.c:62 rcu_dump_cpu_stacks kernel/rcu/tree_stall.h:335 rcu_sched_clock_irq.cold kernel/rcu/tree.c:2590 update_process_times kernel/time/timer.c:1953 tick_sched_handle kernel/time/tick-sched.c:227 tick_sched_timer kernel/time/tick-sched.c:1399 __hrtimer_run_queues kernel/time/hrtimer.c:1652 hrtimer_interrupt kernel/time/hrtimer.c:1717 __sysvec_apic_timer_interrupt arch/x86/kernel/apic/apic.c:1113 asm_call_irq_on_stack arch/x86/entry/entry_64.S:808 netlink_attachskb net/netlink/af_netlink.c:1234 netlink_unicast net/netlink/af_netlink.c:1349 kauditd_send_queue kernel/audit.c:776 kauditd_thread kernel/audit.c:897 kthread kernel/kthread.c:328 ret_from_fork arch/x86/entry/entry_64.S:304 Restore the original behavior of the check which commit in Fixes accidentally missed when restructuring the code. Found by Linux Verification Center (linuxtesting.org).\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-835 Loop with Unreachable Exit Condition ('Infinite Loop')\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-38728\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: smb3: fix for slab out of bounds on mount to ksmbd With KASAN enabled, it is possible to get a slab out of bounds during mount to ksmbd due to missing check in parse_server_interfaces() (see below): BUG: KASAN: slab-out-of-bounds in parse_server_interfaces+0x14ee/0x1880 [cifs] Read of size 4 at addr ffff8881433dba98 by task mount/9827 CPU: 5 UID: 0 PID: 9827 Comm: mount Tainted: G OE 6.16.0-rc2-kasan #2 PREEMPT(voluntary) Tainted: [O]=OOT_MODULE, [E]=UNSIGNED_MODULE Hardware name: Dell Inc. Precision Tower 3620/0MWYPT, BIOS 2.13.1 06/14/2019 Call Trace: dump_stack_lvl+0x9f/0xf0 print_report+0xd1/0x670 __virt_addr_valid+0x22c/0x430 ? parse_server_interfaces+0x14ee/0x1880 [cifs] ? kasan_complete_mode_report_info+0x2a/0x1f0 ? parse_server_interfaces+0x14ee/0x1880 [cifs] kasan_report+0xd6/0x110 parse_server_interfaces+0x14ee/0x1880 [cifs] __asan_report_load_n_noabort+0x13/0x20 parse_server_interfaces+0x14ee/0x1880 [cifs] ? __pfx_parse_server_interfaces+0x10/0x10 [cifs] ? trace_hardirqs_on+0x51/0x60 SMB3_request_interfaces+0x1ad/0x3f0 [cifs] ? __pfx_SMB3_request_interfaces+0x10/0x10 [cifs] ? SMB2_tcon+0x23c/0x15d0 [cifs] smb3_qfs_tcon+0x173/0x2b0 [cifs] ? __pfx_smb3_qfs_tcon+0x10/0x10 [cifs] ? cifs_get_tcon+0x105d/0x2120 [cifs] ? do_raw_spin_unlock+0x5d/0x200 ? cifs_get_tcon+0x105d/0x2120 [cifs] ? __pfx_smb3_qfs_tcon+0x10/0x10 [cifs] cifs_mount_get_tcon+0x369/0xb90 [cifs] ? dfs_cache_find+0xe7/0x150 [cifs] dfs_mount_share+0x985/0x2970 [cifs] ? check_path.constprop.0+0x28/0x50 ? save_trace+0x54/0x370 ? __pfx_dfs_mount_share+0x10/0x10 [cifs] ? __lock_acquire+0xb82/0x2ba0 ? __kasan_check_write+0x18/0x20 cifs_mount+0xbc/0x9e0 [cifs] ? __pfx_cifs_mount+0x10/0x10 [cifs] ? do_raw_spin_unlock+0x5d/0x200 ? cifs_setup_cifs_sb+0x29d/0x810 [cifs] cifs_smb3_do_mount+0x263/0x1990 [cifs]\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-125 Out-of-bounds Read\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-38729\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: ALSA: usb-audio: Validate UAC3 power domain descriptors, too UAC3 power domain descriptors need to be verified with its variable bLength for avoiding the unexpected OOB accesses by malicious firmware, too.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-125 Out-of-bounds Read\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n7.1\nHIGH\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-38732\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: netfilter: nf_reject: don't leak dst refcount for loopback packets recent patches to add a WARN() when replacing skb dst entry found an old bug: WARNING: include/linux/skbuff.h:1165 skb_dst_check_unset include/linux/skbuff.h:1164 [inline] WARNING: include/linux/skbuff.h:1165 skb_dst_set include/linux/skbuff.h:1210 [inline] WARNING: include/linux/skbuff.h:1165 nf_reject_fill_skb_dst+0x2a4/0x330 net/ipv4/netfilter/nf_reject_ipv4.c:234 [..] Call Trace: nf_send_unreach+0x17b/0x6e0 net/ipv4/netfilter/nf_reject_ipv4.c:325 nft_reject_inet_eval+0x4bc/0x690 net/netfilter/nft_reject_inet.c:27 expr_call_ops_eval net/netfilter/nf_tables_core.c:237 [inline] .. This is because blamed commit forgot about loopback packets. Such packets already have a dst_entry attached, even at PRE_ROUTING stage. Instead of checking hook just check if the skb already has a route attached to it.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-911 Improper Update of Reference Count\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.8\nMEDIUM\nCVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-38735\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: gve: prevent ethtool ops after shutdown A crash can occur if an ethtool operation is invoked after shutdown() is called. shutdown() is invoked during system shutdown to stop DMA operations without performing expensive deallocations. It is discouraged to unregister the netdev in this path, so the device may still be visible to userspace and kernel helpers. In gve, shutdown() tears down most internal data structures. If an ethtool operation is dispatched after shutdown(), it will dereference freed or NULL pointers, leading to a kernel panic. While graceful shutdown normally quiesces userspace before invoking the reboot syscall, forced shutdowns (as observed on GCP VMs) can still trigger this path. Fix by calling netif_device_detach() in shutdown(). This marks the device as detached so the ethtool ioctl handler will skip dispatching operations to the driver.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-664 Improper Control of a Resource Through its Lifetime\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-38736\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: net: usb: asix_devices: Fix PHY address mask in MDIO bus initialization Syzbot reported shift-out-of-bounds exception on MDIO bus initialization. The PHY address should be masked to 5 bits (0-31). Without this mask, invalid PHY addresses could be used, potentially causing issues with MDIO bus operations. Fix this by masking the PHY address with 0x1f (31 decimal) to ensure it stays within the valid range.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-20 Improper Input Validation\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39673\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: ppp: fix race conditions in ppp_fill_forward_path ppp_fill_forward_path() has two race conditions: 1. The ppp->channels list can change between list_empty() and list_first_entry(), as ppp_lock() is not held. If the only channel is deleted in ppp_disconnect_channel(), list_first_entry() may access an empty head or a freed entry, and trigger a panic. 2. pch->chan can be NULL. When ppp_unregister_channel() is called, pch->chan is set to NULL before pch is removed from ppp->channels. Fix these by using a lockless RCU approach: - Use list_first_or_null_rcu() to safely test and access the first list entry. - Convert list modifications on ppp->channels to their RCU variants and add synchronize_net() after removal. - Check for a NULL pch->chan before dereferencing it.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-362 Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.9\nMEDIUM\nCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39675\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Add null pointer check in mod_hdcp_hdcp1_create_session() The function mod_hdcp_hdcp1_create_session() calls the function get_first_active_display(), but does not check its return value. The return value is a null pointer if the display list is empty. This will lead to a null pointer dereference. Add a null pointer check for get_first_active_display() and return MOD_HDCP_STATUS_DISPLAY_NOT_FOUND if the function return null. This is similar to the commit c3e9826a2202 (\"drm/amd/display: Add null pointer check for get_first_active_display()\"). (cherry picked from commit 5e43eb3cd731649c4f8b9134f857be62a416c893)\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-20 Improper Input Validation\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39676\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: scsi: qla4xxx: Prevent a potential error pointer dereference The qla4xxx_get_ep_fwdb() function is supposed to return NULL on error, but qla4xxx_ep_connect() returns error pointers. Propagating the error pointers will lead to an Oops in the caller, so change the error pointers to NULL.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-394 Unexpected Status Code or Return Value\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.1\nMEDIUM\nCVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39681\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: x86/cpu/hygon: Add missing resctrl_cpu_detect() in bsp_init helper Since 923f3a2b48bd (\"x86/resctrl: Query LLC monitoring properties once during boot\") resctrl_cpu_detect() has been moved from common CPU initialization code to the vendor-specific BSP init helper, while Hygon didn't put that call in their code. This triggers a division by zero fault during early booting stage on our machines with X86_FEATURE_CQM* supported, where get_rdt_mon_resources() tries to calculate mon_l3_config with uninitialized boot_cpu_data.x86_cache_occ_scale. Add the missing resctrl_cpu_detect() in the Hygon BSP init helper. [ bp: Massage commit message. ]\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-369 Divide By Zero\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39682\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: tls: fix handling of zero-length records on the rx_list Each recvmsg() call must process either - only contiguous DATA records (any number of them) - one non-DATA record If the next record has different type than what has already been processed we break out of the main processing loop. If the record has already been decrypted (which may be the case for TLS 1.3 where we don't know type until decryption) we queue the pending record to the rx_list. Next recvmsg() will pick it up from there. Queuing the skb to rx_list after zero-copy decrypt is not possible, since in that case we decrypted directly to the user space buffer, and we don't have an skb to queue (darg.skb points to the ciphertext skb for access to metadata like length). Only data records are allowed zero-copy, and we break the processing loop after each non-data record. So we should never zero-copy and then find out that the record type has changed. The corner case we missed is when the initial record comes from rx_list, and it's zero length.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-20 Improper Input Validation\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n7\nHIGH\nCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39683\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: tracing: Limit access to parser->buffer when trace_get_user failed When the length of the string written to set_ftrace_filter exceeds FTRACE_BUFF_MAX, the following KASAN alarm will be triggered: BUG: KASAN: slab-out-of-bounds in strsep+0x18c/0x1b0 Read of size 1 at addr ffff0000d00bd5ba by task ash/165 CPU: 1 UID: 0 PID: 165 Comm: ash Not tainted 6.16.0-g6bcdbd62bd56-dirty Hardware name: linux,dummy-virt (DT) Call trace: show_stack+0x34/0x50 (C) dump_stack_lvl+0xa0/0x158 print_address_description.constprop.0+0x88/0x398 print_report+0xb0/0x280 kasan_report+0xa4/0xf0 __asan_report_load1_noabort+0x20/0x30 strsep+0x18c/0x1b0 ftrace_process_regex.isra.0+0x100/0x2d8 ftrace_regex_release+0x484/0x618 __fput+0x364/0xa58 ____fput+0x28/0x40 task_work_run+0x154/0x278 do_notify_resume+0x1f0/0x220 el0_svc+0xec/0xf0 el0t_64_sync_handler+0xa0/0xe8 el0t_64_sync+0x1ac/0x1b0 The reason is that trace_get_user will fail when processing a string longer than FTRACE_BUFF_MAX, but not set the end of parser->buffer to 0. Then an OOB access will be triggered in ftrace_regex_release-> ftrace_process_regex->strsep->strpbrk. We can solve this problem by limiting access to parser->buffer when trace_get_user failed.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-125 Out-of-bounds Read\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n7.1\nHIGH\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39684\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: comedi: Fix use of uninitialized memory in do_insn_ioctl() and do_insnlist_ioctl() syzbot reports a KMSAN kernel-infoleak in `do_insn_ioctl()`. A kernel buffer is allocated to hold `insn->n` samples (each of which is an `unsigned int`). For some instruction types, `insn->n` samples are copied back to user-space, unless an error code is being returned. The problem is that not all the instruction handlers that need to return data to userspace fill in the whole `insn->n` samples, so that there is an information leak. There is a similar syzbot report for `do_insnlist_ioctl()`, although it does not have a reproducer for it at the time of writing. One culprit is `insn_rw_emulate_bits()` which is used as the handler for `INSN_READ` or `INSN_WRITE` instructions for subdevices that do not have a specific handler for that instruction, but do have an `INSN_BITS` handler. For `INSN_READ` it only fills in at most 1 sample, so if `insn->n` is greater than 1, the remaining `insn->n - 1` samples copied to userspace will be uninitialized kernel data. Another culprit is `vm80xx_ai_insn_read()` in the \"vm80xx\" driver. It never returns an error, even if it fails to fill the buffer. Fix it in `do_insn_ioctl()` and `do_insnlist_ioctl()` by making sure that uninitialized parts of the allocated buffer are zeroed before handling each instruction. Thanks to Arnaud Lecomte for their fix to `do_insn_ioctl()`. That fix replaced the call to `kmalloc_array()` with `kcalloc()`, but it is not always necessary to clear the whole buffer.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-20 Improper Input Validation\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39685\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: comedi: pcl726: Prevent invalid irq number The reproducer passed in an irq number(0x80008000) that was too large, which triggered the oob. Added an interrupt number check to prevent users from passing in an irq number that was too large. If `it->options[1]` is 31, then `1 << it->options[1]` is still invalid because it shifts a 1-bit into the sign bit (which is UB in C). Possible solutions include reducing the upper bound on the `it->options[1]` value to 30 or lower, or using `1U << it->options[1]`. The old code would just not attempt to request the IRQ if the `options[1]` value were invalid. And it would still configure the device without interrupts even if the call to `request_irq` returned an error. So it would be better to combine this test with the test below.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-20 Improper Input Validation\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39686\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: comedi: Make insn_rw_emulate_bits() do insn->n samples The `insn_rw_emulate_bits()` function is used as a default handler for `INSN_READ` instructions for subdevices that have a handler for `INSN_BITS` but not for `INSN_READ`. Similarly, it is used as a default handler for `INSN_WRITE` instructions for subdevices that have a handler for `INSN_BITS` but not for `INSN_WRITE`. It works by emulating the `INSN_READ` or `INSN_WRITE` instruction handling with a constructed `INSN_BITS` instruction. However, `INSN_READ` and `INSN_WRITE` instructions are supposed to be able read or write multiple samples, indicated by the `insn->n` value, but `insn_rw_emulate_bits()` currently only handles a single sample. For `INSN_READ`, the comedi core will copy `insn->n` samples back to user-space. (That triggered KASAN kernel-infoleak errors when `insn->n` was greater than 1, but that is being fixed more generally elsewhere in the comedi core.) Make `insn_rw_emulate_bits()` either handle `insn->n` samples, or return an error, to conform to the general expectation for `INSN_READ` and `INSN_WRITE` handlers.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-20 Improper Input Validation\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39687\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: iio: light: as73211: Ensure buffer holes are zeroed Given that the buffer is copied to a kfifo that ultimately user space can read, ensure we zero it.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-20 Improper Input Validation\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39689\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: ftrace: Also allocate and copy hash for reading of filter files Currently the reader of set_ftrace_filter and set_ftrace_notrace just adds the pointer to the global tracer hash to its iterator. Unlike the writer that allocates a copy of the hash, the reader keeps the pointer to the filter hashes. This is problematic because this pointer is static across function calls that release the locks that can update the global tracer hashes. This can cause UAF and similar bugs. Allocate and copy the hash for reading the filter files like it is done for the writers. This not only fixes UAF bugs, but also makes the code a bit simpler as it doesn't have to differentiate when to free the iterator's hash between writers and readers.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-416 Use After Free\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n7.8\nHIGH\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39691\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: fs/buffer: fix use-after-free when call bh_read() helper There's issue as follows: BUG: KASAN: stack-out-of-bounds in end_buffer_read_sync+0xe3/0x110 Read of size 8 at addr ffffc9000168f7f8 by task swapper/3/0 CPU: 3 UID: 0 PID: 0 Comm: swapper/3 Not tainted 6.16.0-862.14.0.6.x86_64 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996) Call Trace: dump_stack_lvl+0x55/0x70 print_address_description.constprop.0+0x2c/0x390 print_report+0xb4/0x270 kasan_report+0xb8/0xf0 end_buffer_read_sync+0xe3/0x110 end_bio_bh_io_sync+0x56/0x80 blk_update_request+0x30a/0x720 scsi_end_request+0x51/0x2b0 scsi_io_completion+0xe3/0x480 ? scsi_device_unbusy+0x11e/0x160 blk_complete_reqs+0x7b/0x90 handle_softirqs+0xef/0x370 irq_exit_rcu+0xa5/0xd0 sysvec_apic_timer_interrupt+0x6e/0x90 Above issue happens when do ntfs3 filesystem mount, issue may happens as follows: mount IRQ ntfs_fill_super read_cache_page do_read_cache_folio filemap_read_folio mpage_read_folio do_mpage_readpage ntfs_get_block_vbo bh_read submit_bh wait_on_buffer(bh); blk_complete_reqs scsi_io_completion scsi_end_request blk_update_request end_bio_bh_io_sync end_buffer_read_sync __end_buffer_read_notouch unlock_buffer wait_on_buffer(bh);--> return will return to caller put_bh --> trigger stack-out-of-bounds In the mpage_read_folio() function, the stack variable 'map_bh' is passed to ntfs_get_block_vbo(). Once unlock_buffer() unlocks and wait_on_buffer() returns to continue processing, the stack variable is likely to be reclaimed. Consequently, during the end_buffer_read_sync() process, calling put_bh() may result in stack overrun. If the bh is not allocated on the stack, it belongs to a folio. Freeing a buffer head which belongs to a folio is done by drop_buffers() which will fail to free buffers which are still locked. So it is safe to call put_bh() before __end_buffer_read_notouch().\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-416 Use After Free\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n4.4\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39692\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: smb: server: split ksmbd_rdma_stop_listening() out of ksmbd_rdma_destroy() We can't call destroy_workqueue(smb_direct_wq); before stop_sessions()! Otherwise already existing connections try to use smb_direct_wq as a NULL pointer.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-20 Improper Input Validation\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39693\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Avoid a NULL pointer dereference [WHY] Although unlikely drm_atomic_get_new_connector_state() or drm_atomic_get_old_connector_state() can return NULL. [HOW] Check returns before dereference. (cherry picked from commit 1e5e8d672fec9f2ab352be121be971877bff2af9)\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-476 NULL Pointer Dereference\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n4.7\nMEDIUM\nCVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39694\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: s390/sclp: Fix SCCB present check Tracing code called by the SCLP interrupt handler contains early exits if the SCCB address associated with an interrupt is NULL. This check is performed after physical to virtual address translation. If the kernel identity mapping does not start at address zero, the resulting virtual address is never zero, so that the NULL checks won't work. Subsequently this may result in incorrect accesses to the first page of the identity mapping. Fix this by introducing a function that handles the NULL case before address translation.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-1285 Improper Validation of Specified Index, Position, or Offset in Input\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n7\nHIGH\nCVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39697\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: NFS: Fix a race when updating an existing write After nfs_lock_and_join_requests() tests for whether the request is still attached to the mapping, nothing prevents a call to nfs_inode_remove_request() from succeeding until we actually lock the page group. The reason is that whoever called nfs_inode_remove_request() doesn't necessarily have a lock on the page group head. So in order to avoid races, let's take the page group lock earlier in nfs_lock_and_join_requests(), and hold it across the removal of the request in nfs_inode_remove_request().\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-362 Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n4.7\nMEDIUM\nCVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39701\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: ACPI: pfr_update: Fix the driver update version check The security-version-number check should be used rather than the runtime version check for driver updates. Otherwise, the firmware update would fail when the update binary had a lower runtime version number than the current one. [ rjw: Changelog edits ]\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-1025 Comparison Using Wrong Factors\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39702\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: ipv6: sr: Fix MAC comparison to be constant-time To prevent timing attacks, MACs need to be compared in constant time. Use the appropriate helper function for this.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-208 Observable Timing Discrepancy\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n7.1\nHIGH\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39703\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: net, hsr: reject HSR frame if skb can't hold tag Receiving HSR frame with insufficient space to hold HSR tag in the skb can result in a crash (kernel BUG): [ 45.390915] skbuff: skb_under_panic: text:ffffffff86f32cac len:26 put:14 head:ffff888042418000 data:ffff888042417ff4 tail:0xe end:0x180 dev:bridge_slave_1 [ 45.392559] ------------[ cut here ]------------ [ 45.392912] kernel BUG at net/core/skbuff.c:211! [ 45.393276] Oops: invalid opcode: 0000 [#1] SMP DEBUG_PAGEALLOC KASAN NOPTI [ 45.393809] CPU: 1 UID: 0 PID: 2496 Comm: reproducer Not tainted 6.15.0 #12 PREEMPT(undef) [ 45.394433] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.16.3-0-ga6ed6b701f0a-prebuilt.qemu.org 04/01/2014 [ 45.395273] RIP: 0010:skb_panic+0x15b/0x1d0 [ 45.402911] Call Trace: [ 45.403105] [ 45.404470] skb_push+0xcd/0xf0 [ 45.404726] br_dev_queue_push_xmit+0x7c/0x6c0 [ 45.406513] br_forward_finish+0x128/0x260 [ 45.408483] __br_forward+0x42d/0x590 [ 45.409464] maybe_deliver+0x2eb/0x420 [ 45.409763] br_flood+0x174/0x4a0 [ 45.410030] br_handle_frame_finish+0xc7c/0x1bc0 [ 45.411618] br_handle_frame+0xac3/0x1230 [ 45.413674] __netif_receive_skb_core.constprop.0+0x808/0x3df0 [ 45.422966] __netif_receive_skb_one_core+0xb4/0x1f0 [ 45.424478] __netif_receive_skb+0x22/0x170 [ 45.424806] process_backlog+0x242/0x6d0 [ 45.425116] __napi_poll+0xbb/0x630 [ 45.425394] net_rx_action+0x4d1/0xcc0 [ 45.427613] handle_softirqs+0x1a4/0x580 [ 45.427926] do_softirq+0x74/0x90 [ 45.428196] This issue was found by syzkaller. The panic happens in br_dev_queue_push_xmit() once it receives a corrupted skb with ETH header already pushed in linear data. When it attempts the skb_push() call, there's not enough headroom and skb_push() panics. The corrupted skb is put on the queue by HSR layer, which makes a sequence of unintended transformations when it receives a specific corrupted HSR frame (with incomplete TAG). Fix it by dropping and consuming frames that are not long enough to contain both ethernet and hsr headers. Alternative fix would be to check for enough headroom before skb_push() in br_dev_queue_push_xmit(). In the reproducer, this is injected via AF_PACKET, but I don't easily see why it couldn't be sent over the wire from adjacent network. Further Details: In the reproducer, the following network interface chain is set up: \u250c\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2510 \u250c\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2510 \u2502 veth0_to_hsr \u251c\u2500\u2500\u2500\u2524 hsr_slave0 \u253c\u2500\u2500\u2500\u2510 \u2514\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2518 \u2514\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2518 \u2502 \u2502 \u250c\u2500\u2500\u2500\u2500\u2500\u2500\u2510 \u251c\u2500\u2524 hsr0 \u251c\u2500\u2500\u2500\u2510 \u2502 \u2514\u2500\u2500\u2500\u2500\u2500\u2500\u2518 \u2502 \u250c\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2510 \u250c\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2510 \u2502 \u2502\u250c\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2510 \u2502 veth1_to_hsr \u253c\u2500\u2500\u2500\u2524 hsr_slave1 \u251c\u2500\u2500\u2500\u2518 \u2514\u2524 \u2502 \u2514\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2518 \u2514\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2518 \u250c\u253c bridge \u2502 \u2502\u2502 \u2502 \u2502\u2514\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2518 \u2502 \u250c\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2510 \u2502 \u2502 ... \u251c\u2500\u2500\u2500\u2500\u2500\u2500\u2518 \u2514\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2518 To trigger the events leading up to crash, reproducer sends a corrupted HSR fr ---truncated---\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-1286 Improper Validation of Syntactic Correctness of Input\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n6.5\nMEDIUM\nCVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39706\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: drm/amdkfd: Destroy KFD debugfs after destroy KFD wq Since KFD proc content was moved to kernel debugfs, we can't destroy KFD debugfs before kfd_process_destroy_wq. Move kfd_process_destroy_wq prior to kfd_debugfs_fini to fix a kernel NULL pointer problem. It happens when /sys/kernel/debug/kfd was already destroyed in kfd_debugfs_fini but kfd_process_destroy_wq calls kfd_debugfs_remove_process. This line debugfs_remove_recursive(entry->proc_dentry); tries to remove /sys/kernel/debug/kfd/proc/ while /sys/kernel/debug/kfd is already gone. It hangs the kernel by kernel NULL pointer. (cherry picked from commit 0333052d90683d88531558dcfdbf2525cc37c233)\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-20 Improper Input Validation\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39709\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: media: venus: protect against spurious interrupts during probe Make sure the interrupt handler is initialized before the interrupt is registered. If the IRQ is registered before hfi_create(), it's possible that an interrupt fires before the handler setup is complete, leading to a NULL dereference. This error condition has been observed during system boot on Rb3Gen2.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-20 Improper Input Validation\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39710\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: media: venus: Add a check for packet size after reading from shared memory Add a check to ensure that the packet size does not exceed the number of available words after reading the packet header from shared memory. This ensures that the size provided by the firmware is safe to process and prevent potential out-of-bounds memory access.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-20 Improper Input Validation\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39713\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: media: rainshadow-cec: fix TOCTOU race condition in rain_interrupt() In the interrupt handler rain_interrupt(), the buffer full check on rain->buf_len is performed before acquiring rain->buf_lock. This creates a Time-of-Check to Time-of-Use (TOCTOU) race condition, as rain->buf_len is concurrently accessed and modified in the work handler rain_irq_work_handler() under the same lock. Multiple interrupt invocations can race, with each reading buf_len before it becomes full and then proceeding. This can lead to both interrupts attempting to write to the buffer, incrementing buf_len beyond its capacity (DATA_SIZE) and causing a buffer overflow. Fix this bug by moving the spin_lock() to before the buffer full check. This ensures that the check and the subsequent buffer modification are performed atomically, preventing the race condition. An corresponding spin_unlock() is added to the overflow path to correctly release the lock. This possible bug was found by an experimental static analysis tool developed by our team.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-20 Improper Input Validation\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39714\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: media: usbtv: Lock resolution while streaming When an program is streaming (ffplay) and another program (qv4l2) changes the TV standard from NTSC to PAL, the kernel crashes due to trying to copy to unmapped memory. Changing from NTSC to PAL increases the resolution in the usbtv struct, but the video plane buffer isn't adjusted, so it overflows. [hverkuil: call vb2_is_busy instead of vb2_is_streaming]\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-20 Improper Input Validation\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39715\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: parisc: Revise gateway LWS calls to probe user read access We use load and stbys,e instructions to trigger memory reference interruptions without writing to memory. Because of the way read access support is implemented, read access interruptions are only triggered at privilege levels 2 and 3. The kernel and gateway page execute at privilege level 0, so this code never triggers a read access interruption. Thus, it is currently possible for user code to execute a LWS compare and swap operation at an address that is read protected at privilege level 3 (PRIV_USER). Fix this by probing read access rights at privilege level 3 and branching to lws_fault if access isn't allowed.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-20 Improper Input Validation\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39716\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: parisc: Revise __get_user() to probe user read access Because of the way read access support is implemented, read access interruptions are only triggered at privilege levels 2 and 3. The kernel executes at privilege level 0, so __get_user() never triggers a read access interruption (code 26). Thus, it is currently possible for user code to access a read protected address via a system call. Fix this by probing read access rights at privilege level 3 (PRIV_USER) and setting __gu_err to -EFAULT (-14) if access isn't allowed. Note the cmpiclr instruction does a 32-bit compare because COND macro doesn't work inside asm.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-20 Improper Input Validation\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39718\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: vsock/virtio: Validate length in packet header before skb_put() When receiving a vsock packet in the guest, only the virtqueue buffer size is validated prior to virtio_vsock_skb_rx_put(). Unfortunately, virtio_vsock_skb_rx_put() uses the length from the packet header as the length argument to skb_put(), potentially resulting in SKB overflow if the host has gone wonky. Validate the length as advertised by the packet header before calling virtio_vsock_skb_rx_put().\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-787 Out-of-bounds Write\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n7.6\nHIGH\nCVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39719\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: iio: imu: bno055: fix OOB access of hw_xlate array Fix a potential out-of-bounds array access of the hw_xlate array in bno055.c. In bno055_get_regmask(), hw_xlate was iterated over the length of the vals array instead of the length of the hw_xlate array. In the case of bno055_gyr_scale, the vals array is larger than the hw_xlate array, so this could result in an out-of-bounds access. In practice, this shouldn't happen though because a match should always be found which breaks out of the for loop before it iterates beyond the end of the hw_xlate array. By adding a new hw_xlate_len field to the bno055_sysfs_attr, we can be sure we are iterating over the correct length.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-20 Improper Input Validation\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39724\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: serial: 8250: fix panic due to PSLVERR When the PSLVERR_RESP_EN parameter is set to 1, the device generates an error response if an attempt is made to read an empty RBR (Receive Buffer Register) while the FIFO is enabled. In serial8250_do_startup(), calling serial_port_out(port, UART_LCR, UART_LCR_WLEN8) triggers dw8250_check_lcr(), which invokes dw8250_force_idle() and serial8250_clear_and_reinit_fifos(). The latter function enables the FIFO via serial_out(p, UART_FCR, p->fcr). Execution proceeds to the serial_port_in(port, UART_RX). This satisfies the PSLVERR trigger condition. When another CPU (e.g., using printk()) is accessing the UART (UART is busy), the current CPU fails the check (value & ~UART_LCR_SPAR) == (lcr & ~UART_LCR_SPAR) in dw8250_check_lcr(), causing it to enter dw8250_force_idle(). Put serial_port_out(port, UART_LCR, UART_LCR_WLEN8) under the port->lock to fix this issue. Panic backtrace: [ 0.442336] Oops - unknown exception [#1] [ 0.442343] epc : dw8250_serial_in32+0x1e/0x4a [ 0.442351] ra : serial8250_do_startup+0x2c8/0x88e ... [ 0.442416] console_on_rootfs+0x26/0x70\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-362 Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39736\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: mm/kmemleak: avoid deadlock by moving pr_warn() outside kmemleak_lock When netpoll is enabled, calling pr_warn_once() while holding kmemleak_lock in mem_pool_alloc() can cause a deadlock due to lock inversion with the netconsole subsystem. This occurs because pr_warn_once() may trigger netpoll, which eventually leads to __alloc_skb() and back into kmemleak code, attempting to reacquire kmemleak_lock. This is the path for the deadlock. mem_pool_alloc() -> raw_spin_lock_irqsave(&kmemleak_lock, flags); -> pr_warn_once() -> netconsole subsystem -> netpoll -> __alloc_skb -> __create_object -> raw_spin_lock_irqsave(&kmemleak_lock, flags); Fix this by setting a flag and issuing the pr_warn_once() after kmemleak_lock is released.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-833 Deadlock\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39737\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: mm/kmemleak: avoid soft lockup in __kmemleak_do_cleanup() A soft lockup warning was observed on a relative small system x86-64 system with 16 GB of memory when running a debug kernel with kmemleak enabled. watchdog: BUG: soft lockup - CPU#8 stuck for 33s! [kworker/8:1:134] The test system was running a workload with hot unplug happening in parallel. Then kemleak decided to disable itself due to its inability to allocate more kmemleak objects. The debug kernel has its CONFIG_DEBUG_KMEMLEAK_MEM_POOL_SIZE set to 40,000. The soft lockup happened in kmemleak_do_cleanup() when the existing kmemleak objects were being removed and deleted one-by-one in a loop via a workqueue. In this particular case, there are at least 40,000 objects that need to be processed and given the slowness of a debug kernel and the fact that a raw_spinlock has to be acquired and released in __delete_object(), it could take a while to properly handle all these objects. As kmemleak has been disabled in this case, the object removal and deletion process can be further optimized as locking isn't really needed. However, it is probably not worth the effort to optimize for such an edge case that should rarely happen. So the simple solution is to call cond_resched() at periodic interval in the iteration loop to avoid soft lockup.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-20 Improper Input Validation\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39738\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: btrfs: do not allow relocation of partially dropped subvolumes [BUG] There is an internal report that balance triggered transaction abort, with the following call trace: item 85 key (594509824 169 0) itemoff 12599 itemsize 33 extent refs 1 gen 197740 flags 2 ref#0: tree block backref root 7 item 86 key (594558976 169 0) itemoff 12566 itemsize 33 extent refs 1 gen 197522 flags 2 ref#0: tree block backref root 7 ... BTRFS error (device loop0): extent item not found for insert, bytenr 594526208 num_bytes 16384 parent 449921024 root_objectid 934 owner 1 offset 0 BTRFS error (device loop0): failed to run delayed ref for logical 594526208 num_bytes 16384 type 182 action 1 ref_mod 1: -117 ------------[ cut here ]------------ BTRFS: Transaction aborted (error -117) WARNING: CPU: 1 PID: 6963 at ../fs/btrfs/extent-tree.c:2168 btrfs_run_delayed_refs+0xfa/0x110 [btrfs] And btrfs check doesn't report anything wrong related to the extent tree. [CAUSE] The cause is a little complex, firstly the extent tree indeed doesn't have the backref for 594526208. The extent tree only have the following two backrefs around that bytenr on-disk: item 65 key (594509824 METADATA_ITEM 0) itemoff 13880 itemsize 33 refs 1 gen 197740 flags TREE_BLOCK tree block skinny level 0 (176 0x7) tree block backref root CSUM_TREE item 66 key (594558976 METADATA_ITEM 0) itemoff 13847 itemsize 33 refs 1 gen 197522 flags TREE_BLOCK tree block skinny level 0 (176 0x7) tree block backref root CSUM_TREE But the such missing backref item is not an corruption on disk, as the offending delayed ref belongs to subvolume 934, and that subvolume is being dropped: item 0 key (934 ROOT_ITEM 198229) itemoff 15844 itemsize 439 generation 198229 root_dirid 256 bytenr 10741039104 byte_limit 0 bytes_used 345571328 last_snapshot 198229 flags 0x1000000000001(RDONLY) refs 0 drop_progress key (206324 EXTENT_DATA 2711650304) drop_level 2 level 2 generation_v2 198229 And that offending tree block 594526208 is inside the dropped range of that subvolume. That explains why there is no backref item for that bytenr and why btrfs check is not reporting anything wrong. But this also shows another problem, as btrfs will do all the orphan subvolume cleanup at a read-write mount. So half-dropped subvolume should not exist after an RW mount, and balance itself is also exclusive to subvolume cleanup, meaning we shouldn't hit a subvolume half-dropped during relocation. The root cause is, there is no orphan item for this subvolume. In fact there are 5 subvolumes from around 2021 that have the same problem. It looks like the original report has some older kernels running, and caused those zombie subvolumes. Thankfully upstream commit 8d488a8c7ba2 (\"btrfs: fix subvolume/snapshot deletion not triggered on mount\") has long fixed the bug. [ENHANCEMENT] For repairing such old fs, btrfs-progs will be enhanced. Considering how delayed the problem will show up (at run delayed ref time) and at that time we have to abort transaction already, it is too late. Instead here we reject any half-dropped subvolume for reloc tree at the earliest time, preventing confusion and extra time wasted on debugging similar bugs.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-20 Improper Input Validation\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39742\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: RDMA: hfi1: fix possible divide-by-zero in find_hw_thread_mask() The function divides number of online CPUs by num_core_siblings, and later checks the divider by zero. This implies a possibility to get and divide-by-zero runtime error. Fix it by moving the check prior to division. This also helps to save one indentation level.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-369 Divide By Zero\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39743\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: jfs: truncate good inode pages when hard link is 0 The fileset value of the inode copy from the disk by the reproducer is AGGR_RESERVED_I. When executing evict, its hard link number is 0, so its inode pages are not truncated. This causes the bugon to be triggered when executing clear_inode() because nrpages is greater than 0.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-20 Improper Input Validation\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n7\nHIGH\nCVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39749\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: rcu: Protect ->defer_qs_iw_pending from data race On kernels built with CONFIG_IRQ_WORK=y, when rcu_read_unlock() is invoked within an interrupts-disabled region of code [1], it will invoke rcu_read_unlock_special(), which uses an irq-work handler to force the system to notice when the RCU read-side critical section actually ends. That end won't happen until interrupts are enabled at the soonest. In some kernels, such as those booted with rcutree.use_softirq=y, the irq-work handler is used unconditionally. The per-CPU rcu_data structure's ->defer_qs_iw_pending field is updated by the irq-work handler and is both read and updated by rcu_read_unlock_special(). This resulted in the following KCSAN splat: ------------------------------------------------------------------------ BUG: KCSAN: data-race in rcu_preempt_deferred_qs_handler / rcu_read_unlock_special read to 0xffff96b95f42d8d8 of 1 bytes by task 90 on cpu 8: rcu_read_unlock_special+0x175/0x260 __rcu_read_unlock+0x92/0xa0 rt_spin_unlock+0x9b/0xc0 __local_bh_enable+0x10d/0x170 __local_bh_enable_ip+0xfb/0x150 rcu_do_batch+0x595/0xc40 rcu_cpu_kthread+0x4e9/0x830 smpboot_thread_fn+0x24d/0x3b0 kthread+0x3bd/0x410 ret_from_fork+0x35/0x40 ret_from_fork_asm+0x1a/0x30 write to 0xffff96b95f42d8d8 of 1 bytes by task 88 on cpu 8: rcu_preempt_deferred_qs_handler+0x1e/0x30 irq_work_single+0xaf/0x160 run_irq_workd+0x91/0xc0 smpboot_thread_fn+0x24d/0x3b0 kthread+0x3bd/0x410 ret_from_fork+0x35/0x40 ret_from_fork_asm+0x1a/0x30 no locks held by irq_work/8/88. irq event stamp: 200272 hardirqs last enabled at (200272): [] finish_task_switch+0x131/0x320 hardirqs last disabled at (200271): [] __schedule+0x129/0xd70 softirqs last enabled at (0): [] copy_process+0x4df/0x1cc0 softirqs last disabled at (0): [<0000000000000000>] 0x0 ------------------------------------------------------------------------ The problem is that irq-work handlers run with interrupts enabled, which means that rcu_preempt_deferred_qs_handler() could be interrupted, and that interrupt handler might contain an RCU read-side critical section, which might invoke rcu_read_unlock_special(). In the strict KCSAN mode of operation used by RCU, this constitutes a data race on the ->defer_qs_iw_pending field. This commit therefore disables interrupts across the portion of the rcu_preempt_deferred_qs_handler() that updates the ->defer_qs_iw_pending field. This suffices because this handler is not a fast path.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-20 Improper Input Validation\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39752\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: ARM: rockchip: fix kernel hang during smp initialization In order to bring up secondary CPUs main CPU write trampoline code to SRAM. The trampoline code is written while secondary CPUs are powered on (at least that true for RK3188 CPU). Sometimes that leads to kernel hang. Probably because secondary CPU execute trampoline code while kernel doesn't expect. The patch moves SRAM initialization step to the point where all secondary CPUs are powered down. That fixes rarely hangs on RK3188: [ 0.091568] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000 [ 0.091996] rockchip_smp_prepare_cpus: ncores 4\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-364 Signal Handler Race Condition\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39756\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: fs: Prevent file descriptor table allocations exceeding INT_MAX When sysctl_nr_open is set to a very high value (for example, 1073741816 as set by systemd), processes attempting to use file descriptors near the limit can trigger massive memory allocation attempts that exceed INT_MAX, resulting in a WARNING in mm/slub.c: WARNING: CPU: 0 PID: 44 at mm/slub.c:5027 __kvmalloc_node_noprof+0x21a/0x288 This happens because kvmalloc_array() and kvmalloc() check if the requested size exceeds INT_MAX and emit a warning when the allocation is not flagged with __GFP_NOWARN. Specifically, when nr_open is set to 1073741816 (0x3ffffff8) and a process calls dup2(oldfd, 1073741880), the kernel attempts to allocate: - File descriptor array: 1073741880 * 8 bytes = 8,589,935,040 bytes - Multiple bitmaps: ~400MB - Total allocation size: > 8GB (exceeding INT_MAX = 2,147,483,647) Reproducer: 1. Set /proc/sys/fs/nr_open to 1073741816: # echo 1073741816 > /proc/sys/fs/nr_open 2. Run a program that uses a high file descriptor: #include #include int main() { struct rlimit rlim = {1073741824, 1073741824}; setrlimit(RLIMIT_NOFILE, &rlim); dup2(2, 1073741880); // Triggers the warning return 0; } 3. Observe WARNING in dmesg at mm/slub.c:5027 systemd commit a8b627a introduced automatic bumping of fs.nr_open to the maximum possible value. The rationale was that systems with memory control groups (memcg) no longer need separate file descriptor limits since memory is properly accounted. However, this change overlooked that: 1. The kernel's allocation functions still enforce INT_MAX as a maximum size regardless of memcg accounting 2. Programs and tests that legitimately test file descriptor limits can inadvertently trigger massive allocations 3. The resulting allocations (>8GB) are impractical and will always fail systemd's algorithm starts with INT_MAX and keeps halving the value until the kernel accepts it. On most systems, this results in nr_open being set to 1073741816 (0x3ffffff8), which is just under 1GB of file descriptors. While processes rarely use file descriptors near this limit in normal operation, certain selftests (like tools/testing/selftests/core/unshare_test.c) and programs that test file descriptor limits can trigger this issue. Fix this by adding a check in alloc_fdtable() to ensure the requested allocation size does not exceed INT_MAX. This causes the operation to fail with -EMFILE instead of triggering a kernel warning and avoids the impractical >8GB memory allocation request.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-401 Missing Release of Memory after Effective Lifetime\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39757\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: ALSA: usb-audio: Validate UAC3 cluster segment descriptors UAC3 class segment descriptors need to be verified whether their sizes match with the declared lengths and whether they fit with the allocated buffer sizes, too. Otherwise malicious firmware may lead to the unexpected OOB accesses.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-20 Improper Input Validation\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n7.1\nHIGH\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39759\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: btrfs: qgroup: fix race between quota disable and quota rescan ioctl There's a race between a task disabling quotas and another running the rescan ioctl that can result in a use-after-free of qgroup records from the fs_info->qgroup_tree rbtree. This happens as follows: 1) Task A enters btrfs_ioctl_quota_rescan() -> btrfs_qgroup_rescan(); 2) Task B enters btrfs_quota_disable() and calls btrfs_qgroup_wait_for_completion(), which does nothing because at that point fs_info->qgroup_rescan_running is false (it wasn't set yet by task A); 3) Task B calls btrfs_free_qgroup_config() which starts freeing qgroups from fs_info->qgroup_tree without taking the lock fs_info->qgroup_lock; 4) Task A enters qgroup_rescan_zero_tracking() which starts iterating the fs_info->qgroup_tree tree while holding fs_info->qgroup_lock, but task B is freeing qgroup records from that tree without holding the lock, resulting in a use-after-free. Fix this by taking fs_info->qgroup_lock at btrfs_free_qgroup_config(). Also at btrfs_qgroup_rescan() don't start the rescan worker if quotas were already disabled.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-20 Improper Input Validation\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39760\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: usb: core: config: Prevent OOB read in SS endpoint companion parsing usb_parse_ss_endpoint_companion() checks descriptor type before length, enabling a potentially odd read outside of the buffer size. Fix this up by checking the size first before looking at any of the fields in the descriptor.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-20 Improper Input Validation\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39766\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: net/sched: Make cake_enqueue return NET_XMIT_CN when past buffer_limit The following setup can trigger a WARNING in htb_activate due to the condition: !cl->leaf.q->q.qlen tc qdisc del dev lo root tc qdisc add dev lo root handle 1: htb default 1 tc class add dev lo parent 1: classid 1:1 \\ htb rate 64bit tc qdisc add dev lo parent 1:1 handle f: \\ cake memlimit 1b ping -I lo -f -c1 -s64 -W0.001 127.0.0.1 This is because the low memlimit leads to a low buffer_limit, which causes packet dropping. However, cake_enqueue still returns NET_XMIT_SUCCESS, causing htb_enqueue to call htb_activate with an empty child qdisc. We should return NET_XMIT_CN when packets are dropped from the same tin and flow. I do not believe return value of NET_XMIT_CN is necessary for packet drops in the case of ack filtering, as that is meant to optimize performance, not to signal congestion.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-20 Improper Input Validation\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n7\nHIGH\nCVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39770\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: net: gso: Forbid IPv6 TSO with extensions on devices with only IPV6_CSUM When performing Generic Segmentation Offload (GSO) on an IPv6 packet that contains extension headers, the kernel incorrectly requests checksum offload if the egress device only advertises NETIF_F_IPV6_CSUM feature, which has a strict contract: it supports checksum offload only for plain TCP or UDP over IPv6 and explicitly does not support packets with extension headers. The current GSO logic violates this contract by failing to disable the feature for packets with extension headers, such as those used in GREoIPv6 tunnels. This violation results in the device being asked to perform an operation it cannot support, leading to a `skb_warn_bad_offload` warning and a collapse of network throughput. While device TSO/USO is correctly bypassed in favor of software GSO for these packets, the GSO stack must be explicitly told not to request checksum offload. Mask NETIF_F_IPV6_CSUM, NETIF_F_TSO6 and NETIF_F_GSO_UDP_L4 in gso_features_check if the IPv6 header contains extension headers to compute checksum in software. The exception is a BIG TCP extension, which, as stated in commit 68e068cabd2c6c53 (\"net: reenable NETIF_F_IPV6_CSUM offload for BIG TCP packets\"): \"The feature is only enabled on devices that support BIG TCP TSO. The header is only present for PF_PACKET taps like tcpdump, and not transmitted by physical devices.\" kernel log output (truncated): WARNING: CPU: 1 PID: 5273 at net/core/dev.c:3535 skb_warn_bad_offload+0x81/0x140 ... Call Trace: skb_checksum_help+0x12a/0x1f0 validate_xmit_skb+0x1a3/0x2d0 validate_xmit_skb_list+0x4f/0x80 sch_direct_xmit+0x1a2/0x380 __dev_xmit_skb+0x242/0x670 __dev_queue_xmit+0x3fc/0x7f0 ip6_finish_output2+0x25e/0x5d0 ip6_finish_output+0x1fc/0x3f0 ip6_tnl_xmit+0x608/0xc00 [ip6_tunnel] ip6gre_tunnel_xmit+0x1c0/0x390 [ip6_gre] dev_hard_start_xmit+0x63/0x1c0 __dev_queue_xmit+0x6d0/0x7f0 ip6_finish_output2+0x214/0x5d0 ip6_finish_output+0x1fc/0x3f0 ip6_xmit+0x2ca/0x6f0 ip6_finish_output+0x1fc/0x3f0 ip6_xmit+0x2ca/0x6f0 inet6_csk_xmit+0xeb/0x150 __tcp_transmit_skb+0x555/0xa80 tcp_write_xmit+0x32a/0xe90 tcp_sendmsg_locked+0x437/0x1110 tcp_sendmsg+0x2f/0x50 ... skb linear: 00000000: e4 3d 1a 7d ec 30 e4 3d 1a 7e 5d 90 86 dd 60 0e skb linear: 00000010: 00 0a 1b 34 3c 40 20 11 00 00 00 00 00 00 00 00 skb linear: 00000020: 00 00 00 00 00 12 20 11 00 00 00 00 00 00 00 00 skb linear: 00000030: 00 00 00 00 00 11 2f 00 04 01 04 01 01 00 00 00 skb linear: 00000040: 86 dd 60 0e 00 0a 1b 00 06 40 20 23 00 00 00 00 skb linear: 00000050: 00 00 00 00 00 00 00 00 00 12 20 23 00 00 00 00 skb linear: 00000060: 00 00 00 00 00 00 00 00 00 11 bf 96 14 51 13 f9 skb linear: 00000070: ae 27 a0 a8 2b e3 80 18 00 40 5b 6f 00 00 01 01 skb linear: 00000080: 08 0a 42 d4 50 d5 4b 70 f8 1a\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-573 Improper Following of Specification by Caller\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39772\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: drm/hisilicon/hibmc: fix the hibmc loaded failed bug When hibmc loaded failed, the driver use hibmc_unload to free the resource, but the mutexes in mode.config are not init, which will access an NULL pointer. Just change goto statement to return, because hibnc_hw_init() doesn't need to free anything.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-20 Improper Input Validation\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39773\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: net: bridge: fix soft lockup in br_multicast_query_expired() When set multicast_query_interval to a large value, the local variable 'time' in br_multicast_send_query() may overflow. If the time is smaller than jiffies, the timer will expire immediately, and then call mod_timer() again, which creates a loop and may trigger the following soft lockup issue. watchdog: BUG: soft lockup - CPU#1 stuck for 221s! [rb_consumer:66] CPU: 1 UID: 0 PID: 66 Comm: rb_consumer Not tainted 6.16.0+ #259 PREEMPT(none) Call Trace: __netdev_alloc_skb+0x2e/0x3a0 br_ip6_multicast_alloc_query+0x212/0x1b70 __br_multicast_send_query+0x376/0xac0 br_multicast_send_query+0x299/0x510 br_multicast_query_expired.constprop.0+0x16d/0x1b0 call_timer_fn+0x3b/0x2a0 __run_timers+0x619/0x950 run_timer_softirq+0x11c/0x220 handle_softirqs+0x18e/0x560 __irq_exit_rcu+0x158/0x1a0 sysvec_apic_timer_interrupt+0x76/0x90 This issue can be reproduced with: ip link add br0 type bridge echo 1 > /sys/class/net/br0/bridge/multicast_querier echo 0xffffffffffffffff > /sys/class/net/br0/bridge/multicast_query_interval ip link set dev br0 up The multicast_startup_query_interval can also cause this issue. Similar to the commit 99b40610956a (\"net: bridge: mcast: add and enforce query interval minimum\"), add check for the query interval maximum to fix this issue.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-667 Improper Locking\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39776\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: mm/debug_vm_pgtable: clear page table entries at destroy_args() The mm/debug_vm_pagetable test allocates manually page table entries for the tests it runs, using also its manually allocated mm_struct. That in itself is ok, but when it exits, at destroy_args() it fails to clear those entries with the *_clear functions. The problem is that leaves stale entries. If another process allocates an mm_struct with a pgd at the same address, it may end up running into the stale entry. This is happening in practice on a debug kernel with CONFIG_DEBUG_VM_PGTABLE=y, for example this is the output with some extra debugging I added (it prints a warning trace if pgtables_bytes goes negative, in addition to the warning at check_mm() function): [ 2.539353] debug_vm_pgtable: [get_random_vaddr ]: random_vaddr is 0x7ea247140000 [ 2.539366] kmem_cache info [ 2.539374] kmem_cachep 0x000000002ce82385 - freelist 0x0000000000000000 - offset 0x508 [ 2.539447] debug_vm_pgtable: [init_args ]: args->mm is 0x000000002267cc9e (...) [ 2.552800] WARNING: CPU: 5 PID: 116 at include/linux/mm.h:2841 free_pud_range+0x8bc/0x8d0 [ 2.552816] Modules linked in: [ 2.552843] CPU: 5 UID: 0 PID: 116 Comm: modprobe Not tainted 6.12.0-105.debug_vm2.el10.ppc64le+debug #1 VOLUNTARY [ 2.552859] Hardware name: IBM,9009-41A POWER9 (architected) 0x4e0202 0xf000005 of:IBM,FW910.00 (VL910_062) hv:phyp pSeries [ 2.552872] NIP: c0000000007eef3c LR: c0000000007eef30 CTR: c0000000003d8c90 [ 2.552885] REGS: c0000000622e73b0 TRAP: 0700 Not tainted (6.12.0-105.debug_vm2.el10.ppc64le+debug) [ 2.552899] MSR: 800000000282b033 CR: 24002822 XER: 0000000a [ 2.552954] CFAR: c0000000008f03f0 IRQMASK: 0 [ 2.552954] GPR00: c0000000007eef30 c0000000622e7650 c000000002b1ac00 0000000000000001 [ 2.552954] GPR04: 0000000000000008 0000000000000000 c0000000007eef30 ffffffffffffffff [ 2.552954] GPR08: 00000000ffff00f5 0000000000000001 0000000000000048 0000000000004000 [ 2.552954] GPR12: 00000003fa440000 c000000017ffa300 c0000000051d9f80 ffffffffffffffdb [ 2.552954] GPR16: 0000000000000000 0000000000000008 000000000000000a 60000000000000e0 [ 2.552954] GPR20: 4080000000000000 c0000000113af038 00007fffcf130000 0000700000000000 [ 2.552954] GPR24: c000000062a6a000 0000000000000001 8000000062a68000 0000000000000001 [ 2.552954] GPR28: 000000000000000a c000000062ebc600 0000000000002000 c000000062ebc760 [ 2.553170] NIP [c0000000007eef3c] free_pud_range+0x8bc/0x8d0 [ 2.553185] LR [c0000000007eef30] free_pud_range+0x8b0/0x8d0 [ 2.553199] Call Trace: [ 2.553207] [c0000000622e7650] [c0000000007eef30] free_pud_range+0x8b0/0x8d0 (unreliable) [ 2.553229] [c0000000622e7750] [c0000000007f40b4] free_pgd_range+0x284/0x3b0 [ 2.553248] [c0000000622e7800] [c0000000007f4630] free_pgtables+0x450/0x570 [ 2.553274] [c0000000622e78e0] [c0000000008161c0] exit_mmap+0x250/0x650 [ 2.553292] [c0000000622e7a30] [c0000000001b95b8] __mmput+0x98/0x290 [ 2.558344] [c0000000622e7a80] [c0000000001d1018] exit_mm+0x118/0x1b0 [ 2.558361] [c0000000622e7ac0] [c0000000001d141c] do_exit+0x2ec/0x870 [ 2.558376] [c0000000622e7b60] [c0000000001d1ca8] do_group_exit+0x88/0x150 [ 2.558391] [c0000000622e7bb0] [c0000000001d1db8] sys_exit_group+0x48/0x50 [ 2.558407] [c0000000622e7be0] [c00000000003d810] system_call_exception+0x1e0/0x4c0 [ 2.558423] [c0000000622e7e50] [c00000000000d05c] system_call_vectored_common+0x15c/0x2ec (...) [ 2.558892] ---[ end trace 0000000000000000 ]--- [ 2.559022] BUG: Bad rss-counter state mm:000000002267cc9e type:MM_ANONPAGES val:1 [ 2.559037] BUG: non-zero pgtables_bytes on freeing mm: -6144 Here the modprobe process ended up with an allocated mm_struct from the mm_struct slab that was used before by the debug_vm_pgtable test. That is not a problem, since the mm_stru ---truncated---\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-20 Improper Input Validation\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39782\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: jbd2: prevent softlockup in jbd2_log_do_checkpoint() Both jbd2_log_do_checkpoint() and jbd2_journal_shrink_checkpoint_list() periodically release j_list_lock after processing a batch of buffers to avoid long hold times on the j_list_lock. However, since both functions contend for j_list_lock, the combined time spent waiting and processing can be significant. jbd2_journal_shrink_checkpoint_list() explicitly calls cond_resched() when need_resched() is true to avoid softlockups during prolonged operations. But jbd2_log_do_checkpoint() only exits its loop when need_resched() is true, relying on potentially sleeping functions like __flush_batch() or wait_on_buffer() to trigger rescheduling. If those functions do not sleep, the kernel may hit a softlockup. watchdog: BUG: soft lockup - CPU#3 stuck for 156s! [kworker/u129:2:373] CPU: 3 PID: 373 Comm: kworker/u129:2 Kdump: loaded Not tainted 6.6.0+ #10 Hardware name: Huawei TaiShan 2280 /BC11SPCD, BIOS 1.27 06/13/2017 Workqueue: writeback wb_workfn (flush-7:2) pstate: 20000005 (nzCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--) pc : native_queued_spin_lock_slowpath+0x358/0x418 lr : jbd2_log_do_checkpoint+0x31c/0x438 [jbd2] Call trace: native_queued_spin_lock_slowpath+0x358/0x418 jbd2_log_do_checkpoint+0x31c/0x438 [jbd2] __jbd2_log_wait_for_space+0xfc/0x2f8 [jbd2] add_transaction_credits+0x3bc/0x418 [jbd2] start_this_handle+0xf8/0x560 [jbd2] jbd2__journal_start+0x118/0x228 [jbd2] __ext4_journal_start_sb+0x110/0x188 [ext4] ext4_do_writepages+0x3dc/0x740 [ext4] ext4_writepages+0xa4/0x190 [ext4] do_writepages+0x94/0x228 __writeback_single_inode+0x48/0x318 writeback_sb_inodes+0x204/0x590 __writeback_inodes_wb+0x54/0xf8 wb_writeback+0x2cc/0x3d8 wb_do_writeback+0x2e0/0x2f8 wb_workfn+0x80/0x2a8 process_one_work+0x178/0x3e8 worker_thread+0x234/0x3b8 kthread+0xf0/0x108 ret_from_fork+0x10/0x20 So explicitly call cond_resched() in jbd2_log_do_checkpoint() to avoid softlockup.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-20 Improper Input Validation\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39783\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: PCI: endpoint: Fix configfs group list head handling Doing a list_del() on the epf_group field of struct pci_epf_driver in pci_epf_remove_cfs() is not correct as this field is a list head, not a list entry. This list_del() call triggers a KASAN warning when an endpoint function driver which has a configfs attribute group is torn down: ================================================================== BUG: KASAN: slab-use-after-free in pci_epf_remove_cfs+0x17c/0x198 Write of size 8 at addr ffff00010f4a0d80 by task rmmod/319 CPU: 3 UID: 0 PID: 319 Comm: rmmod Not tainted 6.16.0-rc2 #1 NONE Hardware name: Radxa ROCK 5B (DT) Call trace: show_stack+0x2c/0x84 (C) dump_stack_lvl+0x70/0x98 print_report+0x17c/0x538 kasan_report+0xb8/0x190 __asan_report_store8_noabort+0x20/0x2c pci_epf_remove_cfs+0x17c/0x198 pci_epf_unregister_driver+0x18/0x30 nvmet_pci_epf_cleanup_module+0x24/0x30 [nvmet_pci_epf] __arm64_sys_delete_module+0x264/0x424 invoke_syscall+0x70/0x260 el0_svc_common.constprop.0+0xac/0x230 do_el0_svc+0x40/0x58 el0_svc+0x48/0xdc el0t_64_sync_handler+0x10c/0x138 el0t_64_sync+0x198/0x19c ... Remove this incorrect list_del() call from pci_epf_remove_cfs().\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-787 Out-of-bounds Write\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n7.8\nHIGH\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39787\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: soc: qcom: mdt_loader: Ensure we don't read past the ELF header When the MDT loader is used in remoteproc, the ELF header is sanitized beforehand, but that's not necessary the case for other clients. Validate the size of the firmware buffer to ensure that we don't read past the end as we iterate over the header. e_phentsize and e_shentsize are validated as well, to ensure that the assumptions about step size in the traversal are valid.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-125 Out-of-bounds Read\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39788\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: scsi: ufs: exynos: Fix programming of HCI_UTRL_NEXUS_TYPE On Google gs101, the number of UTP transfer request slots (nutrs) is 32, and in this case the driver ends up programming the UTRL_NEXUS_TYPE incorrectly as 0. This is because the left hand side of the shift is 1, which is of type int, i.e. 31 bits wide. Shifting by more than that width results in undefined behaviour. Fix this by switching to the BIT() macro, which applies correct type casting as required. This ensures the correct value is written to UTRL_NEXUS_TYPE (0xffffffff on gs101), and it also fixes a UBSAN shift warning: UBSAN: shift-out-of-bounds in drivers/ufs/host/ufs-exynos.c:1113:21 shift exponent 32 is too large for 32-bit type 'int' For consistency, apply the same change to the nutmrs / UTMRL_NEXUS_TYPE write.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-20 Improper Input Validation\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39790\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: bus: mhi: host: Detect events pointing to unexpected TREs When a remote device sends a completion event to the host, it contains a pointer to the consumed TRE. The host uses this pointer to process all of the TREs between it and the host's local copy of the ring's read pointer. This works when processing completion for chained transactions, but can lead to nasty results if the device sends an event for a single-element transaction with a read pointer that is multiple elements ahead of the host's read pointer. For instance, if the host accesses an event ring while the device is updating it, the pointer inside of the event might still point to an old TRE. If the host uses the channel's xfer_cb() to directly free the buffer pointed to by the TRE, the buffer will be double-freed. This behavior was observed on an ep that used upstream EP stack without 'commit 6f18d174b73d (\"bus: mhi: ep: Update read pointer only after buffer is written\")'. Where the device updated the events ring pointer before updating the event contents, so it left a window where the host was able to access the stale data the event pointed to, before the device had the chance to update them. The usual pattern was that the host received an event pointing to a TRE that is not immediately after the last processed one, so it got treated as if it was a chained transaction, processing all of the TREs in between the two read pointers. This commit aims to harden the host by ensuring transactions where the event points to a TRE that isn't local_rp + 1 are chained. [mani: added stable tag and reworded commit message]\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-415 Double Free\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n6.7\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39794\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: ARM: tegra: Use I/O memcpy to write to IRAM Kasan crashes the kernel trying to check boundaries when using the normal memcpy.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-20 Improper Input Validation\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n7.1\nHIGH\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39795\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: block: avoid possible overflow for chunk_sectors check in blk_stack_limits() In blk_stack_limits(), we check that the t->chunk_sectors value is a multiple of the t->physical_block_size value. However, by finding the chunk_sectors value in bytes, we may overflow the unsigned int which holds chunk_sectors, so change the check to be based on sectors.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-674 Uncontrolled Recursion\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39798\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: NFS: Fix the setting of capabilities when automounting a new filesystem Capabilities cannot be inherited when we cross into a new filesystem. They need to be reset to the minimal defaults, and then probed for again.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-273 Improper Check for Dropped Privileges\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39800\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: btrfs: abort transaction on unexpected eb generation at btrfs_copy_root() If we find an unexpected generation for the extent buffer we are cloning at btrfs_copy_root(), we just WARN_ON() and don't error out and abort the transaction, meaning we allow to persist metadata with an unexpected generation. Instead of warning only, abort the transaction and return -EUCLEAN.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-20 Improper Input Validation\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39801\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: usb: dwc3: Remove WARN_ON for device endpoint command timeouts This commit addresses a rarely observed endpoint command timeout which causes kernel panic due to warn when 'panic_on_warn' is enabled and unnecessary call trace prints when 'panic_on_warn' is disabled. It is seen during fast software-controlled connect/disconnect testcases. The following is one such endpoint command timeout that we observed: 1. Connect ======= ->dwc3_thread_interrupt ->dwc3_ep0_interrupt ->configfs_composite_setup ->composite_setup ->usb_ep_queue ->dwc3_gadget_ep0_queue ->__dwc3_gadget_ep0_queue ->__dwc3_ep0_do_control_data ->dwc3_send_gadget_ep_cmd 2. Disconnect ========== ->dwc3_thread_interrupt ->dwc3_gadget_disconnect_interrupt ->dwc3_ep0_reset_state ->dwc3_ep0_end_control_data ->dwc3_send_gadget_ep_cmd In the issue scenario, in Exynos platforms, we observed that control transfers for the previous connect have not yet been completed and end transfer command sent as a part of the disconnect sequence and processing of USB_ENDPOINT_HALT feature request from the host timeout. This maybe an expected scenario since the controller is processing EP commands sent as a part of the previous connect. It maybe better to remove WARN_ON in all places where device endpoint commands are sent to avoid unnecessary kernel panic due to warn.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-20 Improper Input Validation\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39806\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: HID: multitouch: fix slab out-of-bounds access in mt_report_fixup() A malicious HID device can trigger a slab out-of-bounds during mt_report_fixup() by passing in report descriptor smaller than 607 bytes. mt_report_fixup() attempts to patch byte offset 607 of the descriptor with 0x25 by first checking if byte offset 607 is 0x15 however it lacks bounds checks to verify if the descriptor is big enough before conducting this check. Fix this bug by ensuring the descriptor size is at least 608 bytes before accessing it. Below is the KASAN splat after the out of bounds access happens: [ 13.671954] ================================================================== [ 13.672667] BUG: KASAN: slab-out-of-bounds in mt_report_fixup+0x103/0x110 [ 13.673297] Read of size 1 at addr ffff888103df39df by task kworker/0:1/10 [ 13.673297] [ 13.673297] CPU: 0 UID: 0 PID: 10 Comm: kworker/0:1 Not tainted 6.15.0-00005-gec5d573d83f4-dirty #3 [ 13.673297] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.2-debian-1.16.2-1 04/04 [ 13.673297] Call Trace: [ 13.673297] [ 13.673297] dump_stack_lvl+0x5f/0x80 [ 13.673297] print_report+0xd1/0x660 [ 13.673297] kasan_report+0xe5/0x120 [ 13.673297] __asan_report_load1_noabort+0x18/0x20 [ 13.673297] mt_report_fixup+0x103/0x110 [ 13.673297] hid_open_report+0x1ef/0x810 [ 13.673297] mt_probe+0x422/0x960 [ 13.673297] hid_device_probe+0x2e2/0x6f0 [ 13.673297] really_probe+0x1c6/0x6b0 [ 13.673297] __driver_probe_device+0x24f/0x310 [ 13.673297] driver_probe_device+0x4e/0x220 [ 13.673297] __device_attach_driver+0x169/0x320 [ 13.673297] bus_for_each_drv+0x11d/0x1b0 [ 13.673297] __device_attach+0x1b8/0x3e0 [ 13.673297] device_initial_probe+0x12/0x20 [ 13.673297] bus_probe_device+0x13d/0x180 [ 13.673297] device_add+0xe3a/0x1670 [ 13.673297] hid_add_device+0x31d/0xa40 [...]\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-20 Improper Input Validation\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n7\nHIGH\nCVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39808\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: HID: hid-ntrig: fix unable to handle page fault in ntrig_report_version() in ntrig_report_version(), hdev parameter passed from hid_probe(). sending descriptor to /dev/uhid can make hdev->dev.parent->parent to null if hdev->dev.parent->parent is null, usb_dev has invalid address(0xffffffffffffff58) that hid_to_usb_dev(hdev) returned when usb_rcvctrlpipe() use usb_dev,it trigger page fault error for address(0xffffffffffffff58) add null check logic to ntrig_report_version() before calling hid_to_usb_dev()\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-20 Improper Input Validation\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39812\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: sctp: initialize more fields in sctp_v6_from_sk() syzbot found that sin6_scope_id was not properly initialized, leading to undefined behavior. Clear sin6_scope_id and sin6_flowinfo. BUG: KMSAN: uninit-value in __sctp_v6_cmp_addr+0x887/0x8c0 net/sctp/ipv6.c:649 __sctp_v6_cmp_addr+0x887/0x8c0 net/sctp/ipv6.c:649 sctp_inet6_cmp_addr+0x4f2/0x510 net/sctp/ipv6.c:983 sctp_bind_addr_conflict+0x22a/0x3b0 net/sctp/bind_addr.c:390 sctp_get_port_local+0x21eb/0x2440 net/sctp/socket.c:8452 sctp_get_port net/sctp/socket.c:8523 [inline] sctp_listen_start net/sctp/socket.c:8567 [inline] sctp_inet_listen+0x710/0xfd0 net/sctp/socket.c:8636 __sys_listen_socket net/socket.c:1912 [inline] __sys_listen net/socket.c:1927 [inline] __do_sys_listen net/socket.c:1932 [inline] __se_sys_listen net/socket.c:1930 [inline] __x64_sys_listen+0x343/0x4c0 net/socket.c:1930 x64_sys_call+0x271d/0x3e20 arch/x86/include/generated/asm/syscalls_64.h:51 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xd9/0x210 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f Local variable addr.i.i created at: sctp_get_port net/sctp/socket.c:8515 [inline] sctp_listen_start net/sctp/socket.c:8567 [inline] sctp_inet_listen+0x650/0xfd0 net/sctp/socket.c:8636 __sys_listen_socket net/socket.c:1912 [inline] __sys_listen net/socket.c:1927 [inline] __do_sys_listen net/socket.c:1932 [inline] __se_sys_listen net/socket.c:1930 [inline] __x64_sys_listen+0x343/0x4c0 net/socket.c:1930\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-20 Improper Input Validation\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39813\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: ftrace: Fix potential warning in trace_printk_seq during ftrace_dump When calling ftrace_dump_one() concurrently with reading trace_pipe, a WARN_ON_ONCE() in trace_printk_seq() can be triggered due to a race condition. The issue occurs because: CPU0 (ftrace_dump) CPU1 (reader) echo z > /proc/sysrq-trigger !trace_empty(&iter) trace_iterator_reset(&iter) <- len = size = 0 cat /sys/kernel/tracing/trace_pipe trace_find_next_entry_inc(&iter) __find_next_entry ring_buffer_empty_cpu <- all empty return NULL trace_printk_seq(&iter.seq) WARN_ON_ONCE(s->seq.len >= s->seq.size) In the context between trace_empty() and trace_find_next_entry_inc() during ftrace_dump, the ring buffer data was consumed by other readers. This caused trace_find_next_entry_inc to return NULL, failing to populate `iter.seq`. At this point, due to the prior trace_iterator_reset, both `iter.seq.len` and `iter.seq.size` were set to 0. Since they are equal, the WARN_ON_ONCE condition is triggered. Move the trace_printk_seq() into the if block that checks to make sure the return value of trace_find_next_entry_inc() is non-NULL in ftrace_dump_one(), ensuring the 'iter.seq' is properly populated before subsequent operations.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-20 Improper Input Validation\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39817\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: efivarfs: Fix slab-out-of-bounds in efivarfs_d_compare Observed on kernel 6.6 (present on master as well): BUG: KASAN: slab-out-of-bounds in memcmp+0x98/0xd0 Call trace: kasan_check_range+0xe8/0x190 __asan_loadN+0x1c/0x28 memcmp+0x98/0xd0 efivarfs_d_compare+0x68/0xd8 __d_lookup_rcu_op_compare+0x178/0x218 __d_lookup_rcu+0x1f8/0x228 d_alloc_parallel+0x150/0x648 lookup_open.isra.0+0x5f0/0x8d0 open_last_lookups+0x264/0x828 path_openat+0x130/0x3f8 do_filp_open+0x114/0x248 do_sys_openat2+0x340/0x3c0 __arm64_sys_openat+0x120/0x1a0 If dentry->d_name.len < EFI_VARIABLE_GUID_LEN , 'guid' can become negative, leadings to oob. The issue can be triggered by parallel lookups using invalid filename: T1 T2 lookup_open ->lookup simple_lookup d_add // invalid dentry is added to hash list lookup_open d_alloc_parallel __d_lookup_rcu __d_lookup_rcu_op_compare hlist_bl_for_each_entry_rcu // invalid dentry can be retrieved ->d_compare efivarfs_d_compare // oob Fix it by checking 'guid' before cmp.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-20 Improper Input Validation\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n7\nHIGH\nCVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39819\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: fs/smb: Fix inconsistent refcnt update A possible inconsistent update of refcount was identified in `smb2_compound_op`. Such inconsistent update could lead to possible resource leaks. Why it is a possible bug: 1. In the comment section of the function, it clearly states that the reference to `cfile` should be dropped after calling this function. 2. Every control flow path would check and drop the reference to `cfile`, except the patched one. 3. Existing callers would not handle refcount update of `cfile` if -ENOMEM is returned. To fix the bug, an extra goto label \"out\" is added, to make sure that the cleanup logic would always be respected. As the problem is caused by the allocation failure of `vars`, the cleanup logic between label \"finished\" and \"out\" can be safely ignored. According to the definition of function `is_replayable_error`, the error code of \"-ENOMEM\" is not recoverable. Therefore, the replay logic also gets ignored.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-20 Improper Input Validation\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39823\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: KVM: x86: use array_index_nospec with indices that come from guest min and dest_id are guest-controlled indices. Using array_index_nospec() after the bounds checks clamps these values to mitigate speculative execution side-channels.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-20 Improper Input Validation\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n7\nHIGH\nCVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39824\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: HID: asus: fix UAF via HID_CLAIMED_INPUT validation After hid_hw_start() is called hidinput_connect() will eventually be called to set up the device with the input layer since the HID_CONNECT_DEFAULT connect mask is used. During hidinput_connect() all input and output reports are processed and corresponding hid_inputs are allocated and configured via hidinput_configure_usages(). This process involves slot tagging report fields and configuring usages by setting relevant bits in the capability bitmaps. However it is possible that the capability bitmaps are not set at all leading to the subsequent hidinput_has_been_populated() check to fail leading to the freeing of the hid_input and the underlying input device. This becomes problematic because a malicious HID device like a ASUS ROG N-Key keyboard can trigger the above scenario via a specially crafted descriptor which then leads to a user-after-free when the name of the freed input device is written to later on after hid_hw_start(). Below, report 93 intentionally utilises the HID_UP_UNDEFINED Usage Page which is skipped during usage configuration, leading to the frees. 0x05, 0x0D, // Usage Page (Digitizer) 0x09, 0x05, // Usage (Touch Pad) 0xA1, 0x01, // Collection (Application) 0x85, 0x0D, // Report ID (13) 0x06, 0x00, 0xFF, // Usage Page (Vendor Defined 0xFF00) 0x09, 0xC5, // Usage (0xC5) 0x15, 0x00, // Logical Minimum (0) 0x26, 0xFF, 0x00, // Logical Maximum (255) 0x75, 0x08, // Report Size (8) 0x95, 0x04, // Report Count (4) 0xB1, 0x02, // Feature (Data,Var,Abs) 0x85, 0x5D, // Report ID (93) 0x06, 0x00, 0x00, // Usage Page (Undefined) 0x09, 0x01, // Usage (0x01) 0x15, 0x00, // Logical Minimum (0) 0x26, 0xFF, 0x00, // Logical Maximum (255) 0x75, 0x08, // Report Size (8) 0x95, 0x1B, // Report Count (27) 0x81, 0x02, // Input (Data,Var,Abs) 0xC0, // End Collection Below is the KASAN splat after triggering the UAF: [ 21.672709] ================================================================== [ 21.673700] BUG: KASAN: slab-use-after-free in asus_probe+0xeeb/0xf80 [ 21.673700] Write of size 8 at addr ffff88810a0ac000 by task kworker/1:2/54 [ 21.673700] [ 21.673700] CPU: 1 UID: 0 PID: 54 Comm: kworker/1:2 Not tainted 6.16.0-rc4-g9773391cf4dd-dirty #36 PREEMPT(voluntary) [ 21.673700] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.2-debian-1.16.2-1 04/01/2014 [ 21.673700] Call Trace: [ 21.673700] [ 21.673700] dump_stack_lvl+0x5f/0x80 [ 21.673700] print_report+0xd1/0x660 [ 21.673700] kasan_report+0xe5/0x120 [ 21.673700] __asan_report_store8_noabort+0x1b/0x30 [ 21.673700] asus_probe+0xeeb/0xf80 [ 21.673700] hid_device_probe+0x2ee/0x700 [ 21.673700] really_probe+0x1c6/0x6b0 [ 21.673700] __driver_probe_device+0x24f/0x310 [ 21.673700] driver_probe_device+0x4e/0x220 [...] [ 21.673700] [ 21.673700] Allocated by task 54: [ 21.673700] kasan_save_stack+0x3d/0x60 [ 21.673700] kasan_save_track+0x18/0x40 [ 21.673700] kasan_save_alloc_info+0x3b/0x50 [ 21.673700] __kasan_kmalloc+0x9c/0xa0 [ 21.673700] __kmalloc_cache_noprof+0x139/0x340 [ 21.673700] input_allocate_device+0x44/0x370 [ 21.673700] hidinput_connect+0xcb6/0x2630 [ 21.673700] hid_connect+0xf74/0x1d60 [ 21.673700] hid_hw_start+0x8c/0x110 [ 21.673700] asus_probe+0x5a3/0xf80 [ 21.673700] hid_device_probe+0x2ee/0x700 [ 21.673700] really_probe+0x1c6/0x6b0 [ 21.673700] __driver_probe_device+0x24f/0x310 [ 21.673700] driver_probe_device+0x4e/0x220 [...] [ 21.673700] [ 21.673700] Freed by task 54: [ 21.673700] kasan_save_stack+0x3d/0x60 [ 21.673700] kasan_save_track+0x18/0x40 [ 21.673700] kasan_save_free_info+0x3f/0x60 [ 21.673700] __kasan_slab_free+0x3c/0x50 [ 21.673700] kfre ---truncated---\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-20 Improper Input Validation\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n7\nHIGH\nCVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39825\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: smb: client: fix race with concurrent opens in rename(2) Besides sending the rename request to the server, the rename process also involves closing any deferred close, waiting for outstanding I/O to complete as well as marking all existing open handles as deleted to prevent them from deferring closes, which increases the race window for potential concurrent opens on the target file. Fix this by unhashing the dentry in advance to prevent any concurrent opens on the target.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-20 Improper Input Validation\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n7\nHIGH\nCVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39826\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: net: rose: convert 'use' field to refcount_t The 'use' field in struct rose_neigh is used as a reference counter but lacks atomicity. This can lead to race conditions where a rose_neigh structure is freed while still being referenced by other code paths. For example, when rose_neigh->use becomes zero during an ioctl operation via rose_rt_ioctl(), the structure may be removed while its timer is still active, potentially causing use-after-free issues. This patch changes the type of 'use' from unsigned short to refcount_t and updates all code paths to use rose_neigh_hold() and rose_neigh_put() which operate reference counts atomically.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-20 Improper Input Validation\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39827\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: net: rose: include node references in rose_neigh refcount Current implementation maintains two separate reference counting mechanisms: the 'count' field in struct rose_neigh tracks references from rose_node structures, while the 'use' field (now refcount_t) tracks references from rose_sock. This patch merges these two reference counting systems using 'use' field for proper reference management. Specifically, this patch adds incrementing and decrementing of rose_neigh->use when rose_neigh->count is incremented or decremented. This patch also modifies rose_rt_free(), rose_rt_device_down() and rose_clear_route() to properly release references to rose_neigh objects before freeing a rose_node through rose_remove_node(). These changes ensure rose_neigh structures are properly freed only when all references, including those from rose_node structures, are released. As a result, this resolves a slab-use-after-free issue reported by Syzbot.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-20 Improper Input Validation\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39828\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: atm: atmtcp: Prevent arbitrary write in atmtcp_recv_control(). syzbot reported the splat below. [0] When atmtcp_v_open() or atmtcp_v_close() is called via connect() or close(), atmtcp_send_control() is called to send an in-kernel special message. The message has ATMTCP_HDR_MAGIC in atmtcp_control.hdr.length. Also, a pointer of struct atm_vcc is set to atmtcp_control.vcc. The notable thing is struct atmtcp_control is uAPI but has a space for an in-kernel pointer. struct atmtcp_control { struct atmtcp_hdr hdr; /* must be first */ ... atm_kptr_t vcc; /* both directions */ ... } __ATM_API_ALIGN; typedef struct { unsigned char _[8]; } __ATM_API_ALIGN atm_kptr_t; The special message is processed in atmtcp_recv_control() called from atmtcp_c_send(). atmtcp_c_send() is vcc->dev->ops->send() and called from 2 paths: 1. .ndo_start_xmit() (vcc->send() == atm_send_aal0()) 2. vcc_sendmsg() The problem is sendmsg() does not validate the message length and userspace can abuse atmtcp_recv_control() to overwrite any kptr by atmtcp_control. Let's add a new ->pre_send() hook to validate messages from sendmsg(). [0]: Oops: general protection fault, probably for non-canonical address 0xdffffc00200000ab: 0000 [#1] SMP KASAN PTI KASAN: probably user-memory-access in range [0x0000000100000558-0x000000010000055f] CPU: 0 UID: 0 PID: 5865 Comm: syz-executor331 Not tainted 6.17.0-rc1-syzkaller-00215-gbab3ce404553 #0 PREEMPT(full) Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/12/2025 RIP: 0010:atmtcp_recv_control drivers/atm/atmtcp.c:93 [inline] RIP: 0010:atmtcp_c_send+0x1da/0x950 drivers/atm/atmtcp.c:297 Code: 4d 8d 75 1a 4c 89 f0 48 c1 e8 03 42 0f b6 04 20 84 c0 0f 85 15 06 00 00 41 0f b7 1e 4d 8d b7 60 05 00 00 4c 89 f0 48 c1 e8 03 <42> 0f b6 04 20 84 c0 0f 85 13 06 00 00 66 41 89 1e 4d 8d 75 1c 4c RSP: 0018:ffffc90003f5f810 EFLAGS: 00010203 RAX: 00000000200000ab RBX: 0000000000000000 RCX: 0000000000000000 RDX: ffff88802a510000 RSI: 00000000ffffffff RDI: ffff888030a6068c RBP: ffff88802699fb40 R08: ffff888030a606eb R09: 1ffff1100614c0dd R10: dffffc0000000000 R11: ffffffff8718fc40 R12: dffffc0000000000 R13: ffff888030a60680 R14: 000000010000055f R15: 00000000ffffffff FS: 00007f8d7e9236c0(0000) GS:ffff888125c1c000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 000000000045ad50 CR3: 0000000075bde000 CR4: 00000000003526f0 Call Trace: vcc_sendmsg+0xa10/0xc60 net/atm/common.c:645 sock_sendmsg_nosec net/socket.c:714 [inline] __sock_sendmsg+0x219/0x270 net/socket.c:729 ____sys_sendmsg+0x505/0x830 net/socket.c:2614 ___sys_sendmsg+0x21f/0x2a0 net/socket.c:2668 __sys_sendmsg net/socket.c:2700 [inline] __do_sys_sendmsg net/socket.c:2705 [inline] __se_sys_sendmsg net/socket.c:2703 [inline] __x64_sys_sendmsg+0x19b/0x260 net/socket.c:2703 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xfa/0x3b0 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7f8d7e96a4a9 Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 51 18 00 00 90 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b0 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007f8d7e923198 EFLAGS: 00000246 ORIG_RAX: 000000000000002e RAX: ffffffffffffffda RBX: 00007f8d7e9f4308 RCX: 00007f8d7e96a4a9 RDX: 0000000000000000 RSI: 0000200000000240 RDI: 0000000000000005 RBP: 00007f8d7e9f4300 R08: 65732f636f72702f R09: 65732f636f72702f R10: 65732f636f72702f R11: 0000000000000246 R12: 00007f8d7e9c10ac R13: 00007f8d7e9231a0 R14: 0000200000000200 R15: 0000200000000250 Modules linked in:\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-20 Improper Input Validation\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n7\nHIGH\nCVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39835\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: xfs: do not propagate ENODATA disk errors into xattr code ENODATA (aka ENOATTR) has a very specific meaning in the xfs xattr code; namely, that the requested attribute name could not be found. However, a medium error from disk may also return ENODATA. At best, this medium error may escape to userspace as \"attribute not found\" when in fact it's an IO (disk) error. At worst, we may oops in xfs_attr_leaf_get() when we do: error = xfs_attr_leaf_hasname(args, &bp); if (error == -ENOATTR) { xfs_trans_brelse(args->trans, bp); return error; } because an ENODATA/ENOATTR error from disk leaves us with a null bp, and the xfs_trans_brelse will then null-deref it. As discussed on the list, we really need to modify the lower level IO functions to trap all disk errors and ensure that we don't let unique errors like this leak up into higher xfs functions - many like this should be remapped to EIO. However, this patch directly addresses a reported bug in the xattr code, and should be safe to backport to stable kernels. A larger-scope patch to handle more unique errors at lower levels can follow later. (Note, prior to 07120f1abdff we did not oops, but we did return the wrong error code to userspace.)\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-20 Improper Input Validation\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39838\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: cifs: prevent NULL pointer dereference in UTF16 conversion There can be a NULL pointer dereference bug here. NULL is passed to __cifs_sfu_make_node without checks, which passes it unchecked to cifs_strndup_to_utf16, which in turn passes it to cifs_local_to_utf16_bytes where '*from' is dereferenced, causing a crash. This patch adds a check for NULL 'src' in cifs_strndup_to_utf16 and returns NULL early to prevent dereferencing NULL pointer. Found by Linux Verification Center (linuxtesting.org) with SVACE\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-20 Improper Input Validation\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n7\nHIGH\nCVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39839\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: batman-adv: fix OOB read/write in network-coding decode batadv_nc_skb_decode_packet() trusts coded_len and checks only against skb->len. XOR starts at sizeof(struct batadv_unicast_packet), reducing payload headroom, and the source skb length is not verified, allowing an out-of-bounds read and a small out-of-bounds write. Validate that coded_len fits within the payload area of both destination and source sk_buffs before XORing.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-20 Improper Input Validation\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39841\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: scsi: lpfc: Fix buffer free/clear order in deferred receive path Fix a use-after-free window by correcting the buffer release sequence in the deferred receive path. The code freed the RQ buffer first and only then cleared the context pointer under the lock. Concurrent paths (e.g., ABTS and the repost path) also inspect and release the same pointer under the lock, so the old order could lead to double-free/UAF. Note that the repost path already uses the correct pattern: detach the pointer under the lock, then free it after dropping the lock. The deferred path should do the same.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-20 Improper Input Validation\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n7.8\nHIGH\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39842\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: ocfs2: prevent release journal inode after journal shutdown Before calling ocfs2_delete_osb(), ocfs2_journal_shutdown() has already been executed in ocfs2_dismount_volume(), so osb->journal must be NULL. Therefore, the following calltrace will inevitably fail when it reaches jbd2_journal_release_jbd_inode(). ocfs2_dismount_volume()-> ocfs2_delete_osb()-> ocfs2_free_slot_info()-> __ocfs2_free_slot_info()-> evict()-> ocfs2_evict_inode()-> ocfs2_clear_inode()-> jbd2_journal_release_jbd_inode(osb->journal->j_journal, Adding osb->journal checks will prevent null-ptr-deref during the above execution path.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-20 Improper Input Validation\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39843\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: mm: slub: avoid wake up kswapd in set_track_prepare set_track_prepare() can incur lock recursion. The issue is that it is called from hrtimer_start_range_ns holding the per_cpu(hrtimer_bases)[n].lock, but when enabled CONFIG_DEBUG_OBJECTS_TIMERS, may wake up kswapd in set_track_prepare, and try to hold the per_cpu(hrtimer_bases)[n].lock. Avoid deadlock caused by implicitly waking up kswapd by passing in allocation flags, which do not contain __GFP_KSWAPD_RECLAIM in the debug_objects_fill_pool() case. Inside stack depot they are processed by gfp_nested_mask(). Since ___slab_alloc() has preemption disabled, we mask out __GFP_DIRECT_RECLAIM from the flags there. The oops looks something like: BUG: spinlock recursion on CPU#3, swapper/3/0 lock: 0xffffff8a4bf29c80, .magic: dead4ead, .owner: swapper/3/0, .owner_cpu: 3 Hardware name: Qualcomm Technologies, Inc. Popsicle based on SM8850 (DT) Call trace: spin_bug+0x0 _raw_spin_lock_irqsave+0x80 hrtimer_try_to_cancel+0x94 task_contending+0x10c enqueue_dl_entity+0x2a4 dl_server_start+0x74 enqueue_task_fair+0x568 enqueue_task+0xac do_activate_task+0x14c ttwu_do_activate+0xcc try_to_wake_up+0x6c8 default_wake_function+0x20 autoremove_wake_function+0x1c __wake_up+0xac wakeup_kswapd+0x19c wake_all_kswapds+0x78 __alloc_pages_slowpath+0x1ac __alloc_pages_noprof+0x298 stack_depot_save_flags+0x6b0 stack_depot_save+0x14 set_track_prepare+0x5c ___slab_alloc+0xccc __kmalloc_cache_noprof+0x470 __set_page_owner+0x2bc post_alloc_hook[jt]+0x1b8 prep_new_page+0x28 get_page_from_freelist+0x1edc __alloc_pages_noprof+0x13c alloc_slab_page+0x244 allocate_slab+0x7c ___slab_alloc+0x8e8 kmem_cache_alloc_noprof+0x450 debug_objects_fill_pool+0x22c debug_object_activate+0x40 enqueue_hrtimer[jt]+0xdc hrtimer_start_range_ns+0x5f8 ...\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-20 Improper Input Validation\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n7\nHIGH\nCVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39844\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: mm: move page table sync declarations to linux/pgtable.h During our internal testing, we started observing intermittent boot failures when the machine uses 4-level paging and has a large amount of persistent memory: BUG: unable to handle page fault for address: ffffe70000000034 #PF: supervisor write access in kernel mode #PF: error_code(0x0002) - not-present page PGD 0 P4D 0 Oops: 0002 [#1] SMP NOPTI RIP: 0010:__init_single_page+0x9/0x6d Call Trace: __init_zone_device_page+0x17/0x5d memmap_init_zone_device+0x154/0x1bb pagemap_range+0x2e0/0x40f memremap_pages+0x10b/0x2f0 devm_memremap_pages+0x1e/0x60 dev_dax_probe+0xce/0x2ec [device_dax] dax_bus_probe+0x6d/0xc9 [... snip ...] It turns out that the kernel panics while initializing vmemmap (struct page array) when the vmemmap region spans two PGD entries, because the new PGD entry is only installed in init_mm.pgd, but not in the page tables of other tasks. And looking at __populate_section_memmap(): if (vmemmap_can_optimize(altmap, pgmap)) // does not sync top level page tables r = vmemmap_populate_compound_pages(pfn, start, end, nid, pgmap); else // sync top level page tables in x86 r = vmemmap_populate(start, end, nid, altmap); In the normal path, vmemmap_populate() in arch/x86/mm/init_64.c synchronizes the top level page table (See commit 9b861528a801 (\"x86-64, mem: Update all PGDs for direct mapping and vmemmap mapping changes\")) so that all tasks in the system can see the new vmemmap area. However, when vmemmap_can_optimize() returns true, the optimized path skips synchronization of top-level page tables. This is because vmemmap_populate_compound_pages() is implemented in core MM code, which does not handle synchronization of the top-level page tables. Instead, the core MM has historically relied on each architecture to perform this synchronization manually. We're not the first party to encounter a crash caused by not-sync'd top level page tables: earlier this year, Gwan-gyeong Mun attempted to address the issue [1] [2] after hitting a kernel panic when x86 code accessed the vmemmap area before the corresponding top-level entries were synced. At that time, the issue was believed to be triggered only when struct page was enlarged for debugging purposes, and the patch did not get further updates. It turns out that current approach of relying on each arch to handle the page table sync manually is fragile because 1) it's easy to forget to sync the top level page table, and 2) it's also easy to overlook that the kernel should not access the vmemmap and direct mapping areas before the sync. # The solution: Make page table sync more code robust and harder to miss To address this, Dave Hansen suggested [3] [4] introducing {pgd,p4d}_populate_kernel() for updating kernel portion of the page tables and allow each architecture to explicitly perform synchronization when installing top-level entries. With this approach, we no longer need to worry about missing the sync step, reducing the risk of future regressions. The new interface reuses existing ARCH_PAGE_TABLE_SYNC_MASK, PGTBL_P*D_MODIFIED and arch_sync_kernel_mappings() facility used by vmalloc and ioremap to synchronize page tables. pgd_populate_kernel() looks like this: static inline void pgd_populate_kernel(unsigned long addr, pgd_t *pgd, p4d_t *p4d) { pgd_populate(&init_mm, pgd, p4d); if (ARCH_PAGE_TABLE_SYNC_MASK & PGTBL_PGD_MODIFIED) arch_sync_kernel_mappings(addr, addr); } It is worth noting that vmalloc() and apply_to_range() carefully synchronizes page tables by calling p*d_alloc_track() and arch_sync_kernel_mappings(), and thus they are not affected by ---truncated---\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-20 Improper Input Validation\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39845\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: x86/mm/64: define ARCH_PAGE_TABLE_SYNC_MASK and arch_sync_kernel_mappings() Define ARCH_PAGE_TABLE_SYNC_MASK and arch_sync_kernel_mappings() to ensure page tables are properly synchronized when calling p*d_populate_kernel(). For 5-level paging, synchronization is performed via pgd_populate_kernel(). In 4-level paging, pgd_populate() is a no-op, so synchronization is instead performed at the P4D level via p4d_populate_kernel(). This fixes intermittent boot failures on systems using 4-level paging and a large amount of persistent memory: BUG: unable to handle page fault for address: ffffe70000000034 #PF: supervisor write access in kernel mode #PF: error_code(0x0002) - not-present page PGD 0 P4D 0 Oops: 0002 [#1] SMP NOPTI RIP: 0010:__init_single_page+0x9/0x6d Call Trace: __init_zone_device_page+0x17/0x5d memmap_init_zone_device+0x154/0x1bb pagemap_range+0x2e0/0x40f memremap_pages+0x10b/0x2f0 devm_memremap_pages+0x1e/0x60 dev_dax_probe+0xce/0x2ec [device_dax] dax_bus_probe+0x6d/0xc9 [... snip ...] It also fixes a crash in vmemmap_set_pmd() caused by accessing vmemmap before sync_global_pgds() [1]: BUG: unable to handle page fault for address: ffffeb3ff1200000 #PF: supervisor write access in kernel mode #PF: error_code(0x0002) - not-present page PGD 0 P4D 0 Oops: Oops: 0002 [#1] PREEMPT SMP NOPTI Tainted: [W]=WARN RIP: 0010:vmemmap_set_pmd+0xff/0x230 vmemmap_populate_hugepages+0x176/0x180 vmemmap_populate+0x34/0x80 __populate_section_memmap+0x41/0x90 sparse_add_section+0x121/0x3e0 __add_pages+0xba/0x150 add_pages+0x1d/0x70 memremap_pages+0x3dc/0x810 devm_memremap_pages+0x1c/0x60 xe_devm_add+0x8b/0x100 [xe] xe_tile_init_noalloc+0x6a/0x70 [xe] xe_device_probe+0x48c/0x740 [xe] [... snip ...]\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-20 Improper Input Validation\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39846\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: pcmcia: Fix a NULL pointer dereference in __iodyn_find_io_region() In __iodyn_find_io_region(), pcmcia_make_resource() is assigned to res and used in pci_bus_alloc_resource(). There is a dereference of res in pci_bus_alloc_resource(), which could lead to a NULL pointer dereference on failure of pcmcia_make_resource(). Fix this bug by adding a check of res.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-20 Improper Input Validation\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39847\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: ppp: fix memory leak in pad_compress_skb If alloc_skb() fails in pad_compress_skb(), it returns NULL without releasing the old skb. The caller does: skb = pad_compress_skb(ppp, skb); if (!skb) goto drop; drop: kfree_skb(skb); When pad_compress_skb() returns NULL, the reference to the old skb is lost and kfree_skb(skb) ends up doing nothing, leading to a memory leak. Align pad_compress_skb() semantics with realloc(): only free the old skb if allocation and compression succeed. At the call site, use the new_skb variable so the original skb is not lost when pad_compress_skb() fails.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-772 Missing Release of Resource after Effective Lifetime\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39848\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: ax25: properly unshare skbs in ax25_kiss_rcv() Bernard Pidoux reported a regression apparently caused by commit c353e8983e0d (\"net: introduce per netns packet chains\"). skb->dev becomes NULL and we crash in __netif_receive_skb_core(). Before above commit, different kind of bugs or corruptions could happen without a major crash. But the root cause is that ax25_kiss_rcv() can queue/mangle input skb without checking if this skb is shared or not. Many thanks to Bernard Pidoux for his help, diagnosis and tests. We had a similar issue years ago fixed with commit 7aaed57c5c28 (\"phonet: properly unshare skbs in phonet_rcv()\").\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-20 Improper Input Validation\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39849\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: wifi: cfg80211: sme: cap SSID length in __cfg80211_connect_result() If the ssid->datalen is more than IEEE80211_MAX_SSID_LEN (32) it would lead to memory corruption so add some bounds checking.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-20 Improper Input Validation\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39853\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: i40e: Fix potential invalid access when MAC list is empty list_first_entry() never returns NULL - if the list is empty, it still returns a pointer to an invalid object, leading to potential invalid memory access when dereferenced. Fix this by using list_first_entry_or_null instead of list_first_entry.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-20 Improper Input Validation\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39857\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: net/smc: fix one NULL pointer dereference in smc_ib_is_sg_need_sync() BUG: kernel NULL pointer dereference, address: 00000000000002ec PGD 0 P4D 0 Oops: Oops: 0000 [#1] SMP PTI CPU: 28 UID: 0 PID: 343 Comm: kworker/28:1 Kdump: loaded Tainted: G OE 6.17.0-rc2+ #9 NONE Tainted: [O]=OOT_MODULE, [E]=UNSIGNED_MODULE Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.15.0-1 04/01/2014 Workqueue: smc_hs_wq smc_listen_work [smc] RIP: 0010:smc_ib_is_sg_need_sync+0x9e/0xd0 [smc] ... Call Trace: smcr_buf_map_link+0x211/0x2a0 [smc] __smc_buf_create+0x522/0x970 [smc] smc_buf_create+0x3a/0x110 [smc] smc_find_rdma_v2_device_serv+0x18f/0x240 [smc] ? smc_vlan_by_tcpsk+0x7e/0xe0 [smc] smc_listen_find_device+0x1dd/0x2b0 [smc] smc_listen_work+0x30f/0x580 [smc] process_one_work+0x18c/0x340 worker_thread+0x242/0x360 kthread+0xe7/0x220 ret_from_fork+0x13a/0x160 ret_from_fork_asm+0x1a/0x30 If the software RoCE device is used, ibdev->dma_device is a null pointer. As a result, the problem occurs. Null pointer detection is added to prevent problems.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-20 Improper Input Validation\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n7\nHIGH\nCVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39860\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: Bluetooth: Fix use-after-free in l2cap_sock_cleanup_listen() syzbot reported the splat below without a repro. In the splat, a single thread calling bt_accept_dequeue() freed sk and touched it after that. The root cause would be the racy l2cap_sock_cleanup_listen() call added by the cited commit. bt_accept_dequeue() is called under lock_sock() except for l2cap_sock_release(). Two threads could see the same socket during the list iteration in bt_accept_dequeue(): CPU1 CPU2 (close()) ---- ---- sock_hold(sk) sock_hold(sk); lock_sock(sk) <-- block close() sock_put(sk) bt_accept_unlink(sk) sock_put(sk) <-- refcnt by bt_accept_enqueue() release_sock(sk) lock_sock(sk) sock_put(sk) bt_accept_unlink(sk) sock_put(sk) <-- last refcnt bt_accept_unlink(sk) <-- UAF Depending on the timing, the other thread could show up in the \"Freed by task\" part. Let's call l2cap_sock_cleanup_listen() under lock_sock() in l2cap_sock_release(). [0]: BUG: KASAN: slab-use-after-free in debug_spin_lock_before kernel/locking/spinlock_debug.c:86 [inline] BUG: KASAN: slab-use-after-free in do_raw_spin_lock+0x26f/0x2b0 kernel/locking/spinlock_debug.c:115 Read of size 4 at addr ffff88803b7eb1c4 by task syz.5.3276/16995 CPU: 3 UID: 0 PID: 16995 Comm: syz.5.3276 Not tainted syzkaller #0 PREEMPT(full) Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2~bpo12+1 04/01/2014 Call Trace: __dump_stack lib/dump_stack.c:94 [inline] dump_stack_lvl+0x116/0x1f0 lib/dump_stack.c:120 print_address_description mm/kasan/report.c:378 [inline] print_report+0xcd/0x630 mm/kasan/report.c:482 kasan_report+0xe0/0x110 mm/kasan/report.c:595 debug_spin_lock_before kernel/locking/spinlock_debug.c:86 [inline] do_raw_spin_lock+0x26f/0x2b0 kernel/locking/spinlock_debug.c:115 spin_lock_bh include/linux/spinlock.h:356 [inline] release_sock+0x21/0x220 net/core/sock.c:3746 bt_accept_dequeue+0x505/0x600 net/bluetooth/af_bluetooth.c:312 l2cap_sock_cleanup_listen+0x5c/0x2a0 net/bluetooth/l2cap_sock.c:1451 l2cap_sock_release+0x5c/0x210 net/bluetooth/l2cap_sock.c:1425 __sock_release+0xb3/0x270 net/socket.c:649 sock_close+0x1c/0x30 net/socket.c:1439 __fput+0x3ff/0xb70 fs/file_table.c:468 task_work_run+0x14d/0x240 kernel/task_work.c:227 resume_user_mode_work include/linux/resume_user_mode.h:50 [inline] exit_to_user_mode_loop+0xeb/0x110 kernel/entry/common.c:43 exit_to_user_mode_prepare include/linux/irq-entry-common.h:225 [inline] syscall_exit_to_user_mode_work include/linux/entry-common.h:175 [inline] syscall_exit_to_user_mode include/linux/entry-common.h:210 [inline] do_syscall_64+0x3f6/0x4c0 arch/x86/entry/syscall_64.c:100 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7f2accf8ebe9 Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 a8 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007ffdb6cb1378 EFLAGS: 00000246 ORIG_RAX: 00000000000001b4 RAX: 0000000000000000 RBX: 00000000000426fb RCX: 00007f2accf8ebe9 RDX: 0000000000000000 RSI: 000000000000001e RDI: 0000000000000003 RBP: 00007f2acd1b7da0 R08: 0000000000000001 R09: 00000012b6cb166f R10: 0000001b30e20000 R11: 0000000000000246 R12: 00007f2acd1b609c R13: 00007f2acd1b6090 R14: ffffffffffffffff R15: 00007ffdb6cb1490 Allocated by task 5326: kasan_save_stack+0x33/0x60 mm/kasan/common.c:47 kasan_save_track+0x14/0x30 mm/kasan/common.c:68 poison_kmalloc_redzone mm/kasan/common.c:388 [inline] __kasan_kmalloc+0xaa/0xb0 mm/kasan/common.c:405 kasan_kmalloc include/linux/kasan.h:260 [inline] __do_kmalloc_node mm/slub.c:4365 [inline] __kmalloc_nopro ---truncated---\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-20 Improper Input Validation\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n7.1\nHIGH\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39864\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: wifi: cfg80211: fix use-after-free in cmp_bss() Following bss_free() quirk introduced in commit 776b3580178f (\"cfg80211: track hidden SSID networks properly\"), adjust cfg80211_update_known_bss() to free the last beacon frame elements only if they're not shared via the corresponding 'hidden_beacon_bss' pointer.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-20 Improper Input Validation\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n7.8\nHIGH\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39865\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: tee: fix NULL pointer dereference in tee_shm_put tee_shm_put have NULL pointer dereference: __optee_disable_shm_cache --> shm = reg_pair_to_ptr(...);//shm maybe return NULL tee_shm_free(shm); --> tee_shm_put(shm);//crash Add check in tee_shm_put to fix it. panic log: Unable to handle kernel paging request at virtual address 0000000000100cca Mem abort info: ESR = 0x0000000096000004 EC = 0x25: DABT (current EL), IL = 32 bits SET = 0, FnV = 0 EA = 0, S1PTW = 0 FSC = 0x04: level 0 translation fault Data abort info: ISV = 0, ISS = 0x00000004, ISS2 = 0x00000000 CM = 0, WnR = 0, TnD = 0, TagAccess = 0 GCS = 0, Overlay = 0, DirtyBit = 0, Xs = 0 user pgtable: 4k pages, 48-bit VAs, pgdp=0000002049d07000 [0000000000100cca] pgd=0000000000000000, p4d=0000000000000000 Internal error: Oops: 0000000096000004 [#1] SMP CPU: 2 PID: 14442 Comm: systemd-sleep Tainted: P OE ------- ---- 6.6.0-39-generic #38 Source Version: 938b255f6cb8817c95b0dd5c8c2944acfce94b07 Hardware name: greatwall GW-001Y1A-FTH, BIOS Great Wall BIOS V3.0 10/26/2022 pstate: 80000005 (Nzcv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--) pc : tee_shm_put+0x24/0x188 lr : tee_shm_free+0x14/0x28 sp : ffff001f98f9faf0 x29: ffff001f98f9faf0 x28: ffff0020df543cc0 x27: 0000000000000000 x26: ffff001f811344a0 x25: ffff8000818dac00 x24: ffff800082d8d048 x23: ffff001f850fcd18 x22: 0000000000000001 x21: ffff001f98f9fb88 x20: ffff001f83e76218 x19: ffff001f83e761e0 x18: 000000000000ffff x17: 303a30303a303030 x16: 0000000000000000 x15: 0000000000000003 x14: 0000000000000001 x13: 0000000000000000 x12: 0101010101010101 x11: 0000000000000001 x10: 0000000000000001 x9 : ffff800080e08d0c x8 : ffff001f98f9fb88 x7 : 0000000000000000 x6 : 0000000000000000 x5 : 0000000000000000 x4 : 0000000000000000 x3 : 0000000000000000 x2 : ffff001f83e761e0 x1 : 00000000ffff001f x0 : 0000000000100cca Call trace: tee_shm_put+0x24/0x188 tee_shm_free+0x14/0x28 __optee_disable_shm_cache+0xa8/0x108 optee_shutdown+0x28/0x38 platform_shutdown+0x28/0x40 device_shutdown+0x144/0x2b0 kernel_power_off+0x3c/0x80 hibernate+0x35c/0x388 state_store+0x64/0x80 kobj_attr_store+0x14/0x28 sysfs_kf_write+0x48/0x60 kernfs_fop_write_iter+0x128/0x1c0 vfs_write+0x270/0x370 ksys_write+0x6c/0x100 __arm64_sys_write+0x20/0x30 invoke_syscall+0x4c/0x120 el0_svc_common.constprop.0+0x44/0xf0 do_el0_svc+0x24/0x38 el0_svc+0x24/0x88 el0t_64_sync_handler+0x134/0x150 el0t_64_sync+0x14c/0x15\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-20 Improper Input Validation\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n7\nHIGH\nCVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-39866\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: fs: writeback: fix use-after-free in __mark_inode_dirty() An use-after-free issue occurred when __mark_inode_dirty() get the bdi_writeback that was in the progress of switching. CPU: 1 PID: 562 Comm: systemd-random- Not tainted 6.6.56-gb4403bd46a8e #1 ...... pstate: 60400005 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) pc : __mark_inode_dirty+0x124/0x418 lr : __mark_inode_dirty+0x118/0x418 sp : ffffffc08c9dbbc0 ........ Call trace: __mark_inode_dirty+0x124/0x418 generic_update_time+0x4c/0x60 file_modified+0xcc/0xd0 ext4_buffered_write_iter+0x58/0x124 ext4_file_write_iter+0x54/0x704 vfs_write+0x1c0/0x308 ksys_write+0x74/0x10c __arm64_sys_write+0x1c/0x28 invoke_syscall+0x48/0x114 el0_svc_common.constprop.0+0xc0/0xe0 do_el0_svc+0x1c/0x28 el0_svc+0x40/0xe4 el0t_64_sync_handler+0x120/0x12c el0t_64_sync+0x194/0x198 Root cause is: systemd-random-seed kworker ---------------------------------------------------------------------- ___mark_inode_dirty inode_switch_wbs_work_fn spin_lock(&inode->i_lock); inode_attach_wb locked_inode_to_wb_and_lock_list get inode->i_wb spin_unlock(&inode->i_lock); spin_lock(&wb->list_lock) spin_lock(&inode->i_lock) inode_io_list_move_locked spin_unlock(&wb->list_lock) spin_unlock(&inode->i_lock) spin_lock(&old_wb->list_lock) inode_do_switch_wbs spin_lock(&inode->i_lock) inode->i_wb = new_wb spin_unlock(&inode->i_lock) spin_unlock(&old_wb->list_lock) wb_put_many(old_wb, nr_switched) cgwb_release old wb released wb_wakeup_delayed() accesses wb, then trigger the use-after-free issue Fix this race condition by holding inode spinlock until wb_wakeup_delayed() finished.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-416 Use After Free\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n7.8\nHIGH\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-40300\n<div class=\"csaf-accordion-content\">\n\nIn the Linux kernel, the following vulnerability has been resolved: x86/vmscape: Add conditional IBPB mitigation VMSCAPE is a vulnerability that exploits insufficient branch predictor isolation between a guest and a userspace hypervisor (like QEMU). Existing mitigations already protect kernel/KVM from a malicious guest. Userspace can additionally be protected by flushing the branch predictors after a VMexit. Since it is the userspace that consumes the poisoned branch predictors, conditionally issue an IBPB after a VMexit and before returning to userspace. Workloads that frequently switch between hypervisor and userspace will incur the most overhead from the new IBPB. This new IBPB is not integrated with the existing IBPB sites. For instance, a task can use the existing speculation control prctl() to get an IBPB at context switch time. With this implementation, the IBPB is doubled up: one at context switch and another before running userspace. The intent is to integrate and optimize these cases post-embargo. [ dhansen: elaborate on suboptimal IBPB solution ]\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-402 Transmission of Private Resources into a New Sphere ('Resource Leak')\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n6.5\nMEDIUM\nCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-43368\n<div class=\"csaf-accordion-content\">\n\nA use-after-free issue was addressed with improved memory management. This issue is fixed in Safari 26, iOS 26 and iPadOS 26, macOS Tahoe 26. Processing maliciously crafted web content may lead to an unexpected Safari crash.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-416 Use After Free\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n4.3\nMEDIUM\nCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-47219\n<div class=\"csaf-accordion-content\">\n\nIn GStreamer through 1.26.1, the isomp4 plugin's qtdemux_parse_trak function may read past the end of a heap buffer while parsing an MP4 file, possibly leading to information disclosure.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-125 Out-of-bounds Read\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n8.1\nHIGH\nCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-48989\n<div class=\"csaf-accordion-content\">\n\nImproper Resource Shutdown or Release vulnerability in Apache Tomcat made Tomcat vulnerable to the made you reset attack. This issue affects Apache Tomcat: from 11.0.0-M1 through 11.0.9, from 10.1.0-M1 through 10.1.43 and from 9.0.0.M1 through 9.0.107. Older, EOL versions may also be affected. Users are recommended to upgrade to one of versions 11.0.10, 10.1.44 or 9.0.108 which fix the issue.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-404 Improper Resource Shutdown or Release\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n7.5\nHIGH\nCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-53057\n<div class=\"csaf-accordion-content\">\n\nVulnerability in the Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition product of Oracle Java SE (component: Security). Supported versions that are affected are Oracle Java SE: 8u461, 8u461-perf, 11.0.28, 17.0.16, 21.0.8, 25; Oracle GraalVM for JDK: 17.0.16 and 21.0.8; Oracle GraalVM Enterprise Edition: 21.3.15. Difficult to exploit vulnerability allows unauthenticated attacker with network access via multiple protocols to compromise Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition. Successful attacks of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition accessible data. Note: This vulnerability can be exploited by using APIs in the specified Component, e.g., through a web service which supplies data to the APIs. This vulnerability also applies to Java deployments, typically in clients running sandboxed Java Web Start applications or sandboxed Java applets, that load and run untrusted code (e.g., code that comes from the internet) and rely on the Java sandbox for security. CVSS 3.1 Base Score 5.9 (Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N).\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-284 Improper Access Control\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.9\nMEDIUM\nCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-53066\n<div class=\"csaf-accordion-content\">\n\nVulnerability in the Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition product of Oracle Java SE (component: JAXP). Supported versions that are affected are Oracle Java SE: 8u461, 8u461-perf, 11.0.28, 17.0.16, 21.0.8, 25; Oracle GraalVM for JDK: 17.0.16 and 21.0.8; Oracle GraalVM Enterprise Edition: 21.3.15. Easily exploitable vulnerability allows unauthenticated attacker with network access via multiple protocols to compromise Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition. Successful attacks of this vulnerability can result in unauthorized access to critical data or complete access to all Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition accessible data. Note: This vulnerability can be exploited by using APIs in the specified Component, e.g., through a web service which supplies data to the APIs. This vulnerability also applies to Java deployments, typically in clients running sandboxed Java Web Start applications or sandboxed Java applets, that load and run untrusted code (e.g., code that comes from the internet) and rely on the Java sandbox for security. CVSS 3.1 Base Score 7.5 (Confidentiality impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N).\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-200 Exposure of Sensitive Information to an Unauthorized Actor\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n7.5\nHIGH\nCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-55752\n<div class=\"csaf-accordion-content\">\n\nRelative Path Traversal vulnerability in Apache Tomcat. The fix for bug 60013 introduced a regression where the rewritten URL was normalized before it was decoded. This introduced the possibility that, for rewrite rules that rewrite query parameters to the URL, an attacker could manipulate the request URI to bypass security constraints including the protection for /WEB-INF/ and /META-INF/. If PUT requests were also enabled then malicious files could be uploaded leading to remote code execution. PUT requests are normally limited to trusted users and it is considered unlikely that PUT requests would be enabled in conjunction with a rewrite that manipulated the URI. This issue affects Apache Tomcat: from 11.0.0-M1 through 11.0.10, from 10.1.0-M1 through 10.1.44, from 9.0.0.M11 through 9.0.108. The following versions were EOL at the time the CVE was created but are known to be affected: 8.5.6 though 8.5.100. Other, older, EOL versions may also be affected. Users are recommended to upgrade to version 11.0.11 or later, 10.1.45 or later or 9.0.109 or later, which fix the issue.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-23 Relative Path Traversal\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n7.5\nHIGH\nCVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-55754\n<div class=\"csaf-accordion-content\">\n\nImproper Neutralization of Escape, Meta, or Control Sequences vulnerability in Apache Tomcat. Tomcat did not escape ANSI escape sequences in log messages. If Tomcat was running in a console on a Windows operating system, and the console supported ANSI escape sequences, it was possible for an attacker to use a specially crafted URL to inject ANSI escape sequences to manipulate the console and the clipboard and attempt to trick an administrator into running an attacker controlled command. While no attack vector was found, it may have been possible to mount this attack on other operating systems. This issue affects Apache Tomcat: from 11.0.0-M1 through 11.0.10, from 10.1.0-M1 through 10.1.44, from 9.0.40 through 9.0.108. The following versions were EOL at the time the CVE was created but are known to be affected: 8.5.60 though 8.5.100. Other, older, EOL versions may also be affected. Users are recommended to upgrade to version 11.0.11 or later, 10.1.45 or later or 9.0.109 or later, which fix the issue.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-150 Improper Neutralization of Escape, Meta, or Control Sequences\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n9.6\nCRITICAL\nCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-61748\n<div class=\"csaf-accordion-content\">\n\nVulnerability in the Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition product of Oracle Java SE (component: Libraries). Supported versions that are affected are Oracle Java SE: 21.0.8 and 25; Oracle GraalVM for JDK: 21.0.8; Oracle GraalVM Enterprise Edition: 21.3.15. Difficult to exploit vulnerability allows unauthenticated attacker with network access via multiple protocols to compromise Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition. Successful attacks of this vulnerability can result in unauthorized update, insert or delete access to some of Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition accessible data. Note: This vulnerability can be exploited by using APIs in the specified Component, e.g., through a web service which supplies data to the APIs. This vulnerability also applies to Java deployments, typically in clients running sandboxed Java Web Start applications or sandboxed Java applets, that load and run untrusted code (e.g., code that comes from the internet) and rely on the Java sandbox for security. CVSS 3.1 Base Score 3.7 (Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N).\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-284 Improper Access Control\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n3.7\nLOW\nCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2025-61795\n<div class=\"csaf-accordion-content\">\n\nImproper Resource Shutdown or Release vulnerability in Apache Tomcat. If an error occurred (including exceeding limits) during the processing of a multipart upload, temporary copies of the uploaded parts written to disc were not cleaned up immediately but left for the garbage collection process to delete. Depending on JVM settings, application memory usage and application load, it was possible that space for the temporary copies of uploaded parts would be filled faster than GC cleared it, leading to a DoS. This issue affects Apache Tomcat: from 11.0.0-M1 through 11.0.11, from 10.1.0-M1 through 10.1.46, from 9.0.0.M1 through 9.0.109. The following versions were EOL at the time the CVE was created but are known to be affected: 8.5.0 though 8.5.100. Other, older, EOL versions may also be affected. Users are recommended to upgrade to version 11.0.12 or later, 10.1.47 or later or 9.0.110 or later which fixes the issue.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-404 Improper Resource Shutdown or Release\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n5.3\nMEDIUM\nCVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2026-2673\n<div class=\"csaf-accordion-content\">\n\nIssue summary: An OpenSSL TLS 1.3 server may fail to negotiate the expected preferred key exchange group when its key exchange group configuration includes the default by using the 'DEFAULT' keyword. Impact summary: A less preferred key exchange may be used even when a more preferred group is supported by both client and server, if the group was not included among the client's initial predicated keyshares. This will sometimes be the case with the new hybrid post-quantum groups, if the client chooses to defer their use until specifically requested by the server. If an OpenSSL TLS 1.3 server's configuration uses the 'DEFAULT' keyword to interpolate the built-in default group list into its own configuration, perhaps adding or removing specific elements, then an implementation defect causes the 'DEFAULT' list to lose its 'tuple' structure, and all server-supported groups were treated as a single sufficiently secure 'tuple', with the server not sending a Hello Retry Request (HRR) even when a group in a more preferred tuple was mutually supported. As a result, the client and server might fail to negotiate a mutually supported post-quantum key agreement group, such as 'X25519MLKEM768', if the client's configuration results in only 'classical' groups (such as 'X25519' being the only ones in the client's initial keyshare prediction). OpenSSL 3.5 and later support a new syntax for selecting the most preferred TLS 1.3 key agreement group on TLS servers. The old syntax had a single 'flat' list of groups, and treated all the supported groups as sufficiently secure. If any of the keyshares predicted by the client were supported by the server the most preferred among these was selected, even if other groups supported by the client, but not included in the list of predicted keyshares would have been more preferred, if included. The new syntax partitions the groups into distinct 'tuples' of roughly equivalent security. Within each tuple the most preferred group included among the client's predicted keyshares is chosen, but if the client supports a group from a more preferred tuple, but did not predict any corresponding keyshares, the server will ask the client to retry the ClientHello (by issuing a Hello Retry Request or HRR) with the most preferred mutually supported group. The above works as expected when the server's configuration uses the built-in default group list, or explicitly defines its own list by directly defining the various desired groups and group 'tuples'. No OpenSSL FIPS modules are affected by this issue, the code in question lies outside the FIPS boundary. OpenSSL 3.6 and 3.5 are vulnerable to this issue. OpenSSL 3.6 users should upgrade to OpenSSL 3.6.2 once it is released. OpenSSL 3.5 users should upgrade to OpenSSL 3.5.6 once it is released. OpenSSL 3.4, 3.3, 3.0, 1.0.2 and 1.1.1 are not affected by this issue.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-757 Selection of Less-Secure Algorithm During Negotiation ('Algorithm Downgrade')\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n7.5\nHIGH\nCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2026-21925\n<div class=\"csaf-accordion-content\">\n\nVulnerability in the Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition product of Oracle Java SE (component: RMI). Supported versions that are affected are Oracle Java SE: 8u471, 8u471-b50, 8u471-perf, 11.0.29, 17.0.17, 21.0.9, 25.0.1; Oracle GraalVM for JDK: 17.0.17 and 21.0.9; Oracle GraalVM Enterprise Edition: 21.3.16. Difficult to exploit vulnerability allows unauthenticated attacker with network access via multiple protocols to compromise Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition. Successful attacks of this vulnerability can result in unauthorized update, insert or delete access to some of Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition accessible data as well as unauthorized read access to a subset of Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition accessible data. Note: This vulnerability can be exploited by using APIs in the specified Component, e.g., through a web service which supplies data to the APIs. This vulnerability also applies to Java deployments, typically in clients running sandboxed Java Web Start applications or sandboxed Java applets, that load and run untrusted code (e.g., code that comes from the internet) and rely on the Java sandbox for security. CVSS 3.1 Base Score 4.8 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N).\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-20 Improper Input Validation\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n4.8\nMEDIUM\nCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2026-21932\n<div class=\"csaf-accordion-content\">\n\nVulnerability in the Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition product of Oracle Java SE (component: AWT, JavaFX). Supported versions that are affected are Oracle Java SE: 8u471, 8u471-b50, 8u471-perf, 11.0.29, 17.0.17, 21.0.9, 25.0.1; Oracle GraalVM for JDK: 17.0.17 and 21.0.9; Oracle GraalVM Enterprise Edition: 21.3.16. Easily exploitable vulnerability allows unauthenticated attacker with network access via multiple protocols to compromise Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition. Successful attacks require human interaction from a person other than the attacker and while the vulnerability is in Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition accessible data. Note: This vulnerability applies to Java deployments, typically in clients running sandboxed Java Web Start applications or sandboxed Java applets, that load and run untrusted code (e.g., code that comes from the internet) and rely on the Java sandbox for security. This vulnerability does not apply to Java deployments, typically in servers, that load and run only trusted code (e.g., code installed by an administrator). CVSS 3.1 Base Score 7.4 (Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:N/I:H/A:N).\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-20 Improper Input Validation\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n7.4\nHIGH\nCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:N/I:H/A:N\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2026-21933\n<div class=\"csaf-accordion-content\">\n\nVulnerability in the Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition product of Oracle Java SE (component: Networking). Supported versions that are affected are Oracle Java SE: 8u471, 8u471-b50, 8u471-perf, 11.0.29, 17.0.17, 21.0.9, 25.0.1; Oracle GraalVM for JDK: 17.0.17 and 21.0.9; Oracle GraalVM Enterprise Edition: 21.3.16. Easily exploitable vulnerability allows unauthenticated attacker with network access via multiple protocols to compromise Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition. Successful attacks require human interaction from a person other than the attacker and while the vulnerability is in Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in unauthorized update, insert or delete access to some of Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition accessible data as well as unauthorized read access to a subset of Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition accessible data. Note: This vulnerability can be exploited by using APIs in the specified Component, e.g., through a web service which supplies data to the APIs. This vulnerability also applies to Java deployments, typically in clients running sandboxed Java Web Start applications or sandboxed Java applets, that load and run untrusted code (e.g., code that comes from the internet) and rely on the Java sandbox for security. CVSS 3.1 Base Score 6.1 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N).\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-20 Improper Input Validation\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n6.1\nMEDIUM\nCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2026-21945\n<div class=\"csaf-accordion-content\">\n\nVulnerability in the Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition product of Oracle Java SE (component: Security). Supported versions that are affected are Oracle Java SE: 8u471, 8u471-b50, 8u471-perf, 11.0.29, 17.0.17, 21.0.9, 25.0.1; Oracle GraalVM for JDK: 17.0.17 and 21.0.9; Oracle GraalVM Enterprise Edition: 21.3.16. Easily exploitable vulnerability allows unauthenticated attacker with network access via multiple protocols to compromise Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition. Successful attacks of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition. Note: This vulnerability applies to Java deployments, typically in clients running sandboxed Java Web Start applications or sandboxed Java applets, that load and run untrusted code (e.g., code that comes from the internet) and rely on the Java sandbox for security. This vulnerability does not apply to Java deployments, typically in servers, that load and run only trusted code (e.g., code installed by an administrator). CVSS 3.1 Base Score 7.5 (Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H).\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-400 Uncontrolled Resource Consumption\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n7.5\nHIGH\nCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2026-21947\n<div class=\"csaf-accordion-content\">\n\nVulnerability in Oracle Java SE (component: JavaFX). Supported versions that are affected are Oracle Java SE: 8u471-b50. Difficult to exploit vulnerability allows unauthenticated attacker with network access via multiple protocols to compromise Oracle Java SE. Successful attacks require human interaction from a person other than the attacker. Successful attacks of this vulnerability can result in unauthorized update, insert or delete access to some of Oracle Java SE accessible data. Note: This vulnerability applies to Java deployments, typically in clients running sandboxed Java Web Start applications or sandboxed Java applets, that load and run untrusted code (e.g., code that comes from the internet) and rely on the Java sandbox for security. This vulnerability does not apply to Java deployments, typically in servers, that load and run only trusted code (e.g., code installed by an administrator). CVSS 3.1 Base Score 3.1 (Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:L/A:N).\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-79 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n3.1\nLOW\nCVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:L/A:N\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2026-22924\n<div class=\"csaf-accordion-content\">\n\nThe affected application does not properly restrict unauthenticated connections and is susceptible to resource exhaustion conditions. This could allow an attacker to disrupt normal operations or perform unauthorized actions, potentially impacting system availability and integrity.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-306 Missing Authentication for Critical Function\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n9.1\nCRITICAL\nCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2026-22925\n<div class=\"csaf-accordion-content\">\n\nThe affected application is susceptible to resource exhaustion when subjected to high volume of TCP SYN packets This could allow an attacker to render the service unavailable and cause denial-of-service conditions by overwhelming system resources.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-770 Allocation of Resources Without Limits or Throttling\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n7.5\nHIGH\nCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2026-28387\n<div class=\"csaf-accordion-content\">\n\nIssue summary: An uncommon configuration of clients performing DANE TLSA-based server authentication, when paired with uncommon server DANE TLSA records, may result in a use-after-free and/or double-free on the client side. Impact summary: A use after free can have a range of potential consequences such as the corruption of valid data, crashes or execution of arbitrary code. However, the issue only affects clients that make use of TLSA records with both the PKIX-TA(0/PKIX-EE(1) certificate usages and the DANE-TA(2) certificate usage. By far the most common deployment of DANE is in SMTP MTAs for which RFC7672 recommends that clients treat as 'unusable' any TLSA records that have the PKIX certificate usages. These SMTP (or other similar) clients are not vulnerable to this issue. Conversely, any clients that support only the PKIX usages, and ignore the DANE-TA(2) usage are also not vulnerable. The client would also need to be communicating with a server that publishes a TLSA RRset with both types of TLSA records. No FIPS modules are affected by this issue, the problem code is outside the FIPS module boundary.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-416 Use After Free\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n7\nHIGH\nCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2026-28388\n<div class=\"csaf-accordion-content\">\n\nIssue summary: When a delta CRL that contains a Delta CRL Indicator extension is processed a NULL pointer dereference might happen if the required CRL Number extension is missing. Impact summary: A NULL pointer dereference can trigger a crash which leads to a Denial of Service for an application. When CRL processing and delta CRL processing is enabled during X.509 certificate verification, the delta CRL processing does not check whether the CRL Number extension is NULL before dereferencing it. When a malformed delta CRL file is being processed, this parameter can be NULL, causing a NULL pointer dereference. Exploiting this issue requires the X509_V_FLAG_USE_DELTAS flag to be enabled in the verification context, the certificate being verified to contain a freshestCRL extension or the base CRL to have the EXFLAG_FRESHEST flag set, and an attacker to provide a malformed CRL to an application that processes it. The vulnerability is limited to Denial of Service and cannot be escalated to achieve code execution or memory disclosure. For that reason the issue was assessed as Low severity according to our Security Policy. The FIPS modules in 3.6, 3.5, 3.4, 3.3 and 3.0 are not affected by this issue, as the affected code is outside the OpenSSL FIPS module boundary.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-476 NULL Pointer Dereference\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n7.5\nHIGH\nCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2026-28389\n<div class=\"csaf-accordion-content\">\n\nIssue summary: During processing of a crafted CMS EnvelopedData message with KeyAgreeRecipientInfo a NULL pointer dereference can happen. Impact summary: Applications that process attacker-controlled CMS data may crash before authentication or cryptographic operations occur resulting in Denial of Service. When a CMS EnvelopedData message that uses KeyAgreeRecipientInfo is processed, the optional parameters field of KeyEncryptionAlgorithmIdentifier is examined without checking for its presence. This results in a NULL pointer dereference if the field is missing. Applications and services that call CMS_decrypt() on untrusted input (e.g., S/MIME processing or CMS-based protocols) are vulnerable. The FIPS modules in 3.6, 3.5, 3.4, 3.3 and 3.0 are not affected by this issue, as the affected code is outside the OpenSSL FIPS module boundary.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-476 NULL Pointer Dereference\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n7.5\nHIGH\nCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2026-28390\n<div class=\"csaf-accordion-content\">\n\nIssue summary: During processing of a crafted CMS EnvelopedData message with KeyTransportRecipientInfo a NULL pointer dereference can happen. Impact summary: Applications that process attacker-controlled CMS data may crash before authentication or cryptographic operations occur resulting in Denial of Service. When a CMS EnvelopedData message that uses KeyTransportRecipientInfo with RSA-OAEP encryption is processed, the optional parameters field of RSA-OAEP SourceFunc algorithm identifier is examined without checking for its presence. This results in a NULL pointer dereference if the field is missing. Applications and services that call CMS_decrypt() on untrusted input (e.g., S/MIME processing or CMS-based protocols) are vulnerable. The FIPS modules in 3.6, 3.5, 3.4, 3.3 and 3.0 are not affected by this issue, as the affected code is outside the OpenSSL FIPS module boundary.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-476 NULL Pointer Dereference\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n7.5\nHIGH\nCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2026-31789\n<div class=\"csaf-accordion-content\">\n\nIssue summary: Converting an excessively large OCTET STRING value to a hexadecimal string leads to a heap buffer overflow on 32 bit platforms. Impact summary: A heap buffer overflow may lead to a crash or possibly an attacker controlled code execution or other undefined behavior. If an attacker can supply a crafted X.509 certificate with an excessively large OCTET STRING value in extensions such as the Subject Key Identifier (SKID) or Authority Key Identifier (AKID) which are being converted to hex, the size of the buffer needed for the result is calculated as multiplication of the input length by 3. On 32 bit platforms, this multiplication may overflow resulting in the allocation of a smaller buffer and a heap buffer overflow. Applications and services that print or log contents of untrusted X.509 certificates are vulnerable to this issue. As the certificates would have to have sizes of over 1 Gigabyte, printing or logging such certificates is a fairly unlikely operation and only 32 bit platforms are affected, this issue was assigned Low severity. The FIPS modules in 3.6, 3.5, 3.4, 3.3 and 3.0 are not affected by this issue, as the affected code is outside the OpenSSL FIPS module boundary.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-787 Out-of-bounds Write\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n7\nHIGH\nCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:H\n\n\n\n</div>\n</div>\n</div>\n<div class=\"csaf-accordion-item\">\n\nCVE-2026-31790\n<div class=\"csaf-accordion-content\">\n\nIssue summary: Applications using RSASVE key encapsulation to establish a secret encryption key can send contents of an uninitialized memory buffer to a malicious peer. Impact summary: The uninitialized buffer might contain sensitive data from the previous execution of the application process which leads to sensitive data leakage to an attacker. RSA_public_encrypt() returns the number of bytes written on success and -1 on error. The affected code tests only whether the return value is non-zero. As a result, if RSA encryption fails, encapsulation can still return success to the caller, set the output lengths, and leave the caller to use the contents of the ciphertext buffer as if a valid KEM ciphertext had been produced. If applications use EVP_PKEY_encapsulate() with RSA/RSASVE on an attacker-supplied invalid RSA public key without first validating that key, then this may cause stale or uninitialized contents of the caller-provided ciphertext buffer to be disclosed to the attacker in place of the KEM ciphertext. As a workaround calling EVP_PKEY_public_check() or EVP_PKEY_public_check_quick() before EVP_PKEY_encapsulate() will mitigate the issue. The FIPS modules in 3.6, 3.5, 3.4, 3.3, 3.1 and 3.0 are affected by this issue.\n\nView CVE Details\n\n\n\nAffected Products\n\nSiemens SIMATIC\n<div class=\"ics-vendor-version-status\">\n<div class=\"ics-vendor\">Vendor:Siemens</div>\n<div class=\"ics-version\">Product Version:SIMATIC CN 4100</div>\n<div class=\"ics-status\">Product Status:known_affected</div>\n</div>\n<div class=\"ics-remediations\">\n\nRemediations\n\nVendor fixUpdate to V5.0 or later versionhttps://support.industry.siemens.com/cs/ww/en/view/109814144/\n</div>\n\nRelevant CWE: CWE-754 Improper Check for Unusual or Exceptional Conditions\n\n\n\nMetrics\n<div class=\"csaf-table csaf-metrics-table\">\n\n\n\n\nCVSS Version\nBase Score\nBase Severity\nVector String\n\n\n\n\n3.1\n7.5\nHIGH\nCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N\n\n\n\n</div>\n</div>\n</div>\n</div>\n\n\n\nAcknowledgments\n\n\n\nSiemens ProductCERT reported these vulnerabilities to CISA.\n\n\n\n\nGeneral Recommendations\n\nAs a general security measure, Siemens strongly recommends to protect network access to devices with appropriate mechanisms. In order to operate the devices in a protected IT environment, Siemens recommends to configure the environment according to Siemens' operational guidelines for Industrial Security (Download: https://www.siemens.com/cert/operational-guidelines-industrial-security), and to follow the recommendations in the product manuals. Additional information on Industrial Security by Siemens can be found at: https://www.siemens.com/industrialsecurity\n\n\n\nAdditional Resources\n\nFor further inquiries on security vulnerabilities in Siemens products and solutions, please contact the Siemens ProductCERT: https://www.siemens.com/cert/advisories\n\n\n\nTerms of Use\n\nThe use of Siemens Security Advisories is subject to the terms and conditions listed on: https://www.siemens.com/productcert/terms-of-use.\n\n\n\nLegal Notice and Terms of Use\n\nThis product is provided subject to this Notification (https://www.cisa.gov/notification) and this Privacy & Use policy (https://www.cisa.gov/privacy-policy).\n\n\n\nRecommended Practices\n\nCISA recommends users take defensive measures to minimize the exploitation risk of this vulnerability.\n\nMinimize network exposure for all control system devices and/or systems, and ensure they are not accessible from the internet.\n\nLocate control system networks and remote devices behind firewalls and isolate them from business networks.\n\nWhen remote access is required, use more secure methods, such as Virtual Private Networks (VPNs), recognizing VPNs may have vulnerabilities and should be updated to the most recent version available. Also recognize VPN is only as secure as its connected devices.\n\nCISA reminds organizations to perform proper impact analysis and risk assessment prior to deploying defensive measures.\n\nCISA also provides a section for control systems security recommended practices on the ICS webpage on cisa.gov. Several CISA products detailing cyber defense best practices are available for reading and download, including Improving Industrial Control Systems Cybersecurity with Defense-in-Depth Strategies.\n\nCISA encourages organizations to implement recommended cybersecurity strategies for proactive defense of ICS assets. Additional mitigation guidance and recommended practices are publicly available on the ICS webpage at cisa.gov in the technical information paper, ICS-TIP-12-146-01B--Targeted Cyber Intrusion Detection and Mitigation Strategies.\n\nOrganizations observing suspected malicious activity should follow established internal procedures and report findings to CISA for tracking and correlation against other incidents.\n\n\n\nAdvisory Conversion Disclaimer\n\nThis ICSA is a verbatim republication of Siemens ProductCERT SSA-032379 from a direct conversion of the vendor's Common Security Advisory Framework (CSAF) advisory. This is republished to CISA's website as a means of increasing visibility and is provided \"as-is\" for informational purposes only. CISA is not responsible for the editorial or technical accuracy of republished advisories and provides no warranties of any kind regarding any information contained within this advisory. Further, CISA does not endorse any commercial product or service. Please contact Siemens ProductCERT directly for any questions regarding this advisory.\n\nRevision History\n\n\n\nInitial Release Date: 2026-05-12\n\n\n\n\n\nDate\nRevision\nSummary\n\n\n\n\n2026-05-12\n1\nPublication Date\n\n\n2026-05-14\n2\nInitial CISA Republication of Siemens ProductCERT SSA-032379 advisory\n\n\n\n\n\n\nLegal Notice and Terms of Use", "creation_timestamp": "2026-05-14T10:00:00.000000Z"}, {"uuid": "c6262c2a-4864-449f-b7f4-47267863c65f", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37899", "type": "published-proof-of-concept", "source": "https://t.me/hn_best_comments/24847", "content": "Re: I used o3 to find a remote zeroday in the Linux SM...\n        \nA small thing, but I found the author's project-organization practices useful \u2013 creating individual .prompt files for system prompt, background information, and auxiliary instructions [1], and then running it through `llm`.\n\nIt reveals how good LLM use, like any other engineering tool, requires good engineering thinking \u2013 methodical, and oriented around thoughtful specifications that balance design constraints \u2013 for best results.\n\n[1] https://github.com/SeanHeelan/o3_finds_cve-2025-37899\n        \nnxobject, 1 day ago", "creation_timestamp": "2026-08-01T08:00:04.732264Z"}, {"uuid": "08ecc581-d818-404e-b73e-f131de3ffdce", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37164", "type": "seen", "source": "https://t.me/breachdetect/1005371", "content": "{\n  \"Source\": \"https://htdark.com/index.php\",\n  \"Content\": \"Nuclei Templetes - Detection for CVE-2025-37164 - HPE OneView\", \n  \"author\": \" (dEEpEst)\",\n  \"Detection Date\": \"19 Dec 2025\",\n  \"Type\": \"Data leak\"\n}\n\ud83d\udd39 t.me/breachdetect  \ud83d\udd39", "creation_timestamp": "2026-08-22T14:00:15.084052Z"}, {"uuid": "db78e31c-ea9b-48a3-b3f9-1405de563dd1", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37947", "type": "seen", "source": "https://t.me/purp_sec/1191", "content": "\ud83d\ude0f \u0421\u0435\u0433\u043e\u0434\u043d\u044f \u044d\u043a\u0441\u043f\u043b\u0443\u0430\u0442\u0438\u0440\u0443\u0435\u043c \u0431\u0430\u0433 \u0432 \u043f\u043e\u0434\u0441\u0438\u0441\u0442\u0435\u043c\u0435 ksmbd \u044f\u0434\u0440\u0430 Linux \u0447\u0442\u043e\u0431\u044b \u043f\u043e\u0432\u044b\u0441\u0438\u0442\u044c \u043f\u0440\u0438\u0432\u0438\u043b\u0435\u0433\u0438\u0438 \u0434\u043e root\n\n\u0420\u0435\u0431\u044f\u0442\u0430 \u0438\u0437 Doyensec \u043e\u043f\u0443\u0431\u043b\u0438\u043a\u043e\u0432\u0430\u043b\u0438 PoC \u0434\u043b\u044f \u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u0438 CVE-2025-37947. \u0421\u0443\u0442\u044c \u0431\u0430\u0433\u0430 \u0432 \u0442\u043e\u043c, \u0444\u0443\u043d\u043a\u0446\u0438\u044f ksmbd_vfs_stream_write() \u043f\u0440\u043e\u0432\u0435\u0440\u044f\u0435\u0442 pos + count \u0438 \u043e\u0431\u0440\u0435\u0437\u0430\u0435\u0442 size \u0434\u043e 0x10000 (\u043c\u0430\u043a\u0441\u0438\u043c\u0443\u043c \u0434\u043b\u044f xattr). \u041d\u043e \u0434\u0430\u043b\u044c\u0448\u0435 \u043e\u043d\u0430 \u0432\u0441\u0435 \u0440\u0430\u0432\u043d\u043e \u0434\u0435\u043b\u0430\u0435\u0442 memcpy(&stream_buf[pos], buf, count). \u0418 \u0435\u0441\u043b\u0438 pos >= 0x10000, \u0441\u043c\u0435\u0449\u0435\u043d\u0438\u0435 \u0443\u043a\u0430\u0437\u044b\u0432\u0430\u0435\u0442 \u0437\u0430 \u043f\u0440\u0435\u0434\u0435\u043b\u044b \u0431\u0443\u0444\u0435\u0440\u0430, \u0438 count \u043a\u043e\u043f\u0438\u0440\u0443\u0435\u0442\u0441\u044f \u043f\u043e\u0432\u0435\u0440\u0445 \u0441\u043e\u0441\u0435\u0434\u043d\u0438\u0445 \u043e\u0431\u044a\u0435\u043a\u0442\u043e\u0432 \u0432 \u043f\u0430\u043c\u044f\u0442\u0438 \u044f\u0434\u0440\u0430. \u0412 \u0438\u0442\u043e\u0433\u0435 \u043f\u043e\u043b\u0443\u0447\u0430\u0435\u043c \u0443\u043f\u0440\u0430\u0432\u043b\u044f\u0435\u043c\u0443\u044e \u0437\u0430\u043f\u0438\u0441\u044c \u0437\u0430 \u0433\u0440\u0430\u043d\u0438\u0446\u044b \u043c\u0430\u0441\u0441\u0438\u0432\u0430.\n\n\u042d\u043a\u0441\u043f\u043b\u0443\u0430\u0442\u0430\u0446\u0438\u044f \u0441\u0440\u0430\u0431\u043e\u0442\u0430\u0435\u0442, \u0435\u0441\u043b\u0438 \u0432 \u043a\u043e\u043d\u0444\u0438\u0433\u0435 \u0432\u043a\u043b\u044e\u0447\u0435\u043d streams_xattr \u0438 \u0448\u0430\u0440 \u0434\u043e\u0441\u0442\u0443\u043f\u0435\u043d \u043d\u0430 \u0437\u0430\u043f\u0438\u0441\u044c.\n\n\u0427\u0442\u043e \u0434\u0435\u043b\u0430\u0435\u043c:\n\n\u23fa \u0427\u0435\u0440\u0435\u0437 spray System V msg_msg \u0444\u043e\u0440\u0441\u0438\u0440\u0443\u0435\u043c \u0432\u044b\u0434\u0435\u043b\u0435\u043d\u0438\u0435 slab-\u043e\u0431\u044a\u0435\u043a\u0442\u043e\u0432 \u043d\u0443\u0436\u043d\u043e\u0433\u043e \u0440\u0430\u0437\u043c\u0435\u0440\u0430 \u0440\u044f\u0434\u043e\u043c \u0441 \u0443\u044f\u0437\u0432\u0438\u043c\u044b\u043c stream_buf \u0432 ksmbd. \n\u23fa \u041d\u0435\u043a\u043e\u0440\u0440\u0435\u043a\u0442\u043d\u0430\u044f \u043e\u0431\u0440\u0430\u0431\u043e\u0442\u043a\u0430 pos/count \u0432 ksmbd_vfs_stream_write() \u043f\u0440\u0438\u0432\u043e\u0434\u0438\u0442 \u043a OOB-\u0437\u0430\u043f\u0438\u0441\u0438, \u043a\u043e\u0442\u043e\u0440\u0430\u044f \u043f\u043e\u0432\u0440\u0435\u0436\u0434\u0430\u0435\u0442 \u043f\u043e\u043b\u044f \u0441\u043e\u0441\u0435\u0434\u043d\u0435\u0433\u043e msg_msg. \n\u23fa \u041f\u043e\u0441\u043b\u0435 \u043e\u0441\u0432\u043e\u0431\u043e\u0436\u0434\u0435\u043d\u0438\u044f \u044d\u0442\u043e\u0433\u043e \u0441\u043e\u043e\u0431\u0449\u0435\u043d\u0438\u044f \u0437\u0430\u043f\u043e\u043b\u043d\u044f\u0435\u043c \u0441\u043b\u043e\u0442 \u0444\u0435\u0439\u043a\u043e\u0432\u043e\u0439 \u0441\u0442\u0440\u0443\u043a\u0442\u0443\u0440\u043e\u0439 \u0438 \u043f\u043e msgrcv(MSG_COPY) \u0447\u0438\u0442\u0430\u0435\u043c \u043f\u043e\u0434\u0441\u0442\u0430\u0432\u043b\u0435\u043d\u043d\u044b\u0435 \u043f\u043e\u043b\u044f, \u043f\u043e\u043b\u0443\u0447\u0430\u044f infoleak \u0438 \u0441\u043d\u0438\u043c\u0430\u044f KASLR. \n\u23fa \u041f\u043e\u0434\u0434\u0435\u043b\u044b\u0432\u0430\u0435\u043c callback-\u0442\u0430\u0431\u043b\u0438\u0446\u044b (\u043d\u0430\u043f\u0440\u0438\u043c\u0435\u0440, pipe_buf_operations), \u043f\u0440\u0438 \u0432\u044b\u0437\u043e\u0432\u0435 \u043a\u043e\u0442\u043e\u0440\u044b\u0445 \u0437\u0430\u043f\u0443\u0441\u043a\u0430\u0435\u0442\u0441\u044f ROP-\u0446\u0435\u043f\u043e\u0447\u043a\u0430, \u0434\u043e\u0441\u0442\u0438\u0433\u0430\u044e\u0449\u0430\u044f \u0438\u0441\u043f\u043e\u043b\u043d\u0435\u043d\u0438\u044f \u0432 \u044f\u0434\u0440\u0435 \u0438 \u043b\u043e\u043a\u0430\u043b\u044c\u043d\u043e\u0433\u043e \u043f\u043e\u0432\u044b\u0448\u0435\u043d\u0438\u044f \u043f\u0440\u0438\u0432\u0438\u043b\u0435\u0433\u0438\u0439 \u0434\u043e root.\n\n\ud83d\udcac \u041f\u043e\u0434\u0440\u043e\u0431\u043d\u043e\u0441\u0442\u0438 \u043f\u043e \u0441\u0441\u044b\u043b\u043a\u0435.\n\n#red_team #Linux", "creation_timestamp": "2026-08-14T16:00:05.853766Z"}, {"uuid": "26cc3036-39c0-4ee3-b99f-d02ee0235ad6", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2025-37926", "type": "seen", "source": "https://www.hkcert.org/security-bulletin/ubuntu-linux-kernel-multiple-vulnerabilities_20260602", "content": "", "creation_timestamp": "2026-06-01T18:00:00.000000Z"}, {"uuid": "8e3959e4-f4a8-435e-b2d8-44907eae1341", "vulnerability_lookup_origin": "caeb2787-0d58-4236-9039-7c86c3e566f3", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37164", "type": "exploited", "source": "https://vulnerability.circl.lu/known-exploited-vulnerabilities-catalog/94a6e03e-43b1-4354-bde7-bef3da2b13df", "content": "", "creation_timestamp": "2026-06-19T12:45:19.984590Z"}, {"uuid": "70cda8d2-f755-46a3-aa68-d28b4a829606", "vulnerability_lookup_origin": "caeb2787-0d58-4236-9039-7c86c3e566f3", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37899", "type": "exploited", "source": "https://vulnerability.circl.lu/known-exploited-vulnerabilities-catalog/2050fd28-1cb5-4c01-bfaa-7b9bf6f7732e", "content": "", "creation_timestamp": "2026-06-19T12:45:51.150615Z"}, {"uuid": "8d05d0d7-209a-4d03-a5ed-1862b2094e91", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37947", "type": "published-proof-of-concept", "source": "https://t.me/purp_sec/1191", "content": "\ud83d\ude0f \u0421\u0435\u0433\u043e\u0434\u043d\u044f \u044d\u043a\u0441\u043f\u043b\u0443\u0430\u0442\u0438\u0440\u0443\u0435\u043c \u0431\u0430\u0433 \u0432 \u043f\u043e\u0434\u0441\u0438\u0441\u0442\u0435\u043c\u0435 ksmbd \u044f\u0434\u0440\u0430 Linux \u0447\u0442\u043e\u0431\u044b \u043f\u043e\u0432\u044b\u0441\u0438\u0442\u044c \u043f\u0440\u0438\u0432\u0438\u043b\u0435\u0433\u0438\u0438 \u0434\u043e root\n\n\u0420\u0435\u0431\u044f\u0442\u0430 \u0438\u0437 Doyensec \u043e\u043f\u0443\u0431\u043b\u0438\u043a\u043e\u0432\u0430\u043b\u0438 PoC \u0434\u043b\u044f \u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u0438 CVE-2025-37947. \u0421\u0443\u0442\u044c \u0431\u0430\u0433\u0430 \u0432 \u0442\u043e\u043c, \u0444\u0443\u043d\u043a\u0446\u0438\u044f ksmbd_vfs_stream_write() \u043f\u0440\u043e\u0432\u0435\u0440\u044f\u0435\u0442 pos + count \u0438 \u043e\u0431\u0440\u0435\u0437\u0430\u0435\u0442 size \u0434\u043e 0x10000 (\u043c\u0430\u043a\u0441\u0438\u043c\u0443\u043c \u0434\u043b\u044f xattr). \u041d\u043e \u0434\u0430\u043b\u044c\u0448\u0435 \u043e\u043d\u0430 \u0432\u0441\u0435 \u0440\u0430\u0432\u043d\u043e \u0434\u0435\u043b\u0430\u0435\u0442 memcpy(&stream_buf[pos], buf, count). \u0418 \u0435\u0441\u043b\u0438 pos >= 0x10000, \u0441\u043c\u0435\u0449\u0435\u043d\u0438\u0435 \u0443\u043a\u0430\u0437\u044b\u0432\u0430\u0435\u0442 \u0437\u0430 \u043f\u0440\u0435\u0434\u0435\u043b\u044b \u0431\u0443\u0444\u0435\u0440\u0430, \u0438 count \u043a\u043e\u043f\u0438\u0440\u0443\u0435\u0442\u0441\u044f \u043f\u043e\u0432\u0435\u0440\u0445 \u0441\u043e\u0441\u0435\u0434\u043d\u0438\u0445 \u043e\u0431\u044a\u0435\u043a\u0442\u043e\u0432 \u0432 \u043f\u0430\u043c\u044f\u0442\u0438 \u044f\u0434\u0440\u0430. \u0412 \u0438\u0442\u043e\u0433\u0435 \u043f\u043e\u043b\u0443\u0447\u0430\u0435\u043c \u0443\u043f\u0440\u0430\u0432\u043b\u044f\u0435\u043c\u0443\u044e \u0437\u0430\u043f\u0438\u0441\u044c \u0437\u0430 \u0433\u0440\u0430\u043d\u0438\u0446\u044b \u043c\u0430\u0441\u0441\u0438\u0432\u0430.\n\n\u042d\u043a\u0441\u043f\u043b\u0443\u0430\u0442\u0430\u0446\u0438\u044f \u0441\u0440\u0430\u0431\u043e\u0442\u0430\u0435\u0442, \u0435\u0441\u043b\u0438 \u0432 \u043a\u043e\u043d\u0444\u0438\u0433\u0435 \u0432\u043a\u043b\u044e\u0447\u0435\u043d streams_xattr \u0438 \u0448\u0430\u0440 \u0434\u043e\u0441\u0442\u0443\u043f\u0435\u043d \u043d\u0430 \u0437\u0430\u043f\u0438\u0441\u044c.\n\n\u0427\u0442\u043e \u0434\u0435\u043b\u0430\u0435\u043c:\n\n\u23fa \u0427\u0435\u0440\u0435\u0437 spray System V msg_msg \u0444\u043e\u0440\u0441\u0438\u0440\u0443\u0435\u043c \u0432\u044b\u0434\u0435\u043b\u0435\u043d\u0438\u0435 slab-\u043e\u0431\u044a\u0435\u043a\u0442\u043e\u0432 \u043d\u0443\u0436\u043d\u043e\u0433\u043e \u0440\u0430\u0437\u043c\u0435\u0440\u0430 \u0440\u044f\u0434\u043e\u043c \u0441 \u0443\u044f\u0437\u0432\u0438\u043c\u044b\u043c stream_buf \u0432 ksmbd. \n\u23fa \u041d\u0435\u043a\u043e\u0440\u0440\u0435\u043a\u0442\u043d\u0430\u044f \u043e\u0431\u0440\u0430\u0431\u043e\u0442\u043a\u0430 pos/count \u0432 ksmbd_vfs_stream_write() \u043f\u0440\u0438\u0432\u043e\u0434\u0438\u0442 \u043a OOB-\u0437\u0430\u043f\u0438\u0441\u0438, \u043a\u043e\u0442\u043e\u0440\u0430\u044f \u043f\u043e\u0432\u0440\u0435\u0436\u0434\u0430\u0435\u0442 \u043f\u043e\u043b\u044f \u0441\u043e\u0441\u0435\u0434\u043d\u0435\u0433\u043e msg_msg. \n\u23fa \u041f\u043e\u0441\u043b\u0435 \u043e\u0441\u0432\u043e\u0431\u043e\u0436\u0434\u0435\u043d\u0438\u044f \u044d\u0442\u043e\u0433\u043e \u0441\u043e\u043e\u0431\u0449\u0435\u043d\u0438\u044f \u0437\u0430\u043f\u043e\u043b\u043d\u044f\u0435\u043c \u0441\u043b\u043e\u0442 \u0444\u0435\u0439\u043a\u043e\u0432\u043e\u0439 \u0441\u0442\u0440\u0443\u043a\u0442\u0443\u0440\u043e\u0439 \u0438 \u043f\u043e msgrcv(MSG_COPY) \u0447\u0438\u0442\u0430\u0435\u043c \u043f\u043e\u0434\u0441\u0442\u0430\u0432\u043b\u0435\u043d\u043d\u044b\u0435 \u043f\u043e\u043b\u044f, \u043f\u043e\u043b\u0443\u0447\u0430\u044f infoleak \u0438 \u0441\u043d\u0438\u043c\u0430\u044f KASLR. \n\u23fa \u041f\u043e\u0434\u0434\u0435\u043b\u044b\u0432\u0430\u0435\u043c callback-\u0442\u0430\u0431\u043b\u0438\u0446\u044b (\u043d\u0430\u043f\u0440\u0438\u043c\u0435\u0440, pipe_buf_operations), \u043f\u0440\u0438 \u0432\u044b\u0437\u043e\u0432\u0435 \u043a\u043e\u0442\u043e\u0440\u044b\u0445 \u0437\u0430\u043f\u0443\u0441\u043a\u0430\u0435\u0442\u0441\u044f ROP-\u0446\u0435\u043f\u043e\u0447\u043a\u0430, \u0434\u043e\u0441\u0442\u0438\u0433\u0430\u044e\u0449\u0430\u044f \u0438\u0441\u043f\u043e\u043b\u043d\u0435\u043d\u0438\u044f \u0432 \u044f\u0434\u0440\u0435 \u0438 \u043b\u043e\u043a\u0430\u043b\u044c\u043d\u043e\u0433\u043e \u043f\u043e\u0432\u044b\u0448\u0435\u043d\u0438\u044f \u043f\u0440\u0438\u0432\u0438\u043b\u0435\u0433\u0438\u0439 \u0434\u043e root.\n\n\ud83d\udcac \u041f\u043e\u0434\u0440\u043e\u0431\u043d\u043e\u0441\u0442\u0438 \u043f\u043e \u0441\u0441\u044b\u043b\u043a\u0435.\n\n#red_team #Linux", "creation_timestamp": "2026-08-15T00:00:32.308367Z"}, {"uuid": "517d1d14-9cd8-4297-9249-e5a7e48f021a", "vulnerability_lookup_origin": "caeb2787-0d58-4236-9039-7c86c3e566f3", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37164", "type": "exploited", "source": "https://vulnerability.circl.lu/known-exploited-vulnerabilities-catalog/90f2570a-c6ae-407a-b90c-bfa99ba17c21", "content": "", "creation_timestamp": "2026-06-23T14:03:45.572158Z"}, {"uuid": "7e49c54b-3dd6-484a-b896-ef96f5f5b6fc", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37882", "type": "seen", "source": "https://bsky.app/profile/cybernewsroom.bsky.social/post/3mph3na654l2w", "content": "A Silent Data Killer: The Threat of CVE-2025-37882", "creation_timestamp": "2026-06-29T18:12:24.507312Z"}, {"uuid": "3a474270-439d-499f-a8f1-db2a4e8cf1ef", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37745", "type": "seen", "source": "https://bsky.app/profile/cybernewsroom.bsky.social/post/3mph4ulwudj2i", "content": "CVE-2025-37745: Another Hobbled Fable in the Hibernate Saga", "creation_timestamp": "2026-06-29T18:34:25.479532Z"}, {"uuid": "f8db135a-b2fb-4c76-b863-d7b5feb518f2", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37747", "type": "seen", "source": "https://bsky.app/profile/cybernewsroom.bsky.social/post/3mpgz6gyyyj2o", "content": "CVE-2025-37747: Don't Get Caught in a Performance Hang-Up", "creation_timestamp": "2026-06-29T17:28:20.577828Z"}, {"uuid": "252641fd-16a7-4818-b931-fac93cf8c1b2", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37747", "type": "seen", "source": "https://bsky.app/profile/cybernewsroom.bsky.social/post/3mpgz6jufnb2g", "content": "A Silent Threat: How CVE-2025-37747 Could Hang Your Defenses", "creation_timestamp": "2026-06-29T17:28:23.517230Z"}, {"uuid": "c0c38952-b754-4726-93d2-c1f0461586a0", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37750", "type": "seen", "source": "https://bsky.app/profile/cybernewsroom.bsky.social/post/3mpgye4sxd622", "content": "Breach Risks Soar with CVE-2025-37750: Fix Your SMB Client Now", "creation_timestamp": "2026-06-29T17:13:37.791926Z"}, {"uuid": "cbeecf8c-9405-4e04-b040-32d4f08e483a", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37750", "type": "seen", "source": "https://bsky.app/profile/cybernewsroom.bsky.social/post/3mpgye6yfqb2q", "content": "CVE-2025-37750: A Recipe for Chaos in SMB Client Security", "creation_timestamp": "2026-06-29T17:13:39.589386Z"}, {"uuid": "faee459a-8035-400a-9fa2-0d9c36b68e39", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37750", "type": "seen", "source": "https://bsky.app/profile/cybernewsroom.bsky.social/post/3mpgyo4lttz2w", "content": "CVE-2025-37750: A Chilling Reminder of the Fragility of Trust in SMB Protocols", "creation_timestamp": "2026-06-29T17:19:12.962629Z"}, {"uuid": "1ed50b9b-52d3-40fe-876a-f78b22668355", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37750", "type": "seen", "source": "https://bsky.app/profile/cybernewsroom.bsky.social/post/3mpgyocnykn2b", "content": "CVE-2025-37750: When Fixes Are Only Half the Battle Against Systemic Weakness", "creation_timestamp": "2026-06-29T17:19:19.541397Z"}, {"uuid": "bc02de84-f18f-4150-95e4-625273a00a59", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37750", "type": "seen", "source": "https://bsky.app/profile/cybernewsroom.bsky.social/post/3mpgyohmszn2l", "content": "CVE-2025-37750: Another CVE with More Questions than Answers", "creation_timestamp": "2026-06-29T17:19:24.499842Z"}, {"uuid": "b676e42c-d98d-48e0-a30b-7a64edeca07a", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37750", "type": "seen", "source": "https://bsky.app/profile/cybernewsroom.bsky.social/post/3mpgyok73lj2g", "content": "Roundtable: CVE-2025-37750 smb: client: fix UAF in decryption with multichannel", "creation_timestamp": "2026-06-29T17:19:27.016766Z"}, {"uuid": "72a6ffaa-750a-4d53-8735-878e39a14930", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37747", "type": "seen", "source": "https://bsky.app/profile/cybernewsroom.bsky.social/post/3mpgz6luzsk2i", "content": "CVE-2025-37747: Another Hidden Fault Line in Microsoft's Security Narrative", "creation_timestamp": "2026-06-29T17:28:25.621364Z"}, {"uuid": "ff1bcf16-8c10-4d17-b048-e4b8faa5769b", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37747", "type": "seen", "source": "https://bsky.app/profile/cybernewsroom.bsky.social/post/3mpgz6o5kkj2g", "content": "CVE-2025-37747: A Serious Oversight in Microsoft\u2019s Performance Security", "creation_timestamp": "2026-06-29T17:28:28.033330Z"}, {"uuid": "f47bcb72-31e7-4c1a-9ac8-f583f389e0f9", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37747", "type": "seen", "source": "https://bsky.app/profile/cybernewsroom.bsky.social/post/3mpgz6pxync2o", "content": "CVE-2025-37747: Another Performance Flaw with More Questions than Answers", "creation_timestamp": "2026-06-29T17:28:29.907125Z"}, {"uuid": "5308945f-90b7-4e75-bddb-656ee1ff7827", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37747", "type": "seen", "source": "https://bsky.app/profile/cybernewsroom.bsky.social/post/3mpgz6rynmx22", "content": "The Tension Over CVE-2025-37747: Urgency, Exploitation, and Ethical Risks", "creation_timestamp": "2026-06-29T17:28:32.131377Z"}, {"uuid": "213a1d0d-bec9-4865-a9c3-31f7aaee3aa7", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37807", "type": "seen", "source": "https://bsky.app/profile/cybernewsroom.bsky.social/post/3mph2ei3sra2v", "content": "Yet Another Dangerous Memory Leak: CVE-2025-37807 Demands Your Attention", "creation_timestamp": "2026-06-29T17:49:36.888118Z"}, {"uuid": "5c974cd2-5da3-4151-943c-9d4053253a46", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37807", "type": "seen", "source": "https://bsky.app/profile/cybernewsroom.bsky.social/post/3mph2ejw3sw27", "content": "CVE-2025-37807: When Memory Leaks Become Ticking Time Bombs", "creation_timestamp": "2026-06-29T17:49:39.076309Z"}, {"uuid": "10715248-2c66-48ad-97d6-9e768e303828", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37807", "type": "seen", "source": "https://bsky.app/profile/cybernewsroom.bsky.social/post/3mph2elzamy2w", "content": "A Patch or a Band-Aid? Examining the Shadows of CVE-2025-37807", "creation_timestamp": "2026-06-29T17:49:41.008381Z"}, {"uuid": "c43c8888-7314-4480-9ccf-12f8447c5fa9", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37807", "type": "seen", "source": "https://bsky.app/profile/cybernewsroom.bsky.social/post/3mph2eo24gg27", "content": "CVE-2025-37807: A Cautionary Reminder of Governance Failures in Cybersecurity Disclosures", "creation_timestamp": "2026-06-29T17:49:43.109456Z"}, {"uuid": "f1725095-6987-43f3-8e5c-0414773027ac", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37807", "type": "seen", "source": "https://bsky.app/profile/cybernewsroom.bsky.social/post/3mph2eqb6mr2o", "content": "CVE-2025-37807: A Vulnerability Wrapped in Ambiguity", "creation_timestamp": "2026-06-29T17:49:45.307245Z"}, {"uuid": "6cd9ac7e-a83c-4063-839a-3beb39454301", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37807", "type": "seen", "source": "https://bsky.app/profile/cybernewsroom.bsky.social/post/3mph2es7hw62i", "content": "Fault Lines: How the Security Community is Divided on CVE-2025-37807", "creation_timestamp": "2026-06-29T17:49:47.758151Z"}, {"uuid": "8915ccf8-466f-4fbb-988f-1b634eaf2a0d", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37861", "type": "seen", "source": "https://bsky.app/profile/cybernewsroom.bsky.social/post/3mph356o5sl2g", "content": "Undue Optimism Around CVE-2025-37861 Conceals Systemic Oversight", "creation_timestamp": "2026-06-29T18:03:25.804145Z"}, {"uuid": "d47e32b3-c7f2-4f93-9106-03e6e4a9785d", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37861", "type": "seen", "source": "https://bsky.app/profile/cybernewsroom.bsky.social/post/3mph35bc5qu2o", "content": "CVE-2025-37861: Potential Panic or Just Another Overhyped Flaw?", "creation_timestamp": "2026-06-29T18:03:28.488582Z"}, {"uuid": "c26b65bb-f0c3-465c-a10f-d865ee716638", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37861", "type": "seen", "source": "https://bsky.app/profile/cybernewsroom.bsky.social/post/3mph35dbo5322", "content": "Fault Lines: How the Security Community is Divided on CVE-2025-37861", "creation_timestamp": "2026-06-29T18:03:30.629626Z"}, {"uuid": "4d602943-0d53-4167-b152-0c50d9ddc4a3", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37882", "type": "seen", "source": "https://bsky.app/profile/cybernewsroom.bsky.social/post/3mph3n5woez2i", "content": "CVE-2025-37882: A Potential USB Meltdown You Can't Ignore", "creation_timestamp": "2026-06-29T18:12:22.334489Z"}, {"uuid": "d9f80161-0deb-457a-9825-b34d66fb416a", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37882", "type": "seen", "source": "https://bsky.app/profile/cybernewsroom.bsky.social/post/3mph3nc5nbp2o", "content": "CVE-2025-37882: A Warning on USB Security Gaps and Our Blind Trust in Fixes", "creation_timestamp": "2026-06-29T18:12:26.545022Z"}, {"uuid": "8362421a-db02-4238-9b17-4be84f8f7651", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37882", "type": "seen", "source": "https://bsky.app/profile/cybernewsroom.bsky.social/post/3mph3neatqd2w", "content": "CVE-2025-37882: A Revealing Glimpse into Systemic Weaknesses in USB Handling", "creation_timestamp": "2026-06-29T18:12:29.233543Z"}, {"uuid": "e6218dc7-4cc0-4f7a-bea6-f30c2259cdc5", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37882", "type": "seen", "source": "https://bsky.app/profile/cybernewsroom.bsky.social/post/3mph3ng656y2i", "content": "CVE-2025-37882: Another USB Flaw with Questionable Urgency", "creation_timestamp": "2026-06-29T18:12:30.735088Z"}, {"uuid": "330730a5-c16f-4f3f-8a9d-dd54ab12c44e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37882", "type": "seen", "source": "https://bsky.app/profile/cybernewsroom.bsky.social/post/3mph3niczca2i", "content": "Roundtable: CVE-2025-37882 usb: xhci: Fix isochronous Ring Underrun/Overrun event handling", "creation_timestamp": "2026-06-29T18:12:32.815758Z"}, {"uuid": "db98939c-89e9-40fc-b4e4-8b6e626dd69d", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37856", "type": "seen", "source": "https://bsky.app/profile/cybernewsroom.bsky.social/post/3mph4e6pmua2o", "content": "Another Day, Another Race Condition: Stop Ignoring CVE-2025-37856", "creation_timestamp": "2026-06-29T18:25:14.661600Z"}, {"uuid": "4e24a050-92a4-4539-a7de-3b742c03670a", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37856", "type": "seen", "source": "https://bsky.app/profile/cybernewsroom.bsky.social/post/3mph4eawr2q2l", "content": "CVE-2025-37856: A Race Condition Waiting for its Attacker", "creation_timestamp": "2026-06-29T18:25:17.127284Z"}, {"uuid": "2e54de01-ddcc-432a-b7cd-4043cf6ae750", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37856", "type": "seen", "source": "https://bsky.app/profile/cybernewsroom.bsky.social/post/3mph4edbhhy27", "content": "CVE-2025-37856: A Necessary Fix or Overhyped Security Theater?", "creation_timestamp": "2026-06-29T18:25:19.092394Z"}, {"uuid": "881f071d-7b95-48d3-8fa2-c60b1fcda025", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37856", "type": "seen", "source": "https://bsky.app/profile/cybernewsroom.bsky.social/post/3mph4efr72g2i", "content": "CVE-2025-37856: A Vulnerability That Challenges Operational Accountability in Software Development", "creation_timestamp": "2026-06-29T18:25:21.809105Z"}, {"uuid": "f5999bac-20fd-4f3e-a398-f5c67af9a6e1", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37856", "type": "seen", "source": "https://bsky.app/profile/cybernewsroom.bsky.social/post/3mph4ei7lu62o", "content": "CVE-2025-37856: A Token Fix for an Elusive Threat", "creation_timestamp": "2026-06-29T18:25:24.383621Z"}, {"uuid": "988ccd19-ad05-46cd-be47-2c855a72c7fb", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37856", "type": "seen", "source": "https://bsky.app/profile/cybernewsroom.bsky.social/post/3mph4ekql3g2b", "content": "Roundtable: CVE-2025-37856 btrfs: harden block_group::bg_list against list_del() races", "creation_timestamp": "2026-06-29T18:25:26.987837Z"}, {"uuid": "35b4a739-d010-4c9c-b1b7-ec677e4971f8", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37745", "type": "seen", "source": "https://bsky.app/profile/cybernewsroom.bsky.social/post/3mph4udk2ej2g", "content": "Critical System Instability: Act Fast on CVE-2025-37745", "creation_timestamp": "2026-06-29T18:34:16.595441Z"}, {"uuid": "ccea6d89-6913-4ca7-a049-5d3b2b6b84db", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37745", "type": "seen", "source": "https://bsky.app/profile/cybernewsroom.bsky.social/post/3mph4ufhfnz2i", "content": "CVE-2025-37745: Another Example of Systemic Overconfidence in Hibernate Stability", "creation_timestamp": "2026-06-29T18:34:18.211138Z"}, {"uuid": "3c382b01-b923-41d0-8a19-2a819041581e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37745", "type": "seen", "source": "https://bsky.app/profile/cybernewsroom.bsky.social/post/3mph4uhwhex2b", "content": "CVE-2025-37745: An Underreported Threat in System Stability with Privacy Implications", "creation_timestamp": "2026-06-29T18:34:20.721153Z"}, {"uuid": "f1bc2bb7-5741-4b58-92f7-0b14fd165dad", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37745", "type": "seen", "source": "https://bsky.app/profile/cybernewsroom.bsky.social/post/3mph4ujva5c2l", "content": "CVE-2025-37745: A Systemic Risk Through Insufficient Disclosure", "creation_timestamp": "2026-06-29T18:34:23.089019Z"}, {"uuid": "828ed4cd-ed4b-4d23-8b1f-4c1f99091315", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37745", "type": "seen", "source": "https://bsky.app/profile/cybernewsroom.bsky.social/post/3mph4unzaw32o", "content": "Roundtable: CVE-2025-37745 PM: hibernate: Avoid deadlock in hibernate_compressor_param_set()", "creation_timestamp": "2026-06-29T18:34:27.283988Z"}, {"uuid": "677c84bb-e104-46ef-b345-739cd29ccd75", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37826", "type": "seen", "source": "https://bsky.app/profile/cybernewsroom.bsky.social/post/3mph5lly3sn24", "content": "The Divide on CVE-2025-37826: Urgency vs. Caution in Vulnerability Response", "creation_timestamp": "2026-06-29T18:47:17.216976Z"}, {"uuid": "c56bdc6e-9c40-4813-875b-f07a7768e973", "vulnerability_lookup_origin": "c8fb6bf1-f81f-4cb8-95b1-eadbb3b54ee8", "author": "af0120d0-3dac-4a6a-974b-a9f33d2a9846", "vulnerability": "CVE-2025-37164", "type": "exploited", "source": "https://vulnerability.circl.lu/known-exploited-vulnerabilities-catalog/e43e5d7e-3f98-4df5-aff8-a79553d32660", "content": "", "creation_timestamp": "2026-06-30T09:42:36.162292Z"}, {"uuid": "e8c0d9ec-971d-448b-9713-810493c39cb6", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2025-37778", "type": "seen", "source": "https://www.hkcert.org/security-bulletin/ubuntu-linux-kernel-multiple-vulnerabilities_20260702", "content": "", "creation_timestamp": "2026-07-02T05:45:05.288909Z"}, {"uuid": "c0424a7c-aac4-41cf-95f4-6f2da3d9f582", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2025-37822", "type": "seen", "source": "https://www.hkcert.org/security-bulletin/ubuntu-linux-kernel-multiple-vulnerabilities_20260702", "content": "", "creation_timestamp": "2026-07-02T05:45:07.492652Z"}, {"uuid": "f94c3a88-294f-4911-824a-ac51a7402409", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2025-37924", "type": "seen", "source": "https://www.hkcert.org/security-bulletin/ubuntu-linux-kernel-multiple-vulnerabilities_20260702", "content": "", "creation_timestamp": "2026-07-02T05:45:10.061366Z"}, {"uuid": "54c85c62-1d67-4733-b213-2f27c04b0d2c", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2025-37864", "type": "seen", "source": "https://www.hkcert.org/security-bulletin/debian-linux-kernel-multiple-vulnerabilities_20260706", "content": "", "creation_timestamp": "2026-07-06T05:48:43.684514Z"}, {"uuid": "d6e094a8-c83d-4a39-9023-994e6ee3ead4", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2025-37926", "type": "seen", "source": "https://www.hkcert.org/security-bulletin/ubuntu-linux-kernel-multiple-vulnerabilities_20260702", "content": "", "creation_timestamp": "2026-07-09T00:45:56.329899Z"}, {"uuid": "76276895-4c7b-41c0-849d-4ad258e7aad3", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37164", "type": "seen", "source": "https://t.me/iiLinux/3164", "content": "CVE-2025-37164: Unauthenticated RCE in HPE OneView.\n\nUnauthenticated RCE (10.0 CVSS) vulnerability, in Hewlett Packard Enterprise (HPE) OneView via an unauthenticated REST endpoint called executeCommand. All versions below 11.00 are vulnerable (so long as the vendor supplied hotfix has not been applied), however some VM product versions do not enable the vulnerable \"ID Pools\" endpoint, and are not exploitable.\n\nPOC : https://github.com/g0vguy/CVE-2025-37164-PoC", "creation_timestamp": "2026-07-09T03:00:04.260871Z"}, {"uuid": "b78f4c45-0b14-4ea6-a8a5-219004daa764", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37164", "type": "seen", "source": "https://t.me/iiLinux/3164", "content": "CVE-2025-37164: Unauthenticated RCE in HPE OneView.\n\nUnauthenticated RCE (10.0 CVSS) vulnerability, in Hewlett Packard Enterprise (HPE) OneView via an unauthenticated REST endpoint called executeCommand. All versions below 11.00 are vulnerable (so long as the vendor supplied hotfix has not been applied), however some VM product versions do not enable the vulnerable \"ID Pools\" endpoint, and are not exploitable.\n\nPOC : https://github.com/g0vguy/CVE-2025-37164-PoC", "creation_timestamp": "2026-07-10T00:00:11.303364Z"}, {"uuid": "21e31187-0e1b-41f5-b366-a886a3fe8a40", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37164", "type": "published-proof-of-concept", "source": "https://t.me/iiLinux/3164", "content": "CVE-2025-37164: Unauthenticated RCE in HPE OneView.\n\nUnauthenticated RCE (10.0 CVSS) vulnerability, in Hewlett Packard Enterprise (HPE) OneView via an unauthenticated REST endpoint called executeCommand. All versions below 11.00 are vulnerable (so long as the vendor supplied hotfix has not been applied), however some VM product versions do not enable the vulnerable \"ID Pools\" endpoint, and are not exploitable.\n\nPOC : https://github.com/g0vguy/CVE-2025-37164-PoC", "creation_timestamp": "2026-07-11T09:00:04.948377Z"}, {"uuid": "f7c9373d-b381-47bf-b1b8-b2aab82c3279", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37164", "type": "published-proof-of-concept", "source": "https://t.me/iiLinux/3164", "content": "CVE-2025-37164: Unauthenticated RCE in HPE OneView.\n\nUnauthenticated RCE (10.0 CVSS) vulnerability, in Hewlett Packard Enterprise (HPE) OneView via an unauthenticated REST endpoint called executeCommand. All versions below 11.00 are vulnerable (so long as the vendor supplied hotfix has not been applied), however some VM product versions do not enable the vulnerable \"ID Pools\" endpoint, and are not exploitable.\n\nPOC : https://github.com/g0vguy/CVE-2025-37164-PoC", "creation_timestamp": "2026-07-12T00:00:55.112265Z"}, {"uuid": "d987d3c9-4f1d-4395-aae0-7c11ea18263b", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37164", "type": "published-proof-of-concept", "source": "https://t.me/libs_of_hackers/1053", "content": "\u0412 HPE OneView \u0438\u0441\u043f\u0440\u0430\u0432\u0438\u043b\u0438 \u043a\u0440\u0438\u0442\u0438\u0447\u0435\u0441\u043a\u0438\u0439 RCE-\u0431\u0430\u0433 \n \n\u0420\u0430\u0437\u0440\u0430\u0431\u043e\u0442\u0447\u0438\u043a\u0438 Hewlett Packard Enterprise (HPE) \u0432\u044b\u043f\u0443\u0441\u0442\u0438\u043b\u0438 \u0438\u0441\u043f\u0440\u0430\u0432\u043b\u0435\u043d\u0438\u044f \u0434\u043b\u044f \u043a\u0440\u0438\u0442\u0438\u0447\u0435\u0441\u043a\u043e\u0439 \u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u0438 \u0443\u0434\u0430\u043b\u0435\u043d\u043d\u043e\u0433\u043e \u0432\u044b\u043f\u043e\u043b\u043d\u0435\u043d\u0438\u044f \u043a\u043e\u0434\u0430, \u043e\u0431\u043d\u0430\u0440\u0443\u0436\u0435\u043d\u043d\u043e\u0439 \u0432 \u041f\u041e \u0434\u043b\u044f \u0443\u043f\u0440\u0430\u0432\u043b\u0435\u043d\u0438\u044f \u0418\u0422-\u0438\u043d\u0444\u0440\u0430\u0441\u0442\u0440\u0443\u043a\u0442\u0443\u0440\u043e\u0439 OneView. \u041f\u0440\u043e\u0431\u043b\u0435\u043c\u0430 \u043f\u043e\u043b\u0443\u0447\u0438\u043b\u0430 \u0438\u0434\u0435\u043d\u0442\u0438\u0444\u0438\u043a\u0430\u0442\u043e\u0440 CVE-2025-37164 (\u043c\u0430\u043a\u0441\u0438\u043c\u0430\u043b\u044c\u043d\u044b\u0435 10,0 \u0431\u0430\u043b\u043b\u0430 \u043f\u043e \u0448\u043a\u0430\u043b\u0435 CVSS) \u0438 \u043c\u043e\u0436\u0435\u0442 \u0438\u0441\u043f\u043e\u043b\u044c\u0437\u043e\u0432\u0430\u0442\u044c\u0441\u044f \u0431\u0435\u0437 \u0430\u0443\u0442\u0435\u043d\u0442\u0438\u0444\u0438\u043a\u0430\u0446\u0438\u0438. \n \nhttps://xakep.ru/2025/12/23/cve-2025-37164/\n\n@libs_of_hackers", "creation_timestamp": "2026-07-16T07:00:04.402234Z"}, {"uuid": "81ce7225-fb81-4a8c-bf70-9454f7c377ae", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37164", "type": "published-proof-of-concept", "source": "https://t.me/libs_of_hackers/1053", "content": "\u0412 HPE OneView \u0438\u0441\u043f\u0440\u0430\u0432\u0438\u043b\u0438 \u043a\u0440\u0438\u0442\u0438\u0447\u0435\u0441\u043a\u0438\u0439 RCE-\u0431\u0430\u0433 \n \n\u0420\u0430\u0437\u0440\u0430\u0431\u043e\u0442\u0447\u0438\u043a\u0438 Hewlett Packard Enterprise (HPE) \u0432\u044b\u043f\u0443\u0441\u0442\u0438\u043b\u0438 \u0438\u0441\u043f\u0440\u0430\u0432\u043b\u0435\u043d\u0438\u044f \u0434\u043b\u044f \u043a\u0440\u0438\u0442\u0438\u0447\u0435\u0441\u043a\u043e\u0439 \u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u0438 \u0443\u0434\u0430\u043b\u0435\u043d\u043d\u043e\u0433\u043e \u0432\u044b\u043f\u043e\u043b\u043d\u0435\u043d\u0438\u044f \u043a\u043e\u0434\u0430, \u043e\u0431\u043d\u0430\u0440\u0443\u0436\u0435\u043d\u043d\u043e\u0439 \u0432 \u041f\u041e \u0434\u043b\u044f \u0443\u043f\u0440\u0430\u0432\u043b\u0435\u043d\u0438\u044f \u0418\u0422-\u0438\u043d\u0444\u0440\u0430\u0441\u0442\u0440\u0443\u043a\u0442\u0443\u0440\u043e\u0439 OneView. \u041f\u0440\u043e\u0431\u043b\u0435\u043c\u0430 \u043f\u043e\u043b\u0443\u0447\u0438\u043b\u0430 \u0438\u0434\u0435\u043d\u0442\u0438\u0444\u0438\u043a\u0430\u0442\u043e\u0440 CVE-2025-37164 (\u043c\u0430\u043a\u0441\u0438\u043c\u0430\u043b\u044c\u043d\u044b\u0435 10,0 \u0431\u0430\u043b\u043b\u0430 \u043f\u043e \u0448\u043a\u0430\u043b\u0435 CVSS) \u0438 \u043c\u043e\u0436\u0435\u0442 \u0438\u0441\u043f\u043e\u043b\u044c\u0437\u043e\u0432\u0430\u0442\u044c\u0441\u044f \u0431\u0435\u0437 \u0430\u0443\u0442\u0435\u043d\u0442\u0438\u0444\u0438\u043a\u0430\u0446\u0438\u0438. \n \nhttps://xakep.ru/2025/12/23/cve-2025-37164/\n\n@libs_of_hackers", "creation_timestamp": "2026-07-17T00:00:56.085536Z"}, {"uuid": "b8a2944a-a236-4d04-adc8-c580348dc483", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37654", "type": "seen", "source": "Telegram/0Lzh2WjQOWsuTydOW_ekHZzZKDiwWQ3j_cpMbWJHlr9U_UA", "content": "", "creation_timestamp": "2026-08-24T21:00:05.306989Z"}, {"uuid": "37e4e42f-8b40-4b6c-b0b3-d7fb2e69376e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37164", "type": "seen", "source": "https://t.me/proxy_bar/2979", "content": "CVE-2025-37164 HPE OneView\n*\nunauth RCE exploit module", "creation_timestamp": "2026-07-20T19:00:08.874019Z"}, {"uuid": "8aa41ced-5a26-4d38-b8b9-1d187a38b684", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37164", "type": "seen", "source": "https://t.me/breachdetect/1005371", "content": "{\n  \"Source\": \"https://htdark.com/index.php\",\n  \"Content\": \"Nuclei Templetes - Detection for CVE-2025-37164 - HPE OneView\", \n  \"author\": \" (dEEpEst)\",\n  \"Detection Date\": \"19 Dec 2025\",\n  \"Type\": \"Data leak\"\n}\n\ud83d\udd39 t.me/breachdetect  \ud83d\udd39", "creation_timestamp": "2026-08-23T00:00:39.890163Z"}, {"uuid": "f4a95817-bfd0-4b56-b4d4-9270c27185ba", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37164", "type": "seen", "source": "https://t.me/proxy_bar/2979", "content": "CVE-2025-37164 HPE OneView\n*\nunauth RCE exploit module", "creation_timestamp": "2026-07-21T00:00:27.570066Z"}, {"uuid": "c57241b8-66fe-4d71-ad05-9dabb7b2b7c6", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37164", "type": "published-proof-of-concept", "source": "https://t.me/proxy_bar/2979", "content": "CVE-2025-37164 HPE OneView\n*\nunauth RCE exploit module", "creation_timestamp": "2026-07-22T00:00:26.711264Z"}, {"uuid": "a6b535bd-df04-4987-b884-76ac5c113190", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37654", "type": "published-proof-of-concept", "source": "Telegram/0Lzh2WjQOWsuTydOW_ekHZzZKDiwWQ3j_cpMbWJHlr9U_UA", "content": "", "creation_timestamp": "2026-08-25T00:00:08.448893Z"}, {"uuid": "e288888f-04d8-4567-a115-b28ca8cd2bda", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37654", "type": "seen", "source": "https://t.me/GithubRedTeam/99424", "content": "\ud83d\udea8 GitHub \u76d1\u63a7\u6d88\u606f\u63d0\u9192\n\n\ud83d\udea8 \u53d1\u73b0\u5173\u952e\u8bcd\uff1a #XSS #CVE\n\n\ud83d\udce6 \u9879\u76ee\u540d\u79f0\uff1a patch-CVE-2025-37654\n\ud83d\udc64 \u9879\u76ee\u4f5c\u8005\uff1a gduma-phData\n\ud83d\udee0 \u5f00\u53d1\u8bed\u8a00\uff1a Unknown\n\u2b50 Star\u6570\u91cf\uff1a 0  |  \ud83c\udf74 Fork\u6570\u91cf\uff1a 0\n\ud83d\udcc5 \u66f4\u65b0\u65f6\u95f4\uff1a 2026-08-24 03:03:53\n\n\ud83d\udcdd \u9879\u76ee\u63cf\u8ff0\uff1a\nPatch: XSS leading to RCE (Zimbra Collaboration)\n\n\ud83d\udd17 \u70b9\u51fb\u8bbf\u95ee\u9879\u76ee\u5730\u5740", "creation_timestamp": "2026-08-25T00:00:25.222900Z"}, {"uuid": "b4f2f4e4-fa79-4573-aea5-3cf0c4523ac4", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37093", "type": "seen", "source": "https://t.me/ZerodayAlert/515", "content": "\u041a\u043e\u0433\u0434\u0430 \u043e\u0431\u043d\u043e\u0432\u043b\u0435\u043d\u0438\u0435 \u0432\u0430\u0436\u043d\u0435\u0435, \u0447\u0435\u043c \u0431\u044d\u043a\u0430\u043f\n\n\ud83d\udccd \u0423\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u044c \u0432 StoreOnce \u2014 \u043d\u0430\u043f\u043e\u043c\u0438\u043d\u0430\u043d\u0438\u0435: \u0431\u0435\u0437\u043e\u043f\u0430\u0441\u043d\u043e\u0441\u0442\u044c \u0441\u0438\u0441\u0442\u0435\u043c\u044b \u0445\u0440\u0430\u043d\u0435\u043d\u0438\u044f \u0434\u0430\u043d\u043d\u044b\u0445 \u0432\u0430\u0436\u043d\u0430 \u043d\u0435 \u043c\u0435\u043d\u044c\u0448\u0435, \u0447\u0435\u043c \u0435\u0451 \u043d\u0430\u0434\u0451\u0436\u043d\u043e\u0441\u0442\u044c. CVE-2025-37093 \u043f\u043e\u043a\u0430\u0437\u044b\u0432\u0430\u0435\u0442, \u043a\u0430\u043a \u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u044c \u043d\u0430 \u0443\u0440\u043e\u0432\u043d\u0435 \u0430\u0443\u0442\u0435\u043d\u0442\u0438\u0444\u0438\u043a\u0430\u0446\u0438\u0438 \u043f\u0440\u0435\u0432\u0440\u0430\u0449\u0430\u0435\u0442 \u0438\u043d\u0441\u0442\u0440\u0443\u043c\u0435\u043d\u0442 \u0440\u0435\u0437\u0435\u0440\u0432\u043d\u043e\u0433\u043e \u043a\u043e\u043f\u0438\u0440\u043e\u0432\u0430\u043d\u0438\u044f \u0432 \u0442\u043e\u0447\u043a\u0443 \u0440\u0438\u0441\u043a\u0430, \u0430 \u043d\u0435 \u0437\u0430\u0449\u0438\u0442\u044b. \u041e\u0441\u043e\u0431\u0435\u043d\u043d\u043e \u043a\u043e\u0433\u0434\u0430 \u0440\u0435\u0447\u044c \u043e \u043f\u043b\u0430\u0442\u0444\u043e\u0440\u043c\u0430\u0445, \u0441\u0442\u043e\u044f\u0449\u0438\u0445 \u0432 \u0446\u0435\u043d\u0442\u0440\u0435 \u0418\u0422-\u043b\u0430\u043d\u0434\u0448\u0430\u0444\u0442\u0430.\n\n\ud83d\udd0d \u0421\u0442\u0440\u0430\u0442\u0435\u0433\u0438\u0447\u0435\u0441\u043a\u0438 \u0432\u0430\u0436\u043d\u043e \u0434\u0440\u0443\u0433\u043e\u0435: \u043a\u0430\u043a StoreOnce \u043e\u043a\u0430\u0437\u0430\u043b\u0441\u044f \u0443\u044f\u0437\u0432\u0438\u043c \u0432 \u0442\u0435\u0447\u0435\u043d\u0438\u0435 \u043f\u043e\u043b\u0443\u0433\u043e\u0434\u0430 \u0431\u0435\u0437 \u043f\u0443\u0431\u043b\u0438\u0447\u043d\u044b\u0445 \u043f\u0440\u0438\u0437\u043d\u0430\u043a\u043e\u0432 \u0430\u043a\u0442\u0438\u0432\u043d\u043e\u0441\u0442\u0438? \u042d\u0442\u043e \u0438\u043b\u043b\u044e\u0441\u0442\u0440\u0430\u0446\u0438\u044f \u0441\u043b\u0435\u043f\u043e\u0439 \u0437\u043e\u043d\u044b, \u043a\u043e\u0433\u0434\u0430 \u0438\u043d\u0444\u0440\u0430\u0441\u0442\u0440\u0443\u043a\u0442\u0443\u0440\u043d\u044b\u0435 \u043f\u0440\u043e\u0434\u0443\u043a\u0442\u044b \u043a\u0430\u0436\u0443\u0442\u0441\u044f \u00ab\u043c\u043e\u043b\u0447\u0430\u0449\u0438\u043c\u0438\u00bb \u0438 \u044f\u043a\u043e\u0431\u044b \u0431\u0435\u0437\u043e\u043f\u0430\u0441\u043d\u044b\u043c\u0438. \u041d\u043e \u0438\u043c\u0435\u043d\u043d\u043e \u0442\u0430\u043a\u0438\u0435 \u0442\u0438\u0445\u0438\u0435 \u0443\u0437\u043b\u044b \u2014 \u0438\u0434\u0435\u0430\u043b\u044c\u043d\u044b\u0435 \u0446\u0435\u043b\u0438: \u043d\u0438\u043a\u0442\u043e \u043d\u0435 \u043e\u0436\u0438\u0434\u0430\u0435\u0442 \u0430\u0442\u0430\u043a\u0438 \u043d\u0430 \u0440\u0435\u0448\u0435\u043d\u0438\u0435, \u0437\u0430\u0449\u0438\u0449\u0430\u044e\u0449\u0435\u0435 \u0434\u0430\u043d\u043d\u044b\u0435.\n\n\ud83d\udccc \u0421\u0435\u0439\u0447\u0430\u0441 StoreOnce \u043d\u0435 \u043f\u0440\u0435\u0434\u043b\u0430\u0433\u0430\u0435\u0442 \u0432\u0440\u0435\u043c\u0435\u043d\u043d\u044b\u0445 \u043c\u0435\u0440 \u0437\u0430\u0449\u0438\u0442\u044b \u2014 \u0442\u043e\u043b\u044c\u043a\u043e \u043e\u0431\u043d\u043e\u0432\u043b\u0435\u043d\u0438\u0435. \u0415\u0441\u043b\u0438 \u043f\u043b\u0430\u0442\u0444\u043e\u0440\u043c\u0430 \u0438\u0441\u043f\u043e\u043b\u044c\u0437\u0443\u0435\u0442\u0441\u044f \u0432 \u043a\u0440\u0438\u0442\u0438\u0447\u0435\u0441\u043a\u0438\u0445 \u0441\u0440\u0435\u0434\u0430\u0445, \u043e\u0442\u043b\u043e\u0436\u0435\u043d\u043d\u043e\u0435 \u043e\u0431\u043d\u043e\u0432\u043b\u0435\u043d\u0438\u0435 \u2014 \u043d\u0435 \u043f\u0440\u043e\u0441\u0442\u043e \u0440\u0438\u0441\u043a, \u044d\u0442\u043e \u0432\u043e\u0437\u043c\u043e\u0436\u043d\u0430\u044f \u0442\u043e\u0447\u043a\u0430 \u043e\u0442\u043a\u0430\u0437\u0430 \u0432\u0441\u0435\u0439 \u0431\u0438\u0437\u043d\u0435\u0441-\u043d\u0435\u043f\u0440\u0435\u0440\u044b\u0432\u043d\u043e\u0441\u0442\u0438.\n\n#hpe #storeonce #\u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u044c #\u0440\u0435\u0437\u0435\u0440\u0432\u043d\u043e\u0435\u043a\u043e\u043f\u0438\u0440\u043e\u0432\u0430\u043d\u0438\u0435\n\n@ZerodayAlert", "creation_timestamp": "2026-07-25T15:00:12.847301Z"}, {"uuid": "90b069e7-9d9a-48d0-92a7-119223a3ddb9", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37164", "type": "seen", "source": "https://t.me/CyberDispatch/525", "content": "Check Point says CVE-2025-37164 is being mass-exploited to spread the RondoDox botnet, with 40,000+ attacks on Jan 7.\n\nThe activity targeted government, finance, and industrial sectors, prompting same-day KEV inclusion.", "creation_timestamp": "2026-08-29T20:00:23.670456Z"}, {"uuid": "a9128e34-3f50-448d-9a4d-657e1739fe5d", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37093", "type": "seen", "source": "https://t.me/ZerodayAlert/515", "content": "\u041a\u043e\u0433\u0434\u0430 \u043e\u0431\u043d\u043e\u0432\u043b\u0435\u043d\u0438\u0435 \u0432\u0430\u0436\u043d\u0435\u0435, \u0447\u0435\u043c \u0431\u044d\u043a\u0430\u043f\n\n\ud83d\udccd \u0423\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u044c \u0432 StoreOnce \u2014 \u043d\u0430\u043f\u043e\u043c\u0438\u043d\u0430\u043d\u0438\u0435: \u0431\u0435\u0437\u043e\u043f\u0430\u0441\u043d\u043e\u0441\u0442\u044c \u0441\u0438\u0441\u0442\u0435\u043c\u044b \u0445\u0440\u0430\u043d\u0435\u043d\u0438\u044f \u0434\u0430\u043d\u043d\u044b\u0445 \u0432\u0430\u0436\u043d\u0430 \u043d\u0435 \u043c\u0435\u043d\u044c\u0448\u0435, \u0447\u0435\u043c \u0435\u0451 \u043d\u0430\u0434\u0451\u0436\u043d\u043e\u0441\u0442\u044c. CVE-2025-37093 \u043f\u043e\u043a\u0430\u0437\u044b\u0432\u0430\u0435\u0442, \u043a\u0430\u043a \u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u044c \u043d\u0430 \u0443\u0440\u043e\u0432\u043d\u0435 \u0430\u0443\u0442\u0435\u043d\u0442\u0438\u0444\u0438\u043a\u0430\u0446\u0438\u0438 \u043f\u0440\u0435\u0432\u0440\u0430\u0449\u0430\u0435\u0442 \u0438\u043d\u0441\u0442\u0440\u0443\u043c\u0435\u043d\u0442 \u0440\u0435\u0437\u0435\u0440\u0432\u043d\u043e\u0433\u043e \u043a\u043e\u043f\u0438\u0440\u043e\u0432\u0430\u043d\u0438\u044f \u0432 \u0442\u043e\u0447\u043a\u0443 \u0440\u0438\u0441\u043a\u0430, \u0430 \u043d\u0435 \u0437\u0430\u0449\u0438\u0442\u044b. \u041e\u0441\u043e\u0431\u0435\u043d\u043d\u043e \u043a\u043e\u0433\u0434\u0430 \u0440\u0435\u0447\u044c \u043e \u043f\u043b\u0430\u0442\u0444\u043e\u0440\u043c\u0430\u0445, \u0441\u0442\u043e\u044f\u0449\u0438\u0445 \u0432 \u0446\u0435\u043d\u0442\u0440\u0435 \u0418\u0422-\u043b\u0430\u043d\u0434\u0448\u0430\u0444\u0442\u0430.\n\n\ud83d\udd0d \u0421\u0442\u0440\u0430\u0442\u0435\u0433\u0438\u0447\u0435\u0441\u043a\u0438 \u0432\u0430\u0436\u043d\u043e \u0434\u0440\u0443\u0433\u043e\u0435: \u043a\u0430\u043a StoreOnce \u043e\u043a\u0430\u0437\u0430\u043b\u0441\u044f \u0443\u044f\u0437\u0432\u0438\u043c \u0432 \u0442\u0435\u0447\u0435\u043d\u0438\u0435 \u043f\u043e\u043b\u0443\u0433\u043e\u0434\u0430 \u0431\u0435\u0437 \u043f\u0443\u0431\u043b\u0438\u0447\u043d\u044b\u0445 \u043f\u0440\u0438\u0437\u043d\u0430\u043a\u043e\u0432 \u0430\u043a\u0442\u0438\u0432\u043d\u043e\u0441\u0442\u0438? \u042d\u0442\u043e \u0438\u043b\u043b\u044e\u0441\u0442\u0440\u0430\u0446\u0438\u044f \u0441\u043b\u0435\u043f\u043e\u0439 \u0437\u043e\u043d\u044b, \u043a\u043e\u0433\u0434\u0430 \u0438\u043d\u0444\u0440\u0430\u0441\u0442\u0440\u0443\u043a\u0442\u0443\u0440\u043d\u044b\u0435 \u043f\u0440\u043e\u0434\u0443\u043a\u0442\u044b \u043a\u0430\u0436\u0443\u0442\u0441\u044f \u00ab\u043c\u043e\u043b\u0447\u0430\u0449\u0438\u043c\u0438\u00bb \u0438 \u044f\u043a\u043e\u0431\u044b \u0431\u0435\u0437\u043e\u043f\u0430\u0441\u043d\u044b\u043c\u0438. \u041d\u043e \u0438\u043c\u0435\u043d\u043d\u043e \u0442\u0430\u043a\u0438\u0435 \u0442\u0438\u0445\u0438\u0435 \u0443\u0437\u043b\u044b \u2014 \u0438\u0434\u0435\u0430\u043b\u044c\u043d\u044b\u0435 \u0446\u0435\u043b\u0438: \u043d\u0438\u043a\u0442\u043e \u043d\u0435 \u043e\u0436\u0438\u0434\u0430\u0435\u0442 \u0430\u0442\u0430\u043a\u0438 \u043d\u0430 \u0440\u0435\u0448\u0435\u043d\u0438\u0435, \u0437\u0430\u0449\u0438\u0449\u0430\u044e\u0449\u0435\u0435 \u0434\u0430\u043d\u043d\u044b\u0435.\n\n\ud83d\udccc \u0421\u0435\u0439\u0447\u0430\u0441 StoreOnce \u043d\u0435 \u043f\u0440\u0435\u0434\u043b\u0430\u0433\u0430\u0435\u0442 \u0432\u0440\u0435\u043c\u0435\u043d\u043d\u044b\u0445 \u043c\u0435\u0440 \u0437\u0430\u0449\u0438\u0442\u044b \u2014 \u0442\u043e\u043b\u044c\u043a\u043e \u043e\u0431\u043d\u043e\u0432\u043b\u0435\u043d\u0438\u0435. \u0415\u0441\u043b\u0438 \u043f\u043b\u0430\u0442\u0444\u043e\u0440\u043c\u0430 \u0438\u0441\u043f\u043e\u043b\u044c\u0437\u0443\u0435\u0442\u0441\u044f \u0432 \u043a\u0440\u0438\u0442\u0438\u0447\u0435\u0441\u043a\u0438\u0445 \u0441\u0440\u0435\u0434\u0430\u0445, \u043e\u0442\u043b\u043e\u0436\u0435\u043d\u043d\u043e\u0435 \u043e\u0431\u043d\u043e\u0432\u043b\u0435\u043d\u0438\u0435 \u2014 \u043d\u0435 \u043f\u0440\u043e\u0441\u0442\u043e \u0440\u0438\u0441\u043a, \u044d\u0442\u043e \u0432\u043e\u0437\u043c\u043e\u0436\u043d\u0430\u044f \u0442\u043e\u0447\u043a\u0430 \u043e\u0442\u043a\u0430\u0437\u0430 \u0432\u0441\u0435\u0439 \u0431\u0438\u0437\u043d\u0435\u0441-\u043d\u0435\u043f\u0440\u0435\u0440\u044b\u0432\u043d\u043e\u0441\u0442\u0438.\n\n#hpe #storeonce #\u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u044c #\u0440\u0435\u0437\u0435\u0440\u0432\u043d\u043e\u0435\u043a\u043e\u043f\u0438\u0440\u043e\u0432\u0430\u043d\u0438\u0435\n\n@ZerodayAlert", "creation_timestamp": "2026-07-26T00:00:30.874487Z"}, {"uuid": "46dcb772-3317-4c61-be9a-6ab7e4ea8e7c", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37899", "type": "seen", "source": "https://t.me/cyberwarehouse/830", "content": "https://sean.heelan.io/2025/05/22/how-i-used-o3-to-find-cve-2025-37899-a-remote-zeroday-vulnerability-in-the-linux-kernels-smb-implementation/", "creation_timestamp": "2026-07-26T02:00:12.457597Z"}, {"uuid": "04c7a8e0-a6bf-4b13-b44c-494f45876af5", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37899", "type": "seen", "source": "https://t.me/EchelonEyes/3876", "content": "\u0418\u0441\u0441\u043b\u0435\u0434\u043e\u0432\u0430\u0442\u0435\u043b\u044c \u0441 \u043f\u043e\u043c\u043e\u0449\u044c\u044e OpenAI o3 \u043e\u0431\u043d\u0430\u0440\u0443\u0436\u0438\u043b \u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u044c \u0442\u0438\u043f\u0430 use-after-free (CVE-2025-37899) \u0432 \u043c\u043e\u0434\u0443\u043b\u0435 ksmbd \u044f\u0434\u0440\u0430 Linux. \u041c\u043e\u0434\u0435\u043b\u044c \u0430\u043d\u0430\u043b\u0438\u0437\u0438\u0440\u043e\u0432\u0430\u043b\u0430 \u043a\u043e\u0434 \u0447\u0430\u0441\u0442\u044f\u043c\u0438, \u0432\u044b\u044f\u0432\u0438\u0432 \u043e\u0448\u0438\u0431\u043a\u0443 \u0432 \u043e\u0431\u0440\u0430\u0431\u043e\u0442\u043a\u0435 SMB logoff, \u0433\u0434\u0435 \u0432\u043e\u0437\u043c\u043e\u0436\u0435\u043d \u0434\u043e\u0441\u0442\u0443\u043f \u043a \u043e\u0441\u0432\u043e\u0431\u043e\u0436\u0434\u0435\u043d\u043d\u043e\u0439 \u043f\u0430\u043c\u044f\u0442\u0438.\n\n\u041c\u043e\u0434\u0435\u043b\u044c \u0418\u0418 o3 \u043d\u0435 \u0442\u043e\u043b\u044c\u043a\u043e \u043d\u0430\u0448\u043b\u0430 \u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u044c, \u043d\u043e \u0438 \u0442\u043e\u0447\u043d\u043e \u043e\u043f\u0440\u0435\u0434\u0435\u043b\u0438\u043b\u0430 \u0443\u0441\u043b\u043e\u0432\u0438\u044f \u0435\u0451 \u0432\u043e\u0437\u043d\u0438\u043a\u043d\u043e\u0432\u0435\u043d\u0438\u044f. \u042d\u0442\u043e \u043f\u0435\u0440\u0432\u044b\u0439 \u0441\u043b\u0443\u0447\u0430\u0439 \u0441\u0430\u043c\u043e\u0441\u0442\u043e\u044f\u0442\u0435\u043b\u044c\u043d\u043e\u0433\u043e \u043e\u0431\u043d\u0430\u0440\u0443\u0436\u0435\u043d\u0438\u044f \u0418\u0418 \u0441\u043b\u043e\u0436\u043d\u043e\u0439 \u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u0438 \u0432 \u044f\u0434\u0440\u0435 \u041e\u0421.\n\n\u0420\u0430\u0437\u0440\u0430\u0431\u043e\u0442\u0447\u0438\u043a\u0438 Linux \u0443\u0436\u0435 \u0432\u044b\u043f\u0443\u0441\u0442\u0438\u043b\u0438 \u0438\u0441\u043f\u0440\u0430\u0432\u043b\u0435\u043d\u0438\u0435. \u042d\u0442\u043e \u043e\u0442\u043a\u0440\u044b\u0442\u0438\u0435 \u0434\u0435\u043c\u043e\u043d\u0441\u0442\u0440\u0438\u0440\u0443\u0435\u0442 \u0440\u0430\u0441\u0442\u0443\u0449\u0443\u044e \u0440\u043e\u043b\u044c \u0418\u0418 \u0432 \u043a\u0438\u0431\u0435\u0440\u0431\u0435\u0437\u043e\u043f\u0430\u0441\u043d\u043e\u0441\u0442\u0438, \u043e\u0441\u043e\u0431\u0435\u043d\u043d\u043e \u043f\u0440\u0438 \u0430\u043d\u0430\u043b\u0438\u0437\u0435 \u0431\u043e\u043b\u044c\u0448\u0438\u0445 \u043e\u0431\u044a\u0451\u043c\u043e\u0432 \u043a\u043e\u0434\u0430. \n\n#\u0418\u0418 #\u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u044c\n\n\u0418\u0441\u0442\u043e\u0447\u043d\u0438\u043a: https://eyes.etecs.ru/r/436ddf", "creation_timestamp": "2026-07-26T02:00:30.602918Z"}, {"uuid": "6970322e-42a7-46f9-8cb2-d17b07d58a54", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37899", "type": "published-proof-of-concept", "source": "https://t.me/cyberwarehouse/830", "content": "https://sean.heelan.io/2025/05/22/how-i-used-o3-to-find-cve-2025-37899-a-remote-zeroday-vulnerability-in-the-linux-kernels-smb-implementation/", "creation_timestamp": "2026-07-27T00:00:30.044864Z"}, {"uuid": "1c5ff584-392f-4a91-b324-5456df859d54", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37899", "type": "seen", "source": "https://t.me/EchelonEyes/3876", "content": "\u0418\u0441\u0441\u043b\u0435\u0434\u043e\u0432\u0430\u0442\u0435\u043b\u044c \u0441 \u043f\u043e\u043c\u043e\u0449\u044c\u044e OpenAI o3 \u043e\u0431\u043d\u0430\u0440\u0443\u0436\u0438\u043b \u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u044c \u0442\u0438\u043f\u0430 use-after-free (CVE-2025-37899) \u0432 \u043c\u043e\u0434\u0443\u043b\u0435 ksmbd \u044f\u0434\u0440\u0430 Linux. \u041c\u043e\u0434\u0435\u043b\u044c \u0430\u043d\u0430\u043b\u0438\u0437\u0438\u0440\u043e\u0432\u0430\u043b\u0430 \u043a\u043e\u0434 \u0447\u0430\u0441\u0442\u044f\u043c\u0438, \u0432\u044b\u044f\u0432\u0438\u0432 \u043e\u0448\u0438\u0431\u043a\u0443 \u0432 \u043e\u0431\u0440\u0430\u0431\u043e\u0442\u043a\u0435 SMB logoff, \u0433\u0434\u0435 \u0432\u043e\u0437\u043c\u043e\u0436\u0435\u043d \u0434\u043e\u0441\u0442\u0443\u043f \u043a \u043e\u0441\u0432\u043e\u0431\u043e\u0436\u0434\u0435\u043d\u043d\u043e\u0439 \u043f\u0430\u043c\u044f\u0442\u0438.\n\n\u041c\u043e\u0434\u0435\u043b\u044c \u0418\u0418 o3 \u043d\u0435 \u0442\u043e\u043b\u044c\u043a\u043e \u043d\u0430\u0448\u043b\u0430 \u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u044c, \u043d\u043e \u0438 \u0442\u043e\u0447\u043d\u043e \u043e\u043f\u0440\u0435\u0434\u0435\u043b\u0438\u043b\u0430 \u0443\u0441\u043b\u043e\u0432\u0438\u044f \u0435\u0451 \u0432\u043e\u0437\u043d\u0438\u043a\u043d\u043e\u0432\u0435\u043d\u0438\u044f. \u042d\u0442\u043e \u043f\u0435\u0440\u0432\u044b\u0439 \u0441\u043b\u0443\u0447\u0430\u0439 \u0441\u0430\u043c\u043e\u0441\u0442\u043e\u044f\u0442\u0435\u043b\u044c\u043d\u043e\u0433\u043e \u043e\u0431\u043d\u0430\u0440\u0443\u0436\u0435\u043d\u0438\u044f \u0418\u0418 \u0441\u043b\u043e\u0436\u043d\u043e\u0439 \u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u0438 \u0432 \u044f\u0434\u0440\u0435 \u041e\u0421.\n\n\u0420\u0430\u0437\u0440\u0430\u0431\u043e\u0442\u0447\u0438\u043a\u0438 Linux \u0443\u0436\u0435 \u0432\u044b\u043f\u0443\u0441\u0442\u0438\u043b\u0438 \u0438\u0441\u043f\u0440\u0430\u0432\u043b\u0435\u043d\u0438\u0435. \u042d\u0442\u043e \u043e\u0442\u043a\u0440\u044b\u0442\u0438\u0435 \u0434\u0435\u043c\u043e\u043d\u0441\u0442\u0440\u0438\u0440\u0443\u0435\u0442 \u0440\u0430\u0441\u0442\u0443\u0449\u0443\u044e \u0440\u043e\u043b\u044c \u0418\u0418 \u0432 \u043a\u0438\u0431\u0435\u0440\u0431\u0435\u0437\u043e\u043f\u0430\u0441\u043d\u043e\u0441\u0442\u0438, \u043e\u0441\u043e\u0431\u0435\u043d\u043d\u043e \u043f\u0440\u0438 \u0430\u043d\u0430\u043b\u0438\u0437\u0435 \u0431\u043e\u043b\u044c\u0448\u0438\u0445 \u043e\u0431\u044a\u0451\u043c\u043e\u0432 \u043a\u043e\u0434\u0430. \n\n#\u0418\u0418 #\u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u044c\n\n\u0418\u0441\u0442\u043e\u0447\u043d\u0438\u043a: https://eyes.etecs.ru/r/436ddf", "creation_timestamp": "2026-07-27T00:00:35.576478Z"}, {"uuid": "2efe3c1e-58c5-4610-9d19-cd40b12bb3af", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37899", "type": "published-proof-of-concept", "source": "https://t.me/EchelonEyes/3876", "content": "\u0418\u0441\u0441\u043b\u0435\u0434\u043e\u0432\u0430\u0442\u0435\u043b\u044c \u0441 \u043f\u043e\u043c\u043e\u0449\u044c\u044e OpenAI o3 \u043e\u0431\u043d\u0430\u0440\u0443\u0436\u0438\u043b \u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u044c \u0442\u0438\u043f\u0430 use-after-free (CVE-2025-37899) \u0432 \u043c\u043e\u0434\u0443\u043b\u0435 ksmbd \u044f\u0434\u0440\u0430 Linux. \u041c\u043e\u0434\u0435\u043b\u044c \u0430\u043d\u0430\u043b\u0438\u0437\u0438\u0440\u043e\u0432\u0430\u043b\u0430 \u043a\u043e\u0434 \u0447\u0430\u0441\u0442\u044f\u043c\u0438, \u0432\u044b\u044f\u0432\u0438\u0432 \u043e\u0448\u0438\u0431\u043a\u0443 \u0432 \u043e\u0431\u0440\u0430\u0431\u043e\u0442\u043a\u0435 SMB logoff, \u0433\u0434\u0435 \u0432\u043e\u0437\u043c\u043e\u0436\u0435\u043d \u0434\u043e\u0441\u0442\u0443\u043f \u043a \u043e\u0441\u0432\u043e\u0431\u043e\u0436\u0434\u0435\u043d\u043d\u043e\u0439 \u043f\u0430\u043c\u044f\u0442\u0438.\n\n\u041c\u043e\u0434\u0435\u043b\u044c \u0418\u0418 o3 \u043d\u0435 \u0442\u043e\u043b\u044c\u043a\u043e \u043d\u0430\u0448\u043b\u0430 \u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u044c, \u043d\u043e \u0438 \u0442\u043e\u0447\u043d\u043e \u043e\u043f\u0440\u0435\u0434\u0435\u043b\u0438\u043b\u0430 \u0443\u0441\u043b\u043e\u0432\u0438\u044f \u0435\u0451 \u0432\u043e\u0437\u043d\u0438\u043a\u043d\u043e\u0432\u0435\u043d\u0438\u044f. \u042d\u0442\u043e \u043f\u0435\u0440\u0432\u044b\u0439 \u0441\u043b\u0443\u0447\u0430\u0439 \u0441\u0430\u043c\u043e\u0441\u0442\u043e\u044f\u0442\u0435\u043b\u044c\u043d\u043e\u0433\u043e \u043e\u0431\u043d\u0430\u0440\u0443\u0436\u0435\u043d\u0438\u044f \u0418\u0418 \u0441\u043b\u043e\u0436\u043d\u043e\u0439 \u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u0438 \u0432 \u044f\u0434\u0440\u0435 \u041e\u0421.\n\n\u0420\u0430\u0437\u0440\u0430\u0431\u043e\u0442\u0447\u0438\u043a\u0438 Linux \u0443\u0436\u0435 \u0432\u044b\u043f\u0443\u0441\u0442\u0438\u043b\u0438 \u0438\u0441\u043f\u0440\u0430\u0432\u043b\u0435\u043d\u0438\u0435. \u042d\u0442\u043e \u043e\u0442\u043a\u0440\u044b\u0442\u0438\u0435 \u0434\u0435\u043c\u043e\u043d\u0441\u0442\u0440\u0438\u0440\u0443\u0435\u0442 \u0440\u0430\u0441\u0442\u0443\u0449\u0443\u044e \u0440\u043e\u043b\u044c \u0418\u0418 \u0432 \u043a\u0438\u0431\u0435\u0440\u0431\u0435\u0437\u043e\u043f\u0430\u0441\u043d\u043e\u0441\u0442\u0438, \u043e\u0441\u043e\u0431\u0435\u043d\u043d\u043e \u043f\u0440\u0438 \u0430\u043d\u0430\u043b\u0438\u0437\u0435 \u0431\u043e\u043b\u044c\u0448\u0438\u0445 \u043e\u0431\u044a\u0451\u043c\u043e\u0432 \u043a\u043e\u0434\u0430. \n\n#\u0418\u0418 #\u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u044c\n\n\u0418\u0441\u0442\u043e\u0447\u043d\u0438\u043a: https://eyes.etecs.ru/r/436ddf", "creation_timestamp": "2026-07-28T00:00:53.530245Z"}, {"uuid": "75200362-f6e7-440f-9af1-090c10730810", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37654", "type": "seen", "source": "https://t.me/GithubRedTeam/99424", "content": "\ud83d\udea8 GitHub \u76d1\u63a7\u6d88\u606f\u63d0\u9192\n\n\ud83d\udea8 \u53d1\u73b0\u5173\u952e\u8bcd\uff1a #XSS #CVE\n\n\ud83d\udce6 \u9879\u76ee\u540d\u79f0\uff1a patch-CVE-2025-37654\n\ud83d\udc64 \u9879\u76ee\u4f5c\u8005\uff1a gduma-phData\n\ud83d\udee0 \u5f00\u53d1\u8bed\u8a00\uff1a Unknown\n\u2b50 Star\u6570\u91cf\uff1a 0  |  \ud83c\udf74 Fork\u6570\u91cf\uff1a 0\n\ud83d\udcc5 \u66f4\u65b0\u65f6\u95f4\uff1a 2026-08-24 03:03:53\n\n\ud83d\udcdd \u9879\u76ee\u63cf\u8ff0\uff1a\nPatch: XSS leading to RCE (Zimbra Collaboration)\n\n\ud83d\udd17 \u70b9\u51fb\u8bbf\u95ee\u9879\u76ee\u5730\u5740", "creation_timestamp": "2026-08-24T08:00:03.415062Z"}, {"uuid": "68868ab4-0844-4b76-b579-01ce7805b77e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2025-37785", "type": "seen", "source": "https://www.cisa.gov/news-events/ics-advisories/icsa-26-209-04", "content": "", "creation_timestamp": "2026-07-28T16:18:37.651823Z"}, {"uuid": "b636e188-517b-40c3-8cf4-b8d458dc229b", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2025-37909", "type": "seen", "source": "https://www.cisa.gov/news-events/ics-advisories/icsa-26-209-04", "content": "", "creation_timestamp": "2026-07-28T16:18:40.050035Z"}, {"uuid": "f30318e1-b3cd-4130-92ac-91751f0e27bc", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2025-37917", "type": "seen", "source": "https://www.cisa.gov/news-events/ics-advisories/icsa-26-209-04", "content": "", "creation_timestamp": "2026-07-28T16:18:42.420982Z"}, {"uuid": "88e28571-d6f1-4c27-a68c-2f03b760deb7", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2025-37959", "type": "seen", "source": "https://www.cisa.gov/news-events/ics-advisories/icsa-26-209-04", "content": "", "creation_timestamp": "2026-07-28T16:18:47.174108Z"}, {"uuid": "912eb64f-3ded-4b6a-bb66-9d3fbc86d8df", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2025-37972", "type": "seen", "source": "https://www.cisa.gov/news-events/ics-advisories/icsa-26-209-04", "content": "", "creation_timestamp": "2026-07-28T16:18:51.931218Z"}, {"uuid": "1a6a152d-69a3-40d4-bf3c-b7a0e9697d2e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2025-37945", "type": "seen", "source": "https://www.cisa.gov/news-events/ics-advisories/icsa-26-209-04", "content": "", "creation_timestamp": "2026-07-28T16:18:44.786026Z"}, {"uuid": "c5f8802c-2a41-46f7-a7aa-a17cd11197e5", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2025-37964", "type": "seen", "source": "https://www.cisa.gov/news-events/ics-advisories/icsa-26-209-04", "content": "", "creation_timestamp": "2026-07-28T16:18:49.557207Z"}, {"uuid": "253612f2-a3e9-4096-966f-ff5cc0faa7d4", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2025-37980", "type": "seen", "source": "https://www.cisa.gov/news-events/ics-advisories/icsa-26-209-04", "content": "", "creation_timestamp": "2026-07-28T16:18:54.315788Z"}, {"uuid": "ff59ab4f-97e7-430b-931f-ad757fa9ed83", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37899", "type": "seen", "source": "https://t.me/hn_best_comments/24847", "content": "Re: I used o3 to find a remote zeroday in the Linux SM...\n        \nA small thing, but I found the author's project-organization practices useful \u2013 creating individual .prompt files for system prompt, background information, and auxiliary instructions [1], and then running it through `llm`.\n\nIt reveals how good LLM use, like any other engineering tool, requires good engineering thinking \u2013 methodical, and oriented around thoughtful specifications that balance design constraints \u2013 for best results.\n\n[1] https://github.com/SeanHeelan/o3_finds_cve-2025-37899\n        \nnxobject, 1 day ago", "creation_timestamp": "2026-07-29T12:01:06.980403Z"}, {"uuid": "a753195e-9287-4b12-a0a4-7b59582632f7", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37947", "type": "seen", "source": "https://t.me/reverseame/5424", "content": "ksmbd - Exploiting CVE-2025-37947 (3/3) #CVE202537947 #ksmbd #OOBWrite #PrivilegeEscalation #LinuxKernel https://blog.doyensec.com/2025/10/08/ksmbd-3.html", "creation_timestamp": "2026-07-29T12:02:01.460127Z"}, {"uuid": "1909a61d-353c-44d5-bf42-2326c054d606", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37899", "type": "seen", "source": "https://t.me/hn_best_comments/24847", "content": "Re: I used o3 to find a remote zeroday in the Linux SM...\n        \nA small thing, but I found the author's project-organization practices useful \u2013 creating individual .prompt files for system prompt, background information, and auxiliary instructions [1], and then running it through `llm`.\n\nIt reveals how good LLM use, like any other engineering tool, requires good engineering thinking \u2013 methodical, and oriented around thoughtful specifications that balance design constraints \u2013 for best results.\n\n[1] https://github.com/SeanHeelan/o3_finds_cve-2025-37899\n        \nnxobject, 1 day ago", "creation_timestamp": "2026-07-30T00:01:47.169824Z"}, {"uuid": "62576fb2-8cde-425b-985d-942f45ed9abf", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37947", "type": "seen", "source": "https://t.me/reverseame/5424", "content": "ksmbd - Exploiting CVE-2025-37947 (3/3) #CVE202537947 #ksmbd #OOBWrite #PrivilegeEscalation #LinuxKernel https://blog.doyensec.com/2025/10/08/ksmbd-3.html", "creation_timestamp": "2026-07-30T00:02:12.030894Z"}, {"uuid": "11ae2144-b2e0-481f-8196-2d956e35a2a9", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37164", "type": "seen", "source": "https://t.me/CyberDispatch/525", "content": "Check Point says CVE-2025-37164 is being mass-exploited to spread the RondoDox botnet, with 40,000+ attacks on Jan 7.\n\nThe activity targeted government, finance, and industrial sectors, prompting same-day KEV inclusion.", "creation_timestamp": "2026-08-30T00:00:49.263064Z"}, {"uuid": "ea5d8be6-c429-418c-a3bf-5549d2375a9c", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37899", "type": "seen", "source": "https://t.me/hacking_Attack/160936", "content": "Your strategy for hunting 0days\nhttps://www.reddit.com/r/redteamsec/comments/1kwtl4f/your_strategy_for_hunting_0days/\n\nI recently read the post about this guy finding a 0day using chatgpt o3 model and it's really interesting the way he talks about how he carefully picks the attack surface for the model to analyze, only providing certain handler functions to look for UAF's, up to a limited call depth. It made me wonder how hunting for 0days requires not only a carefully thought out strategy, but it's also probably different for everyone. I''m curious how different vuln researchers approach this? What is your strategy? How do you pick the codebase/project to research and how do you pick the specific part/section of the source code (or execution flow) to analyze? In general: what is your strategy?    submitted by    /u/Lmao_vogreward_shard  (https://www.reddit.com/user/Lmao_vogreward_shard) \n [link] (https://sean.heelan.io/2025/05/22/how-i-used-o3-to-find-cve-2025-37899-a-remote-zeroday-vulnerability-in-the-linux-kernels-smb-implementation/)   [comments] (https://www.reddit.com/r/redteamsec/comments/1kwtl4f/your_strategy_for_hunting_0days/)", "creation_timestamp": "2026-09-01T20:00:23.771640Z"}, {"uuid": "41beb9c0-9b30-48c0-acae-aa1eb5d50249", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37899", "type": "seen", "source": "https://t.me/hacking_Attack/160936", "content": "Your strategy for hunting 0days\nhttps://www.reddit.com/r/redteamsec/comments/1kwtl4f/your_strategy_for_hunting_0days/\n\nI recently read the post about this guy finding a 0day using chatgpt o3 model and it's really interesting the way he talks about how he carefully picks the attack surface for the model to analyze, only providing certain handler functions to look for UAF's, up to a limited call depth. It made me wonder how hunting for 0days requires not only a carefully thought out strategy, but it's also probably different for everyone. I''m curious how different vuln researchers approach this? What is your strategy? How do you pick the codebase/project to research and how do you pick the specific part/section of the source code (or execution flow) to analyze? In general: what is your strategy?    submitted by    /u/Lmao_vogreward_shard  (https://www.reddit.com/user/Lmao_vogreward_shard) \n [link] (https://sean.heelan.io/2025/05/22/how-i-used-o3-to-find-cve-2025-37899-a-remote-zeroday-vulnerability-in-the-linux-kernels-smb-implementation/)   [comments] (https://www.reddit.com/r/redteamsec/comments/1kwtl4f/your_strategy_for_hunting_0days/)", "creation_timestamp": "2026-09-02T01:00:40.316224Z"}, {"uuid": "0a67c05e-6c7a-40a6-86d0-a92854b593bd", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37899", "type": "published-proof-of-concept", "source": "https://t.me/hacking_Attack/160936", "content": "Your strategy for hunting 0days\nhttps://www.reddit.com/r/redteamsec/comments/1kwtl4f/your_strategy_for_hunting_0days/\n\nI recently read the post about this guy finding a 0day using chatgpt o3 model and it's really interesting the way he talks about how he carefully picks the attack surface for the model to analyze, only providing certain handler functions to look for UAF's, up to a limited call depth. It made me wonder how hunting for 0days requires not only a carefully thought out strategy, but it's also probably different for everyone. I''m curious how different vuln researchers approach this? What is your strategy? How do you pick the codebase/project to research and how do you pick the specific part/section of the source code (or execution flow) to analyze? In general: what is your strategy?    submitted by    /u/Lmao_vogreward_shard  (https://www.reddit.com/user/Lmao_vogreward_shard) \n [link] (https://sean.heelan.io/2025/05/22/how-i-used-o3-to-find-cve-2025-37899-a-remote-zeroday-vulnerability-in-the-linux-kernels-smb-implementation/)   [comments] (https://www.reddit.com/r/redteamsec/comments/1kwtl4f/your_strategy_for_hunting_0days/)", "creation_timestamp": "2026-09-03T10:00:04.241147Z"}, {"uuid": "c63568c0-6eed-46bb-a6b3-6eefc11e980d", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37899", "type": "published-proof-of-concept", "source": "https://t.me/hacking_Attack/160936", "content": "Your strategy for hunting 0days\nhttps://www.reddit.com/r/redteamsec/comments/1kwtl4f/your_strategy_for_hunting_0days/\n\nI recently read the post about this guy finding a 0day using chatgpt o3 model and it's really interesting the way he talks about how he carefully picks the attack surface for the model to analyze, only providing certain handler functions to look for UAF's, up to a limited call depth. It made me wonder how hunting for 0days requires not only a carefully thought out strategy, but it's also probably different for everyone. I''m curious how different vuln researchers approach this? What is your strategy? How do you pick the codebase/project to research and how do you pick the specific part/section of the source code (or execution flow) to analyze? In general: what is your strategy?    submitted by    /u/Lmao_vogreward_shard  (https://www.reddit.com/user/Lmao_vogreward_shard) \n [link] (https://sean.heelan.io/2025/05/22/how-i-used-o3-to-find-cve-2025-37899-a-remote-zeroday-vulnerability-in-the-linux-kernels-smb-implementation/)   [comments] (https://www.reddit.com/r/redteamsec/comments/1kwtl4f/your_strategy_for_hunting_0days/)", "creation_timestamp": "2026-09-04T00:00:53.645721Z"}, {"uuid": "e7f7e20f-e922-4fd9-b5db-e00eb9f27e2a", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37164", "type": "seen", "source": "https://github.com/rapid7/metasploit-framework/blob/master/modules/exploits/linux/http/hpe_oneview_rce.rb", "content": "{\"aliases\": [], \"arch\": \"cmd\", \"author\": [\"Nguyen Quoc Khanh\", \"remmons-r7\", \"sfewer-r7\"], \"autofilter_ports\": [80, 8080, 443, 8000, 8888, 8880, 8008, 3000, 8443], \"autofilter_services\": [\"http\", \"https\"], \"check\": true, \"default_credential\": false, \"description\": \"This module exploits an unauthenticated RCE vulnerability, CVE-2025-37164, against Hewlett Packard Enterprise\\n          (HPE) OneView. All versions below 11.00 are vulnerable (so long as the vendor supplied hotfix has not been\\n          applied), however some VM product versions do not enable the vulnerable \\\"ID Pools\\\" endpoint, and are not\\n          exploitable.\", \"disclosure_date\": \"2025-12-16\", \"fullname\": \"exploit/linux/http/hpe_oneview_rce\", \"is_install_path\": true, \"mod_time\": \"2025-12-19 15:38:43 +0000\", \"name\": \"HPE OneView unauthenticated RCE\", \"needs_cleanup\": null, \"notes\": {\"Reliability\": [\"repeatable-session\"], \"SideEffects\": [\"ioc-in-logs\"], \"Stability\": [\"crash-safe\"]}, \"path\": \"/modules/exploits/linux/http/hpe_oneview_rce.rb\", \"platform\": \"Linux,Unix\", \"post_auth\": false, \"rank\": 600, \"ref_name\": \"linux/http/hpe_oneview_rce\", \"references\": [\"CVE-2025-37164\", \"URL-https://support.hpe.com/hpesc/public/docDisplay?docId=hpesbgn04985en_us&docLocale=en_US\", \"URL-https://www.rapid7.com/blog/post/etr-cve-2025-37164-critical-unauthenticated-rce-affecting-hewlett-packard-enterprise-oneview/\", \"URL-https://attackerkb.com/topics/ixWdbDvjwX/cve-2025-37164/rapid7-analysis\"], \"rport\": 443, \"session_types\": false, \"targets\": [\"Default\"], \"type\": \"exploit\"}", "creation_timestamp": "2026-09-08T06:48:37.655458Z"}, {"uuid": "f8cbf429-c385-499c-8cf8-9c6e9ca5efef", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37735", "type": "seen", "source": "https://t.me/Intel_Encyclopedia/2016", "content": "\u2728 General Cyber News \u2728\n\n\u041a\u0440\u0438\u0442\u0438\u0447\u0435\u0441\u043a\u0430\u044f \u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u044c \u0432 Elastic Defend \u0434\u043b\u044f Windows \u043f\u043e\u0437\u0432\u043e\u043b\u044f\u0435\u0442 \u043f\u043e\u0432\u044b\u0448\u0430\u0442\u044c \u043f\u0440\u0438\u0432\u0438\u043b\u0435\u0433\u0438\u0438\n\n\u2014\n\nSummary:\n\u041a\u043e\u043c\u043f\u0430\u043d\u0438\u044f Elastic \u0432\u044b\u043f\u0443\u0441\u0442\u0438\u043b\u0430 \u044d\u043a\u0441\u0442\u0440\u0435\u043d\u043d\u043e\u0435 \u043e\u0431\u043d\u043e\u0432\u043b\u0435\u043d\u0438\u0435 \u0431\u0435\u0437\u043e\u043f\u0430\u0441\u043d\u043e\u0441\u0442\u0438 \u0434\u043b\u044f \u0441\u0432\u043e\u0435\u0433\u043e \u043f\u0440\u043e\u0434\u0443\u043a\u0442\u0430 Elastic Defend \u043f\u043e\u0441\u043b\u0435 \u043e\u0431\u043d\u0430\u0440\u0443\u0436\u0435\u043d\u0438\u044f \u043e\u043f\u0430\u0441\u043d\u043e\u0439 \u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u0438, \u043f\u043e\u0437\u0432\u043e\u043b\u044f\u044e\u0449\u0435\u0439 \u0437\u043b\u043e\u0443\u043c\u044b\u0448\u043b\u0435\u043d\u043d\u0438\u043a\u0430\u043c \u043f\u043e\u0432\u044b\u0448\u0430\u0442\u044c \u043f\u0440\u0438\u0432\u0438\u043b\u0435\u0433\u0438\u0438 \u043d\u0430 \u0441\u0438\u0441\u0442\u0435\u043c\u0430\u0445 Windows. \u0423\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u044c, \u043f\u043e\u043b\u0443\u0447\u0438\u0432\u0448\u0430\u044f \u0438\u0434\u0435\u043d\u0442\u0438\u0444\u0438\u043a\u0430\u0442\u043e\u0440 CVE-2025-37735, \u0441\u0432\u044f\u0437\u0430\u043d\u0430 \u0441 \u043d\u0435\u043f\u0440\u0430\u0432\u0438\u043b\u044c\u043d\u044b\u043c \u0441\u043e\u0445\u0440\u0430\u043d\u0435\u043d\u0438\u0435\u043c \u0440\u0430\u0437\u0440\u0435\u0448\u0435\u043d\u0438\u0439 \u0444\u0430\u0439\u043b\u043e\u0432 \u0432 \u0441\u043b\u0443\u0436\u0431\u0435 Defend \u0438 \u043f\u0440\u0435\u0434\u0441\u0442\u0430\u0432\u043b\u044f\u0435\u0442 \u0441\u0435\u0440\u044c\u0435\u0437\u043d\u0443\u044e \u0443\u0433\u0440\u043e\u0437\u0443 \u0434\u043b\u044f \u043e\u0440\u0433\u0430\u043d\u0438\u0437\u0430\u0446\u0438\u0439, \u0438\u0441\u043f\u043e\u043b\u044c\u0437\u0443\u044e\u0449\u0438\u0445 \u044d\u0442\u0443 \u043f\u043b\u0430\u0442\u0444\u043e\u0440\u043c\u0443 \u0437\u0430\u0449\u0438\u0442\u044b \u043a\u043e\u043d\u0435\u0447\u043d\u044b\u0445 \u0442\u043e\u0447\u0435\u043a. \u0414\u0435\u0442\u0430\u043b\u0438 \u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u0438 \u041f\u0440\u043e\u0431\u043b\u0435\u043c\u0430 \u0437\u0430\u0442\u0440\u0430\u0433\u0438\u0432\u0430\u0435\u0442 \u043c\u0435\u0445\u0430\u043d\u0438\u0437\u043c \u043e\u0431\u0440\u0430\u0431\u043e\u0442\u043a\u0438 \u0444\u0430\u0439\u043b\u043e\u0432\u044b\u0445...\n\n\u2014\n\nSource: SEC-1275-1\nPublished: 2025-11-10 07:44 | Author: Vulner Queen\n\n#defend #elastic #general_cyber_news\n\nhttps://1275.ru/vulnerability/kriticheskaya-uyazvimost-v-elastic-defend-dlya-windows-pozvolyaet-povyshat-privilegii_16155", "creation_timestamp": "2026-09-09T05:00:15.454064Z"}, {"uuid": "91c188e5-dc14-4389-8a46-b6502396c780", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37735", "type": "seen", "source": "https://t.me/Intel_Encyclopedia/2016", "content": "\u2728 General Cyber News \u2728\n\n\u041a\u0440\u0438\u0442\u0438\u0447\u0435\u0441\u043a\u0430\u044f \u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u044c \u0432 Elastic Defend \u0434\u043b\u044f Windows \u043f\u043e\u0437\u0432\u043e\u043b\u044f\u0435\u0442 \u043f\u043e\u0432\u044b\u0448\u0430\u0442\u044c \u043f\u0440\u0438\u0432\u0438\u043b\u0435\u0433\u0438\u0438\n\n\u2014\n\nSummary:\n\u041a\u043e\u043c\u043f\u0430\u043d\u0438\u044f Elastic \u0432\u044b\u043f\u0443\u0441\u0442\u0438\u043b\u0430 \u044d\u043a\u0441\u0442\u0440\u0435\u043d\u043d\u043e\u0435 \u043e\u0431\u043d\u043e\u0432\u043b\u0435\u043d\u0438\u0435 \u0431\u0435\u0437\u043e\u043f\u0430\u0441\u043d\u043e\u0441\u0442\u0438 \u0434\u043b\u044f \u0441\u0432\u043e\u0435\u0433\u043e \u043f\u0440\u043e\u0434\u0443\u043a\u0442\u0430 Elastic Defend \u043f\u043e\u0441\u043b\u0435 \u043e\u0431\u043d\u0430\u0440\u0443\u0436\u0435\u043d\u0438\u044f \u043e\u043f\u0430\u0441\u043d\u043e\u0439 \u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u0438, \u043f\u043e\u0437\u0432\u043e\u043b\u044f\u044e\u0449\u0435\u0439 \u0437\u043b\u043e\u0443\u043c\u044b\u0448\u043b\u0435\u043d\u043d\u0438\u043a\u0430\u043c \u043f\u043e\u0432\u044b\u0448\u0430\u0442\u044c \u043f\u0440\u0438\u0432\u0438\u043b\u0435\u0433\u0438\u0438 \u043d\u0430 \u0441\u0438\u0441\u0442\u0435\u043c\u0430\u0445 Windows. \u0423\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u044c, \u043f\u043e\u043b\u0443\u0447\u0438\u0432\u0448\u0430\u044f \u0438\u0434\u0435\u043d\u0442\u0438\u0444\u0438\u043a\u0430\u0442\u043e\u0440 CVE-2025-37735, \u0441\u0432\u044f\u0437\u0430\u043d\u0430 \u0441 \u043d\u0435\u043f\u0440\u0430\u0432\u0438\u043b\u044c\u043d\u044b\u043c \u0441\u043e\u0445\u0440\u0430\u043d\u0435\u043d\u0438\u0435\u043c \u0440\u0430\u0437\u0440\u0435\u0448\u0435\u043d\u0438\u0439 \u0444\u0430\u0439\u043b\u043e\u0432 \u0432 \u0441\u043b\u0443\u0436\u0431\u0435 Defend \u0438 \u043f\u0440\u0435\u0434\u0441\u0442\u0430\u0432\u043b\u044f\u0435\u0442 \u0441\u0435\u0440\u044c\u0435\u0437\u043d\u0443\u044e \u0443\u0433\u0440\u043e\u0437\u0443 \u0434\u043b\u044f \u043e\u0440\u0433\u0430\u043d\u0438\u0437\u0430\u0446\u0438\u0439, \u0438\u0441\u043f\u043e\u043b\u044c\u0437\u0443\u044e\u0449\u0438\u0445 \u044d\u0442\u0443 \u043f\u043b\u0430\u0442\u0444\u043e\u0440\u043c\u0443 \u0437\u0430\u0449\u0438\u0442\u044b \u043a\u043e\u043d\u0435\u0447\u043d\u044b\u0445 \u0442\u043e\u0447\u0435\u043a. \u0414\u0435\u0442\u0430\u043b\u0438 \u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u0438 \u041f\u0440\u043e\u0431\u043b\u0435\u043c\u0430 \u0437\u0430\u0442\u0440\u0430\u0433\u0438\u0432\u0430\u0435\u0442 \u043c\u0435\u0445\u0430\u043d\u0438\u0437\u043c \u043e\u0431\u0440\u0430\u0431\u043e\u0442\u043a\u0438 \u0444\u0430\u0439\u043b\u043e\u0432\u044b\u0445...\n\n\u2014\n\nSource: SEC-1275-1\nPublished: 2025-11-10 07:44 | Author: Vulner Queen\n\n#defend #elastic #general_cyber_news\n\nhttps://1275.ru/vulnerability/kriticheskaya-uyazvimost-v-elastic-defend-dlya-windows-pozvolyaet-povyshat-privilegii_16155", "creation_timestamp": "2026-09-10T00:00:36.172853Z"}]}