Embed Notice

HTML Code

<blockquote style="position: relative; padding-left: 55px;"><section><a href="https://cyberplace.social/users/GossiTheDog/statuses/112818412926980709">Kevin Beaumont (gossithedog@cyberplace.social)'s status on Saturday, 20-Jul-2024 19:46:35 JST</a><a href="https://cyberplace.social/@GossiTheDog" title="gossithedog@cyberplace.social"><img src="https://gnusocial.jp/avatar/38360-48-20240926225417.webp" width="48" height="48" alt="Kevin Beaumont" style="position: absolute; left: 0; top: 0;">Kevin Beaumont</a><div><a href="https://cyberplace.social/@GossiTheDog/112818071532591926" rel="in-reply-to">in reply to</a></div></section><article><p>For the people thinking ‘shouldn’t testing catch this?’, the answer is yes. Clearly something went wrong. </p><p>This isn’t CrowdStrike’s first rodeo on this, although it is the most severe incident so far. </p><p>Eg just last month they had an issue where a content update pushed CPU to 100% on one core: <a href="https://www.thestack.technology/crowdstrike-bug-maxes-out-100-of-cpu-requires-windows-reboots/" rel="nofollow noreferrer">https://www.thestack.technology/crowdstrike-bug-maxes-out-100-of-cpu-requires-windows-reboots/</a> </p><p>Truthfully these issues happen across all vendors - I’ve had my orgs totalled twice now by AV vendors, one while I was on holiday abroad and had to suspend said holiday.</p></article><footer><a rel="bookmark" href="https://gnusocial.jp/conversation/3397127#notice-6693678">In conversation</a><time datetime="2024-07-20T19:46:35+09:00" title="Saturday, 20-Jul-2024 19:46:35 JST">about 4 months ago</time> <span>from <span><a href="https://gnusocial.jp/notice/6693678" rel="external" title="Sent from gnusocial.jp via ActivityPub">gnusocial.jp</a></span></span><a href="https://gnusocial.jp/notice/6693678">permalink</a><h4>Attachments</h4><ol><li><article><header><div>Domain not in remote thumbnail source whitelist: www.thestack.technology</div><h5><a href="https://www.thestack.technology/crowdstrike-bug-maxes-out-100-of-cpu-requires-windows-reboots/">CrowdStrike bug maxes out 100% of CPU, requires Windows reboots</a></h5><div></div></header><div>"Note: This is 100% of a single core. In an 8-core system for example, an additional 12.5% of unexpected total CPU load would be experienced..."</div><footer></footer></article></li></ol></footer></blockquote>

Corresponding Notice

Embed this notice
Kevin Beaumont (gossithedog@cyberplace.social)'s status on Saturday, 20-Jul-2024 19:46:35 JST Kevin Beaumont
in reply to
For the people thinking ‘shouldn’t testing catch this?’, the answer is yes. Clearly something went wrong.
This isn’t CrowdStrike’s first rodeo on this, although it is the most severe incident so far.
Eg just last month they had an issue where a content update pushed CPU to 100% on one core: https://www.thestack.technology/crowdstrike-bug-maxes-out-100-of-cpu-requires-windows-reboots/
Truthfully these issues happen across all vendors - I’ve had my orgs totalled twice now by AV vendors, one while I was on holiday abroad and had to suspend said holiday.
In conversationabout 4 months ago from gnusocial.jppermalink
Attachments
1. Domain not in remote thumbnail source whitelist: www.thestack.technology
  CrowdStrike bug maxes out 100% of CPU, requires Windows reboots
  "Note: This is 100% of a single core. In an 8-core system for example, an additional 12.5% of unexpected total CPU load would be experienced..."

Public

Embed Notice

HTML Code

Corresponding Notice