This is a most excellent place for technology news and articles.
It’s interesting that this supposedly goes back to Windows 3.1 and the original release…
I was curious about the "every version ever shipped."
This gets really old school.
Other articles make more clear why that is.
https://cyberpress.org/windows-agere-modem-driver-0-day-flaws/
Rather than issuing a traditional patch for each vulnerability, Microsoft’s October cumulative update completely removes the ltmdm64.sys driver from affected systems.
As a result, all fax modem hardware relying on the Agere Modem driver will cease to function. While mail and messaging over IP have largely supplanted analog modems, some industrial and legacy applications still depend on fax modems.
Organizations must therefore audit their environments for any remaining modem dependencies and either migrate to supported alternatives or implement workarounds where available.
Microsoft’s advisory explicitly recommends that customers eliminate any reliance on the deprecated hardware to avoid service disruptions.
So maybe not all the way back to the original release, but back to the first release that included this specific telephony modem driver, ltmdm64.sys. If I recall correctly, Windows 3.1 brought networking capabilities.
However, another article claims it has only been shipped with every version of Windows since 2006.
https://www.thestack.technology/windows-users-hacked-due-to-legacy-fax-modem-driver/
CVE-2025-24990 was credited to a security researcher going by the handle @shitsecure who told The Stack by DM “it’s a driver from 2006, never changed… I think it was historically shipped with everything, although that doesn’t make sense at all.”
Which honestly makes a lot more sense, since the "64" part of the driver name implies it's for 64 bit systems, which were first introduced in 2003.
Some more extraneous info on this driver/hardware:
https://www.sysnative.com/forums/drivers/1216/driver
Thanks for the details!
I wonder how often they clean stuff up like this. That crossed my mind earlier, I’m sure there is a bunch of “dormant” software that could be cleaned out or made optional in some way.
But the making it optional idea is easier said than done. Especially from a standpoint of discoverability and usability.
Right, it was referenced in one of the articles that a bunch of legacy industrial machines likely still use this hardware, so the people using those old machines are probably going to have to go dig up PCI modems from that era without the Agere/Lucent chipset.
I'm sure you're right and there's lots of stuff they've missed like this over the years that they sort of kept on for compatibility but that opens exploits due to how old they are.
People using that legacy hardware generally can’t run Windows 10, which just ended support this month. The patch is only for Windows 11, which won’t run on older hardware.
The patch is for Windows 10, Windows 11, and Server 2008 up to Server 2025.
Further, there's companies that make custom-built modern machines that support classic PCI and modern operating systems and classic operating systems.
It's conceivable that legacy systems are using modern OSes with virtualization running a legacy OS and legacy PCI cards, for example. It's not beyond the realm of possibility.
Further, there's companies that make custom-built modern machines that support classic PCI and modern operating systems and classic operating systems.
Yeah, some extremely expensive equipment at my job runs on Adobe Flash. Modern machines won’t even allow Flash to run because it’s so insecure. We just updated the control PC for that equipment last year; It’s a computer that is dual-booting Windows 11 and Windows XP. It boots into WinXP by default, to be able to run Flash. Then if you ever need to update it, you can swap over to Win11 to be able to connect to the internet.
Personally I blame Dave Plummer.
makes you wonder if/how/by who its been used all these years
I expect it's stuff like ATMs, Coinstar machines. Things that may need to phone home regularly but don't need to sit online constantly.
To anyone misreading this, these exploits were patched yesterday and thus were included as the final patch for Windows 10 before the extended security updates requirements kick in.
Known exploits are always reported to the company first to give them time to patch it before releasing info on the exploits.
All Windows 10 users will continue to have access to the patches in this final freely available patch Tuesday for Windows 10. They just can't get new updates without joining the ESU program.
I hate Microsoft too and only use Linux, but let's stop the circlejerk of false claims here please and thank you.
Zero-day means the company had 0 days to fix it before the exploits were made public. Maybe the headline is wrong?
Nope, 0-day means it was exploited in the wild before the company knew about it. Basically, the company had to rush to patch it because it was already being exploited. It means black-hat hackers found it and exploited it before the white/grey-hat hackers reported it. If white-hat hackers found it first, they’d have already alerted the company and given time to patch it before they announced the vulnerability. But since the black-hat hackers found it first, it was a 0-day.
0-day patches are often a bodge, at best. They often consist of “just disable the vulnerable component entirely” to give the company time to work on a more long-term solution. And that’s exactly what happened here. MS didn’t take time to actually fix the driver; They just ripped it out and said “sucks if you needed it. It’s gone now.”
Nope 0 days means
Zero-day vulnerability: A software flaw that attackers discover before the developer does.
Zero-day exploit: The method hackers use to take advantage of this unknown vulnerability.
Zero-day attack: An attack that uses a zero-day exploit to damage a system, steal data, or plant malware before a patch is available. This is a serious risk because no defenses are in place for this specific flaw yet.
The first is the most common one found in the press and is usually reported to the company so they can patch it, before press release.
But it would be weird to call something a "zero-day" if it wasn't being exploited. Like if I discover a vuln, it shouldn't be considered a zero-day, even if I report it, if I'm not exploiting it in the wild.
It was exploited. That's how they proved it worked. They just didn't exploit it to do anything nefarious.
Ahh TIL. Thanks for the clarification!
Perhaps, either that or they made a very quick fix making updates to address them the day before this patch release.
People have probably been sitting on exploits for months or longer. There will probably be another wave after the 1 year extended support ends.
If I remember correctly, MS still pushed some critical patches to Win7 after the support ended as they realized 1/3 of world's computers turning into botnets is probably not in their interests.
It will be interesting what happens with this Windows 10 end of support, this just happens to crop up the day after support ends.
The exploits are addressed in the patch released yesterday, on the final day of support.
Generally such exploits aren't released to the public until they have been patched, to prevent wider abuse of the exploits in the meantime.
https://msrc.microsoft.com/update-guide/en-US/advisory/CVE-2025-24990
As you can see here near the bottom of the page it lists security updates for this epxloit having been released on October 14rh, 2025, the final day of Win10 support. These updates will still be available to Windows 10 systems even after October 14th, they will just be unable to get new patches after that date.
yeah, the timing is 'interesting'
They will continue to releases major security updates for Windows 10 as long as it has double digit installed base share.
So stick with my Linux and don't boot into Windows again. Got it.
Lots of these exploits can be very specific cases so aren't going to threaten the average user. However the point is, Windows 10 is now a huge target and there are lots who would love to take advantage of a freshly open gate.
This is fixed, and the attacked required physical access to the hardware.
These are fixed, but microsoft still includes backdoors for Israel.
Please go away
Fixed and required physical access to the machine. If someone malicious has physical access to your machine you’re already done.
Does it mean you don't think login password with physical token with disk encryption work?
The attacker had to already be logged in to the machine for this exploit.
Thanks for clarifying, guess you meant "required physical access to the machine AND being logged in." then which makes a huge difference.
And it's not likely to be the last.
If true:
Totally none did wait for most popular win10 end supports...
If fake:
Totally none sus this for being fake scarecrow against anyone who would like to stay on non-service, standalone system.
