intellectual-property licensing damages
What happens if I licensed a contribution to an open source project but it is discovered that I did not have the right to do so?
<p>Suppose I made a patch to <a href="https://www.kernel.org/category/about.html" rel="nofollow noreferrer">Linux kernel</a>. I am supposed to <a href="https://www.kernel.org/doc/html/latest/process/submitting-patches.html#developer-s-certificate-of-origin-1-1" rel="nofollow noreferrer">confirm that I own the code</a>. <em>(Forgive me if "own" is not the correct term.)</em> As I understand, this is a specific case of a general concept called a <em>"contributor license agreement"</em>, and I am to sign it rather often if I wish to contribute to high-profile open source projects.</p>

<p>However, there may happen a case that I write the code not in my spare time but while working for hire. Or otherwise not own the rights I am attempting to transfer to the maintainers of the project I am contributing to. That may get discovered quite long a time after the contribution is made, so the code may be in use by many people out there.</p>

<ol>
<li><p>What legal actions may the actual owner of the code attempt, if we suppose that they hate everyone else in the world and want to inflict as much harm as they could, and possibly also obtain money?</p></li>
<li><p>How much of the suffering outlined above will fall on:</p>

<ul>
<li>Myself?</li>
<li>The maintainers of the project I wrongfully contributed to?</li>
<li>The users of the project?</li>
</ul></li>
</ol>

<p><strong>P.S.</strong> I would especially enjoy an answer that highlights the difference between me pushing the code I do not own while signing a license agreement, and pushing the same code while not being required to sign anything − i.e. how does the requiring of a contributor to sign an agreement change the situation, for all the sides involved.</p>

<p>What happened is that you created a legal mess. </p>

<p>You are obviously on the hook for copyright infringement. The maintainers of the project will scramble to replace your code with newly written code. They will likely ask your company which code they are complaining about - that puts your company into the problematic situation that they shouldn't identify code that isn't theirs, that it will be hard to sue for infringing code when they didn't give the project maintainers a chance to fix it, and that everything they identify will be replaced. </p>

<p>Since it is your actions that caused the trouble, anyone suffering damages from your actions can sue you. </p>
